[sf-lug] [DO NOT "REPLY ALL" unless you're on BOTH lists] - "vicki" dom0 upgrade successfully completed

[Michael Paoli]

[DO NOT "REPLY ALL" unless you're on BOTH lists]
Bcc: SF-LUG and BALUG sysadmin folks

The upgrade of the "vicki" (hostname) dom0 (which is the "host" of the
"guest" domUs:
sflug (sf-lug.com. 208.96.15.252 208.96.15.251)
balug (balug-sf-lug-v2.balug.org. 208.96.15.254)
)
from
Debian version 4.0 "etch" to version 5.0.4 "lenny"
was successfully completed by late yesterday.

Likewise upgrading the
sflug (sf-lug.com. 208.96.15.252 208.96.15.251)
domU remains - but I anticipate that will likely be
completed sometime between now and 2010-01-15.

Some slightly higher-level (manual) log entry details for
the interested and/or curious:

2010-02-08 Michael Paoli
Upgraded dom0 Debian from version 4.0 "etch" to version 5.0.4 "lenny",
using:
http://www.debian.org/releases/lenny/i386/release-notes/index.en.html
etc. (and http://www.debian.org/releases/stable/i386/install.txt.en) as guide.
Most of the "gory" details are in:
/root/upgrade-lenny.script
(the above from script(1), with script -t timestamp data in:
/root/upgrade-lenny.time
as per :
http://www.debian.org/releases/lenny/i386/release-notes/ch-upgrading.en.html#record-session
)
Much of the information (shell history) on actions done prior to that point
may be found in:
/root/etch_to_lenny_upgrade_history
starting at or slightly past line 428 - which is the first line
beginning with:
437
in that file.
The /root/etch_to_lenny_upgrade_history file was created via:
# fc -l -5000 -1 > etch_to_lenny_upgrade_history
and was done, if I recall correctly, just before starting script(1) to create
/root/upgrade-lenny.script
Stuff prior to that line 428 (/^437/) location in
/root/etch_to_lenny_upgrade_history
contains details mostly
related to things done in/from dom0 in preparation for and and in support
of upgrading the balug domU Debian
from version 4.0 "etch" to version 5.0.4 "lenny"
and also staging of some bits in preparation for the then forthcoming
dom0 upgrade (such as placement of CD ISO image(s), some slight tweaks
to some config files or putting in some commented out entries into
config files so they could be quickly and conveniently uncommented when
ready to proceed with upgrade(s)).
A bit into the upgrade of dom0, used
# dpkg-reconfigure debconf
to reconfigure debconf to use readline (avoids "pretty" curses based
screens that can commonly not be very pretty, and also makes
reading/reviewing subsequent script(1) data much nicer).
After upgrade, default kernel boot configuration didn't work (it would reset
itself before completing boot), swapped ordering of first two boot
entries in /boot/grub/menu.lst so the default would use
kernel /xen-3.2-1-i386.gz instead of /xen-3.0.3-1-i386-pae.gz - that
seemed to work sufficiently well.
Reconfigured Xen balug domU to use 2.6.26-2-xen-686 kernel


Quoting "Michael Paoli" <Michael.Paoli at cal.berkeley.edu>:

> [DO NOT "REPLY ALL" unless you're on BOTH lists]
>
> Bcc: SF-LUG and BALUG sysadmin folks
>
> The Xen Dom0 hosting sf-lug.com will be going down for maintenance (OS
> upgrades) this evening.  sf-lug.org remains unaffected.
>
> Some not directly "production" (redundant or no direct immediate production
> impact) BALUG systems will also be down this evening (all those on  
> IP 208.96.15.254).  (The Xen domU hosting a BALUG domU will be going  
> down).