In the Gentoo/PPC Handbook the user is asked to bind-mount /dev. A user replies: """ Anyway, I have found that if I bind-mount the /dev-filesystem at "4.f" in the handbook, I get some errors when unpacking the stage 1 tarball later on (5.b/5.c). I find out that if I wait with the bind-mounting until I have unpacked the tarball (that is, between step 5.c and 5.d in the handbook), I can avoid those errors. So my suggestion is that the bind-mounting in step 4.f is moved to after 5.c, if that doesn't break any other function. This way I guess installers (newbies like me) will have it a lot easier, not seeing any errors. """ Why is /dev bindmounted for PPC? Moving it elsewhere isn't very easy since most succeeding chapters are not ppc-arch specific.
Am I right that /dev isn't bind-mounted on x86 any more? The problem we had was with yaboot, the boot-loader, inside the chroot. It needs the correct /dev and not a generic one from the tar-ball. But as yabootconfig is now called from outside the chroot, where a correct /dev exists, this could not cause any problems. I'm just not sure about the manual yaboot installation, where you don't leave the chroot and call mkofboot and ybin -- this could cause problems.
> Am I right that /dev isn't bind-mounted on x86 any more? Yap.
Jochen, please take care of this bug. I believe the hb-install-ppc64-bootloader.xml file is a bit outdated wrt hb-install-ppc-bootloader.xml. Perhaps you can merge both files? The PPC handbook looks resolved, PPC64 however doesn't.
PPC handbook fixed, just forgot to close :-)
