I wanted to post a summary of my experiences with the SLES10 SP1 upgrade
process. Some of these experiences will be submitted as bugs to Novell;
some were just things I felt others might find it useful to be aware of.
Starting with a clone of our (customized) master SLES10 GA system image,
I chose to apply the service pack by IPLing the SP1 DVD installation
system and using YaST2 to update software packages.

Notes:

1. I have a list of 150 RPM packages which have been removed from our
customized master SLES10 GA system image. During the documentation of
this process for the GA release I discovered that it was impossible to
use YaST2 to prevent these packages from being installed to begin with;
it was only possible to let YaST2 install them and then remove them with
"rpm -e", afterward. Of these 150 packages, the SP1 update process
re-installed all but three, despite my having selected the option to
only update installed packages.

2. In addition to the 147 GA packages which had been re-installed, there
were 30 new packages installed with SP1 which did not correspond to ones
I had removed from the GA system. A nubmer of these were new 32-bit
versions of packages which existed in GA as 64-bit only---some, 32-bit
versions of 64-bit packages I had removed:

        audit-libs-32bit
        gtk-sharp2-32bit
        libgsf-32bit
        libgssapi-32bit
        libnscd-32bit
        libpcap-32bit
        mozilla-nspr-32bit
        mozilla-nss-32bit
        openct-32bit
        opensc-32bit

The following appeared in (were available with) GA, but had not been
installed until the SP1 update:

        libiniparser
        xlockmore

The following are the entirely-new packages installed with SP1:

        gtk-engines
        inst-source-utils
        libgdiplus
        libssui
        limal-nfs-server
        limal-nfs-server-perl
        mono-winforms
        pciutils-ids
        sles-heatbeat_en
        sles-preparation-zseries_en
        sles-startup_en
        sles-stor_evms_en
        util-linux-crypto
        yast2-autofs
        yast2-boot-server
        yast2-control-center-qt
        yast2-registration
        zypper

3. There was one package which was automatically removed during the SP1
update:

        autoyast2-utils

4. Several new services were installed and some were automatically
enabled (chkconfig):

        dumpconf        off 
        earlygdm        on
        mon_fsstatd     off
        splash          on
        splash_early    on
        suseRegister    on

5. Of the services I had disabled in GA, the SP1 update re-enabled one
without telling me (chkconfig).

        novell-zmd      

6. The SP1 update also replaced the contents of
/etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.a001, rendering the linux
guest uncommunicative on the network. We have QETH_OPTIONS="fake_ll=1"
set in this file so that DHCP works correctly on our layer 3 VSWITCH.
When this file was replaced, it prevented the linux guest from receiving
its DHCP lease, in turn preventing the second stage of the update from
completing successfully, as YaST2 could not open the X display on my
desktop PC. Since this stage of the update launches YaST2 without giving
the opportunity for a console login session, we had to utilize a rescue
system to make the changes (in our case, a single-user boot option in
zIPL) before we could continue with the update.

I hope some of you may find this information useful.


ok
r.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to