Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Remote console options?



On Mon, 10 Jul 2000, John Chambers wrote:

> 
> Derek D. Martin wrote:
> 	 
> 	 It's VERY easy to configure a Linux box to use the serial port as the
> 	 console.  See /usr/src/linux/Documentation/serial-console.txt for details.
> 
> Hmmm ...  This seems to describe something that implements one of the
> major design failures of Microsoft systems:  In order for a change to
> take effect, you have to reboot.

You have to change your running kernel to have support for this option...
it's not a widely used option so it doesn't get compiled in by default.
This is very normal under Linux.  Any time you add a FEATURE to the linux
kernel, you have to reboot for your new kernel to take effect.

Not so if you add a DRIVER which can be compiled as a module, but the
serial console doesn't have a module, presumably because it has to be
there before most of the kernel initializes (in order to display
initialization messages, obviously), so it can't be a module.

Oh well...  Talk to your distribution vendor to have them compile in
support with their stock kernel, and you won't need to reboot...


-- 
Derek Martin
System Administrator
Mission Critical Linux
martin at MissionCriticalLinux.com 

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org