Linux or FreeBSD?

Linux or FreeBSD?

I have decided to free myself from the Microsoft Botnet, it's taking away user control as well. Windows isn't comfy any more.

I'm hearing good things about BSD over Linux. Which one is more reliable?

Other urls found in this thread:

news.ycombinator.com/item?id=13587531
github.com/systemd/systemd/pull/2500#issuecomment-178071901
youtube.com/watch?v=oC5D9fenQBs
twitter.com/AnonBabble

There is no best.
Choose what suits you.

I recommend Devuan. I used to think that the hatred of systemd was autistic, but it does too much and could eventually be used to do malicious things. It goes too far beyond an init system, and just ate udev. It's an ever-hungry beast. Debian based distros are stable and have the most commonly used software available. It's easy to use too. Pick Cinnamon as the DE. It just works and it looks decent.

>just ate udev.
how?

By opening its wide jaws and sucking it in.
news.ycombinator.com/item?id=13587531
github.com/systemd/systemd/pull/2500#issuecomment-178071901

windows

Not any more, thank you

BSD is probably more reliable, but I'd say it's close.

Maybe you should ask which one supports the applications and hardware you want to use. BSD has shit support for hardware.

I agree with this person:
But I personally prefer OpenBSD.

Linux has the best hardware and software support
BSD is honestly very very lacking in both of those

you'll be back anyways unless you go macOS
enjoy your time away!

off-topic but who the fuck is that neckbeard in the bottom right? did microsoft really set up a tablet on a fucking easle?

this whole webpage is cringeworthy because of how desperately it tries to appeal to normies with "3d for everyone" instead of making software that people actually use instead of being forced to

Well if you want a deskop environment BSD is out.

If you want a server to go and never stop, Linux is out.

Pick your poison.

>Well if you want a deskop environment BSD is out.
That's not true, though. I've been using OpenBSD as my desktop for about a whole year now.

>Devuan
>still in Jessie beta
Might as well install Debian and change to Sid.

I'm sure you have. I didn't say you can't, but you wouldn't.

>If you want a server to go and never stop, Linux is out.
>implying CentOS ever goes out
Even Debian is great with that shit.

>If you want a server to go and never stop, Linux is out.

Funny because last I checked only Linux could patch without needing to restart services.

It's not hard, since it has all the same software as GNU/Linux, pretty much, if you want that GNU/Linux software. The userland is definitely better than the GNU userland, though.

BSD is better but has less drivers.

For a desktop, go with Linux.

This always comes up, X lacks drivers. How to I learn to write drivers? can they be 'ported' between FOSS OSs? Has anyone here ever written a *nix driver?

To an extent, they can be ported. It depends on how well the original driver was written.

Probably not everyone has baby duck syndrome, retard

Install TrueOS

youtube.com/watch?v=oC5D9fenQBs

Kek. Install SmartOs

Reliable for what?

What do you actually need it to do, and what hardware do you need it to run on?

macOS is the only good OS nowadays. Linux is dying and Windows is Windows.

Stop shilling Mac OS X, idiot.

Stallman is a great man, but he lives in a different world. You don't have the powers he has. It's time you give in to the machine.

Besides, you don't hate your refrigerator because you can't replace the cooling coils with your own shitty ones you made in your garage.

>Besides, you don't hate your refrigerator because you can't replace the cooling coils with your own shitty ones you made in your garage.
Actually, you're wrong. I hate closed-source hardware.

Try both, but first linux because it has bigger community. But I can be mistaken, I've never used bsd

Do you mod your computer monitor and tv remote too? You're pretty dumb user, but you sound young so we'll let it slide for now.

the image looks good. sadly i use windows 7

>justifying closed-source: the post
You obviously don't care about technology.

That's weird. It's almost like technology and freedom (philosophy) are two distinct things. I'm just pointing out your hypocrisy.

>technology and freedom (philosophy) are two distinct things
Since when? Technology used to be about empowering people to do things.

Did you fell for the botnet meme? I'm sorry man.

Well, it hasn't empowered you to realize technology and philosophy are distinct disciplines, so I suppose it has failed in that regard.

You're not being effective enough to earn rupees. Sorry.

You are wrong, making technology is artistic autism, it's awful without freedom because people will have to repeat each other's work, many won't be able even to start implementing their idea because of lack of money. Non free technology isn't real technology because if the company goes bankrupt, everything they've done disappeares.

Now the stinky Linux virgin is failing to form coherent thoughts. Technology cannot save you my friend, no matter which OS you choose.

>not using GNU/Hurd

Does it work nicely?

>Linux is dying
>macOS good
It's MacOS that's dying, you sad person. Linux is gaining more and more momentum

>my laptop will disappear if Apple goes bankrupt

It will. If a single closed-source component dies, you won't be able to replace it.

The posibility to intel processor from your laptop will disappear if intel goes bankrupt. Same with all proprietary hardware. Osx will quickly become outdated and unusable (literaly disappear) if apple goes bankrupt.

posibility to make*

Nice try, shill.

>source: me

restistance is futile

assimulate to systemD

