- Timestamp:
- Jun 21, 2006, 2:53:33 PM (19 years ago)
- Children:
- 73c89fd
- Parents:
- 9fcb5e4
- Location:
- chroot/common
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chroot/common/changingowner.xml
r9fcb5e4 rb71fa50 17 17 class="directory">/tools</filename> and <filename 18 18 class="directory">/cross-tools</filename> directories can be deleted 19 once the LFS system has been finished, they can be retained to build20 additional LFS systems. If the <filename class="directory">/tools</filename>19 once the CLFS system has been finished, they can be retained to build 20 additional CLFS systems. If the <filename class="directory">/tools</filename> 21 21 and <filename class="directory">/cross-tools</filename> directories are 22 22 kept as is, the files are owned by a user ID without a corresponding … … 27 27 28 28 <para os="b">To avoid this issue, add the <systemitem 29 class="username">lfs</systemitem> user to the new LFS system later when29 class="username">lfs</systemitem> user to the new CLFS system later when 30 30 creating the <filename>/etc/passwd</filename> file, taking care to assign 31 31 it the same user and group IDs as on the host system. Alternatively, -
chroot/common/chroot.xml
r9fcb5e4 rb71fa50 12 12 13 13 <para>It is time to enter the chroot environment to begin building 14 and installing the final LFS system. As user <systemitem14 and installing the final CLFS system. As user <systemitem 15 15 class="username">root</systemitem>, run the following command to 16 16 enter the realm that is, at the moment, populated with only the … … 37 37 <para>From this point on, there is no need to use the 38 38 <envar>LFS</envar> variable anymore, because all work will be 39 restricted to the LFS file system. This is because the Bash shell is39 restricted to the CLFS file system. This is because the Bash shell is 40 40 told that <filename class="directory">$LFS</filename> is now the root 41 41 (<filename class="directory">/</filename>) directory.</para> -
chroot/common/kernfs.xml
r9fcb5e4 rb71fa50 30 30 mount -vt sysfs sysfs $LFS/sys</userinput></screen> 31 31 32 <para>Remember that if for any reason you stop working on the LFS system32 <para>Remember that if for any reason you stop working on the CLFS system 33 33 and start again later, it is important to check that these file systems 34 34 are mounted again before entering the chroot environment.</para> … … 44 44 nodes are created by the Udev package. Since this package is not 45 45 available to us right now, we must take other steps to provide device 46 nodes under on the LFS filesystem. We will use the <quote>bind</quote>46 nodes under on the CLFS filesystem. We will use the <quote>bind</quote> 47 47 option in the mount command to make our host system's /dev structure 48 appear in the new LFS filesystem:</para>48 appear in the new CLFS filesystem:</para> 49 49 50 50 <screen><userinput>/tools/bin/mount -o bind /dev $LFS/dev</userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.