On Sun, May 8, 2011 at 3:25 PM, roberth <rob...@openbsd.pap.st> wrote:
> Uhum. Sure that's a way to approach this. > That's the supported way. With that ammount of "support" required. > Fine with that. I usually build the new kernel, major utilities that require the new kernel as per http://openbsd.org/faq/current.html and http://openbsd.org/upgrade*.html. Then reboot to the new kernel, and build userland. I assume the machine is out of production until it's done. > On the otherhand, i have been running -current for years and never have > had any problem with building source with the previouse kernel (without > reboot) that i can remember. The occasional problem exists. Mostly due to a kernel call after a library is installed before the userland is upgraded. > Concerning remote-updates, "from source" will run into more problems > than "from a known good set of tarballs". That's simple statistics, > because of how many binarys are involved. > (remote console access helps, but still might mess up your sla.) I always build release from an already upgraded master build server, so there's no potentially off binaries being distributed. jb
