Re: Distros: The Fast Food Of GNU/Linux

On 8/3/26 08:03, Joel W. Crump wrote:
> On 8/2/2026 6:12 PM, Leroy H wrote:
> 
>> How many have decided to install systemd for themselves?
>>
>> Answer: No one. Their disrtos made the decision on systemd
>> and they could only helplessly follow suit.
>>
>> How many have decided to install Wayland for themselves?
>>
>> Answer: No one. Their disrtos made the decision on Wayland
>> and they could only helplessly follow suit.
>>
>> The same pattern obtains for each and every change no matter
>> how big or how small.
>>
>> The lusers on this group do not represent GNU/Linux USERS,
>> who study and and understand the system, but only GNU/Linux
>> MOOCHERS who can only accept what is shoved down their
>> ignorant throats.
>>
>> Disagree?
>>
>> All disagreements are just pathetic attempts to save face
>> against the very ugly truth.
> 
> 
> Wrong.

   The poster seems to HATE systemd - for no really
   obvious reasons. As such, add the proverbial grain
   of salt to his posts.

   I write a lot of little daemons. I like the paradigm.
   Each one would also need a 'watchdog' to restart them
   Just In Case. Twice the work - and who watchdogs the
   watchdogs ? Systemd has this built in - use it to start
   the daemons AND watchdog/restart them Just In Case.

   SO, these days, I always install systemd - and if not
   included in the distro I *would* add it.

   What I *don't* like are distros that default to
   fuckin' WAYLAND .... ruins 90% of existing related
   video utilities. Just installed a Pi02w - cute
   little things. Wondered for a while why no VNC
   xstartup worked. Reason = WAYLAND. Reconfigured
   to use Xorg and it all worked perfectly.

   Oh, Pi02w ... the on-setup networking detection
   may HANG. Ya have to skip it, then use the GUI
   network thingie to connect to yer wifi and
   do the updates. Then it's all good. (also tried
   "DietPI" ... weird nasty error messages relating
   to the 'expanded' EXT4 internal drive. Nothing
   OBVIOUSLY wrong with it, the usual utils said it
   was a perfectly good drive, but STILL the big
   error splash, refs to a utility, which said all
   was OK - but the errors wouldn't go away. PLONK !)

   DID use DietPI on a Pi3 long back, connected to the
   company network. That DID work. Used IceWM to save
   a little. Did its thing well for a couple of years
   until I made a bigger/better solution. Wrote a
   client/server system monitor app, 'C', CPU core temps,
   disk space, free mem, external mounts - the usual
   stuff. The PI was the client, made a report. Yea
   yea there's pre-writ software for that stuff but
   most of it is OVERkill. I just ran the normal
   utilities and parsed-out the needed figures. Told
   me what I needed to know. The client was Python,
   easier to compose nice reports.

   Hey, DO like to roll my own - then I get EXACTLY
   what I want exactly how I want it.