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.
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.
