On Tue, 3 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..
>
> upon further consideration, i think the reason it fails to write to
> /dev/console is that the nfs fil
> > 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..
upon further consideration, i think the reason it fails to write to
/dev/console is that the nfs filesystem is mounted read-only.
even though there is a
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.
M
> I don't see a need to mount devfs in the netboot-initrd.
> /sbin/init does a conditional mount of devfs in the nfs(ch)root
> just before pivot_root which seems sane. lessdisk seems to produce a sane
> chroot in that /dev is populated and any non-lessdisk chroot should (in my
> opinion) also have
I don't see a need to mount devfs in the netboot-initrd.
/sbin/init does a conditional mount of devfs in the nfs(ch)root
just before pivot_root which seems sane. lessdisk seems to produce a sane
chroot in that /dev is populated and any non-lessdisk chroot should (in my
opinion) also have a sane /de
5 matches
Mail list logo
