Openbsd | HardenedBSD

Caring more about license than code quality is retarded. I GPL all my shit but that doesn't mean I'm going to run shit software just because of the license they're using.

Nevermind, retarded kernel panics on both that I don't feel like fixing.
I'll just install gentoo on this box. Developers need to step their game up and port their shit to legacy hardware if they ever want actual users.

What are you mean by "legacy"? You are running something older then VAX? DEC Alpha?

It is your own responsibility to port their shit to legacy hardware. It is not the developer's responsibility to work for you.

Not sure what he is talking about legacy hardware. OBSD will run on a fucking 486DX. Most likely he fucked up his "dual" boot and the panic is from not finding root.

OBSD is not kind to retards or casuals.

Do not dual boot unless you understand what you're doing.
Dual booting is hard, you're much better off testing in a VM or just installing to a separate HDD and booting via the BIOS Boot menu prompt.

Are you suuuuuure it's the legacy hardware?

Dual booting isn't hard if you read to website faq and man pages. OpenBSD doesn't provide a boot manager, so you have to use another one, like grub or whatever. But it's better the first time if you just install the OS on its own disk. Once you're familiar with the booting process and how the pieces fit together, dual-booting is easy.

Not so easy when you can't be bothered to RTFM like OP.

Booting into the live medium causes a kernel panic on my machine, I don't feel like sealing with it more than that. Dell Demension 9150.

Here's the panic if you want to figure it out.

panic: lock "msgbuf" 0xfffff8013fffffe0 already initialized
Kbd: stack backtrace:
#0 0xffffffff80a5b877 at ??+0
#1 0xffffffff80a1d556 at ??+0
#2 0xffffffff80a1d3c6 at ??+0
#3 0xffffffff80a5cab8 at ??+0
#4 0xffffffff80a01280 at ??+0
#5 0xffffffff80a62261 at ??+0
#6 0xffffffff80e57553 at ??+0
#7 0xffffffff802ff024 at ??+0

I guess I didn't read the fucking manual.
Suck it theo.