up vote 0 down vote favorite
share [g+] share [fb]

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.

link|improve this question
100% accept rate
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
feedback

3 Answers

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.

link|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
feedback
up vote 0 down vote

The answer is: udev

It's magical!

link|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
feedback
up vote 0 down vote

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.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

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