Hello all...
I apologize for the delay in this summary. Here was my original post:
On Mon, Oct 04, 1999 at 11:15:32AM -0700, Kathy Kost wrote:
> I have never used jumpstart to install patches and am about to
> try doing this with Solaris 2.7. Someone told me that when patching
> the boot image for a net install the patches are indeed installed but
> they don't show up in /var/sadm/patch afterwards. So according to
> the system (via showrev -p) nothing was/is installed.
>
> Does this really happen and if so, is there a way to get the system
> to recognize the installed patches? Or is this not a problem at all
> as long as you're doing it correctly? If this is the case any pearls
> of wisdom would be appreciated.
Thanks to the following people who responded so promptly to my question:
Willi Burmeister <wib+netmail@cs.uni-kiel.de>
Jens Fischer <fischjns@ina.de>
Lars Balker Rasmussen <lbr@mjolner.dk>
Arthur Darren Dunham <add@netcom.com>
Matthew Stier <Matthew.Stier@tddny.fujitsu.com>
Some of the source of my question comes from Solaris documentation,
whereby it states that you can patch a mini root with:
patchadd -C <install_image>
The description in the documentation states: "A command to patch
the files located on the mini root (i.e. Solaris_2.7/Tools/Boot) on
a net install image created by setup_install_server. This enables Solaris
installation commands and other mini root-specific commands to be patched.
install_image is the absolute pathname of the net install image. See
patchadd (1M) man page for more information."
A couple of people pointed out that patching the mini-root doesn't
necessarily end up in a patched jumpstarted workstation. If this is
the case then, I guess I'm still confused as to what the original
intent was in making this patchadd -C option. What would you use
it for then? One person pointed out that if you were to patch the
mini-root then it would be unclear as to how these patches would
behave since during jumpstart the workstations are running as if diskless
clients.
So, most of the folks responding preferred doing the patching via
some sort of finish script, so that's what I'm going to do. Lars and
Matthew contributed some scripts and they're included below.
Thanks very much for the help with this!
Kathy Kost
kathyk@wolfenet.com
-----------------------------------
>From Lars:
mkdir -p /a/users
mount server:/export/home /a/users
if [ `uname -r` = "5.7" ]; then
if [# maintenance updates ]; then
cd /a/users/solaris-patches/mu/7
./install_mu -d -f -R /a
# various patches
cd /a/users/solaris-patches/7
patchadd -M . -R /a *
else
...
fi
else
...
fi
-----------------------------
>From Matthew:
> The best solution, is to install a script in /etc/rc2.d or /etc/rc3.d
> that installs the patches you want during the first reboot.
#!/bin/sh
DIRNAME=/etc/rc2.d
BASENAME=S98install
(
#
# Move this script out of the way
#
if [ -f ${DIRNAME}/${BASENAME} ]; then
/usr/bin/mv ${DIRNAME}/${BASENAME} ${DIRNAME}/.${BASENAME}
fi
#
# Go to the patch directory and install patches
#
PATCHES=/apps/jumpstart/patches
if [ -d ${PATCHES} ]; then
(
cd ${PATCHES}
for PATCHDIR in 2.6_Recommended
do
if [ -d ${PATCHDIR} ]; then
(
cd ${PATCHDIR}
./install_cluster -q
)
fi
done
)
fi
# Do post-patch/pre-reboot work
:
) | /usr/bin/tee /var/tmp/patch.log
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:28 CDT