mount -o remount,rw,nosuid -t ext2 /dev/hdaN /mnt/hdaN See the following discussion http://www.knoppix.net/forum/viewtopic.php?p=62780 My suggestion would be to add a note in section 6. Installing the Gentoo Base System under 6.a. Chrooting
Isn't the "mount -o remount,dev" what you would need? It's mentioned in the thread as well...
It's my humble suggestion that this bit of information be grouped with the documentation that deals with knoppix or other livecd(s) that exibit the same behaviour. an additional note. I don't believe it is mentioned anywhere in the gentoo documentation.
We have a small Knoppix excerpt in our alternative installation manual (http://www.gentoo.org/doc/en/altinstall.xml#doc_chap3) which might benefit from an update... but until now I don't have enough information on what really needs to happen (and why).
OK, I'm really a newbie to Linux, but from what I've been able to understand, when you use Knoppix to recover a failed Gentoo install by chrooting into it, the /dev subdirectory (or at least the null device) is not functional. This is evidenced by the 'permission denied' errors portage operations return. Although the error messages state that there are problems with permission levels, this is not truly the case; folders or devices under /dev may indeed sport the right permissions and owner, but are not usable. Instead, (re)mounting the /dev folder with the following parameters - mount -o remount,rw,nosuid -t ext2 /dev/hdaN /mnt/hdaN renders the null device (and possibly others?) functional. Oddly enough, I originally prepared (partitioned, formatted) the environment with Knoppix, using the default knoppix mount behaviours and the methods outlined in the Gentoo install handbook and had no problems at all with portage or anything, but shortly before I finished the installation, my network link broke, disconnecting me from the chrooted environment I had created and in so doing closed the bash session that contained the chrooted environment. When I re-established the environment, the dev/null errors appeared and no amount of shutting down and restarting the host made any difference. So it appears that this is only germane for those who use knoppix to install Gentoo, but fail to complete the installation in one session. I wish I could give the full technical reasons why this is necessary, but I am ignorant for the moment about what these are.
I'd rather have a second opinion on this matter, especially since it works in one session but not if you split it up :S
Okay, I found a few postings on our forums mentioning the need to bind-mount dev (which looks like a saner solution). I hear nothing about this proposed patch and also no second opinions, so I'll just implement the bind-mounting (again).
Bind-mounting added. Also added a comment for the documentation developers that, in case we get issues with this bind-mounting again, we should try this magical approach...
