forked from pikhq/sabotage
-
Notifications
You must be signed in to change notification settings - Fork 68
chroot troubles
rofl0r edited this page May 9, 2012
·
7 revisions
it sometimes happen to me that upon leaving a chroot, the umount will fail due to some /dev file still being open.
in this case, trying to rm -rf $R can cause major havoc, such as a deleted /dev/null
restore it using
mknod --mode=666 /dev/null c 1 3
others:
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mknod /dev/systty c 4 0
mknod /dev/tty c 5 0
mknod /dev/console c 5 1
mknod /dev/ptmx c 5 2
mknod /dev/rtc c 10 135
mknod /dev/tty0 c 4 0
mknod /dev/tty1 c 4 1
mknod /dev/tty2 c 4 2
mknod /dev/tty3 c 4 3
mknod /dev/tty4 c 4 4
mknod /dev/tty5 c 4 5
mknod /dev/tty6 c 4 6
mknod /dev/tty7 c 4 7
mknod /dev/tty8 c 4 8
mknod /dev/tty9 c 4 9
mknod /dev/tty10 c 4 10
mknod /dev/tty11 c 4 11
mknod /dev/tty12 c 4 12
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
mknod /dev/ttyS3 c 4 67
from https://bugzilla.redhat.com/show_bug.cgi?id=196828
and
mknod -m 644 /dev/random c 1 8
mknod -m 644 /dev/urandom c 1 9
chown root:root /dev/random /dev/urandom
http://linux.die.net/man/4/random
deleted sound devices etc can be regenerated using
udevadm --trigger
this could be needed as well
mkdir /dev/input
mknod /dev/input/event0 c 13 64
mknod /dev/input/event1 c 13 65
mknod /dev/input/event2 c 13 66