>BSD has shit support for hardware.

Most drivers Linux has are actually ported from *BSD.

The main exception is graphics, which drivers usually flow the opposite direction.

Try both, see what suits your usecase best.

FreeBSD has less support for hardware from various vendors, but has a respectable amount of FOSS drivers, can't do much about proprietary stuff. It has a large number of advanced technologies that are very stable, and research often happens on it, resulting in new and powerful concepts being developed on FreeBSD.

Linux on the other hand often gets support from proprietary vendors, and like FreeBSD, gets research done on it, but not nearly as much in terms of systems research. It's more user friendly, but not as stable. For servers I'd argue less user friendly, but that comes down to preference really. It's got games, which, while you can run them on FreeBSD, you'll spend a month getting 1 thing running, so it wins there.

This is just a short rundown of both systems. I recommend you inform yourself in more detail, try them out and see what you like most. You can always hop onto different irc channels and ask away.

, Whenever new hardware gets supported by the Linux kernel when it's published, an new version of DRM usually gets ported over to the BSDs quite soon, as there are always commiters working on that. The problem is that it stays in -CURRENT for a long time to get properly tested, then gets MFC'd into -STABLE (unless there are ABI changes), at which point you have to wait for a new -RELEASE to get cut, or track -STABLE. DRM-next (with Broadwell and Skylake support) is in -CURRENT on FreeBSD (and has been for a long time now), and OpenBSD has already integrated support for Broadwell but is missing Skylake.
All the BSDs impliment some form of ports which has +26000 entries for software that can be installed directly, and any POSIX compatible software that isn't badly written can run on the BSDs with little to no tweaking (especially with the Linux compat layer or a linux userland in a jail).

So yes, they can be ported, but you can't just get a commit bit yourself, you have to have your code vetted and sponsored first, before you've proven yourself. FreeBSD has a bunch of additional handbooks like Porters Handbook, and Developers Handbook.

Yeah, the "BSDs can't DE" is a meme.

Stallman has done NOTHING in his entire life. Emacs was simply a re-implementation of an existing product as open-source code, and the proprietary drivers for printers that inspired him to create GNU still run proprietary drivers all these years later.

Back when I did game, I would dual-boot to Windows - but since I've been using FreeBSD since 2001, I've kinda out-grown gaming - so I'm not really up-to-speed anymore, but I believe the biggest blocker for gaming on FreeBSD at least was that Valve implemented Steam with x86 rather than x86_64/AMD64.

>Most drivers on *BSD are actually ported based on documentation released for Linux.
Fix'd. Maybe FreeBSD got some driver and ZFS from opensolaris, but that shouldn't be news for anyone. GPLv2 and BSDwhatever isn't compatible, so code cannot be reused, not to mention the different kernel ABI.

BSD is the next wave. systemd brings all the problems of Windows to Linux. You will not escape systemd.

It's a simple thing to remove SystemD from Deb8. I bet they will make it a pain in the ass to strip it out of 9.

Fuck systemd and fuck Poettering.

>systemd brings all the problems of Windows to Linux

Finally i will have font rendering in the kernelspace? :^)
No one cares about systemd autismo rant.

...

>Stallman has done NOTHING in his entire life
He wrote GCC.

Why not both?

Spend one Saturday installing dual boot. Or, if you do virtualization, then install gentoo (or whatever) and virtualize BSD.

Come back and tell us how that worked out after three or four weeks using only those systems and not any windows or mac.

Also, next time: describe what the fuck you intend to use your system for. We are not fucking mind readers.

If the only thing you do is shitpoast on 4chinnz and masturbate to futa porn while texting your mom for more hot pockets, get a fucking Pi 3, install a minimalist linux and leave us the fuck alone.


> really getting sick of these helpless millenial faggots who think every single question is "either - or" and no question has context of any other question previous or future

How the God damned fuck do you children function on a day-to-day basis?

People who actually have to work with systemd for a living do.

Isn't it wonderful when your log files don't tell you jack shit because of how retarded systemd logging/service handling is? Don't you just have a grand time when you hear about systemd's latest security fuckup and know that your livelihood depends on that piece of shit software?

systemd has the same methodology issues Windows does. Piling more shit into a single program doesn't make up for its shortcomings.

It's GPL that's incompatible with CDDL, dofus. CDDL and BSD actually go together quite well.

