From: Nenhum_de_Nos (matheusbergmail.com)
Date: Thu Nov 01 2007 - 13:46:47 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 11/1/07, Steve Shockley <steve.shockleyshockley.net> wrote:
> Nenhum_de_Nos wrote:
> > but my main question is, how to make obsd allways up to date, keeping
> > it bug free. mas from time to time there is security bugs found and so
> > on.
>
> Simple way: upgrade every six months, and follow the -stable branch.

hmm, thats what I'll do then. but, there is no way to make my
4.2-current to rebirth as an ordinary 4.2 just born ?

> Complex way: Follow -current, upgrade your machines almost constantly.
>
> If you have anything approaching "production", run -stable. Downgrading
> is difficult, and sooner or later you'll hit something that makes your
> life difficult, like changing a major feature (ipf -> pf) or upgrading
> to packages that were built the day the shared library numbers change.
>
> > my question is, how to keep up to date if putting a cdrom and boot for
> > upgrade for me is too much of a problem for me ? and also, just as an
> > example (I'm really not trying to make flame wars or such things, I
> > just want to know how to make things in obsd) in Freebsd i can compile
> > and make almost everything yep online and running. just reboot and if
> > everything is fine, the downtime is just of the reboot itself.
>
> You can do an "unpack the install files over the running OS" upgrade,
> that's detailed in the upgrade guide in the FAQ. Better yet, you can
> put two machines together with CARP and not have any downtime at all.

by what I saw, the way Nick said is what I'll do :)

just want to be 4.2 release again ! :)

(if I cant, I'll install a 4.1 and then do the moves to be 4.2 and
begin the training :) )

thanks all,

matheus

--
We will call you cygnus,
The God of balance you shall be

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]