Proc Does not mount

Amit Mehra amitm at
Mon Jul 21 07:22:46 PDT 2003

Hello Everybody,
I found my queries related to LFS and BLFS hence am posting the queries on both
the mailing lists.

          I have been facing problems configuring my boot scripts. It seems to me
that LFS4.0 doesn't have instructions for proper configuring of few steps, for
example creation of symbolic links from /etc/rc.d/rcsysinit.d/S20mountproc to
/etc/rc.d/init.d/moutproc or to configuring telnet as a deamon.(Although this
being a part of BLFS I did not get information on how to configure inetd).

Thanks to your previous suggestions, creation of sym link did resolve the problem
of Proc. But shouldn't these steps be included LFS 4.0 book or the HTML pages??
Another related question to this is that I have installed inetutils-1.4.2 from
BLFS and am not able to run the telnet like services in this package as a daemon.
I searched the linuxfromscratch site (
for this and found that required configurations are explained on this page but
for an older version of LFS. How do we configure this fro LFS4.0?

Kindly advice.

Stuart Sears wrote:

> On Saturday 19 July 2003 9:15 am, I thought I heard Amit Mehra say
> > Hello Linux World!
> >                                  I finished by LFS4.0 installation over
> > the intel box and found that things were going smooth. But one fine day
> > I noticed that proc does not mount automatically!! Every time I reboot
> > the system i have to manually mount /proc. I defined things in
> > /etc/fstab? but the error still persists.  I have this defined in the
> > /etc/fstab file:
> >
> > proc           /proc       proc       defaults    0       0
> >
> > Also, what I think is the in the file /etc/inittab I see that sysinit is
> > defined like this:
> >
> > S1: :sysinit:/etc/rc.d/init.d/rc sysinit
> >
> > where as on a RedHat 8.0 box it is defined like this:
> >
> > S1: :sysinit:/etc/rc.d/rc.sysinit
> >
> > Is it because of this I am facing this problem?
> nope - RH arranges its startup scripts differently to LFS -
> [simplified explanation of my understanding follows. Plases correct me If I
> am totally wrong! :-) ]
> LFS uses an argument to the /etc/rc.d/init.d/rc script to tell it which
> runlevel to start, it then runs all the scripts in the rc[runlevel].d folder
> (which themselves are symlinks to scripts in /etc/rc.d/init.d) - in this case
> rcsysinit.d
> RH uses an rc.sysinit script to do the same job
> altering your /etc/inittab to match RH would cause all kinds of probs (most
> notably a failure to succesfully boot) as we don't have this script...
> [in response to Ken's answer]
> LFS-4.1 also has an S20mountproc symlink, so nothing has changed there...
> check that you have the same symlink (just as Ken suggested). If not create
> it:
> ln -s ../init.d/mountproc S20mountproc
> if you DO have the symlink already, make sure that the
> /etc/rc.d/init.d/mountproc script is executable, or the script won't run in
> any case...
> if all of this works anyway, but /proc still doesn't mount...
> I take it /proc does succesfully mount when you do it manually?
> if yes, then I think the problem may be that the test is failing in the
> mountproc script on bootup - ie the system 'thinks' that proc is already
> mounted so doesn't mount it automatically
> if no, are you certain you enabled /proc filesystem support in your kernel
> config?
> what message does the startup script return?
> try running the /etc/rc.d/init.d/mountproc script after you have booted and
> before you mount /proc manually - what response do you get?
> just some random suggestions.
> --
> Stuart Sears RHCT (Registered Linux User #284465. LFS user #6416)
> --
>         Even if someone doesn't care what the world thinks
>         about them, they always hope their mother doesn't find out.
> --
> Unsubscribe: send email to listar at
> and put 'unsubscribe lfs-support' in the subject header of the message
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amitm.vcf
Type: text/x-vcard
Size: 346 bytes
Desc: Card for Amit Mehra
URL: <>

More information about the blfs-support mailing list