<meekrob> there's a big problem with the new install doc... <meekrob> mount /proc /gentoo/proc <meekrob> should be <meekrob> mount -o bind /proc /gentoo/proc <meekrob> newbies can't figure it out ... as above Reproducible: Always Steps to Reproduce: 1. 2. 3.
This is how it was previously. There was a short discussion of it and the conclusion was that -o bind was unnecessary, as I recall.
And when I say 'this,' I really mean 'that.' ;-)
could that not cause problems as you do not provide a filesystem?
Well, there is still a problem: groug mnt # mount /proc/ mnt/ mount: /proc/ is not a block device This should be either: mount -o bind /proc /new/place or mount -t proc /proc /new/place First will "hardlink" old location to new location. Only possible in kernels 2.4 and higher. Second is universal and will just mount another instance of proc, which in the end is the same (since hardlinking a dir just creates similar instance..). Personally I would prefer 2nd variant, as sometimes one might need to install off 2.2 kernel series (like upgrading an old box and doing it "live"). George
i think modifying to mount -t proc /proc /mnt/proc is also the most sensible solution. just my 2c
# mount -t /proc /mnt/gentoo/proc # cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf # chroot /mnt/gentoo /bin/bash Just to unify the semi-correct responses to this bug: mount -t proc none /mnt/live This needs to be added to the installation instructions sooner than later.
Blah. That should read: mount -t proc none /mnt/gentoo/proc
ppl, what are you doing? The latest commit now reads """ # <c>mount -t proc proc /mnt/gentoo/proc</c> """ This is still wrong. *Or* you do "mount -t proc none /mnt/gentoo/proc", *or* you do "mount -t proc /proc /mnt/gentoo/proc".
that is correct, it has been verified by at least 4 people in -dev. The doc is fine as is.
I would change to: mount -t proc /proc /mnt/gentoo/proc This will prevent some hassle for newbies.
