News for hackers. Stuff that matters.
Re:Show HN: Interactive systemd (a better way to work with s... by Ayesh on Saturday January 18, 2025 @09:27PM (#42753085)
I think the previous post mentions the `service` command, which has `service foo start` pattern.

I'm used to `service` command, so I have muscle memory which `systemd` breaks. The way `systemd` commands are laid out is better, it just messes with `service` command muscle memory.

Re:Show HN: Interactive systemd (a better way to work with s... by Mayzie on Saturday January 18, 2025 @10:16PM (#42753281)
It's been a decade at this point since the last big distro (and surrounding drama), Debian and Ubuntu following shortly after, moved to systemd.
Re:Show HN: Interactive systemd (a better way to work with s... by kijin on Sunday January 19, 2025 @02:28AM (#42754718)
Many distros still provide the `service` command, and don't print any warnings when you use it. At best, you might get an informational message that the equivalent systemd command is being called. There is no recommendation to call the systemd command directly, or any sign of the `service` command being deprecated any time soon. As a result, a lot of people are probably still relying on their muscle memory for the `service` command.
Re:Show HN: Interactive systemd (a better way to work with s... by cassianoleal on Sunday January 19, 2025 @05:21AM (#42755750)
I disagree that the way systemd is laid out is better.

With initV, issuing many command in sequence to the same service (enable, then start… stop then start… etc) is much quicker and easier as it’s “up-arrow, control-W, type new command. With the systemd option I either need to navigate one word to the left (or more depending on how the shell is configured wrt word separation) before I replace the command, or I need to delete both the command and the service name, and retype more.

It’s not a huge difference but small downgrades in ergonomics add up over time.

Re:Show HN: Interactive systemd (a better way to work with s... by egberts1 on Sunday January 19, 2025 @05:55AM (#42755928)
A huge typing pain.

A backward step in intuitive CLI usage.

We can be such a fuddy-duddy gray-beards.

Re:Show HN: Interactive systemd (a better way to work with s... by noumuon on Sunday January 19, 2025 @07:52AM (#42756555)
Aliases
Re:Show HN: Interactive systemd (a better way to work with s... by ecef9-8c0f-4374 on Sunday January 19, 2025 @10:16AM (#42757702)
duct tape
Re:Show HN: Interactive systemd (a better way to work with s... by egberts1 on Sunday January 19, 2025 @11:22AM (#42758390)
superglue
Re:Show HN: Interactive systemd (a better way to work with s... by BenjiWiebe on Sunday January 19, 2025 @08:50AM (#42756933)
Systemd does have 'restart' and 'enable --now' (which starts the service too).

Too bad it doesn't have a '--status 2' flag to show the status after two seconds too.

Re:Show HN: Interactive systemd (a better way to work with s... by dralley on Sunday January 19, 2025 @09:33AM (#42757318)
The systemd layout allows you to send the same command to multiple services, which is much more frequently useful than sending multiple commands to one service.
Re:Show HN: Interactive systemd (a better way to work with s... by cassianoleal on Tuesday January 21, 2025 @07:16AM (#42779287)
I can't remember the last time I had to send the same command to multiple services/units.

Normally when I'm doing things on the terminal, I do one thing at a time.