Macros in /etc/issue 

Newsgroups:  comp.os.linux.misc
Date:        Wed, 29 Oct 2003 02:02:49 GMT
> Where can I find a list of macros for /etc/issue?

Did you do "man issue"? If you are confused by the format of a config file, "man $CONFIG_FILE" is often helpful.

> Eg., Kernel \r on an \m.  Especially, is there a way to show the
> current tty #?

Like the man page for issue says, the "escape codes" are interpreted by whatever getty you're using, so read the man page for your getty.

Usually, distros use mingetty or agetty for the virtual consoles. Virtual consoles can also use real escape codes (sequences beginning with ASCII 27) to set colors. The sequence ^[[01;31m sets the foreground color to red, f'rexample. "man console_codes" for more.

Matt G

Macros in /etc/issue 

Examine /etc/inittab to see which getty variant you are using (mingetty, agetty, etc.) and then check the manpage for that getty.

Macros in /etc/issue 

> \m. Especially, is there a way to show the current tty #?

Try \n for the hostname and \l to display the tty number.

Andreas Janssen

How to disable booting messages? 

Newsgroups: comp.os.linux.misc,comp.os.linux.setup,linux.redhat.install,linux.redhat.misc Date: Fri, 03 Jan 2003 10:43:14 +0100

> When Linux is booting, it displays the kernel booting messages and init
> script(RedHat) messages on the screen.
>
> Is there anyway to disable all the messages when booting?
> I would like to have my Linux box not to display any kernel messages and
> init script messages and go directly to "login: " screen.

You cannot jump directly to the login prompt: you first need to go through the startup process. It seems you can get rid of the messages by hacking /etc/rc (under Suse, anyway):

if test "$RUNLEVEL" = "0" -o "$RUNLEVEL" = "6" ; then
    case "$REDIRECT" in /dev/tty[1-9]*)
        REDIRECT=/dev/tty1
        setconsole $REDIRECT < $CONSOLE
        set -- $(stty size < $REDIRECT)
        LINES=$1
        COLUMNS=$2
        export LINES COLUMNS
    esac
fi

change that bit to suit you.

However, the down-side to getting rid of them is that you will have some log wait with no messages before your login prompt comes up. This could be very confusing to the user. Also, you'll WANT the output the moment a drive scan fails and you need to see the info.

stephan beal

How to disable booting messages? 

You may silence the kernel-messages with the kernel command line parameter "quiet".

Andreas Rogge