Ben Jackson wrote:
> I just did that upgrade (been with freebsd since 1.1!) and everything
> seems pretty smooth. I did a 2.2->3.1 upgrade on another machine so
> I'm probably glossing over some aout issues (mainly that you have to
> find them and move them into a separate directory).
>
> One thing that confused me for several days and I just figured out:
> sysctl moved from /usr/sbin to /sbin. I have /usr/sbin in my path first,
> so I was getting to old one. It almost works, but not quite. It only
> displays about 15 `kern.' variables and then quits.
>
> Perhaps the upgrade option should at least warn of that possibility
> (maybe obvious, but somewhat unexpected) or even include a list of files
> that once existed in FreeBSD but no longer do (to facilitate removing
> them). I'm thinking about digging out a 2.2.x install cd to build that
> list for myself.
>
> --Ben
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
Whenever I do an upgrade, I always do an ls -alt on /modules, /sbin, /bin,
/usr/bin, /usr/sbin,
/usr/libexec (ignoring the a.out ld.so) and /usr/lib. The bottom of the list
in each case
(where bottom means a date significantly before the rest) needs to be
analyzed and
probably deleted. In the case of /usr/lib, old libraries probably can be
moved into
/usr/lib/compat (a.out ones go in /usr/lib/compat/a.out, of course). I
always catch
some stuff using this procedure. :-)
I also end up hand-merging the backup of /etc made by the upgrade,
/usr/src/etc
for the version in question, and /etc to try and make it look as much like a
fresh
install with customizations as I can. I doubt that any reasonable
programatic way
to do this can be done, apart from what the upgrade already does.
S/MIME Cryptographic Signature
