Which version of BSD should I try out as a beginner? I have basic

>>61530569
Could everybody please just install BSD please.
The sooner you find out for yourselves what utter shit it is, the sooner we can band together and track down and kill the unrelenting shitfuckker who keeps spamming /g/ with these fucking shill threads.

File: OpenBSD_Logo_-_Cartoon_Puffy_with_textual_logo_below.svg.png (184KB, 1200x781px) Image search: [Google]

184KB, 1200x781px

>>61530569
OpenBSD

>>61530616
>T. a raging faggot who eats cock on a daily basis

>>61530569
For what reason should anyone use netbsd or dragonfly bsd?

>>61530616
I thought it wasn't that bad. Needs more wifi drivers though desu.

>>61530616
>The sooner you find out for yourselves what utter shit it is, the sooner we can band together and track down and kill the unrelenting shitfuckker
So never?

File: 1497177778964.png (690KB, 1302x1336px) Image search: [Google]

690KB, 1302x1336px

>>61530616
This.
Except that I personally use OpenBSD on my laptop and fBSD current on my desktop, and I would probably die by BSD.

In all seriousness though, the novelty of various GNU/Linux distros isn't really applicable, because various BSD images are so radically different not only in the sense that they have totally different kernels, userland, & c. but also are starkly different philosophically, which is pretty much the reason why they forked in the first place.

You can harp on someone else's distro as a GNU/Linux user all you want, but, in the end, it's pretty much still GNU/Linux. In BSD, you don't have that freedom, because what you can do in one image may be incredibly different in another, just because of where a team's values are, and, for that reason, BSD communities are often vastly different image-to-image in contrast to distros.

Like, when are you ever going to use Dragonfly as an end user? Even in an enterprise context, HAMMER is unbelievably niche. Conversely, what corporate drone is going to use OpenBSD over Freenas or fBSD with such an archaic filesystem? That's the tradeoff of putting security first.

>>61533136
>openbsd

weren't these the retards that review each line of code and their hardware support is so ancient no one gives a fuck so they literally have to beg each year for funds just to keep their servers alive?

>>61530569
try giving GhostBSD a spin, it has a live cd and it's very easy installable

>>61533182
they don't have to beg anymore

they haven't had to for years

>>61533182
Yes. They are also the retards who develop for the same operating system that they're using, and are actually passionate enough about free software that they not only refrain from using nonfree software but actively criticize the GPL, which is much more than the FreeBSD goys can say.

>>61533264
Yeah, sure. Try getting FreeBSD to boot outside of a vm. I hate to state the obvious, but if no one's using FreeBSD for a desktop, then there's no incentive to maintain desktop packages. FreeBSD is the cancer of the BSD world. It's proof that a lenient stance on free software means your project is going to be overrun by millennial developers who are more than happy to take advantage of the merits of free software while chastising other, more valuable devs for not being politically correct--all the while keeping one foot in the proprietary cesspool known as macOS.

>>61530761
NetBSD has pretty good suspend/resume/overall hardware support. Pkgsrc is also very good.

Dragonfly for many of the same reasons you would use ZFS or BTRFS. It's actually not very practical, but the have a lot better support for the latest graphics/cpu's relative to FreeBSD.

File: oeuo.png (471KB, 745x745px) Image search: [Google]

471KB, 745x745px

>>61534204

It has UEFI support?

File: 1498003317208.png (203KB, 800x689px) Image search: [Google]

203KB, 800x689px

>>61530569
OpenBSD.

FreeBSD has already been infiltrated and sabotaged by the NSA.

>>61530569
OpenBSD is rock solid if it plays nice with your hardware. It's incredibly easy to set up and get running, but in my experience it's also a fairly slow desktop experience.

To be perfectly honest, I'd stick to GNU/Linux on the desktop and *BSD on servers. It seems like they're tailored better to those experiences respectively.