Solaris Live upgrade: questions about /var/sadm/patch

Similar Threads:

1.Repost: Solaris Live Upgrade: questions about /var/sadm

Sorry for the report, seems like my news reader misbehaved (Ah, MSFT!)

 According to the solaris FAQ:

--------8<-----------------

|3.40) 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
    patches.

    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.

|3.41) Do I need to back out previous versions of a patch?

    No, unless otherwise stated in the patch README.
    If the previous patch installation saved the old
    files, you may want to reclaim that space.

    Patches can be backed out with (Solaris 2.6+):
     patchrm <patch-id>

    or in earlier releases:

     /var/sadm/patch/<patch-id>/backoutpatch <patch-id>

    Backoutpatch can take an awful long time, especially when the
    patch contained a lot of files.  This is fixed in later versions
    of backoutpatch.

---------------->8---------------------------

Prior to doing the live upgrade, I would like to minimize the size of my
root partition
(containing /var in my case) Can I safely remove all patches (not just the
save directories)
from /var/sadm/patches or will live upgrade do it automatically ?

I presume that after a solaris upgrade, the liste of installed patches on
the system will be NULL ?

Another last point, does "back out patch" mean to go back to the state
BEFORE the patch was applied ?
I don't understand the 3.41 paragraph. What does it mean ? It seems to mean
that whenever you apply a new
patch, you should go back to the previous version before installing ?

Ex: Original package = blabla-01

Apply patch blabla-02  (BlaBla-01 saved)

You now want to apply patch blabla-03.

Does question 3.41 ask: "if you need to install patch blabla-03 you should
first back ou to blabla-01 ?"

If so, what do you do if the README tells you that you have to, but you
REMOVED the save directory ?

Thanks !

2.Live Upgrade broken for Solaris 9 to Solaris 10 upgrade

Has anyone else run into this problem?  I'm using Live Upgrade to upgrade
a Solaris 9 server to Solaris 10.  I created a boot environment on a
separate disk, and then upgraded it to Solaris 10 with `luupgrade -u'.
Now when I go to use `luupgrade -t' to apply the latest Solaris 10
patches to it, I get this...

  Validating the contents of the media </var/tmp/patches>.
  The media contains 220 software patches that can be added.
  All 220 patches will be added because you did not specify any specific patches to add.
  Mounting the BE <s10lu>.
  ERROR: The boot environment <s10lu> supports non-global zones.The current boot environment does not support non-global zones. Releases prior to Solaris 10 cannot be used to maintain Solaris 10 and later releases that include support for non-global zones. You may only execute the specified operation on a system with Solaris 10 (or later) installed.

Is there a way to make this work?  The new BE can't possibly contain a
a non-global zone.

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

3.for huge "recommended" patch, not enough room in /var/sadm/patch

Not enough room in /var/sadm/patch, the install-script
says.

But on other partitions and disks I have *lots* of
space available.  Just not on the root partition,
which contains /var/sadm/patch (among much else,
of course).

Might this work.

Rename /var/sadm/patch to eg /var/sadm/patch2-original,
then create a patch dir in some partition that had
logs of space, and then make /var/sadm/patch
a symlink to there.



Or should I symlink either higher up the var/sadm tree,
or symlink *several* of those directories?

And is there any reason to *copy* those directories
to where I'm going to symlink to, so that if there's
already some contents, they'll still be "there"?

(That install-script doesn't explicitly check for
this trick -- I hope not.)

-----

Or is there maybe some better way to do surmount this not-enough-disk pbm?



----------

Of course I do down to single-user before doing
the   ./install_cluster,

but any reason I can't leave everything else
mounted?

I mean, in recent years, has anyone *ever* gotten
hurt by doing that?   (If so, please say how, so we
can all get wised-up on this, uh, danger.)


Thanks!!!

David

4.default permission in /var/sadm/patch

Hi all,

does anybody know what the reason is that all directories
in /var/sadm/patch have the permission 0754. Like this
it is impossible to grep for the Synopsis of the patches
in the README files as a normal user. Like this you can
only look at the patchids, which give a user who wants
to hack a system enough information about missing
patches that might offer opportunities to attack.

So what is the point not setting the default permission
to either 0750 (including the directory /var/sadm/patch)
or to 0755 and give users the oportunity to read the
README files of the installed patches?

TIA,
Tom

5.Solaris 8 upgrade using Live upgrade method

I want to get some feedback on the Live upgrade of Solaris 8 (2/04). How was
the upgrade? Was it kind of problem-free? Did Veritas give any problem with
the upgrade?

6. Live Upgrade fails during upgrade from Solaris 10 U7 to U8

7. /var/sadm/pkg is very huge

8. Cleaning Up /var/sadm