Sujet : Re: Distros specifically designed for children
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.os.linux.miscDate : 31. May 2025, 09:18:06
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <101edvu$112mr$2@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
User-Agent : Pan/0.162 (Pokrosvk)
On 31 May 2025 17:38:03 +1000, Computer Nerd Kev wrote:
I do find it hard to look up what all the fields in Systemd services
mean, and the commands to install/enable/inspect them.
It’s all in the man pages, which are also available online at
<
https://systemd.io/>
Like I say if I were editing lots of them regularly it would be
different ...
I don’t edit most of them regularly either. There are lots of
different *nix admin/development things I do, but not frequently
enough to have memorized them. You get used to knowing how and where
to look things up.
In my undergrad physics classes, all the exams were “open book” -- you
were allowed, nay, expected, to bring a copy of the textbook to the
exam. I treat my admin/development work the same way: there’s no shame
in continually looking up docs, particularly nowadays when everything
is available online.
Except you could have just done this on most sysvinit systems:
echo 'echo 50 > /sys/class/power_supply/BAT0/charge_control_end_threshold' >> /etc/rc.local
Fine if that’s the only thing in your rc.local, not so fine if you
start putting multiple things there. (Just another aspect of the
hodgepodge of bits and pieces that make up sysvinit, that have trouble
scaling to more complex real-world uses.)
Or the same in Systemd if you have a service that runs
/etc/rc.local. Or maybe that would be sacrilege? Anyway, each to his
own.
Yes, there is such a service -- part of the sysvinit support, for now.