xfs
[Top] [All Lists]

Re: RedHat 8.0 and XFS, the sad story continues ... (was: Begging :^))

To: Ragnar Kjørstad <xfs@xxxxxxxxxxxxxxxxxxx>
Subject: Re: RedHat 8.0 and XFS, the sad story continues ... (was: Begging :^))
From: Stuart Luppescu <s-luppescu@xxxxxxxxxxxx>
Date: 04 Oct 2002 08:47:37 -0500
Cc: "Linux XFS (SGI)" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20021003190718.D29922@xxxxxxxxxxx>
References: <3D9A838F.8260B8AD@xxxxxxxxxxxxxxxx> <20021002115719.C1780-100000@xxxxxxxxxxxxx> <20021002155655.A7079@xxxxxxxxxxxxx> <20021003165919.GI5852@xxxxxxxxx> <20021003190718.D29922@xxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Thu, 2002-10-03 at 12:07, Ragnar Kjørstad wrote:
> On Thu, Oct 03, 2002 at 12:59:19PM -0400, Theo Van Dinter wrote:
> > On Wed, Oct 02, 2002 at 03:56:55PM +0200, Axel Thimm wrote:
> > > So people using XFS and RedHat in production will have to stay with 7.3 
> > > unless
> > > SGI guys sacrifice their time again (for my personal benefit, I admit 
> > > that I
> > > hope they will). :(
> > 
> > Well, not really...  There is more than one way to upgrade your
> > installation.  I personally copy all of the RPMs into a single directory,
> > remove the ones I know I don't want to install (I have a personal
> > version, etc,) then start going through "rpm -Fvh a*rpm"...  If some
> > dependency comes up, I figure out what I need to install and install it,
> > then continue.
> 
> Apt-get is your friend :-)
> I've updated several servers from 7.1 to 7.3 with no real downtime.
> (except the time it takes to upgrade each package, and a reboot to get
> the new kernel).

I used apt-get very successfully to upgrade 7.2 to 7.3, but with the
switch to gcc 3.2 in 8.0 I wonder how possible this would be.
-- 
Stuart Luppescu -=- s-luppescu@xxxxxxxxxxxx        
University of Chicago -=- CCSR 
才文と智奈美の父 -=-    Kernel 2.4.19-xfs-r1                
There comes a time in the affairs of a man when he 
 has to take the bull by the tail and face the
 situation.   -- W.C. Fields 
 

Attachment: signature.asc
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>