Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm wondering what creates /dev/stderr on FC14. rpm -qf doesn't show any package ownership. I've dug through the init scripts and can't find it anywhere.

To provide some context, I'm creating a chroot'd jail to start with lxc.

share|improve this question
On my (non RedHat) system, /dev/stderr is a symlink to /proc/self/fd/2. – Paul Tomblin Jan 2 '11 at 19:17
But interestingly enough, it's not mentioned in /etc/udev/rules.d anywhere. – Paul Tomblin Jan 2 '11 at 19:19
up vote 3 down vote accepted

The canonical creator of these files is "makedev". It does have a man page. Makedev, however, simply creates symlinks to /proc/self/fd/2 for /dev/stderr.

share|improve this answer
During the install process makedev is run, creating all the devices that you will (hopefully) ever need. – bahamat Jan 3 '11 at 6:55

The answer is: udev

It's magical!

share|improve this answer
Is udev the correct answer for managing /dev entries inside a chroot? – blueben Jan 2 '11 at 23:56
@blueben answer is "maybe" but "probably not". Usually in a chroot you only want to give access to a very limited set of devices, otherwise the chroot could just open /dev/sda1 and go to town. udev may have a limited mode, but I'm not sure. – bahamat Jan 3 '11 at 6:57

There are entries for stdin, stdout and stderr in /lib/udev/devices. I don't think you should have to do anything special for them in a chrooted environment.

See also here. Also interesting.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.