That's what I was afraid of. The only things of consequence that I've
installed are DB2 Connect Enterprise Edition, JBOSS/Tomcat, and brought CVS
to use and have Samba customized to do some stuff that is not stock.
My biggest concerns were migrating the UID/GID structures and the home
directories as we have a bunch of our developers deleriously happy about
CVS. They couldnt make some high profile windows package do what they
needed and CVS did. Not having to re-create the DB2 connect environment
would save me a headache too, but it sounds like I have an excederin level
event in any case.
|---------+---------------------------->
| | "Post, Mark K" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 02/19/2003 09:37 |
| | PM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Upgrading a SuSE 7.0 system to a 7.2 (2.4.9?) kernel in place
|
>------------------------------------------------------------------------------------------------------------------------------|
James,
This is kind of tough call. It may or may not be less work to take this
approach, versus installing a 2.4-based system, and transferring the
necessary configuration files to it. How much have you done to the system
after the install, that "manually re-creating the environment" would be a
hassle?
If you do decide to do it, you'll need to pretty much follow the course you
laid out, but there will be a number of other packages that will need to be
upgraded. Probably (at least?):
gettext
binutils
gcc
glibc
modutils
strace
gdb
There may be others. The order you do it in will be important also, due to
the change in the Linux/390 ELF magic number that was introduced in 2001.
Mark Post
-----Original Message-----
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 10:11 AM
To: [EMAIL PROTECTED]
Subject: Upgrading a SuSE 7.0 system to a 7.2 (2.4.9?) kernel in place
What's the best way to do an in-place upgrade of an existing, functioning
and running Linux system, using the SuSE provided tools (such as Yast)
I am trying to avoid creating a new 2.4 system and manually re-creating the
environment. What I need to do is to update the system to 2.4 on the LDL
dasd I have, and then format the new dasd as CDL and copy the existing
volumes to the corresponding CDL volumes, adjust the /proc/dasd bits and
IPL.
