• 0 Posts
  • 31 Comments
Joined 1 year ago
cake
Cake day: January 20th, 2024

help-circle

  • Problem is, nobody’s alternative solves all of the problems people wanted their init system to solve. sysvinit didn’t solve booting/service supervision well, so it’s hard to say it was really a UNIX philosophy solution, and it wasn’t even part of the OG Unix system but came over a decade later in 1981 with AT&T’s system iii (later included in system v, hence the name sysvinit). There’s nothing sysvinit does well. The most popular services and distributions had simply thrown away so many hours of time and effort bashing their heads against sysvinit’s limitations that they had managed to make them work, but that’s different from the system overall working well.

    Anyways, people don’t like Poettering, but he made inroads with systemd in large part because he actively took notes on what people wanted, and then delivered. He’s an unlikable prick, but he delivered a product it was hard for many projects to say no to. That’s why project after project adopted it. It solved problems that needed solving. This counts for more than adherence to an archaic design philosophy from the 70’s most people don’t follow anyways and which the predecessor wasn’t even a good exemplar of anyways.


  • init.d wasn’t really what you’d call an “init” “system.” It was shell + conventions about how to write shell scripts to manage each service. It effectively offloaded most of the work people wanted an init system/service supervisor to do onto developers that just needed to ship a system service. To be honest, it was insane. Templates/patterns/best practices emerged, but at the end of the day, init.d was just shell, and it caused tons of problems.

    The extra complexity of systemd is in exchange for dependency management, service supervision, tons of things that are important/desirable for sysadmins/developers today, but are all far outside the scope of init. I’d much rather cope with the extra complexity of systemd in exchange for being able to write an actual service definition file.


















  • Eh, there are limits. Utah has a pile of petty claims against the federal government including delusionally contesting ownership of federal lands. There’s a difference between having a narrow policy limiting the degree of law enforcement cooperation on one or two matters, and Utah passing a law that says “if we disagree with the feds on literally anything we can refuse to cooperate with them any time we feel like.” One is a matter of policy and discretion, the other actively flaunts federal supremacy. Utah doesn’t just get to decide it owns the national parks inside its state borders and order its employees to treat National Parks Service workers as trespassers, but it sure seems like this law is carefully crafted to create situations like that.

    This is also hot on the heels of Utah also passing another bill that flaunts federal policy as regards separation of church and state. They really want to pretend they never joined the Union or like there’s never been a conflict between states and the federal government before and like this is somehow new territory.

    Like the lawyer in the article said, this is what we’d call a whacko interpretation of how the Supremacy Clause works and is likely meant to appeal to the voters more than anything else.