Solved - Debian update - keyboard unresponsive

[Lennart Sorensen]

On Thu, Oct 27, 2011 at 03:43:12PM -0400, Russell Reiter wrote:
> So if it is stopped why does it detect devices that weren't plugged in
> when it is first booted.

If the driver is already loaded, the kernel will detect those devices
just fine.

> It is not stopped. Udev is just stopped from being called while it is
> already running.

So you have a udevd running?  If you are running in runlevel 2 with
a script named K02udev in /etc/rc2.d then sysvinit says udev must
be stopped.

If you do have udevd still running, then there must be a bug in the init
system, because that shouldn't be possible.

> Nope I'm not smarter than him.
> 
> Debian just uses LSB headers to deal with package maintainers.

LSB headers deal with dependancies/ordering.  Not deciding if things
should or should not be running.  It also includes default values for
how to generate the runlevel links, but they are only defaults, they
have no influence on what actually happens.

LSB headers don't deal with package maintainers.  Package maintainers
use them to tell init what order things need to be started in.

-- 
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists