Bug#375395: [Pkg-cups-devel] Bug#375395: cupsys: Printer stopped working after upgrade

[Martin-Éric Racine]

ke, 2006-06-28 kello 11:26 +0100, Roger Leigh kirjoitti:
> Henrique de Moraes Holschuh <hmh at debian.org> writes:
> > If you need "lp", you either load it in through discover (which, unlike
> > udev, has the task of finding out all high and low-level drivers that should
> > be loaded in a system), load it in through /etc/modules, load it on an
> > initscript, etc.
> 
> I just installed discover on my i386 test system, and it didn't load
> lp.  I rebooted it to see what happened at startup, and it didn't load
> lp then, either.
> 
> In a way, the fact that we have "lost" the facility to autoload
> modules when the device node is opened, despite the existence of the
> hotplug/udev/discover tools, is a usability problem. 

I see an even bigger issue here:  

We have too many hardware detection layers and none of them able to see
the full picture. Even worse, as witnessed in this particular case, they
all fail at detecting something as simple as the printer driver.

Anyhow, udev and discover duplicate each other in several way; they
ought to be merged the same way that udev integrated hotplug.

The way this could work:

1) detect hotplug events.
2) detect other hardware drivers.
3) detect peripherals attached to ports drivers loaded at 1 and 2.

AFAIK 1 and 2 are already handled by udev, while discover partially
handles 2 and 3.

IMHO, this is a debian-boot issue, not an application issue.

-- 
Martin-Éric Racine
http://q-funk.iki.fi