Rolf Leggewie wrote...
> As I've written in this ticket before, this is not a bug in isdnutils.
> I'm afraid there is no good solution at the moment and I'm not aware of
> anyone working on this in the kernel or udev.
While I support your idea I strongly disagree with your actions.
At the moment, the ISDN subsystem is broken on wheezy, so don't lower
the severity, re-assign instead to whoever you consider is to blame.
Or, besser be realistic: Given the set of packages of (kernel, udev,
isdnutils) that currently are candidates for the upcoming wheezy
release, none of them creates the devices nodes. No doubt kernel and,
through sysfs, udev are the better place for that job but this neither
is implemented yet nor will be until the release. Therefore having
isdnutils doing it is the last resort but the last one that is
feasible for wheezy.
Now if you reject, the ISDN subsystem is broken at least on all
installations that use udev or are newly installed. The logical
consequence then is to consider isdnutils unfit for release and remove
it from wheezy. I doubt that this is your intention.
> 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?
Christoph
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
