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_0
v3_1
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
Line | |
---|
1 | <sect1 id="ch05-proc">
|
---|
2 | <title>Mounting $LFS/proc file system</title>
|
---|
3 |
|
---|
4 | <para>
|
---|
5 | In order for certain programs to function properly the proc file system
|
---|
6 | 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 kernel itself.
|
---|
10 | </para>
|
---|
11 |
|
---|
12 | <para>
|
---|
13 | Mount the proc file system under $LFS/proc by running the following command:
|
---|
14 | </para>
|
---|
15 |
|
---|
16 | <blockquote><literallayout>
|
---|
17 |
|
---|
18 | <userinput>mount proc $LFS/proc -t proc</userinput>
|
---|
19 |
|
---|
20 | </literallayout></blockquote>
|
---|
21 |
|
---|
22 | </sect1>
|
---|
23 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.