Welcome @sepruko ,
Yes, I use artix with Xfce. It is trouble-free for me. I dont use sound though.
Regards
Neville
1 Like
Not just Red Hat (which is now part of IBM) - but Canonical too - and - the Debian team / org…
SystemD is the defacto standard out there in enterprises… Those “shops” not running some Red Hat derived distro (Fedora is sorta/kinda “pre-RHEL” for beta-testing) - like Oracle, Amazon and Azure, will probably be running Ubuntu server, or a few rare “edge” cases with plain Debian (pretty much 100% SystemD from Stretch (9) onwards…
Even before Oracle bought out Sun Microsystems in 2009, Solaris UNIX was headed to something like SystemD - called “SMF” “Service Management Facility” - the defacto init system on Solaris 11… On Solaris 10 you could still do some things with SystemV init - but you needed to understand smf to get vendor support - with commands like “svcs list” or “svcadm”
Last time I looked at IBM’s own UNIX, AIX, 12-15 years ago - some of the init stuff was still kinda like on BSD with RC scripts - no idea if that’s still the case…
2 Likes
It can change quite rapidly.c Look at how quickly people adopt new phones.
I dont care what enterprise does, but I would like to see home computing do something more suitable.
What worries me is that systemd is starting to interfere with what developers can do with other parts of Linux.
2 Likes
Vast corporate entities move an order of magnitude more slowly than the “market”…
And I have hideous legacy “end of life” systems I still have to support running RHEL4 or 5 and cringe when I realise there’s no “service or systemctl” - just shonky /etc/rc.3/ start and kill scripts…
You probably never worked in mult-vendor multi-customer environments before…
“systemd” solved a problem…
I’ve worked on customer servers where some cowboy answer to init was write a shell script that didn’t need parameters (i.e. no “stop” or “start”) it just ran and they linked to it in /etc/init.d/ from rc3.d and had a start script - but - never bothered (because they were a cowboy) to write a kill script (or create a link to /etc/rc3,d/k23kill-It)…
SystemD did do some good things… but I agree on my home system it’s overkill…
But it’s so universal today - you can write an ansible playbook that can do the same thing - consistently - across a farm of 300 servers…
4 Likes
Yeah. CSIRO was diferent … very progressive … wanted the latest and best performing hardware and software… because numerical computing needed it.
All these corporate systems do is shuffle accounting data around … it is a trivial amount of work for a computer . The complications are all to do with access and security. No wonder they stick with something that works.
You are basically saying that systemd solved a problem by stopping idiots from doing half baked solutions with sysvinit. I can appreciate that. It does not stop us from moving on to something better. Both S6 and dinit are far better init systems than èither systemd or sysvinit.
2 Likes
I did a short term (months) contract for the Bureau of Meteorolgy in 2017- some stuff was legacy monolithic - but the UNIX team were actually “agile” (I hate that term - most corporates that spout that are anything but agile - they’re lethargically inclined to do the very least)…
One of the few commonwealth departments that offered Linux on the desktop - you could use an IT “sanctioned” RHEL desktop - which I did for the first fortnight - but got offered a beefy workstation with an NVidia GPU (not a gaming GPU - a Quaddro “workstation” GPU) running a fairly “bleeding edge” version of Fedora - it was great!
It was probably 'cause BoM have scientists… some of whom probably end up in IT… So much in OpenSource and Linux, has been done when scientists stopped “sciencing” and start ed “IT-ing” 
- in the 2010’s one of the key kernel developers was an anaesthetist at a Melbourne hospital…
I doubt the Commonwealth Dept of Finance, or the Tax Office, or CentreLink (mostly privatized and/or farmed out to corporate leaches like KPMG and PWC) would be so accomodating…
3 Likes
Including the original Unix developers at AT&T
I spent a lifetime flipflopping betwen science and computing.
4 Likes
and Tim Berners-Lee…
2 Likes
Mr Intrrnet !
1 Like
[How to geek article on systemd]( Why I'm sticking with systemd-based Linux distros )
3 Likes
The article is well written. This quote worries me
“There might be some concerns about the size of systemd or the supposed dominance of Linux development by Red Hat and its parent company, IBM.”
Also read some of the feedback at the end of the article.
But what you use personally is your free choice. You are doing no harm to anyone, whatever you choose.
2 Likes
of course Nev but… as some have mentioned in this topic (I being one) the sole reliance on systemd and removing other arrangements has impacted the way I have mounted and accessed SAMBA shares for years on the desktop.
I thought FOSS was all about choice - perhaps that was just a tad too naïve?
1 Like
- Unit files are a smoking pile of shit.
- Systemd is not modular.
- It depends on several libraries, which would be way too much on a bare-bones system.
- There is no specification – they could change anything in any way they like at any time, without notifying anyone.
- It integrates services which have nothing to do with init or process management.
Init ought to do one thing and do it well. Now systemd does a lot of things, none of which it does well.
2 Likes
Love your expert analysis and identification made me smile !
3 Likes
How do you know it is a systemd problem ?
Why not test it?
Why not try MX25 where you can have both systemd and sysvinit in one install, and switch between them . It would be easy to test it there.
It is . You are saying you cant choose SAMBA and systemd simultaneously.
That is a bug, not a restriction of choice.
You need to prove it and report it. It may get fixed if you are patient for another few years.
1 Like
Well said.
Can someone explain to me what are Unit Files? … do they belong to SAMBA or systemd? I know nothing about either, as you can see.
I avoid both by using NFS and dinit (or runit or sysvinit or openrc)
1 Like
Unit files are systemd’s answer to sane init scripts. A horrible, cludgy, extremely verbose, non-elegant solution.
You might find I’m slightly biased.
2 Likes
Hooray, someone can see thru all this systemd nonsense.
Have a look at a dinit service file … short, human readable, elegant.
eg
type = process
command = /usr/sbin/chronyd -d
depends-on = loginready
logfile = /var/log/chrony-dinit.log
That is all I have to do to setup chrony in dinit… 4 lines, not a script, just a config file.
“If systemd is the solution, I want my problem back”
1 Like
I spent quite a lot of time testing things out and I did write about what I had done in this very forum (as well as a few others) including the Debian User Forum. The conclusion arrived at (from other sources) pointed to this being a systemd related issue.
As for the other distros option. I did also do some testing in non-GNOME DE’s and the issue persisted. Like it or lump it, I do prefer the GNOME DE and I’m really not interested in going back to more widoze specific and lookalike DE’s.
Besides all that, just now, it’s 40° outside in the fooking shade here in rural SW France and I’m in no mood to go all through and repeat the content I’ve already posted!
3 Likes
You need the Mediterranean with a nice cooling brezze, but our pool rests at 28 at 9 am overnight does not cool much, just had a quick dip and over 32, dried in the sun
3 Likes