Why the Linux hate boner? (From a first time FreeBSD user) reddit / BSD ---------------------------------------------------------------------- demonpotatojacob · 2020-05-13 23:45 I recently switched from Ubuntu Linux to FreeBSD because I had wanted to try a BSD system but never got around to it until now. One thing I've noticed on this subreddit is that a lot of people here seem to have a hate boner for Linux. Why is that? Linux is far from perfect but BSD systems are just as flawed in my eyes. Nothing is perfect, everything has flaws. EDIT: just in case it comes across as an attack, the title is that because I couldn't think of anything else. ---------------------------------------------------------------------- nahnah2017 · 2020-05-13 23:49 At one time, decades ago, we thought of Linux as a kissing cousin. We often helped each other on mailings lists, IRC and forums. But then Linux ventured off on its own path, straying from the Unix philosophy and the science of computing, and thumbing their nose at other systems including BSD. Then it created incompatible systems, incompatible software, made desktop systems and competing against Windows a driving force, etc. In professional areas, you won't find the "hate" as much as annoyance at times. We generally get along with Linux professionals who often join--or wish they could join--the BSD side of things. ---------------------------------------------------------------------- demonpotatojacob · 2020-05-13 23:51 Some Linux systems (such as Void and Slackware) still adhere to Unix philosophies. Yeah that Windows part is true and sad but unfortunately to survive you often need to pander to the lowest common denominator, in this case being Windows users who have nerdy relatives who force them to use something else but don't want them confused because they're out of the loop. ---------------------------------------------------------------------- nahnah2017 · 2020-05-13 23:53 You can find a few of anything. ---------------------------------------------------------------------- demonpotatojacob · 2020-05-13 23:55 Also, thanks for being civil. On the Internet that's a rare site nowadays . EDIT:sight ---------------------------------------------------------------------- Ignorad · 2020-05-13 23:57 Probably depends on the person, but most people wind up with one thing because the other thing annoyed or frustrated them. So some people get pissed at Windows and switch to Linux and become Win-haters. Others dump some brand of Linux for bsd. Others use whatever the best tool for the job is. I'm typing this on a macbook pro, my desktop at work is a beefy HP running Server 2019 and MobaXterm to connect to my production OpenBSD virtual machines and a RDM to connect to all the Win servers I manage. ---------------------------------------------------------------------- ryze_cotch · 2020-05-14 00:27 They are jealous haters. Linux unlike FreeBSD(istro) is a massive success. ---------------------------------------------------------------------- bsdlinuxnerd · 2020-05-14 01:06 BSD hatred from Linux desktop users is even worse. They think BSD is joke and are mad because they had a bad experience when they tried it years ago. The problem is, a lot desktop Linux users are kinda clueless that unix-like OSes are not always developed with the desktop user in mind. There are more use cases for these systems and codebases than a desktop home PC, and it causes an ingorant, uneccessary bias. Example, a person on r/unixporn once told me that OpenBSD was garbage because he couldn't develop Android apps on it. ---------------------------------------------------------------------- nahnah2017 · 2020-05-14 01:06 >Also, thanks for being civil. On the Internet that's a rare site nowadays. "Sight" you twit. ---------------------------------------------------------------------- minus_minus · 2020-05-14 01:06 Maybe I'm getting it wrong, but I feel like it wasn't so much the Linux community as the corporations that co-opted Linux to compete against Microsoft and other Unixes. There's a lot of huge names backing open-source projects up and down the stack these days and I don't think they would bother if the code they were working had a more liberal license. ---------------------------------------------------------------------- minus_minus · 2020-05-14 01:08 Please see Apple's choice of code to base their operating system off of before you say things like this. ---------------------------------------------------------------------- demonpotatojacob · 2020-05-14 01:10 Sorry. ---------------------------------------------------------------------- demonpotatojacob · 2020-05-14 01:13 Oh. That's not something I've seen yet, but that's a pretty shit reason to discredit OpenBSD. ---------------------------------------------------------------------- nahnah2017 · 2020-05-14 01:24 And Netflix. And Whatsapp. And Groupon. And Sony. And ... ---------------------------------------------------------------------- atoponce · 2020-05-14 01:27 Most of the fanboyism happens early in the discovery of a new system. People begin evangelizing it, which means "selling" it. They become emotionally attached to it, and feel attacked when people don't share the same viewpoint. It's not unique to BSD. You'll see Windows hate from Linux users, Linux hate from Windows users, Linux hate from Solaris users, et cetera, et cetera, et cetera. Back in the '80s, there were Amiga versus Commodore 64 flame wars. In the 90s, there was a brief, but rabid fight over BeOS versus Macintosh. Do a web search for the Linux Haters Blog, a blog series of Windows fanboys who hate Linux, or search for the Unix Haters Handbook. Minix users weren't happy Linus created Linux in 1991, and Andrew Tanenbaum, creator of Minix, criticized Linux over his choice of a monolithic kernel instead of a microkernel. I could go on. BSD versus System V R4, NetBSD versus OpenBSD, Android versus iOS, ad infinitum. So long as people have opinions, have invested time and effort into their opinion, they'll defend their choice, even if it means irrational bickering on social media. For the record, I was introduced to Unix through Solaris 7, installed NetBSD on the system when I couldn't upgrade to Solaris 8, and am an Ubuntu, Debian, and CentOS system administrator, with (expired) RHCT & RHCE certs. I'm running an unactivated Windows 10 VM on a Debian Linux host on my laptop. I do a decent amount of development on an OpenBSD server, and I carry my wife's MacBook around with me when on the road sometimes. ---------------------------------------------------------------------- shyouko · 2020-05-14 01:28 Apple's choice is mainly license concern tbh, you may call it successful licensing model? ---------------------------------------------------------------------- flazz · 2020-05-14 01:56 They can try Apple’s BSD ---------------------------------------------------------------------- minus_minus · 2020-05-14 02:45 They use some Apache too. https://github.com/apple?tab=repositories ---------------------------------------------------------------------- shyouko · 2020-05-14 02:46 CDDL too. Anyway, they are not fond of GPL. ---------------------------------------------------------------------- minus_minus · 2020-05-14 02:55 They’ll use GPL too, and just about anything else. https://opensource.apple.com/release/macos-10153.html ---------------------------------------------------------------------- shyouko · 2020-05-14 02:58 I didn't say they don't, they are just not fond of contributing code to GPLv3 licensed project. ---------------------------------------------------------------------- [deleted] · 2020-05-14 03:40 Welcome to BSD! I personally don't hate Linux. Like the BSDs, the Linux kernel has been rock solid in comparison to the alternative. I know that some of us just don't like how **BIG** a Linux distribution has become - with all the fancy things from systemd. Also, I think it's the sharing mandate within the GNU GPL, which is the only way the license can guarantee the freedom to share changes. I get it. Like you said though - It's far from perfect, just like BSD. But these tiny imperfections only give us something to work on together for the betterment of technology for all of us. ---------------------------------------------------------------------- stealer0517 · 2020-05-14 05:11 Don't forget the arguments over aspects inside said OS. Ubuntu vs Debian, SysVinit vs Systemd, various desktop environments. People will pick some really weird things to latch onto and can end up pushing people away because of it. ---------------------------------------------------------------------- tele-caster-blast3r · 2020-05-14 07:36 Sounds like a fairly balanced diet ---------------------------------------------------------------------- mwgkgk · 2020-05-14 08:46 As a consolation, setting up an Android dev environment is a resource- and patience-intensive endeavour under any system ---------------------------------------------------------------------- Xerxero · 2020-05-14 12:46 Wanna checkout the phoronix comments on BSD news ---------------------------------------------------------------------- alx82 · 2020-05-14 17:00 What do you mean by 'Linux'? Are you speaking about the kernel? A specific random distro? What I dislike about the Linux kernel, is the constant kpi breakage... ---------------------------------------------------------------------- [deleted] · 2020-05-14 17:00 Would be using a *BSD permanently if one of them could A catch up and support the 5700xt and B do steam stuff and play games. Untill then I patently wait and love both linux and the bsd's. I say that as someone who got terminally sick of windows 10 and who is relatively new still. ---------------------------------------------------------------------- ahandle · 2020-05-14 18:36 TBF, the Amiga users are still at it. ---------------------------------------------------------------------- iroflmaowtf · 2020-05-14 18:45 > A specific random distro? shots fired! ---------------------------------------------------------------------- iroflmaowtf · 2020-05-14 18:47 > Ubuntu vs Debian we all know which is better . . . debian \*wink\* ---------------------------------------------------------------------- crocflamingo · 2020-05-14 19:42 I don't hate Linux, I mostly use Linux. Freebsd just works better in some cases. ---------------------------------------------------------------------- moboforro · 2020-05-14 19:56 As a longtime linux and unix user I got triggered a bit here. The Unix philosophy is like everyone's granny's apple cake recipe. Each one thinks they are the unix philosophy, hence there is no such thing. ---------------------------------------------------------------------- passthejoe · 2020-05-14 21:06 One thing now about BSD is that it definitely doesn't have systemd, so that is a big difference. The other is that a given laptop, desktop, server, appliance, etc., doesn't have to do absolutely everything. If your development (or other) workflow is supported by a BSD, you can set up a machine to do it. I don't need Netflix on my development laptop. I have a soft spot for OpenBSD, and it's a nice system for a developer or writer. ---------------------------------------------------------------------- Tabsels · 2020-05-14 21:25 > we all know which is better The one with `apt`, right? ---------------------------------------------------------------------- nahnah2017 · 2020-05-14 21:29 So, if it weren't for games, you wouldn't even own a computer, amiright? ---------------------------------------------------------------------- [deleted] · 2020-05-14 21:30 I mean I do browsing too but mainly I game ---------------------------------------------------------------------- nahnah2017 · 2020-05-14 21:34 [The UNIX Philosophy](https://en.wikipedia.org/wiki/Unix_philosophy#Origin) >The Unix philosophy is documented by Doug McIlroy\[1\] in the Bell System Technical Journal from 1978: ---------------------------------------------------------------------- qci · 2020-05-14 21:58 There is no hate for Linux. Most BSD users know much about Linux. It's probably more than the other way around. I'm also happy to try Linux now and then, but it got more and more awkward. Earlier I stayed on various Linux distros for years before returning to FreeBSD, now I cannot bear Linux for more than two weeks. I totally gave up, because I cannot find an adequate distribution anymore. Last time I wanted to try Void, but the founder seems to have quit... Great!! ---------------------------------------------------------------------- FUZxxl · 2020-05-14 23:13 I don't hate Linux. I just find it poorly designed, disorganised, and annoying to use. I switched to FreeBSD because I didn't want to have to deal with systemd (I do have a hate boner for that though). ---------------------------------------------------------------------- eredengrin · 2020-05-15 03:24 Void community picked up where the founder left off, it's still going just fine (well, *was* going just fine until the founder came back and then eventually started stirring up some more drama, but that also seems to have quieted down last I checked). ---------------------------------------------------------------------- moboforro · 2020-05-15 06:48 Last time I tried FreeBSD on my laptop I was shocked how far behind linux it is. Things that are normal requirements such as "suspend" are still a major pain in the ass for FreeBSD. ---------------------------------------------------------------------- iroflmaowtf · 2020-05-15 09:23 LMAO! You got me ---------------------------------------------------------------------- zZGz · 2020-05-15 16:48 I think people just gravitate towards the most obscure software online because if less people know about it the less they can get bullied for it. ---------------------------------------------------------------------- usr91 · 2020-05-18 12:40 > There is no hate for Linux. Most BSD users know much about Linux. It's probably more than the other way around. No, that's not really true, and the systemd-related discussion is proving it. Most of the BSD people you're talking about doesn't even know how the OS they choose is actually working. Operating Systems are a complex matter and most people are just too incompetent to prove themselves able to understand them. ---------------------------------------------------------------------- qci · 2020-05-18 17:18 Just because some people dislike design choices like systemd doesn't mean they hate Linux overall. Some Linux core devs don't find nice words about it. Linus even tends to avoid the topic and finds the systemd devs have awful attitudes towards compatibility. BSD users mostly like to have simple systems, which systemd is not. You don't need to understand an operating system to be a user. ---------------------------------------------------------------------- usr91 · 2020-05-18 17:39 And what is the bad design choice behind systemd? Is having an integrated userland tools for a specific kernel so bad? I'm sorry, but isn't this what BSDs did from the prime time? Sorry but, I didn't know you could use the FreeBSD userland on top of the OpenBSD kernel or viceversa. I didn't know you could use a FreeBSD-current userland on top of a FreeBSD-RELEASE kernel (technically speaking you can, but it's a not a recommended practice). Having kernel and userland tightly integrated each other is one of the selling point that BSD users always claimed against Linux. And now that Linux has its own one, now it become a bad thing because "being free to replace components is better!!", despite NO ONE could replace critical parts of their OS since it would be called a fork of the project and it would be a burden to maintain it. I'm sorry but I'm seeing a very childish attitude around this tools. Did you replace your INIT or claiming that developers should let you choose it before the appearance of systemd? I don't think so. Also, systemd is not a simple system, you say? Are you sure? What did it of not so simple? Its configurations are plain text and they are in INI syntax, that it's a easily parsable structured format. Also is the *standard* format for Freedesktop projects. And it uses such format for *everything*, be them configurations or UNITs (services, mountpoints, timers, targets etc.). I'd like you to remember that you guys in FreeBSD created and are using the UCL format for configurations, that is: - not standard - not easily parsable from a shell (JSON-like syntax for OS configs? And yet you're talking bad of systemd! Seriously?) - not used across the OS but only on few recently developed components. And the last point is the worst of all. You developed a configuration syntax and yet FreeBSD is still using N-bazillions of different syntaxes for every different component of the OS. Truly a good engineering, isn't it? > You don't need to understand an operating system to be a user. No, but you need to be competent enough to judge a design of a piece of software. And majority of people are not. People are complaining about systemd because the tool that they learned years ago is slowly changing. It doesn't matter if it is changing for the goods (like systemd is doing) or the bads. They are just complaining because they still want to use their '70s-era workflow. Grow a bit guys. *EVERY* operating system is going to evolve, because the world around you is not the same as 40 or 50 years ago. ---------------------------------------------------------------------- qci · 2020-05-18 18:09 We have been talking about Linux first of all. You don't need to defend your preferences with systemd. And I don't need to defend any "tightly integrated userland tools" in BSD systems. Next time you try to integrate BSD user tools in Linux, you can tell me how hard it is in combination with systemd and how it was with sysvinit. And you can of course try to integrate systemd in FreeBSD and you'll perhaps see what I mean. I don't really need to configure much for services except rc.conf. And things like packet filters have their own syntax, because it's more efficient for networking. And startup scripts are scripts. Why? Because I can insert a printf or other things where ever I want to enhance the behavior. Try to output internal states or extend parts of systemd units that show undesired behavior or you like to see working differently. Like for example those weird hanging bouncing asterisks. Try to interrupt this. And just to get an impression how buggy systemd is, search for "systemd bug". The results are horrifying. Maybe FreeBSD gets its own init replacement. It could happen, but it will probably be a portable product and you might see it on other BSDs, too, one day. And, guess what, I don't need to be a fan of this, either. It's still *my own preference* what I like and what not. ---------------------------------------------------------------------- usr91 · 2020-05-18 18:44 > Next time you try to integrate BSD user tools in Linux, you can tell me how hard it is in combination with systemd and how it was with sysvinit. It's hard in the same way as the FreeBSD userland is tightly integrated with the FreeBSD kernel and it would be not functional for the most parts. And if you don't believe me, just ask that to the Debian GNU/kFreeBSD developers that struggled for *years* to integrate a FreeBSD kernel with a GNU userland. And note that the GNU userland, despite it sucks, is much more OS agnostic than FreeBSD's. And yet the OS was so full of bugs that a lot of their repository was even failing when it was compiling. The only BSD userland you could port with much less effort would be NetBSD's, as the developers wants everything to be as much portable as possibile. Let me repeat some concept: it is not even recommended using a FreeBSD-current userland on top of a RELEASE kernel, because of the possible incompatibilities. So how can you blame systemd for this? Also, since when INITs are portable? INIT is mostly an OS-dependent feature. And it was *always* be like this. > I don't really need to configure much for services except rc.conf But you are talking from a user point of view. And this is true for systemd as well. Or maybe are you trying to say that using a simple `systemctl enable ` is more difficult than editing `/etc/rc.conf`? How about talking from an engineer point of view, instead? Did you ever see a systemd UNIT definition? Are you trying to say that from a developer point of view writing five lines in an INI config file is more difficult than write a script shell, that is parsing functions from another default source file and that needs for you to write the logic of start, PID checking etc.? Seriously? Also, if your machine needs a custom configurations, how you are going to do it with INIT? Some scripts are using the *flags* directive, but it is not enough sometimes. What about if you need for a service to wait for another one to start (think about a MariaDB that needs to wait for an iSCSI LUN to be seen from the OS), but only in one of your servers? Are you going to write such logic in rc.conf? Are your solutions only based on hacks? Because with systemd I can just write a drop-in file that is going to replace a particular part of the UNIT. Most of the time is a one-line file. > And things like packet filters have their own syntax, because it's more efficient for networking No, they have their own syntax because they were developed with a mentality that simply doesn't care for coherence. Everyone is develop its own small part and doesn't care for the rest. > Try to output internal states or extend parts of systemd units that show undesired behavior or you like to see working differently. So are you trying to debug a systemd UNIT behavior like a script and you're complaining that it doesn't works? Are you serious? Why don't you start learning how you have to manage it before try to using it? > And just to get an impression how buggy systemd is, search for "systemd bug". The results are horrifying. Yes, and think about it: it's the same when I try to search for "FreeBSD bugs". So what? Every software has bugs. Did you find one? Good, than just report it. > Maybe FreeBSD gets its own init replacement. It could happen, but it will probably be a portable product and you might see it on other BSDs, too, one day ROTFL Sure. You're developing in a so portable way that porting a driver from a BSD to another one is more painful than porting a Linux driver to a BSD kernel. HAMMERFS is one of the most notable example. Are you joking right? You're pretty much incompatible with each other even when we're talking about POSIX syscalls, that one could not have still implemented (see why openfortivpn can't compile on NetBSD and OpenBSD). > It's still my own preference what I like and what not. Sure but still you *HAVE* to stick with what the developers chose for you, or just fork the project and maintain it yourself. No one developer will let you choose. You're a user. INIT freedom just never existed. ---------------------------------------------------------------------- qci · 2020-05-18 19:37 Please don't mix up low-level stuff and also kernel parts (a filesystem) with generic userland. Also when people talk about tight integration they don't mean the integration all system tools, but specifically that init is simply init and does one thing well, while systemd is a huge monster that tries to do too many things as a single monolith and is disputable how well it handles all the things it does. If the only thing you can port is NetBSD, explain why Mac OS X, Nintendo Switch and Playstation 4 exist. Of course you cannot exchange kernels with differing ABIs freely, like RELEASE and CURRENT. It's a distribution, not merely a kernel. And if you think, BSDs are not downward compatible, then explain the COMPAT_[4-11] options in the GENERIC kernel. How is `service start/stop` any different than `systemctl` usage? I've seen a unit file definition and it's declarative, while rcng is declarative where it needs to be and allows to hack programmatically, if there is advanced stuff to do. And you don't even need to look at files, if you use `sysrc`. I have never had any problems with PID files. It's simple and it works fine. And dependencies are very easy to handle in rcng. If you need mysql start after filesystem, you just add "REQUIRE: filesystem" or something like this `rcorder` will tell you more how the dependencies are resolved. Complex systems like Bluetooth have been ported as kernel modules. Some kernel modules are not really very difficult to port because they share similar things. There is even the wireless drivers architecture ported (ndis) from Windows to Linux and BSDs. I wouldn't say exactly that Windows is very portable. As I said, I'm not forced to like what the distribution devs choose. I can decide that if I don't like a decision, I can swallow it down or choose to leave. I have done it multiple times already. I don't like many things about FreeBSD at the moment and I already consider switching. But it is none of the things you criticized above. ---------------------------------------------------------------------- usr91 · 2020-05-18 20:15 > Please don't mix up low-level stuff and also kernel parts (a filesystem) with generic userland. systemd *is* a low level stuff. It's not a generic stuff. For that part there is GNU. > that init is simply init and does one thing well, while systemd is a huge monster that tries to do too many things as a single monolith And yet you have: - systemd for services - journald for logs - networkd for networks - timedated for ntp and timezones - hostnamed for managing hostname (transients and statics) - nspawn and machinectl for managing machines (containers, VMs etc.) ... and so on where is the monolithic architecture you're talking about? There is one tool for every task you're going to do. Pretty UNIXy, isn't it? Or perhaps do you want to start a service by spawning a half of the userland just to obtain the same result? And please note that most of those components are optional, so you don't have to use them if you don't want to do so. > and is disputable how well it handles all the things it does. What is not doing so well? And how plain INIT is better than it? The only thing that is disputable is that is not working well. It is working, and it is doing it better than the alternatives. > If the only thing you can port is NetBSD, explain why Mac OS X, Nintendo Switch and Playstation 4 exist. Since when Mac OS X is just a FreeBSD on top of a different kernel? Mac OS X is OpenSTEP+FreeBSD+NetBSD combined together. It's a *different* operating system and it was heavily modified from Apple. Also, I never said you couldn't port anything but NetBSD. I said that if we're going to compare the userlands, NetBSD is the most easily portable one between the BSDs. > And if you think, BSDs are not downward compatible Never said that. *Me* was the one who said that was still technically possible. I just said a different thing. > How is service start/stop any different than sysctl usage? `sysctl` != `systemctl`. Also, there is no difference. In fact, that was a question I said to you in my post. > while rcng is declarative where it needs to be and allows to hack programmatically, if there is advanced stuff to do And it is just what systemd is trying not to do. "Hacking programmatically". An operating system should not be a bunch of hacks. Things should be configured, not hacked. > I have never had any problems with PID files. It's simple and it works fine. And it's also a fragile method for tracking processes. Especially when there is a double fork and software you're starting was not meant to trap it and remove its own PID file. And there are *many* softwares that behave like this. systemd can track them by forcing every UNIT to run attached to its own cgroup. > you just add "REQUIRE: filesystem" So are you saying that you can specify *what* mountpoint you have to wait at start and at shutdown? Because with systemd I can say "start this service when this mountpoint is up", and "shutdown it *before* that mountpoint will go down". And I can also specify in cascaded mode, for other software that depends on my unit. If so, and you can do easily (and without hacks), ok, then good for you. I don't feel animosity towards BSD. In fact, I'm a BSD user myself. Point is: Linux alternatives couldn't do it. And that's why we have systemd. > Complex systems like Bluetooth have been ported as kernel modules. [...] I wouldn't say exactly that Windows is very portable. Right, but still you're missing my point. The point is: you're complaining about the missing compatibility of systemd with non-Linux systems, despite it was born as a Linux suite for managing Linux systems just like in FreeBSD you're developing things for managing *yours* systems, and yet you're failing to port something (be it a driver or a simple software like openfortivpn) from a BSD to one another. > I can swallow it down or choose to leave. And this is *exactly* my point. You don't have the right to choose how your OS is engineered. You can just use it or not. That's why I said that there is NO init freedom. > But it is none of the things you criticized above. You know what is funny about every post of this discussion? I didn't criticize FreeBSD or other BSD OSes in any of my posts. I'm just fed up of all of this Linux or systemd shitting, spreaded by people who DON'T KNOW how it's working. ---------------------------------------------------------------------- qci · 2020-05-18 20:53 I don't usually change startup routines programmatically, but I can also see clearly what happens, if I take a look at the scripts. And I can work around it. I cannot workaround things with systemd like "shutdown waiting 30 minutes" (one of the first bugs when you search for "systemd bugs"). One word about PID files. They are in a persistent filesystem (/var), so you can even see across sudden reboots that a service failed uncleanly and needs attention. Then PID files don't need to be deleted, they need to be unlocked (lockf) to be considered unattached to any process. Since I am a ZFS user I unmount datasets with zfs command and not services. It shouldn't be allowed to unmount a filesystem that is actively used. It's been working like this since I know Unix-like systems. I have certain rights, I've successfully changed disputable behavior of a tool lately. The change gets committed soon. I don't have a problem with changes against my own ideas. I have a problem when other people tell me what I should think. I am not obligated to like systemd, but it is not my main concern, because I like Linux. >I'm just fed up of all of this Linux or systemd shitting, spreaded by people who DON'T KNOW how it's working. Do I need to know how it works? I thought I shouldn't look at it much as a user. You told me before I shouldn't look at init scripts to know how they work. You are a bit unfair here. I encountered 2 major boot failures with systemd: Introduction of systemd on Arch with race conditions and broken shutdown phase, and unclean unmounts on Debian that wrecked the filesystem recently. Both have been horrible to fix. And I have several screenshots of systemd failures and hangs. These are well known problems and I haven't seen comparable problems for ages on FreeBSD. I am agnostic in the choice of my operating system. I just want the applications to run. I just have to admit that I don't have much time to learn the details of new systems, so FreeBSD is my safe choice at the moment, because it causes zero troubles on operating system level. ---------------------------------------------------------------------- usr91 · 2020-05-18 21:15 > I cannot workaround things with systemd like "shutdown waiting 30 minutes" (one of the first bugs when you search for "systemd bugs"). As I said, this is a bug. And a bug should be reported. > they need to be unlocked (lockf) to be considered unattached to any process. You're technically right. But yet things are not always going to be like this. > It shouldn't be allowed to unmount a filesystem that is actively used. You don't know how many times I saw a DB crashing because the mount point just "disappeared" before it could stop itself. And I'm not talking about Linux servers. Everywhere I went I always saw DBAs launch their stop/start script just because of that reason. > I have certain rights, I've successfully changed disputable behavior of a tool lately. The change gets committed soon. Well, you're not being fair here, though. We're talking about users, not contributors. > Do I need to know how it works? Yes, if you want to judge its design. But this true is for everything. How can you judge something when you don't even know what are you talking about. Wouldn't it be called FUD? > You told me before I shouldn't look at init scripts to know how they work. You are a bit unfair here. Huh? Seriously, where I said such thing? I'm not trolling. > These are well known problems and I haven't seen comparable problems for ages on FreeBSD. Sure and I have one of my laptops that can't boot NetBSD because some random failures in a driver. Just like I saw a lot of RHEL 7 in production that run smoothly with systemd, and some of them were even hotpatched and never rebooted, with the systemd restarted while still running with `systemctl daemon-reexec`. As I said: every software has bugs. ---------------------------------------------------------------------- demonpotatojacob · 2020-10-07 23:20 >If the only thing you can port is NetBSD, explain why Mac OS X, Nintendo Switch and Playstation 4 exist. The PS4 uses an x86_64 processor, and the Switch uses a Tegra X1, which is ARM.