3 ms·

> Have you tried? Then: > Then run [...] Then try [...] I believe that last time I tried, systemd had different semantics (no mask/unmask, etc), but memory m

> Have you tried? Then: > Then run [...] Then try [...] I believe that last time I tried, systemd had different semantics (no mask/unmask, etc), but memory might fail me here. Thing is, I don't want to do any of those things. It is not looking healthy to me that a simple unix instance needs dancing around to execute /etc/rc.local. The only solution that looks sane to me is "if /etc/rc.local is present and executable - run it". Yeah, I can understand the security implications of that. > but nothing stops you from also running a cron For now. Apple already deprecated and banned cron from running on macOS instances in favor of their absolutely batshit insane launchd (which was the inspiration for systemd, hence the inherited brain damage). Before long Ubuntu will ship with no cron installed and then just a bit later it won't even be available in packages. Not even as a rust rewrite.

vidarh 1y ago
>> Then: Only if you're running a distro that lacks basic defaults from Systemd. Are you a distro like that? Have you tried just creating /etc/rc.local and seen if it gets executed? It's not systemd's fault if your distro ships with a broken systemd install. > "if /etc/rc.local is present and executable - run it". Yeah, I can understand the security implications of that. That is indeed what happens if you're on a distro with a non-broken systemd install. > Before long Ubuntu will ship with no cron installed and then just a bit later it won't even be available in packages. Not even as a rust rewrite. Then don't use Ubuntu. Still not systemd's fault.
- egorfine 1y ago
  > It's not systemd's fault if your distro ships with a broken systemd install Technically yes. Realistically systemd fosters insane decisions like ssh socket activation or killing of cron by providing features. Useless, unnecessary, unwanted, unrequested features that solves no real problems. Wait until they start from scratch by rewriting everything in Rust. This absolutely will happen one day.
  - vidarh 1y ago
    We're never going to agree on this. I have plenty of issues with systemd, but as I've shown you, the rc.local support you claimed isn't there, is in fact there, and doesn't require you to do anything, and then the goal posts moved to pure fear over features you don't like and the hypothetical removal of things they have no control over.

vidarh 1y ago

>> Then: Only if you're running a distro that lacks basic defaults from Systemd. Are you a distro like that? Have you tried just creating /etc/rc.local and seen if it gets executed? It's not systemd's fault if your distro ships with a broken systemd install. > "if /etc/rc.local is present and executable - run it". Yeah, I can understand the security implications of that. That is indeed what happens if you're on a distro with a non-broken systemd install. > Before long Ubuntu will ship with no cron installed and then just a bit later it won't even be available in packages. Not even as a rust rewrite. Then don't use Ubuntu. Still not systemd's fault.

egorfine 1y ago
> It's not systemd's fault if your distro ships with a broken systemd install Technically yes. Realistically systemd fosters insane decisions like ssh socket activation or killing of cron by providing features. Useless, unnecessary, unwanted, unrequested features that solves no real problems. Wait until they start from scratch by rewriting everything in Rust. This absolutely will happen one day.
- vidarh 1y ago
  We're never going to agree on this. I have plenty of issues with systemd, but as I've shown you, the rc.local support you claimed isn't there, is in fact there, and doesn't require you to do anything, and then the goal posts moved to pure fear over features you don't like and the hypothetical removal of things they have no control over.