Date: Tue, 4 Jul 2000 02:05:00 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: Scott Michel <scottm@cs.ucla.edu> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: manifest? Message-ID: <20000704020500.E679@dialin-client.earthlink.net> In-Reply-To: <200007022019.NAA21335@mordred.cs.ucla.edu>; from scottm@cs.ucla.edu on Sun, Jul 02, 2000 at 01:19:00PM -0700 References: <200007022019.NAA21335@mordred.cs.ucla.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 02, 2000 at 01:19:00PM -0700, Scott Michel wrote: > Is there a manifest of what files should be in a 4.x system, excluding ports, > so that one can clean up after an upgrade, e.g. delete shared libs that used > to belong to older versions of FreeBSD? > > I know that ports will link older files, but they can always be rebuilt. I think this would be a problem when people customize their make world via /etc/make.conf. It will look like there are a lot of files missing. If you are worried about old libs hanging around, they only really live in one place, # ls -lt /usr/lib/*.so* Should give you the info you need to delete the files (there are not that many) that might have changed. Watch out for broken symlinks too. What I found a little more worrisome on a 3.x to 4.0 upgrade was that some things moved from /usr/sbin to /sbin. There were two executables hanging about. Immediately after the make world, you can look at all of the old files left by doing something like, # find / -type d -mtime +1 -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000704020500.E679>