Date: Mon, 11 Mar 1996 21:10:59 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: changes to /etc/ttys Message-ID: <199603112010.VAA06762@uriah.heep.sax.de> In-Reply-To: <Pine.BSF.3.91.960311000957.2290M-100000@nervosa.com> from "invalid opcode" at Mar 11, 96 00:10:09 am
next in thread | previous in thread | raw e-mail | index | archive | help
As invalid opcode wrote:
> Exactly, that was my point entirely. A true console. I don't think
> keyboard input would matter that much though, seeing as all it does is
> get echoed.
I'm still missing the point why you don't want a getty on it? If i've
got a serial console, i usually also run a getty on it. If i don't
like the console behaviour (syslog messages all over the place), i
don't need to log in there.
Btw., i usually tweak the login message on the console, using a
different gettytab entry:
# console: add a newline after prompt
C|Pc-co|Pc on console:\
:co:lm=Console login^M:tc=Pc:
This way, my console looks like:
Console login
Mar 10 10:32:16 uriah login: ROOT LOGIN (r) ON ttyv0
Mar 10 10:32:16 uriah login: login on ttyv0 as r
Mar 10 10:33:11 uriah login: ROOT LOGIN (xdm) ON ttyv0
Mar 10 10:33:11 uriah login: login on ttyv0 as xdm
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603112010.VAA06762>