Hi,

I'm preparing a Slack11 partition and having installed everything on it, I chroot into it because I want to do some compiling of stuff.

I verify that I am root with whoami, but I am denied permission to /dev/null which has permission setting crw-rw-rw-, so I can't understand it.

Under what circumstances can you be denied permission to a file/device if you are root? I know it's a chroot environment, but that shouldn't have any bearing on the permissions issue, I don't think. Any suggestions?

Thanks in advance.

When/how exactly are you “denied permission to /dev/null”? Do you have a /dev/null in your soon-to-be root?

root@box # echo "hi" > /dev/null
/dev/null permission denied.

This is after chrooting.

ok, managed to do a bit of googling on this. It would appear to have something to do with udev.

That's less surprising because udev is kind of dynamic. I think I have to do some unmount and then re mounting with new permissions.

So although, in linux, "everything is a file" and "ls -l" gives you their permissions, some files are "equaller than others" to borrow George Orwell and may deny your permission over and above what "ls -l" says.

Can'tbe bothered going into this. Other things have popped up. udev, seems difficult somehow.

Sorry for reviving such an old thread, but I had this same issue, and found a fix.

For me, the problem occurred when I mounted the partition via a GUI file browser, and then tried to chroot. The chroot worked, but things like /dev/null gave me problems.

When I unmounted the partition in the file browser, remounted the partition myself with a simple # mount /dev/sda1 /mnt, and then chrooted, everything was fine.

It must be something to do with the permissions the file browser mounts the partition with.

I hope this port help someone, even if it's only me searching for this issue again in six months.

1 members found this post helpful.