Marco d'Itri wrote:
Again, please explain what do you think needs to be fixed in the udev
package.
Well, I originally submitted the bug; I'm not sure where this should be
fixed. What happened was: I installed a more-or-less complete desktop;
udev was pulled in by some GNOME package (via hal, I think). I also
installed alsa-*. Much later, I de-installed the GNOME packages;
unbeknownst to me, udev disappeared. This broke alsa-base.
alsa-base does not need udev to work (it has been explained to me). But
if udev is running, it installs itself one way; if udev is not
installed, it installs itself another way (creates device nodes). If
udev is subsequently removed, it does not know it has to create the
device nodes, and so simply breaks. This can be fixed by either
reinstalling udev, or (I think) reinstalling alsa-base. But there is not
really any way for the user, who (at least in my case) had not thought
of doing anything to either udev or alsa-base, to know why their sound
suddenly stopped working.
In any case, I don't know what package this bug belongs on or what the
correct solution is. But it seems that every package needing to create
device nodes will have the same problem: it cannot create them if udev
is running, so if udev is ever removed it must create them then. So any
such package is liable to be broken by the removal of udev.
I suppose one solution would be for packages of this sort to be split:
alsa-base-dev and alsa-base-udev, with appropriate Depends and Conflicts
lines. This would replace the code which autodetects the presence of udev.
Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
