Grant Likely wrote: > Hey Behan, a few more comments... > > On Fri, Aug 8, 2008 at 11:03 AM, Behan Webster <behanw@xxxxxxxxxxxxxxx> wrote: > >> Geert Uytterhoeven wrote: >> >>> Thanks for this useful tool! >>> I'm used to plain debootstrap, but decided to give your elbs-rootfs a try for >>> creating up a mipsel and a powerpc NFS root file system. It worked fine, >>> except for one minor nit. As an NFS root file system is mounted read-only by >>> default, I had to manually do >>> >>> | mount -n proc /proc -t proc >>> | mount -n -o remount -w / >>> >>> before running finish.sh. Perhaps this can be added to the top of finish.sh? >>> >>> >> Odd. I never had this issue. It has always just worked for me. >> > > I had to do this also, and I had to explicitly "export PATH" to get > the finish script to work. Otherwise I dpkg complains > I've also never had this issue, but I will add it to the script. > What I probably did differently is that I booted the system with > "init=/bin/bash" on the command line instead of letting it just run > init. I needed to do this because if I let it run init, I got > complaints about PAM failures when trying to log in as root. How are > you booting the system on first run? > There's your problem. You may have had pam failures before you used elbs-rootfs, but you shouldn't when using it. My script twiddles with inittab to give you a getty with a bash shell without a password, and then fixes it in the finish.sh script. If you just boot with it normally it should just work. I'm too lazy to type init=/bin/bash, so the script does it for you. :) > Also, when booting on something like a 5200 with an uncommon serial > ports name (ttyPSC0), I had to manually add the /dev/ttyPSC0 device > file before it would boot. > You're using an older version then. The latest (v1.2) allows you to specify the serial port/baud rate when running the tool. Behan -- Behan Webster behanw@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
