Changeset 799de33 for BOOK/chroot/common/kernfs.xml
- Timestamp:
- Jul 14, 2014, 9:29:19 AM (10 years ago)
- Branches:
- clfs-3.0.0-systemd, master, systemd
- Children:
- a34becea
- Parents:
- 0d9d44d
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/chroot/common/kernfs.xml
r0d9d44d r799de33 27 27 be mounted:</para> 28 28 29 <screen><userinput>mkdir -pv ${CLFS}/{dev,proc,sys}</userinput></screen> 30 31 <para>Now mount the file systems:</para> 32 33 <screen><userinput>mount -vt proc proc ${CLFS}/proc 34 mount -vt sysfs sysfs ${CLFS}/sys</userinput></screen> 35 36 <para>Remember that if for any reason you stop working on the CLFS system 37 and start again later, it is important to check that these file systems 38 are mounted again before entering the chroot environment.</para> 29 <screen><userinput>mkdir -pv ${CLFS}/{dev,proc,run,sys}</userinput></screen> 39 30 40 31 <para>Two device nodes, <filename class="devicefile">/dev/console</filename> 41 32 and <filename class="devicefile">/dev/null</filename>, are required to be 42 present on the file system.These are needed by the kernel even before33 present on the file system. These are needed by the kernel even before 43 34 starting Udev early in the boot process, so we create them here:</para> 44 35 … … 50 41 <systemitem class="filesystem">devtmpfs</systemitem> file system. For now 51 42 though, we will just use the <quote>bind</quote> option in the mount command 52 to make our host system's /dev structure appear in the new CLFS filesystem:</para>43 to make our host system's <filename class="directory">/dev</filename> structure appear in the new CLFS file system:</para> 53 44 54 45 <screen><userinput>mount -v -o bind /dev ${CLFS}/dev</userinput></screen> 55 46 56 <para>Additional file systems will soon be mounted from within the chroot 57 environment. To keep the host up to date, perform a <quote>fake mount</quote> 58 for each of these now:</para> 47 <para>Now mount the remaining file systems:</para> 59 48 60 <screen><userinput>if [ -h ${CLFS}/dev/shm ]; then 61 link=$(readlink ${CLFS}/dev/shm) 62 mkdir -p ${CLFS}/$link 63 mount -f -vt tmpfs shm ${CLFS}/$link 64 unset link 65 else 66 mount -f -vt tmpfs shm ${CLFS}/dev/shm 67 fi 68 mount -f -vt devpts -o gid=&gid-tty;,mode=620 devpts ${CLFS}/dev/pts</userinput></screen> 49 <screen><userinput>mount -vt devpts -o gid=&gid-tty;,mode=620 devpts ${CLFS}/dev/pts 50 mount -vt proc proc ${CLFS}/proc 51 mount -vt tmpfs tmpfs ${CLFS}/run 52 mount -vt sysfs sysfs ${CLFS}/sys</userinput></screen> 53 54 <para>On some host systems, <filename class="directory">/dev/shm</filename> 55 is a symbolic link to <filename class="directory">/run/shm</filename>. 56 If it is, create a directory in <filename class="directory">/run</filename>:</para> 57 58 <screen><userinput>[ -h ${CLFS}/dev/shm ] && mkdir -pv ${CLFS}/$(readlink ${CLFS}/dev/shm)</userinput></screen> 59 60 <para>Remember that if for any reason you stop working on the CLFS system 61 and start again later, it is important to check that these file systems 62 are mounted again before entering the chroot environment.</para> 69 63 70 64 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.