mf@ircam.fr (Michel Fingerhut) (10/27/90)
In our lil' DEC sub-universe, I rdist files which I believe should be identical on all these planets--e.g., termcap, gettytab, and whatever. I recently noticed that /etc/gettytab was distributed from time to time, while it never appeared to have been modified--I keep it under SCCS, it's read only and its contents have not changed: but it has obviously been touched, and that triggered the rdist. Well, I finally found what happened: /etc/rc.local EDITS this file every time the machine is rebooted and puts into it the current ULTRIX version number (which changes much less often than the number of reboots, on such systems as ours at least). I knew that motd is thus handled by /etc/rc on most systems and that's fine, since it's a file which is supposed to change. Oh well... Incidentally, is the header of /etc/gettytab indicative of the way Unix was converted to Ultrix (%s/ni/ltri/g)? # @(#)gettytab 4.1.1.4 (ULTRIX) 11/18/88 # Based on 4.2bsd labelled: 4.7 (Berkeley) 85/02/05 # Most of the table entries here are just copies of the # old getty table, it is by no means certain, or even likely, # then any of them are optimal for any purpose whatever. # Nor is it likely that more than a couple are even correct
rusty@belch.Berkeley.EDU (rusty wright) (10/30/90)
People who worry about security say that you shouldn't have things like your OS version and unix flavor in your login banner so I changed my default gettytab entry to be default:\ :ap:fd#1000:\ :im=\r\n:\ :sp#1200: Voila! No more magically changing gettytab. (Note to Sun sysadmins; this doesn't work 100% on Suns as telnetd has the "im" hard-wired into its code.)