[EMAIL PROTECTED] (Marco d'Itri) writes:

> On Jul 08, Ferenc Wagner <[EMAIL PROTECTED]> wrote:
>
>> Or if you feel like it isn't worth the formal hassle of releasing
>> another version, please send me a pointer to the reasoning behind.
>
> links.conf exists because Debian policy for right or wrong forbids to
> ship device nodes in packages, and udev needs /dev/null and /dev/console.

Okay, thank you.  I don't know the policy rationale either.  Maybe you
could instead create them from the postinst script on first install.

> The reason for the other devices is explained in the first section of
> the file.

I'm afraid there's some misunderstanding here.  It was perfectly clear
why the nodes mentioned in links.conf have to be created manually.
Now it's also clear why you haven't followed your own advice and
created the nodes under /lib/udev/devices.  So why not tell the user:

# The udev daemon needs /dev/null and /dev/console, so the udev init
# script creates those nodes based on this file before starting udevd.
# To keep the usual configuration in one place, other static links and
# nodes are also created from here.
#
# If you need further manually created devices, create them in
# /lib/udev/devices/ to avoid conffile conflicts on upgrade.
# The Debian package can not do this for Policy reasons.

L fd            /proc/self/fd
L stdin         /proc/self/fd/0
L stdout        /proc/self/fd/1
L stderr        /proc/self/fd/2
L core          /proc/kcore
L sndstat       /proc/asound/oss/sndstat

D pts
D shm

M null          c   1 3
M console       c   5 1

# udev can not manage these devices (cf. README.Debian)
M ppp           c 108 0
M loop0         b   7 0
D net
M net/tun       c  10 200


Btw. why is loop0 special?

As far as I can see, initramfs-tools manually creates /dev/null and
/dev/console, and those nodes are also passed into the final /dev.  I
tested commenting out those two lines and the nodes were present after
a reboot.  Are you sure your hated "hack" is still needed?  Maybe for
compatibility reasons?
-- 
Cheers,
Feri.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to