> Since I went from CD for two versions of -current over a short span of
> time (and didn't use the system much between), I can't say for certain,
> anymore.

Most of the changes went in early July 2003, so both are 'recent'.
(ie post my rototil)

> > The way /etc is handled is broken!
> 
> I wasn't relying on much by way of automation.  The first time around, I just
> did an "update" from the burned CD, and was quasi-manually merging via
> "diff".

>  Most files were unchanged, or varied only by my configuration changes.

Yes - and the files you'd changed probably only contained comments before.

> A few were new.  
> 
> This seemed like not a bad idea, since it helped alert me to changes.

Yes - I distrust 'upgrade' as well!

> I am beginning to believe that I should set up a DHCP server to
> simplify system upgrades for those times when I don't have a pre-update/
> pre-upgrade version of /etc from which to get network configurations...

I did once sort out a list of all the files I had to edit after
a simple re-install....

> > >    The sysinst tool apparently did NOT mount /dev/wd0a, and instead
> > >    quickly filled up the /mnt *directory* (on ramdisk?), producing a
> > >    stream of errors.
> > 
> > mmm which version of sysinst were you running?
> > /dev/wd0a should (now) have been mounted of /targetroot
> > Anything that assumes /mnt needs fixing.
> 
> Whatever I got from building -current to "release" and then "sets".

There must be a lurking /mnt somewhere.....

> The first time, it might have been from as far back as sometime in
> early September.

Plenty new enough...

> In all cases?  I confess to not attempting to find and examine
> the sysinst sources.  (^&

Unfortunately I made the mistake of looking into the bag :-(

	David

-- 
David Laight: david@l8s.co.uk