pin Ok to recap, based also on the other posts. (maybe i can write a tutorial for people coming from a rolling GNU/Linux distribution)
Basically differing from GNU/Linux, NetBSD splits (as other BSD do) in base system + utilities and packages.
Basically in BSD we have more flexibility in managing what to track.
NetBSD has three kind of major tracks for the base system: STABLE, RELEASE, CURRENT.
Stable are the "stable tracks" such as 7/8/9 and so on.
RELEASE versions are minor versions forked off STABLEs such as 8.1 or 9.1.
While CURRENT contains the most bleeding edge features that may break stuff.
In addition basically there are daily builds of STABLE,CURRENT (and probably also RELEASE? i don't know about RELEASE) hence to have a system as a sort of GNU/Linux rolling release we can update STABLE every week (more or less) that would update the base system.
And that's all for the base system.
For what concerns the packages, NetBSD uses pkgsrc, so basically here we can track quarterly / by version or -current.
In this case to have a sort of rolling OS for software utilities we just track -current.
Finally an acceptable approximation (although they are not comparable) of a sort of "rolling OS" a-la' arch would
be to update the base system every week or two with a STABLE daily + track pkgsrc -current.
Am I getting this right?
Can you correct me on things I got wrong.
P.S.:Again, I know that NetBSD is not comparable to Arch or any other distro. I am just trying to have my system reasonably updated while also keeping bleeding-edge software.