On Mon, 2 May 2005, Vagrant Cascadian wrote: > in my experience, if you do not mount /mnt/dev from the initrd, you get > a message saying that it was unable to write to /dev/console.. maybe > only when you chroot to /mnt... but this is necessary for some of the > initrd-netboot scripts to work.
My suspision is that this is due to one of two things: [1] The nfsroot:/dev tree is empty (ie has not got the charachter device console) and so as you sat not mounting devfs leads to "unable to write to /dev/console" error. - This could be fixed by ensuring /dev/console DOES exist in the nfsroot. [My experiance of building a lessdisk chroot using the debian packages leads me to believe that the nfsroot:/dev tree IS populated] [2] If devfs (or any other filesystem for that matter) is not mounted inside the chroot then the e2fsprogs initrd script unmounts the nfsroot at /mnt and then when "pivot_root" and "chroot" are called at the end of the initrd:/sbin/init they correctly state that /dev/console does not exists... indeed in this case nothing exists as the nfsroot was unmounted. - This could be worked arround by disabling the script from e2fsprogs by setting "PKGSCRIPTS=no" in /etc/mkinitrd/mkinitrd.conf. Maybe I'll find some time to play with lessdisk further and find out more about this devfs issue... Anyway please excuse me for restating these points! Thanks for saying you'll include the use_devfs option upstream and as ever thanks for writing the whole lessdisk package! Regards Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
