What creates /dev/stderr in FC14?

Question

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.

On my (non RedHat) system, /dev/stderr is a symlink to /proc/self/fd/2. — Paul Tomblin, Jan 02 '11 at 19:17
But interestingly enough, it's not mentioned in /etc/udev/rules.d anywhere. — Paul Tomblin, Jan 02 '11 at 19:19

score 3 · Accepted Answer · answered Jan 02 '11 at 22:36

3

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.

answered Jan 02 '11 at 22:36

blueben

3,487
1
15
15

During the install process makedev is run, creating all the devices that you will (hopefully) ever need. – bahamat Jan 03 '11 at 06:55

score 0 · Answer 2 · answered Jan 02 '11 at 23:51

0

The answer is: udev

It's magical!

answered Jan 02 '11 at 23:51

Curtis Doty

476
1
5
6

Is udev the correct answer for managing /dev entries inside a chroot? – blueben Jan 02 '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 03 '11 at 06:57

score 0 · Answer 3 · edited Apr 13 '17 at 12:14

0

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.

What creates /dev/stderr in FC14?

3 Answers3