Solved - Debian update - keyboard unresponsive

[Russell Reiter]

On Thu, Oct 27, 2011 at 1:17 PM, Lennart Sorensen
<lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
> On Thu, Oct 27, 2011 at 12:49:30PM -0400, Russell Reiter wrote:
>> No it means to disable it in this runlevel. ie. not use it in this runlevel.
>
> Yes, that's it.  It disables the _service_ in this run level by
> stopping it.  When you move from runlevel to runlevel, anything labeled
> S## is started, and anything labeled K## is stopped.  That's what
> runlevels are for.
>
> Anything not labeled S... or K... does nothing.
>
>> In development there is a foreknowledge that things will change and
>> maybe even interfere with something it shouldn't. The idea is to
>> provide an avenue to a timely fix. Different process's use different
>> runlevels for different purposes. Why not have the ability to change
>> that feature just by a name change.
>>
>> Don't delete the work just make sure everything has the ability to be
>> reordered correctly.
>>
>> So tell me what is broken here?
>
> If you rename S02udev to K02udev in rc2.d then you are telling the
> system to stop udev in runlevel 2.  So now your system no longer has
> udev running.
>
> Since udev is expected to be running, that is a problem.

Udev was running and tried to run again from a different runlevel,
that was the problem.

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

>From my perspective it's about having a condition state of ready for purpose.

So what's broken here?




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