lkml.org 
[lkml]   [2004]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: keyboard problem with 2.6.6
From
Date
>>>>> "Valdis" == Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:

Valdis> The whole 'init=/bin/bash' style of recovery has been
Valdis> widely documented and often used (for instance, it's
Valdis> covered in the RHCE class and used in one of the hands-on
Valdis> labs to recover a non-booting system). That's a lot of
Valdis> people to retrain, and a lot of systems that need
Valdis> changing...

Valdis> (Trust me - if it's 3AM, and you type 'init=/bin/sh' and
Valdis> it outputs the '#' but won't take input, you WONT think of
Valdis> that kernel and initscripts change from 3 months ago...)

Explain to me how a kernel compiled with
CONFIG_SERIO=m
CONFIG_KEYBOARD_ATKBD=m
would be able to boot with "init=/bin/sh" and still have the keyboard
working.

I've just verified that "make allmodconfig", which is what many people
are tempted to do once they've learnt about it, will produce such a
.config.




--
Sau Dan LEE 李守敦(Big5) ~{@nJX6X~}(HZ)

E-mail: danlee@informatik.uni-freiburg.de
Home page: http://www.informatik.uni-freiburg.de/~danlee

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

\
 
 \ /
  Last update: 2005-03-22 14:03    [W:0.229 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site