xfs
[Top] [All Lists]

Re: 2.4.18 update details

To: "D. Stimits" <stimits@xxxxxxxxxx>
Subject: Re: 2.4.18 update details
From: Nathan Scott <nathans@xxxxxxx>
Date: Tue, 26 Feb 2002 13:29:40 +1100
Cc: "XFS: linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx>
In-reply-to: <3C7AF03F.8384BF25@idcomm.com>; from stimits@idcomm.com on Mon, Feb 25, 2002 at 07:17:35PM -0700
References: <20020226114324.J193798@wobbly.melbourne.sgi.com> <3C7AF03F.8384BF25@idcomm.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
hi,

On Mon, Feb 25, 2002 at 07:17:35PM -0700, D. Stimits wrote:
> Since this release is different than other releases (it requires
> different tools), I'd like to ask what the recommended update procedure
> is? Imagine we have multiple booting with older kernels as well, and we
> want to make both old kernel and this new kernel remain bootable...at

Both the new and the old kernels do remain bootable.

Boot the new kernel, install the new tools, and you're done.
Or, installing the new tools then booting the new kernel would
also work fine.

> least until it has had time to be tested...what would be the way to go
> about this and not end up with an unmanageable machine should the tool
> update and new kernel not go in exactly as expected?

I can't see any way you could possibly end up with an unmanageable
machine because of this change.  [ no, thats not a dare ;) ]

Iff you have mismatched kernels and tools, you would be unable to do
things like view/change EAs or ACLs, or restore dumps which have EAs
(because xfsrestore uses new/old syscalls, depending on its version).
There are no on-disk (fs) or on-tape (dump) format changes here, so
as long as you align your versions, everything should be fine.  And
if you don't, the consequences wouldn't be catastrophic.

cheers.

-- 
Nathan


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