- Timestamp:
- 01/23/2002 06:21:39 PM (23 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 12.2, 12.2-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 062461b
- Parents:
- 0aecdec
- Location:
- chapter05
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter05/chapter05.xml
r0aecdec r93dba6ab 5 5 &c5-introduction; 6 6 &c5-whystatic; 7 &c5-installasroot; 7 &c5-installasuser; 8 &c5-creatingdirs; 8 9 &c5-bash; 9 10 &c5-binutils; -
chapter05/kernel-exp.xml
r0aecdec r93dba6ab 26 26 <filename>$LFS/usr/include</filename>.</para> 27 27 28 <para><userinput>chown -R root.root $LFS/usr/include</userinput>:29 This ensures all header files under <filename>$LFS/usr/include</filename>30 are owned by user root and group root.</para>31 32 28 </sect2> 33 29 -
chapter05/kernel-inst.xml
r0aecdec r93dba6ab 15 15 make dep && 16 16 cp -HR include/asm $LFS/usr/include && 17 cp -HR include/linux $LFS/usr/include && 18 chown -R root.root $LFS/usr/include</userinput></screen></para> 17 cp -HR include/linux $LFS/usr/include</userinput></screen></para> 19 18 20 19 </sect2> -
chapter05/proc.xml
r0aecdec r93dba6ab 3 3 <?dbhtml filename="proc.html" dir="chapter05"?> 4 4 5 <para>In order for certain programs to function properly, the proc file system6 must be mounted and available from within the chroot'ed environment as 7 well. It's not a problem to mount the proc file system twice 8 or even more than that, since it's a virtual file system maintained by 9 the kernelitself.</para>5 <para>In order for certain programs to function properly, the proc file 6 system must be mounted and available from within the chroot'ed environment 7 as well. It's not a problem to mount the proc file system twice or even 8 more than that, since it's a virtual file system maintained by the kernel 9 itself.</para> 10 10 11 <para>The proc file system is mounted under $LFS/proc by running the following 12 command:</para> 11 <para>If you're still logged in as user "lfs", you should log out and log 12 in again as user root. The reason for this is simple: only root is allowed 13 to mount filesystems and to run chroot.</para> 14 15 <para>The proc file system is mounted under $LFS/proc by running the 16 following command:</para> 13 17 14 18 <para><screen><userinput>mount proc $LFS/proc -t proc</userinput></screen></para> -
chapter05/shellutils-inst.xml
r0aecdec r93dba6ab 20 20 cd $LFS/usr/bin && 21 21 mv date echo false pwd stty $LFS/bin && 22 mv sutrue uname hostname $LFS/bin</userinput></screen></para>22 mv true uname hostname $LFS/bin</userinput></screen></para> 23 23 24 24 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.