From: Rick Miller - Linux Device Registrar (rick@ee.uwm.edu)
Date: 05/03/93


From: rick@ee.uwm.edu (Rick Miller - Linux Device Registrar)
Subject: [ANSWERS]: Non-obvious Non-FAQ questions
Date: 3 May 1993 10:05:37 GMT

khamer@sumax.seattleu.edu (Kenneth Hamer) writes:
>Well, perhaps they are obvious to someone else... (I hope)
>
>1) How do I allow root logins on non-console terminals? Currently, if I
>have a terminal hooked up to a serial port it won't allow root or anyone
>in the root group to log on.

The file "/etc/securetty" contains a list of all tty's on which root login
is to be allowed. Normally, this lists only virtual consoles for security
reasons. The *better* way of logging in as root from a remote terminal is
to login as a normal user and then use the "su" command to become root only
when you *have* to. It's not good practice to be root all the time, since
if you screw up it can make your system unusable for long periods of time.

>2) How do I make the screen erase when I log out so that only a login
>prompt shows?

The most reliable method (because it even works on dumb terminals) is simply
to put 26 empty lines at the top of your "/etc/issue" file. Since getty will
display "/etc/issue" before displaying the login: prompt, your screen will be
clear of other debris.

The more elegant method is to include the "clear" command in your shell's
logout file (if it can do that). BASH uses "~/.bash_logout". This file is
executed *after* you type "logout" or "bye".

Sorry, but I don't know the answer to the Seyon question.

Rick Miller <rick@ee.uwm.edu> | <ricxjo@discus.mil.wi.us> Ricxjo Muelisto
Send a postcard, get one back! | Enposxtigu bildkarton kaj vi ricevos alion!
          RICK MILLER // 16203 WOODS // MUSKEGO, WIS. 53150 // USA