just got a mesage from our favorite keeper of the faq. he mentions that my
fix won't work. on upgrades the filesystems gets mounted on /a so we need
the ln to point to ../usr/var/sadm
----- Original Message -----
From: "Casper Dik" <Casper.Dik@holland.sun.com>
To: "Erin Jones" <firstname.lastname@example.org>
Sent: Friday, November 03, 2000 4:39 AM
Subject: Re: SUMMARY: /var/sadm is too damn big
: >119214 /usr/var/sadm
: >119214 /var/sadm
: ># ln -s /usr/var/sadm/ /var/sadm
: Don't do this. You've just rendered your system unupgradable.
: You recover, do this:
: rm /var/sadm
: ln -s ../usr/var/sadm /var/sadm
: (I think I got the one ".." right)
: That allows you to recover.
: If you need to remove data from /var/sadm, go for the undo files.
: rm -rf /var/sadm/pkg/*/save/1?????-??
: gets rid of all the old patch files.
: The solaris FAQ says:
: 3.39) Why does installing patches take so much space in /var/sadm?
: All the files that are replaced by a patch are stored under
: /var/sadm/patch/<patch-id>/save so the patch can be safely
: backed out. Newer patches will save the old files
: under /var/sadm/pkg/<pkg>/save/<patch-id>/undo.Z, for each package
: You can remove the <patchdir>/save directory provided you also
: remove the <patchdir>/.oldfilessaved file. Newer patches will not
: install a .oldfilessaved file.
: Alternatively, you can install a patch w/o saving the old
: files by using the "-d" flag to installpatch.
: --- end of excerpt from the FAQ
: The most recently posted version of the FAQ is available from
U BEFORE POSTING please READ the FAQ located at
. and the list POLICY statement located at
A To submit questions/summaries to this list send your email message to:
A To unsubscribe from this list please send an email message to:
E and in the BODY type:
R unsubscribe sun-managers
. unsubscribe sun-managers email@example.com
L To view an archive of this list please visit:
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:21 CDT