Nenhum_de_Nos wrote:

quoted text
> hail all,

>

> I use FreeBSD for a long time and now I'm changing my routers slowly

> to OpenBSD. I have one router running 4.2-current (or anything like

> this, uname shows 4.2 but motd shows 4.2-current. I confess this still

> confuses me) and I'm studying it to be confident enough to make it the

> one.

dmesg tells the story.  You are running 4.2-current.
> but my main question is, how to make obsd allways up to date, keeping

quoted text
> it bug free. mas from time to time there is security bugs found and so

> on.

an important question, most certainly.
> for what I saw in obsd web

quoted text
> site(http://www.openbsd.org/faq/faq5.html#Flavors), when 4.1 is

> released 3.9 is not suported aymore.

correct.
> my question is, how to keep up to date if putting a cdrom and boot for

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

>

> as a pf fan, and as i prefer to use pf in obsd itself, is there a way

> to do things this way in obsd ?

For updates to the latest patched -stable, just follow FAQ5's

instructions. Same thing...compile, reboot, done.
For upGRADING between versions, follow the upgrade guide.

   http://www.openbsd.org/faq/upgrade42.html

Upgrading to a new version by source is NOT supported, and often is

not possible for sane definitions of "possible".  Don't waste your

time trying.
The first time you do it, allow an hour from start to finish.

Second time, a LOT less.  With a moderately fast machine, you can

probably do it in about ten minutes, with only two reboots of complete

down-time.
Since you are running -current, you will have to stay with -current,

at least until 4.3.

Just untar a snapshot, look at

   http://www.openbsd.org/faq/current.html

make any adjustments needed, then reboot.  Look, no compiling! :)

(a little secret: Assuming no show-stoppers in current.html, I tend to

upgrade all my machines' /etc files at every release, then just untar

file sets to snapshots in between releases.  Granted, a very large

reason why I do this is to give me lots of machines to test the

upgradeXX.html process, but it often works fine between releases to

just ignore the /etc file changes.  This was not a recommendation, just

a "what I do that is wrong, but I get away with it" :)
Nick.