|-----Original Message-----
|From: Clemens Adler [mailto:[EMAIL PROTECTED]]
|Sent: Monday, June 15, 1998 10:48 AM
|To: [EMAIL PROTECTED]
|Subject: Re: upgrading and configuration files
|
|
|Well, upgrading the kernel is no pain, just get an kernel rpm. I belive
|that's all.
| about the rest of your question upgrading the system I'd be interested
|also.

It's not quite so simple.  An upgraded kernel can require that other
packages be upgraded  which in turn require yet others (a ripple effect).
When you try to use rpm to install an upgraded kernel it will refuse if
other packages it interacts with are not at the required rev level or
better.  I can take this route, but it would be painful.

In order to reduce the hassle of having to identify, acquire, and upgrade
the individual pieces one at a time, I could just get redhat 5.1 and do an
upgrade of the entire OS (kernel and related packages), but before I head
that way, I was curious to find out what the impact would be on all the
/etc/* configuration files I've tweaked.  If I could do a wholesale redhat
upgrade and preserve/restore the custom configuration without a huge hassle,
that would probably be simplest.

|-------------------------------------------------------------------
|----------
|Clemens Adler                 e-mail: [EMAIL PROTECTED]
|                                      [EMAIL PROTECTED]
|Institut fuer Kernphysik
|Universitaet Frankfurt               office phone:  069-798-24285
|
|On Mon, 15 Jun 1998, Tony Garland wrote:
|
|> Being a newcomer to Redhat 5.0 and only having had previous painful
|> experience upgrading Windows NT versions, I'm curious if anyone
|can describe
|> or point me to information regarding the "typical" sequence of steps one
|> takes to upgrade Redhat from one version to another?
|>
|> The tiny bit of experience I've had considering upgrading the kernel
|> indicates that there can be a significant ripple effect between upgrading
|> the kernel, which requires upgrades to modules, which in turn require
|> upgrade of some packages, which in turn require upgrade of other
|packages,
|> etc.
|>
|> I'm particularly interested in how one goes about upgrading either the
|> kernel or the entire redhat release (say from 5.0 to 5.1) while
|minimizing
|> the impact on the current configuration of the machine.  For
|example, when
|> you do an upgrade, what happens to existing configuration files (such as
|> those under /etc) and how can you restore proper operation of
|your machine
|> using the previous configuration, but with the upgraded OS or kernel in
|> place?
|>
|> (Please excuse me if this is a stupid question--I've been badly burnt on
|> this in the Win95/NT world so am a bit shell-shocked about
|upgrades now.  I
|> want to pick up a change to the smbfs which is part of kernel 2.1.* and
|> redhat 5.1, but want to do so while minimizing negative impact
|on the work
|> I've put into configuration to date.)
|>
|>
|> --
|>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST
|ARCHIVES!
|> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips
|/mailing-lists
|>          To unsubscribe: mail [EMAIL PROTECTED] with
|>                        "unsubscribe" as the Subject.
|>
|>
|


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to