Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!xanth!nic.MR.NET!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: /etc/issue Message-ID: <13673@ncoast.ORG> Date: 22 May 89 23:30:11 GMT References: <222@dftsrv.gsfc.nasa.gov> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.unix.wizards Distribution: usa Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 32 As quoted from <222@dftsrv.gsfc.nasa.gov> by stailey@iris613.gsfc.nasa.gov (Ken Stailey): +--------------- | "The file /etc/issue contains the _issue_ or project identifcation to be | printed as a login prompt. This is an ASCII file which is read by [the] | program _getty_ and then written to any terminal spawned or respawed from | the _lines_ file." | | The trouble is it doesn't work as advertised, and there's no docs for the | mysterious "lines" file. +--------------- The so-called "lines" file should be shown as /etc/inittab. It is in our manuals. I've used /etc/issue on many systems; it works fine. Note, however, that it is *not* a "login prompt" (who wrote that manual, anyway?); it is a banner displayed BEFORE the login prompt: FooBar, Incorporated UNIX (foobar) login: _ The first two lines (yes, the blank line as well) come from /etc/issue; the last line is from /etc/gettydefs. If you're using SCO Xenix, all bets are off: in its infinite wisdom, SCO decided that inittab wasn't the way to go, and kept the old-fashioned init and getty. Unless you have a *very* recent version of SCO Xenix 386, you're out of ck. -- Brandon S. Allbery, moderator of comp.sources.misc allbery@ncoast.org uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu Send comp.sources.misc submissions to comp-sources-misc@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser