GentooThis forum is for the discussion of Gentoo Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I installed Gentoo 2008 from the minimal install CD but I forgot to follow one step of the installation instructions from the x86 Gentoo Handbook about mounting the /proc directory on the CD to the /proc directory on the partition I was installing Gentoo on. I forgot to run the following command:
mount -t proc none /mnt/gentoo/proc
I then continued to install the stage three tarball and the portage tarball and the installation seemed successful and I can boot up to a nice prompt and I ran emerge --sync with no problems (no gui installed yet).
In your opinion, will this installation be stable and not cause any problems later on down the road since I forgot to mount /proc? Or should I reformat and start all over again and include the missing step? Exactly why should /proc be mounted?
Thank you,
Roy
Last edited by rrrssssss; 10-22-2009 at 05:48 PM..
I then continued to install the stage three tarball ...
You have to install the stagetarball before mounting /proc to gentoo/proc since the gentoo/proc directory is created while extracting the tarball.
Quote:
In your opinion, will this installation be stable and not cause any problems later on down the road since I forgot to mount /proc?
in my opinion, if you didn't experience any problems while the installation everything is ok.
Quote:
Exactly why should /proc be mounted?
proc is a pseudofilesystem which manages the access to processes within the kernel and kernelmodules. If you mount the /proc filesystem to your chroot-environment you make it possible to access this kernelprocesses from within the chroot environment.
There's absolutely no problem, as said, if you had not a single problem during the installation, it really doesn't matter. /proc doesn't truly exist in the same sense that the rest of the fs's. /proc is a convenient way to access the OS structures in an fs-like fashion, but it only exists in the kernel memory, and not in the disk as the rest of the fs's do.
In /proc you can see, amongst many other things, a whole image of the kernel allocated memory that will be big but as said don't worry since it doesn't take any disk space at all (/proc/kcore), structures relevant to the current processes (a lot of dirs named with numbers under /proc, like /proc/1 and so on), and some others created by specific drivers or kernel parts, like /proc/cpuinfo. This structures can be navigated and some of them can be viewed with a simple "cat <filename>" to get live info about your kernel and drivers, processes, etc.
This is created by the kernel itself, so there's nothing from the livecd or the install phase remaining in there. Don't worry.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.