From: Henrik N. <um...@hn...> - 2005-09-25 12:50:01
|
On Fri, 23 Sep 2005, Rob Landley wrote: > There is indeed a console= switch, but I haven't found a way to get it to do > anything useful. (when I use console=/dev/tty0 it immediately exits with no > error message. Same for console=4,1. Strangely, console=tty0 boots, but > seems to be a NOP.) See Documentation/serial-console.txt and Documentation/devices.txt for details on how the console= option and /dev/console works. In short console= tells the kernel where to log messages. Can be specified multiple times if you want the kernel to report messages on more than one tty. If none is specified the kernel probes all the available tty drivers in a predefined order, usually tty0 (vt), ttyS0 (first serial port), lp. The first found console driver is then linked to /dev/console for userspace to attach to, and given as stdin/out/err to init. Note: tty0 is a magic vt device linked to the current foreground virtual terminal, not one specific terminal. This should only be used in singleuser mode as it competes with the real ttyX for the same virtual terminal. The ctty program mentioned has only been truly tested from inittab. Does not seem to work proper when used as init= so it's probably missing some process group thing or similar. Did work when executed interactively from a init=/bin/sh shell however. To be honest it skips quite many steps in the terminal initialization compared to how getty etc opens their terminal. Regards Henrik |