Re: sharing disk between current and stable?

[Kris Kennaway]

On Mon, Aug 20, 2001 at 01:09:12PM -0400, Andrew Gallatin wrote:
 
 Is it safe to share a disk between -current and -stable these days?
 
 I've been away from freebsd for the last few months and have a fuzzy
 recollection that something about the on-disk superblock structure
 changed in -current earlier this summer (related to dirprefs?) and
 fsck on -stable wouldn't be able to fsck a fs used by current.
 
 Is that still a problem?

When I reverted to -stable, I had fsck come up with a long list of
complaints about snapshot files which should have been deleted long
ago.  Probably they were caused by a failed background fsck under
-current (I had an unexpected softupdates inconsistency on the
partition due to a kernel panic, and background fsck would just wedge
the entire machine when trying to deal with it).  However, I don't
know why they weren't dealt with by fsck under -current.

Kris

 PGP signature

Re: sharing disk between current and stable?

[David Wolfskill]

From: Andrew Gallatin [EMAIL PROTECTED]
Date: Mon, 20 Aug 2001 13:09:12 -0400 (EDT)

Is it safe to share a disk between -current and -stable these days?

I've ben doing in since about the 2nd week of March, tracking -STABLE 
-CURRENT daily (with a few exceptions; sometimes I couldn't build
-CURRENT for as much as a day).

I've been away from freebsd for the last few months and have a fuzzy
recollection that something about the on-disk superblock structure
changed in -current earlier this summer (related to dirprefs?) and
fsck on -stable wouldn't be able to fsck a fs used by current.

Is that still a problem?

It doesn't seem to be a problem for me.  YMMV; void where prohibited,
taxed, or otherwise restricted, etc.

Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message