>Date: Sat, 21 Apr 2001 16:49:24 +0200
>From: Sheldon Hearn <[EMAIL PROTECTED]>

>After downgrading to RELENG_4 for a while to prove to my team mates
>that 3 months of pain were the result of hardware instability and not
>features of HEAD, I'm ready to get back on the wagon.

>I didn't follow the FILE size change debarcle, because I assumed that
>the problem would be resolved by the time I was ready for -CURRENT
>again.  However, the entry for 20010211 in UPDATING suggests that I was

>       The size of FILE was changed.  This breaks upgrading.  If
>       you must upgrade, be prepared for pain.  It also breaks almost
>       all binaries that you've compiled on -current.  You are warned

>Is this still true?

Well, I acquired my laptop in early March, got 4.2 running on it, then
cloned the / & /usr from that to another slice, and upgraded the clone
to -CURRENT.  I've been tracking both -STABLE & -CURRENT (daily) since.

I do not recall encountering any problems attributable to the above.

Indeed, the only undesirable side-effect of the procedure has been that
there was some cruft left over from 4.x -- the old kernel & modules.  Oh
yeah; when I'm running -STABLE, I see that there is a populated /dev
over on the -CURRENT side (that is hidden by the devfs mounted on /dev
when I'm running -CURRENT).

I suppose I could try wiping the cruft out; hasn't been enough of an
issue to bother with, though.

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

Reply via email to