The thing is, it's a really sad state of affairs that the majority of major linux distributions use the systemd suite now (yes, in theory you can get along just with systemd and nothing else, but none of them do). So what little choice you have is some ricers paradise where you can forget all about binaries. Nonetheless, the systemd is the cancer that is killing linux, and Poettering needs to fucking be unemployed, or he'll have single-handedly destroyed linux in a few years time (which was probably what he set out to do, since he doesn't like POSIX and wants Linux to be 1 OS, which it will be, under its ~benevolent~ Redhat leader).
Also, source on that image? In b4 whale.

Fucking hell, I can't imagine what pain it must be. Thank fuck the little sysadmining I do happens on FreeBSD, and I mostly stick to networks with Juniper.

>systemd is the cancer that is killing linux
Just gives me a good excuse to get BSD going.

It is a shame but Linux has been shit for a decade. To many cooks.

Nice bait, some retard can't read the Handbook and it's not his fault, it's FreeBSD's for not holding his micropenis.

Millennials are used to the didactic, they've been brainwashed even more effectively than boomers were.

It's up to Gen X to save humanity.

What, you need an excuse?
>a complete lack of systemd anywhere, that you don't have to work around
How's that?

It's always FreeBSDs fault when some newfag can't read the handbook or manpage, or doesn't act like an adult and be responsible for the system he's working with, instead of expecting it to handhold everything for him.
It's fucking easy to tell that these fuckers started out on Windows, because that's where they learned those bad habits, and they stick with them across all OS choices they make; it's the same reason why there are so many "Howtos" and "FAQs" for Linux, it's so these fuckers can just copy/paste instead of thinking.

>systemd is the cancer that is killing linux

This lasts forever. So?

No. Cancer either kills you, or you manage to kill it with various cancer therapies. Trust me, I got diagnosed with the fucking disease last year, and it's NOT been a cakewalk through surgery, radiation, and chemotherapy.

So let's drive some nails into the Linux coffin. Why even bother? I just got a T60 and it will run BSD.

Actually my analogy works quite well - at this point the systemd is a cancer that's metastasized into a systemd suite which doesn't just need surgery, it needs radiation and chemotherapy too.

Holy shit, it's rare that I come up with ideas this brilliant.

Holy crap...

Holy crap what?

>emacs was simply a re-implementation of an existing product as open-source code
Rewriting code is writing code.

is always the user's fault with you

1) Copy
2) Paste
3) Change variable names
4) Obfuscate code a tiny bit
5) ????
6) Profit, instantly become a god to angsty teenagers everywhere who thinks copyleft means the slightest thing to anyone.

Yes, it always is the users fault. You'd know this if you'd worked a day in your life in a place where Triple A is implemented and you're responsible for systems instead of just shitposting on Sup Forums while you suckle at the teet of society on the dole.

If you've never used either and want a drop-in replacement, don't use BSD, use some "beginner" distro like Xubuntu or Mint
If you've never used either and want/have the time to gradually learn everything there is to know about Unix-like operating systems, AND you are willing to not be able to do certain things until you figure out why they don't work (i.e. you're not an impatient, immature, whiny cunt and you don't have a job that requires specialized software, connecting to a Windows network in your office for shared drives/printers, etc.), AND you want to feel like the member of some super-exclusive smarter-than-everyone club, use BSD (or Slackware).
If the above but you don't care as much about being a member of said club, CentOS, Debian, or SuSE.

It's rare that I run into things that don't work, but when I do, it's nice that I'm paid to figure out why, and make it work - but that assumes you're not stuck in some shitty day-job where you're not paid to think.
Otherwise, you're not entirely wrong.

It was a copycat, but he have to rewritten it shortly after the first GNU emacs. Now the "original" is in the ebin.

I love my refrigerator because it doesn't restrict what food I can put it in, or magically make my food disappear or replace it different food when I'm not looking. And it doesn't cost twice as much as a refrigerator of comparable size and power.

Yes, but my point is that he wasn't involved in the first version, and he based his rewrite off another rewrite that was written almost a decade later than the first one.

As someone who started using Linux at a young age with no prior experience in a time where there were no wikis and very limited third-party package support and you had to write your XF86Config by hand and if you did something terribly wrong your monitor would explode, it took me a good 5 years before I was able to diagnose and solve most problems on my own, and I consider myself someone of average technical competence for this board.

Granted, in this day and age with much more hardware support, community support, automatic configuration, etc. it would probably take someone much less time to be able to solve problems themselves and even if they did not understand what they were doing it should be relatively simple to find solutions or support online, but if you're just starting out with any system that is not designed to hold your hand and do everything for you, there will be a period of adjustment when you have no idea what the fuck is going on.

Sure, but I started with FreeBSD back around the same time, and I had to learn just like you did. All I had was the FreeBSD Handbook (I ended up picking FreeBSD over Debian because of the FreeBSD Handbook, actually). The problem is that a lot of young people nowadays don't ever learn to troubleshoot, because they've been fostered up on systems that handhold them through everything, so when they try something else they either run into a wall or learn the bad habit of simply copy/pasting, since it's easier than actually thinking, and nobody tells them that doing this is wrong.

Mind you, young people aren't the only ones doing this, but they have the least excuse, since they've had computers from their childhood and have had the option to learn when their brains are best at learning.

You are a newbie

go with some ubuntu or linux mint

That's why I used all those conditionals about not being impatient, not being whiny, not needing immediate use of things that are even slightly complicated to set up, understanding what a learning process is, etc.
Personally I believe people who don't fit that description shouldn't even use "beginner" distros unless they have an IRL guru willing to solve problems for them because they will eventually run into problems and the only thing worse than not being able to do something is thinking that you are, because that's how you fuck up your system and start complaining about how horrible LInux/BSD is.

I couldn't agree more if I tried.