Christoph Biedl wrote: > Rolf Leggewie wrote... >> For the time being the administrator needs to make sure the devices are >> created.
> So you want each isdnutils user to manually hack some mknod statements > into the bootup scripts as you consider it a bad idea providing that as > package maintainer? Seriously? To add my 2¢: As a long time Debian user (and admin of some 100 servers) I always liked the "just works" way of usage of Debian packages. Install a deb, tweak the configuration and be done with it. I would be quite disappointed if I now have to add mknod statements to my own init script or the isdnutils init script or rc.local. (It is besides the point that I know how to do this. Some other user may lack the knowledge how to correctly create init scripts.) Of course, nowadays device nodes should be created by udev, acting upon events from the kernel. And most drivers are able to generate these events. But the old ISDN4Linux code has never been ported and probably never will. So far this statement from Karsten Keil from 2004 (!) still stands: ,----[ http://osdir.com/ml/linux.isdn.i4l.user/2004-05/msg00012.html | > - what is the best way to get these device nodes? | | create it in the ISDN start script with mknod `---- Insisting upon the standpoint "but the kernel/udev has to create the device nodes" will not solve the problem for this release at this time in the freeze process. The Debian Policy states: ,---- | 10.6 Device files | | [...] | | If a package needs any special device files that are not included in the | base system, it must call MAKEDEV in the postinst script, after notifying | the user (This notification could be done via a (low-priority) debconf message, or | an echo (printf) statement.) | | [...] `---- I fail to find any policy which forces the use of udev or similar mechanisms. Of course, having the kernel/udev create the device nodes is technically correct but horribly broken in this special case. I'd like a little bit ugly but working solution, please without the need for the user/admin to manually hack the init scripts. Grüße, Sven. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
