"Maintaining your installation" question

From: Stephan van Beerschoten (stephanb_at_whacky.net)
Date: 06/22/04

  • Next message: Ian FREISLICH: "Re: New preview patch for ipfw to pfil_hooks conversion" 
    Date: Tue, 22 Jun 2004 10:23:39 +0200
To: current@freebsd.org

    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?

    From time to time I find myself wondering through my lib/, bin/ and
    sbin/ directories (and others) to see, using `ls -lt`, which files
    haven't been updated lately. I then doublecheck to see if it is no
    longer in the base and I make an educated guess whether or not I
    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 

    -- 
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

  • Next message: Ian FREISLICH: "Re: New preview patch for ipfw to pfil_hooks conversion"

    Relevant Pages

    • Re: "Maintaining your installation" question
      ... > 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. ... > old doc files? ...
      (freebsd-current)
    • Re: Question about building modules on W2K
      ... The Perl I have is 5.8 but it's pretty ... MSVC++ 6 working quite happily on a perl built using the gcc compiler - ... And the binaries that ActiveState provide generally end up on machines ...
      (comp.lang.perl.modules)
    • Re: Mapping a directory to another for a non-privileged user
      ... stilllearning wrote: ... compiled my sysadmin tools (PERL, ... path is referenced in some of the tools, including some binaries. ...
      (comp.unix.admin)
    • Announce: Set::Array, Set::Hash, Set::String - new maintainer
      ... The author of these 3 modules, Daniel Berger, has asked me to take over maintenance of them, and I've agreed. ... He's moving out of Perl, poor chap. ...
      (comp.lang.perl.modules)
    • restructuring Perl installation
      ... I want to restructure my Perl installation so it's a bit more ... /usr/local/perl5.6.1/bin/ (lke perl and a whole bunch of other binaries ...
      (comp.lang.perl.misc)