[lkml]   [2004]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: keyboard problem with 2.6.6
On Sun, 2004-06-06 at 11:37, Sau Dan Lee wrote:
> >>>>> "Valdis" == Valdis Kletnieks <> writes:
> >> You don't tell any kernel about that... it is the bootloader
> >> you are talking to. And that one may very well have integrated
> >> kbd support.
> Valdis> So GRUB knows about keyboards, lets you type in the
> Valdis> "init=/bin/bash", it loads the kernel, the kernel launches
> Valdis> init, /bin/bash gets loaded
> If init can launch /bin/bash (actually, it lauches getty in most
> setups), why can't it start the userland keyboard driver daemon?
> Back in the old days before the introduction of /etc/rc.d/, every
> daemon was started from by init.
> Valdis> - and /bin/bash can't talk to the keyboard because the
> Valdis> userspace handler hasn't happened.
> As soon as the daemon is running, /bin/bash can talk to the keyboard.
> There is not much concurrency problems here. The current input system
> makes it possible for /bin/bash to start opening the keyboard and
> waiting for input before the userspace handler is ready.
> Valdis> At that point you're stuck...
> I can't see how stuck it is. And if you fear that the userland
> keyboard driver would crash (maybe due to bugs), use the 'respawn'
> option in /etc/inittab.

The point is that 'init=/bin/bash' is usually used as a method to
do some _unexpected_ rescue work - meaning you usually do not think
about it (or write a shell script to start a keyboard daemon) until
you need it. Thats it - a rescue method - and its got nothing to do
with what is in inittab, or if getty's are started or not. Some
distro's even have sash installed by default (statically linked) in
case your glibc is borked or such, and you need to cp/mv/gunzip things.

Anyhow, the other point that should be made, is that your are really
getting boring/annoying. Please face the fact that many of us (most?)
do not want a silly daemon for keyboard, but an in-kernel driver.
Guess what else ... Valdis, etc do not even argue with you for wanting
this silliness (besides not wanting to get rid of the in-kernel driver),
but are prepared to add raw access, so that you can go and code/use your
daemon (Ok, so maybe the raw access is for more than what you want, but
anyhow ...).

So please stop being selfish and continuing to spam the list.


Martin Schlemmer
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 14:03    [W:0.058 / U:3.808 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site