Difference between revisions of "Knoppix dev null Permission Denied"


From Knoppix Documentation Wiki
Jump to: navigation, search
(orc4tacel)
m (Reverted edits by 203.158.221.227 (Talk); changed back to last version by Sandbagger)
 
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.
  

Latest revision as of 05:30, 15 July 2008

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:

  1. mount /dev/hda1 /mnt/hda1 -o rw