Message-Id: <200406041837.i54IbfYE023527@turing-police.cc.vt.edu>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: keyboard problem with 2.6.6 
In-Reply-To: Your message of "Fri, 04 Jun 2004 14:17:14 EDT."
             <200406041817.i54IHFgZ004530@eeyore.valparaiso.cl> 
From: Valdis.Kletnieks@vt.edu
References: <200406041817.i54IHFgZ004530@eeyore.valparaiso.cl>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1143825952P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Fri, 04 Jun 2004 14:37:40 -0400
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1234
Lines: 36

--==_Exmh_1143825952P
Content-Type: text/plain; charset=us-ascii

On Fri, 04 Jun 2004 14:17:14 EDT, Horst von Brand said:
> Pavel Machek <pavel@suse.cz> said:

> > You get pretty nasty managment problems. How do you do init=/bin/bash
> > if your keyboard is userspace?
> 
> 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.

So GRUB knows about keyboards, lets you type in the "init=/bin/bash", it loads
the kernel, the kernel launches init, /bin/bash gets loaded - and /bin/bash
can't talk to the keyboard because the userspace handler hasn't happened.  At
that point you're stuck...


--==_Exmh_1143825952P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFAwMF0cC3lWbTT17ARAhZSAKCbF0JntfxgTsKyaGtWBiRVJZZXtgCgqldA
jiINno5aStStjOe8/MugplI=
=EemQ
-----END PGP SIGNATURE-----

--==_Exmh_1143825952P--
-
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/