Hi all,
I have been looking at the handbook section regarding a qemu-user chroot
and have some serious concerns about part of it. Specifically, in the
section for setting up the chroot it is suggested to run
chroot . /bin/busybox mdev -s
Since I (like most others) am currently running udev, this seems to me like
a very bad idea. (And indeed this is confirmed when I try it on my dev VM,
where the permissions for /dev/pts /dev/null /dev/random etc. are messed up
by this)
Can someone please explain the logic here, since as far as I can tell so
far, simply omitting this step does no major harm.
Cheers
Phil Tooley
I have been looking at the handbook section regarding a qemu-user chroot
and have some serious concerns about part of it. Specifically, in the
section for setting up the chroot it is suggested to run
chroot . /bin/busybox mdev -s
Since I (like most others) am currently running udev, this seems to me like
a very bad idea. (And indeed this is confirmed when I try it on my dev VM,
where the permissions for /dev/pts /dev/null /dev/random etc. are messed up
by this)
Can someone please explain the logic here, since as far as I can tell so
far, simply omitting this step does no major harm.
Cheers
Phil Tooley