[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -current "sane to try" yet?



I often live on -current, on my ThinkPad.  Overall its been amazingly
stable, but it could blow up on you in some unexpected way at any
time.  You must always remember this.

If one wishes to play with -current, vital data should be backed
up frequently. I back up my important things to another system
EVERY DAY.  I even make bakups of email inbetween those, such
that in general I can't lose more than about 12 hours of stuff if my
system blows up.

That is the only sane way to use -current.  Its been looking very
good lately, but you never know when it might sprout claws and
fangs--and eat your disk.  Thats why making backups is vital.
If you aren't the adventerous who finds having to extricate oneself
from some disaster fun, stick with -stable.

If you want to join in on -current, grab a snapshot and install it.
I'd then get the src tarballs from a 3.1 CD or the net, and update
that src via cvs to -current..  The documentation in the mini-faq is
pretty decent, but even with that its easy to make mistakes.  I think
its fair to say that problems you encounter during the upgrade and
compile will be your fault.  All of mine occured because I did
something incorrectly.  You'll learn stuff by doing it.  Remember to
think about problems before you ask here, and you'll figure most
of it out by yourself.

Have fun.

--STeve Andre'

On Wednesday 26 June 2002 12:01, Phil Pennock wrote:
> I've got the 3.1 CDs here.  I'm looking at incredible work put into
> OpenBSD since the 3.1 release, especially with the hackathon.
>
> Is it generally believed that -current has stabilised down after the
> upheaval, enough to make it sane to try snapshots and submit bug
> reports?
>
> I've a box, it'd be a clean install.  It doesn't need to be rock solid,
> as it'll be a desktop, but I'd rather it didn't crash once an hour.  ;^)
> I'm (probably) capable of fixing smallish problems myself.
>
> Timeframe is start of next week, next snapshots (including the resolver
> fixes, OpenSSH 3.4, etc).  Snapshots sane or stick to CDs + errata
> fixes?
>
> If the answer is "CDs", is there an rough "wet finger in air" estimate
> of when the developers would like testers to start stressing the
> snapshots more?
>
> Thanks,