Solved - Debian update - keyboard unresponsive

[Lennart Sorensen]

On Thu, Oct 27, 2011 at 02:45:24PM -0400, Russell Reiter wrote:
> Udev was running and tried to run again from a different runlevel,
> that was the problem.

Correct.  That was the problem.

The workaround provided by the original reporter of the bug on the
other hand did not correctly solve that problem.  It replaced it with
a different problem.  That is why the udev package maintainer said in
the comment to the bug "Don't do that.  It is wrong".

> At this moment the fix for the user works, udev initializes on boot.
> It detects and deals with devices and applies its rules appropriately.

udev is not just for boot, it is for handling all hotplugged devices
at runtime.

> From my perspective it's about having a condition state of ready for purpose.
> 
> So what's broken here?

udev is supposed to be always running.  You told it to stop.  That is
what is broken.  You may not have noticed the consequences of that yet,
but they still exist.

Simply rename the incorrect script to anything you want as long as it
doesn't start with K.  Then you will have solved the original problem
and NOT created a new one.

But hey if you think you are smarter than the udev package maintainer,
go ahead.  Break your system.  Who cares.

-- 
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