FreeBSD release still nukes everything on scratch using a big-hammer
method, even if it is nfs-mounted (and, when it is, the expiration policy
may be different). Daily script should by default do nothing to remote
filesystems?
----------------------------
revision 1.8.2.1
date: 1994/04/18 06:37:29; author: rgrimes; state: Exp; lines: +10 -4
Use the hostname.* files created by the installation to reduce the
amount of work one has to do when setting up a system.
----------------------------
----------------------------
revision 1.1.2.1
date: 1994/04/10 20:20:26; author: rgrimes; state: Exp; lines: +11 -5
Use /dev/fd0 instead of /dev/fd0a. Add mounting of mcd1 if mcd0
fails when searching for a cdrom drive.
----------------------------
revision 1.1.2.1
date: 1994/04/10 20:20:25; author: rgrimes; state: Exp; lines: +3 -3
Use /dev/fd0 instead of /dev/fd0a. Add mounting of mcd1 if mcd0
fails when searching for a cdrom drive.
----------------------------
revision 1.53.2.3
date: 1994/04/10 20:19:37; author: rgrimes; state: Exp; lines: +12 -3
Must have etc and usr directories on the cdinstall floppies.
Need to have device files for mcd1.
Create links for usr/libexec and usr/lib on cdinstall floppies so that
shared library code is loaded from cdrom.
----------------------------
revision 1.2.2.3
date: 1994/04/17 19:45:24; author: rgrimes; state: Exp; lines: +13 -2
Eliminate warning messages about /sbin/sh /sbin/init and /etc/termcap
when extracting the bin or des archives. Note this is also the
place I fixed the libc.so.1.0 problem a long time ago by adding
a --exclude libc.so.1.0 to the tar command.
only once an hour instead of every five minutes. This was due to a minute
specification of 0/5 -- which should have been */5. This has been fixed.
Expect your /var/cron/log to grow much faster now.
Used the canonical non-existent file (/nonexistent) instead This should
probably be documented somewhere, but it's unclear where the right
place is (passwd(5)? login(8)? hier(7)? all three?).
installed by default, because then everybody would suddenly start
trying to authenticate themselves in the CS.BERKELEY.EDU realm, which
is really not a very good idea. Maybe the README could get installed.
pair of crunched binaries that are not built by this, but other than
that it is back to an automated procedure. So many changes it is
hard to describe.
