Probably because of the tendency of BSD threads to turn into really ugly flame fests.
Anyway, I’m somewhat surprised that it took so long to implement this, but then again when you install a server why would you install your os at the end of a disk ? Definately one for the dual boot enthousiasts this fix.
I was disappointed when I tried the *BSDs that I couldn’t try out OpenBSD because of this limitation. I have however installed it on my router since but it’s good to see this issue has finally been resolved.
But as mentioned – if OpenBSD is going to be on a machine it should have the respect it deserves and be the ONLY OS on the machine
Finally, this issue really prevented many people from installing openbsd on their machines.
Funny how a friend of mine got this problem today. It’s indeed a long outstanding known bug which is finally fixed. Finally.
Snapshots date is: 2004.01.29 04:56:00
Along with a PF bug fixed which existed a few days in current, i guess this also includes above patch, since they were made only a few hours ago.
Probably because of the tendency of BSD threads to turn into really ugly flame fests.
Anyway, I’m somewhat surprised that it took so long to implement this, but then again when you install a server why would you install your os at the end of a disk ? Definately one for the dual boot enthousiasts this fix.
I was disappointed when I tried the *BSDs that I couldn’t try out OpenBSD because of this limitation. I have however installed it on my router since but it’s good to see this issue has finally been resolved.
But as mentioned – if OpenBSD is going to be on a machine it should have the respect it deserves and be the ONLY OS on the machine
“if OpenBSD is going to be on a machine it should have the respect it deserves and be the ONLY OS on the machine”
Depends on what you’re gonna do with it.
Example: developing + Bochs from host OS ‘x’ to guest OS ‘y’ where either ‘x’ or ‘y’ can be OpenBSD. .. ….
Those OpenBSD guys are really ahead of their time.
Go Theo!