unmount /proc filesystem FAILURE-help??

[battery_included]

This is one of the last messages I see when rebooting or halting my RedHat 7.1 system.
Now, I noticed that mounting the proc filesystem is the first message displayed after entering "Interactive Startup" when
booting.
Of course I tried typing 'man proc', but to
be honest, that screen printout could easily be the poster child for the existence of
LNO. Could someone please let me know if this is a serious problem, and/or how to
troubleshoot it?
Thanks in advance.

[MBMarduk]

The /proc directory is a non-existent directory.
It existst in the sense that THE KERNEL 'virtually' makes /proc appear. (You configure the '/procFS' in the KERNELCONFIG)

/proc gives you and many other programs info on everything your comp/kernel/PROCesses are doing.

This is why 'mount' shows
none on /proc type proc (rw)

'cuz it takes no space on the HDD, only RAM.
It's essential to a healthy system:
ideally you should have this in your /etc/fstab (AND configured in your kernel):

none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0

among other things.

GL,
-Mike

[MBMarduk]

Before I forget...
Dunno why unmounting it might FAIL tho.
Type "mount" and see if its mounted while running your comp.
If it's NOT then either your bootup script FAILED or didn't TRY.
Maybe you compiled a kernel without support for it?

[battery_included]

Originally posted by MBMarduk:
<STRONG>Before I forget...
Dunno why unmounting it might FAIL tho.
Type "mount" and see if its mounted while running your comp.
If it's NOT then either your bootup script FAILED or didn't TRY.
Maybe you compiled a kernel without support for it?</STRONG>

The kernel was compiled during the install. I'm not at a point where I would try compiling it myself. Also, everything seemed fine until I put in a CD-ROM, copied some files I needed from it, and then clicked
'eject' before clicking on 'Unmount' in
GNOME. My fstab file reads as follows:

LABEL=/ / ext2 defaults 1 1

/dev/fd0 /mnt/floppy autonoauto,owner 0 0

none /proc proc defaults 0 0

none /dev/pts devpts gid=5,mode=620 0 0

/dev/hda6 swap swap defaults 0 0

/dev/cdrom /mnt/cdrom iso9660 noauto,oowner, kudzu,ro 0 0


/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,
kudzu,ro 0 0


And when I type 'mount' I get:

/dev/hda5 on / type ext2 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=
620
automount(pid784) on /misc type autofs (rw,
fd5, pfrp=784,minproto=2,maxproto=3)

none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)


I don't know if that would give you, or anyone else here, a clue but I hope so.
Thanks,
Gregg

[MBMarduk]

You're using automount, the name should tell you enough.

Linux wouldn't have LET you eject the CDR without umounting first :D

Still weird the problems persist.
Although I can't imagine big problems arising from keeping the /proc mounted...there's just nothing there so nothing can be corrupted.
If you aren't getting errors otherwise; it isn't serious and try to ignore it.

GL,
-Mike