6 ms·
This article seem to reinforce that there is a split in thinking going on within the Linux community. On the one hand you have the traditional server/sysadmin
by digi_owl 11y ago
This article seem to reinforce that there is a split in thinking going on within the Linux community.
On the one hand you have the traditional server/sysadmin thinking about uptime and stability.
On the other hand you have the desktop/web thinking of rebooting often (or shutting down when not used, starting up before using) and being on the bleeding edge.
Another thing is that his mention about standard ways of doing something. I think that was why Freedesktop was set up in the first place.
But they seem to have gone massively off the rails almost from the outset, or it was simply too dominated by Gnome/Red Hat people (it was after all founded by once such person, Havoc Pennington) to really get things properly generic and modularized.
Asi write this i get to thinking about politics and thinktanks, and how they can make political decisions seem like they are scientifically based, when they really are rubberstamping preconceived political notions.
Similarly it may well be that Freedesktop exist to rubberstamp Red Hat/Gnome notions about Linux, by virtue of appearing to be a independent entity (similarly Gnome has its own foundation, but a large segment of its core developers are under Red Hat employ).
BTW, i seem to recall that while the BSD people had implemented most of the systemd APIs for various settings changes, they had run into a problem with logind.
Probably because logind depends heavily on PAM to get its job done, and PAM seems to fly in the face of basic unix-isms.
- zzalpha 11y agoOn the other hand you have the desktop/web thinking of rebooting often (or shutting down when not used, starting up before using) and being on the bleeding edge. I actually find this line of thinking baffling... I don't remember the last time I actively chose to shutdown/reboot voluntarily. Spending time optimizing the boot sequence strikes me as a total waste of effort. Modern computers support sleep and hibernate... why would anyone choose to reboot except to apply OS updates on certain operating systems that insist on a reboot? I would much rather focus on uptime stability and flawless sleep/hibernate so we can encourage people to never reboot unless they're forced to. That'd better serve phones, tablets, and other devices that share this infrastructure and need this capability, and it would cater to a public that is getting used to always-on, always-available technology.
- digi_owl 11y agoBest i can tell, it comes from the -sec community. This because a encrypted HDD in a laptop is at its safest when the laptop is turned fully off. At that point you have no keys in RAM or anything like that. Thus when you do not use your computer you turn it off, you do not sleep, you do not hibernate, you turn it off. The systemd devs have a thing about listening to the -sec community. You can see this in how while the Linux default is to treat namespace mounts at private, systemd mount them as shared unless told otherwise. This because the -sec people recommend it that way (allows a sysadmin to override mounts from outside the namespace, to avoid dos-ing apparently). Then again they also have a bit of theater in them. For example they accepted a patch to lock the computer if a HID devices was plugged in. But while the original patch did it on any device, they modified it so that it only happens on the device ids of known mouse wigglers used in police computer seizure kits.
- JoshTriplett 11y ago> Then again they also have a bit of theater in them. For example they accepted a patch to lock the computer if a HID devices was plugged in. But while the original patch did it on any device, they modified it so that it only happens on the device ids of known mouse wigglers used in police computer seizure kits. There was a series of two patches: one to logind to add a mechanism to tell all active user sessions to lock, and one to the udev rules provided with systemd to add a policy that plugging in a known mouse wiggler causes all active user sessions to lock. (It wouldn't make any sense to lock the screen when inserting any HID device.) Separately from that, logind also implements other policies for when to lock the screen, such as when closing a laptop lid without an external monitor connected.
- digi_owl 11y agoAnd how bloody hard it is to make the wiggler change the ID to look like any old mouse? Or one gets kitbashed out of a existing mouse? Or a new one comes to market that is not part of the IDs systemd have on file?
- pathsjs 11y ago
- noinsight 11y ago> On the one hand you have the traditional server/sysadmin > On the other hand you have the desktop/web I've understood that systemd is about modernizing the init/service system for modern usage scenarios. Gone are the days of the 80's when hardware was static and always plugged in, these days you have laptops that get docked and undocked, plugged and unplugged, connected to different networks etc. You have NICs and sound cards appearing and disappearing (USB NICs and DAC's), not to mention hard drives and USB drives... All of this needs to be properly supported on modern desktops and laptops and tablets. That's what systemd does.
- pdkl95 11y agoThat was all possible many years before systemd decided to pretend it invented hotplugging and xinetd.
- tremon 11y ago/sbin/systemd doesn't do any of that. Hotplugging devices was the domain of the kernel and udev (and consolekit for user access). The only reason "systemd" does this now is because they replaced consolekit (yay) and absorbed udev (boo). You either love or hate the ambiguity of terms like "systemd" and "modular", and the way it has been exploited to full extent during the systemd takeover. "Modern usage scenario's" should still include reliable boot and predictable behaviour. Systemd seems to have been developed under an assumption of infallibility, which makes recovering from a failing boot much harder. And a failing boot is much more common under systemd, because it has been designed to fail hard instead of fail safe. I'm running Debian on seven systems, and only one of those is running systemd. The others simply won't boot with it, or are headless and I won't risk bricking them (see fail hard above). The one system that I do run systemd on, I've had to disable the lvm and luks generators because they would fail hard, and I've had to compile it from git because Debian's shipped versions of networkd and resolved are broken. I agree with the article that systemd adoption was premature. Throughout the discussion, I got the impression that the decision was forced because of primarily the interests of desktop and service developers, with only a minor nod to system maintenance. imnsho, "systemd" the project was not ready for inclusion. Systemd as PID1 may have been ready, but systemd the project does not allow systemd to run as PID1 without the rest of the project.
- _yy 11y ago> On the one hand you have the traditional server/sysadmin thinking about uptime and stability. For sysadmins, boot times are getting increasingly more important. We're getting to the point where we can spin up a new VM in <100ms, thanks to (in part) systemd. This doesn't matter if you've got a few servers in a rack, but it does if you're spinning up thousands of VMs.
- digi_owl 11y agoAnd for every one that has 1000 VMs to wrangle, there are 1000+ that have a couple of servers in a rack.
- _yy 11y agoNice thing is - systemd works well for both.
- digi_owl 11y agoI have yet to see any evidence of that, as systemd seems liable to blow up at the oddest of moments (thus making it unsuitable for a long term server). It will rearrange the boot sequence on a whim, it will keel over if dbus does, it will fail to boot on the smallest of unit errors (to the point of providing no means of remote access no less). It may work in a cattle ranch, and it may work on someones laptop, but it damn sure does not work in a rack.