gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Added mounting the devpts filesystem into the new LFS partition

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2735 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Jeremy Utley 2003-09-05 02:06:21 +00:00
parent 1a6a5c37b5
commit 5c0b6e70bd
2 changed files with 30 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter01/changelog.xml
View File

@ -82,6 +82,10 @@
</itemizedlist> </itemizedlist>
</para></listitem> </para></listitem>
<listitem><para>September 4th, 2003 [jeremy]: Chapter 6 - Mounting Proc:
Added mounting the devpts filesystem into chroot here. Closes bug 533.</para>
</listitem>
<listitem><para>September 4th, 2003 [jeremy]: Chapter 6 - Mounting Proc: <listitem><para>September 4th, 2003 [jeremy]: Chapter 6 - Mounting Proc:
Added a warning at the end regarding checking that proc is still mounted Added a warning at the end regarding checking that proc is still mounted
if you stop and restart the lfs process.</para></listitem> if you stop and restart the lfs process.</para></listitem>

33
chapter06/mountproc.xml
View File

@ -1,13 +1,13 @@
<sect1 id="ch06-proc"> <sect1 id="ch06-proc">
<title>Mounting the proc file system</title> <title>Mounting the proc and devpts file systems</title>
<?dbhtml filename="proc.html" dir="chapter06"?> <?dbhtml filename="proc.html" dir="chapter06"?>
<para>In order for certain programs to function properly, the proc file <para>In order for certain programs to function properly, the proc and devpts
system must be available within the chroot environment. file systems must be available within the chroot environment.
As a file system can be mounted as many times and in as many places As a file system can be mounted as many times and in as many places
as you like, it's not a problem that the proc file system is already as you like, it's not a problem that the these file systems are already
mounted on your host system -- especially so because proc is a mounted on your host system -- especially so because they are virtual
virtual file system.</para> file systems.</para>
<para>The proc file system is mounted under <para>The proc file system is mounted under
<filename class="directory">/proc</filename> by running the <filename class="directory">/proc</filename> by running the
@ -15,6 +15,25 @@ following command:</para>
<para><screen><userinput>mount proc /proc -t proc</userinput></screen></para> <para><screen><userinput>mount proc /proc -t proc</userinput></screen></para>
<para>The devpts file system is mounted to <filename class="directory">/dev/pts
</filename> by running:</para>
<para><screen><userinput>mount devpts /dev/pts -t devpts</userinput></screen>
</para>
<para>Should this command fail with an error to the effect of:</para>
<blockquote><screen>filesystem devpts not supported by kernel</screen></blockquote>
<para>It means that your host system does not support devpts. You have two
options at this point. You can either not worry about it, in which case some
of the tests we will run later will fail, or you can use the following command
from a terminal not in chroot to put your host's pts system into your new
LFS's filesystem:</para>
<para><screen><userinput>mount --bind /dev/pts $LFS/dev/pts</userinput></screen>
</para>
<para>You might get warning messages from the mount command, such as <para>You might get warning messages from the mount command, such as
these:</para> these:</para>
@ -30,7 +49,7 @@ on your system configuration (such as the host system's Glibc version that was
used to compile the mount program with).</para> used to compile the mount program with).</para>
<para>Remember, if for any reason you stop working on your LFS, and <para>Remember, if for any reason you stop working on your LFS, and
start again later, it's important to check that the proc filesystem is still start again later, it's important to check that these filesystems are still
mounted inside the chroot enviornment. Otherwise, some programs might mounted inside the chroot enviornment. Otherwise, some programs might
end up compiled incorrectly.</para> end up compiled incorrectly.</para>