Sujet : Re: The Tragedy Of systemd
De : lars (at) *nospam* cleo.beagle-ears.com (Lars Poulsen)
Groupes : comp.os.linux.miscDate : 09. Oct 2024, 03:15:34
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <slrnvgbpq6.2n71m.lars@cleo.beagle-ears.com>
References : 1 2 3 4 5 6
User-Agent : slrn/1.0.3 (Linux)
On 2024-10-09, Phillip Frabott <
nntp@fulltermprivacy.com> wrote:
I'm not going to disagree. Systemd is complicated compared to InitV.
That being says, it always comes down to what people like and what works
for them.
The old stuff that we remember from our youth is easy for us; to the
degree that we remember what we did 40 years ago, we don't need to read
the man pages.
But redhat has funding from and obligations to groups that run large
datacenters that need to be managed from control desks based on
parameterized templates, and to support these needs, they built
something that works for that crowd.
I just wish they had some simple articles that I could find that makes
it easier for me to find where thy put the things I need to edit to make
my SMALL and SIMPLE system to work in MY environment.
Where is the per-network-device data that used to be in
/etc/sysconfig/network-scripts now? I know I am supposed to use
network-manager, but how does it play with ifconfig and "ip addr" and
"ip route"? The amount of documentation i need to read to do simple
things like making sure that my default route is correct on bootup is
daunting. So instead I put a startup file in /etc/rc.d/rc.local or
the root crontab "@reboot", even though I am sure there is a systemd
service definition I am supposed to make a simple edit to.