1 http://www.tedunangst.com/flak/post/the-wiki-box-is-out-of-c...
"Check me out with CVS!"
For the most part that's true, but /etc/rc.local is run fairly late, so if you have a sufficiently-crazy setup you might have to edit /etc/rc.
For example, before softraid crypto was integrated into the bootloader I modified /etc/rc to prompt for the keyphrase before it tried to mount the disks.
I'm a basic novice when it comes to OpenBSD (But a huge fan), and that, in addition to discovering that you keep all the old versions of every library ever installed when upgrading, where two things that I had been taught - so I presume that the knowledge was universal.
It stopped for me after I closed the window in disgust.
Internet Jackass Day is bad enough on a fundamental level, but when your jackass behaviour gets in the way of people's actual tasks (and there's no way to say 'stop this BS'), you're not being funny.
[edit - it stops after a while]
Regarding: "The etc sets are now gone. All the sample /etc files are now included in the base set. This should make sysmerge must [sic] easier and faster in the future, since there will be many fewer conflicts to resolve. On the other hand, even rc and rc.conf are now overwritten, so it’s not possible to maintain local mods without additional work. This makes sense, though, since /etc/rc is as much a part of the base system as /sbin/init. You don’t want to be running a five year old edition."
I thought (and the manpages always indicated) that the rule was that /etc/rc and /etc/rc.conf were fair game, and that if you wanted to make changes that weren't overwritten by a system upgrade, to put them in /etc/rc.local and /etc/rc.conf.local. I'm unclear why this is considered a problem.