Difference between revisions of "Knoppix dev null Permission Denied"
From Knoppix Documentation Wiki
Sandbagger (Talk | contribs) m (I guess this is a common error that has been only lightly documented) |
(orc4tacel) |
||
Line 1: | Line 1: | ||
+ | drondelrolr | ||
Its commonly reported that when users chroot into an existing linux environment on their harddrive, they encounter the <code>/dev/null: Permission Denied</code> error message. This page attempts to explain it and how to avoid it. | Its commonly reported that when users chroot into an existing linux environment on their harddrive, they encounter the <code>/dev/null: Permission Denied</code> error message. This page attempts to explain it and how to avoid it. | ||
Revision as of 18:34, 12 July 2008
drondelrolr
Its commonly reported that when users chroot into an existing linux environment on their harddrive, they encounter the /dev/null: Permission Denied
error message. This page attempts to explain it and how to avoid it.
The error is caused by mounting a filesystem with the "nodev" mount option and then chrooting into it. Knoppix automatically places a "users" mount option into the /etc/fstab
file, which implies this "nodev" option.
You can override this option by editting /etc/fstab and appending ",dev" to the options column or simply mount your new chroot filesystem by bypassing the /etc/fstab entirely by typing the following command:
- mount /dev/hda1 /mnt/hda1 -o rw