source: chapter06/kernfs.xml@ 752f4e5

6.0
Last change on this file since 752f4e5 was 752f4e5, checked in by Manuel Canales Esparcia <manuel@…>, 20 years ago

Tags corrections, Chapter 6.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@4132 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 1.6 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
3<sect1 id="ch-system-kernfs">
4<title>Mounting Virtual Kernel File Systems</title>
5<?dbhtml filename="kernfs.html"?>
6
7<para>Various file systems exported by the kernel do not exist on the
8hard drive, but are used to communicate to and from the kernel
9itself.</para>
10
11<para>Begin by creating directories onto which the file systems will be mounted:</para>
12
13<screen><userinput>mkdir -p $LFS/{proc,sys}</userinput></screen>
14
15<para>Now mount the file systems:</para>
16
17<screen><userinput>mount -t proc proc $LFS/proc
18mount -t sysfs sysfs $LFS/sys</userinput></screen>
19
20<para>Remember that if for any reason you stop working on the LFS
21system and start again later, it is important to check that these file
22systems are mounted again before entering the chroot
23environment.</para>
24
25<para>Additional file systems will soon be mounted from within the
26chroot environment. To keep the host up to date, perform a <quote>fake
27mount</quote> for each of these now:</para>
28
29<screen><userinput>mount -f -t ramfs ramfs $LFS/dev
30mount -f -t tmpfs tmpfs $LFS/dev/shm
31mount -f -t devpts -o gid=4,mode=620 devpts $LFS/dev/pts</userinput></screen>
32
33<para>The <command>mount</command> commands executed above may result
34in the following warning message: <computeroutput>can't open /etc/fstab: No
35such file or directory</computeroutput>. This
36file&mdash;<filename>/etc/fstab</filename>&mdash;has
37not been created yet but is also not required for the file systems to
38be properly mounted. As such, the warning can be safely ignored.</para>
39
40</sect1>
41
Note: See TracBrowser for help on using the repository browser.