From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 08:23:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C28616A4CE for ; Tue, 22 Jun 2004 08:23:56 +0000 (GMT) Received: from enigma.whacky.net (enigma.whacky.net [217.148.161.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D4A343D58 for ; Tue, 22 Jun 2004 08:23:55 +0000 (GMT) (envelope-from stephanb@whacky.net) Received: by enigma.whacky.net (Postfix, from userid 1000) id 3A4E020F4D; Tue, 22 Jun 2004 10:23:40 +0200 (CEST) Date: Tue, 22 Jun 2004 10:23:39 +0200 From: Stephan van Beerschoten To: current@freebsd.org Message-ID: <20040622082339.GB8087@enigma.whacky.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: "Maintaining your installation" question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jun 2004 08:23:56 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable As I realise this is a nice and way too broad subject, I do have a question regarding the maintenance of -CURRENT systems in particular. We see libraries being renewer, bumped up, build and eventually installed during many -CURRENT buildworlds and installworlds and the same goes for contributed parts of the base system like gdb (recent example) and perl and lots lots more. Is there a 'best practice' for getting rid of leftover 'old stuff': libs binaries and files as well as (just for example) any updated perl or any old doc files?=20 =46rom time to time I find myself wondering through my lib/, bin/ and sbin/ directories (and others) to see, using `ls -lt`, which files=20 haven't been updated lately. I then doublecheck to see if it is no=20 longer in the base and I make an educated guess whether or not I=20 can remove the file(s) without killing my system. Lately I have done exactly this, and I ended up removing the mount_kernfs (I think I got the exact filename here) binaries from a 4.10-STABLE upgrade I had just done, but what I didn't realize is that the kernfs was still working and I wondered why it dissapeared from the base build. Again, this is even more accurate for -CURRENT systems and I just wanted to hear any thoughts or proven solutions to this matter. /Stephan --=20 Stephan van Beerschoten [KeyID: 0x08F12864] "If you are adminstering UNIX systems and don't master tools such as make, shell, and perl, then you are working too hard." -- Wietse Venema. Fri, 12 Dec 2003 --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA1+yLJliZ6wjxKGQRAl27AJ0cPU2GhHo3NXiNnbyU2HRC1Jo6mQCgqr0q 898kAf22zqAvIr6o/k0wP3M= =uTM/ -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--