Messages in this thread | | | From | Dmitry Torokhov <> | Subject | Re: keyboard problem with 2.6.6 | Date | Sun, 6 Jun 2004 10:09:23 -0500 |
| |
On Sunday 06 June 2004 04:37 am, Sau Dan Lee wrote: > >>>>> "Valdis" == Valdis Kletnieks <Valdis.Kletnieks@vt.edu> 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? >
Init does not start bash, in the case above bash started by the kernel _instead_ of init. The only thing you have is bash. No regular init scripts will be executed, nothing.
> 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.
But nothing has started driver (no scriprs were run, remember?) so it's not running and bash can't get keyboard input.
-- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |