• Colord: The Poster Child For GNU/Linux Degeneracy

    From Farley Flud@ff@linux.rocks to comp.os.linux.advocacy,comp.os.linux.misc on Wed Dec 10 15:26:14 2025
    From Newsgroup: comp.os.linux.advocacy

    GNU/Linux has always been about an OS for competent technical
    people.

    But its initial success has brought about an undeniable developmental pomposity.

    Consider the poster child for "colord," a useless product of the
    equally useless, and pompous, freedesktop.org (i.e. IBM/Redhat):

    https://www.freedesktop.org/software/colord/profiles.html

    This website goes back a long way but the underlying philosophy
    has not changed. According to IBM/RedHat, GNU/Linux development
    will not be directed toward technical excellence but rather toward accommodating digital idiots.

    That web page is totally DISGUSTING. It is reminiscent of a
    marketing ploy for children's breakfast cereal.

    But it reveals the true direction of the now corporate-led
    GNU/Linux development.

    By the way, color management is an EXACT SCIENCE and is perfectly
    possible on GNU/Linux without such ridiculous contrivances as "colord."

    I do it all the time. Do you?

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!
    --
    Gentoo: the only road to GNU/Linux freedom and perfection.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From c186282@c186282@nnada.net to comp.os.linux.advocacy on Wed Dec 10 23:57:22 2025
    From Newsgroup: comp.os.linux.advocacy

    On 12/10/25 10:26, Farley Flud wrote:
    GNU/Linux has always been about an OS for competent technical
    people.

    But its initial success has brought about an undeniable developmental pomposity.

    Consider the poster child for "colord," a useless product of the
    equally useless, and pompous, freedesktop.org (i.e. IBM/Redhat):

    https://www.freedesktop.org/software/colord/profiles.html

    This website goes back a long way but the underlying philosophy
    has not changed. According to IBM/RedHat, GNU/Linux development
    will not be directed toward technical excellence but rather toward accommodating digital idiots.

    That web page is totally DISGUSTING. It is reminiscent of a
    marketing ploy for children's breakfast cereal.

    But it reveals the true direction of the now corporate-led
    GNU/Linux development.

    By the way, color management is an EXACT SCIENCE and is perfectly
    possible on GNU/Linux without such ridiculous contrivances as "colord."

    I do it all the time. Do you?

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

    Gee ... you must REALLY hate that daemon !

    Anyway, stick with non-RH deviv distros. RH
    is all contaminated with the IBM mentality at
    this point.

    It's not an *evil* mentality - but it HAS become
    a bit contrary to good sense sometimes.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bonkmaykr@bonkyboo@canithesis.org to comp.os.linux.advocacy on Sat Dec 13 01:19:15 2025
    From Newsgroup: comp.os.linux.advocacy

    Farley Flud wrote:
    GNU/Linux has always been about an OS for competent technical
    people.

    But its initial success has brought about an undeniable developmental pomposity.

    Consider the poster child for "colord," a useless product of the
    equally useless, and pompous, freedesktop.org (i.e. IBM/Redhat):

    https://www.freedesktop.org/software/colord/profiles.html

    This website goes back a long way but the underlying philosophy
    has not changed. According to IBM/RedHat, GNU/Linux development
    will not be directed toward technical excellence but rather toward accommodating digital idiots.

    That web page is totally DISGUSTING. It is reminiscent of a
    marketing ploy for children's breakfast cereal.

    But it reveals the true direction of the now corporate-led
    GNU/Linux development.

    By the way, color management is an EXACT SCIENCE and is perfectly
    possible on GNU/Linux without such ridiculous contrivances as "colord."

    I do it all the time. Do you?

    Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!


    I often find that the biggest proponents of idiotproofing in Linux are actually the biggest reason why new users find everything more confusing.

    Fresh migrants are waved towards GNOME because it's "familiar" (uh, no?)
    like a smartphone (oh god) and told to preemptively fear actually
    interacting with the system in any way, and to never attempt to learn.

    In reality, they will either be spending all of their time learning the
    "new" thing that tries to be quirky for no reason, for example: https://woltman.com/gnome-bad/
    https://datagubbe.se/decusab/

    ... or will become complacent because everyone wants to copy Windows
    verbatim to the point that users try to act as if it actually is Windows.

    Forcing "user friendliness" onto people who "need" it is counter-intuitive.
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Farley Flud@fflud@gnu.rocks to comp.os.linux.advocacy on Sat Dec 13 14:40:54 2025
    From Newsgroup: comp.os.linux.advocacy

    On Sat, 13 Dec 2025 01:19:15 -0600, bonkmaykr wrote:


    I often find that the biggest proponents of idiotproofing in Linux are actually the biggest reason why new users find everything more confusing.

    Fresh migrants are waved towards GNOME because it's "familiar" (uh, no?) like a smartphone (oh god) and told to preemptively fear actually interacting with the system in any way, and to never attempt to learn.

    In reality, they will either be spending all of their time learning the "new" thing that tries to be quirky for no reason, for example: https://woltman.com/gnome-bad/
    https://datagubbe.se/decusab/

    ... or will become complacent because everyone wants to copy Windows verbatim to the point that users try to act as if it actually is Windows.

    Forcing "user friendliness" onto people who "need" it is counter-intuitive.


    My issue with all of these daemons (i.e. services) that are running
    in the background is that they will perform actions that are unknown
    to the user.

    That is something that I cannot accept. I am master of my machines
    and I must know what is happening at all times.

    I have no daemons on my machine, other that udevd which I am forced
    to permit.

    Also, some graphical software will not function properly without
    the dbus daemon but I have written some bash scripts that invoke
    such software with dbus and then kill the daemon when such software
    is terminated.
    --
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From =?UTF-8?Q?St=C3=A9phane?= CARPENTIER@sc@fiat-linux.fr to comp.os.linux.advocacy on Sat Dec 13 15:26:01 2025
    From Newsgroup: comp.os.linux.advocacy

    Le 13-12-2025, Farley Flud <fflud@gnu.rocks> a écrit :

    My issue with all of these daemons (i.e. services) that are running
    in the background is that they will perform actions that are unknown
    to the user.

    That's a point I can understand and agree with. But the fact that you
    are defending SysV and fighting systemd proves you don't understand what
    you are fighting for.

    That is something that I cannot accept.

    That is something I can agree with.

    I am master of my machines

    I don't believe that.

    and I must know what is happening at all times.

    I agree you should, I don't believe you do. And that's a good argument
    in favor of systemd. A critic of systemd states that systemd does things
    it shouldn't, which is right. Because the purpose of an init system
    should be to only launch startup processes. Which is exactly what SysV
    is doing: it launches startup processes and doesn't care about them
    anymore. Unlike systemd which is launching them, then taking care of
    them until their end.

    Agreed, it shouldn't take care of them once launched but as no other
    process is there to do the job and as it's the only one which knows what
    is launched at the startup, it's the best placed to do the job. So,
    agreed, it does something it shouldn't. But as nothing else does that,
    there is nothing better.

    With SysV you can know what is launched at the startup, but if a process launched at the startup either fails or launches another processes, you
    have no way to know it. When systemd is providing you a lot of ways to
    know what's running on your machine and why. Or why something supposed
    to be running isn't.

    So you proved, once again, that systemd is what you are looking for when
    you are fighting it. Once again you prove you like to shoot your own
    foot.

    I have no daemons on my machine, other that udevd which I am forced
    to permit.

    I don't believe that.
    --
    Si vous avez du temps à perdre :
    https://scarpet42.gitlab.io
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Farley Flud@fflud@gnu.rocks to comp.os.linux.advocacy on Sat Dec 13 15:53:14 2025
    From Newsgroup: comp.os.linux.advocacy

    On 13 Dec 2025 15:26:01 GMT, Stéphane CARPENTIER wrote:


    That's a point I can understand and agree with. But the fact that you
    are defending SysV and fighting systemd proves you don't understand what
    you are fighting for.


    Idiot. I don't use SysV. I use my own init scripts which are
    derived and modified from Linux From Scratch:

    https://www.linuxfromscratch.org/lfs/view/stable/chapter09/bootscripts.html



    I have no daemons on my machine, other that udevd which I am forced
    to permit.

    I don't believe that.


    Idiot. Here is my current process list, with kernel processes excluded.
    Read and weep:

    PID TTY STAT TIME COMMAND
    1 ? Ss 0:00 init [3]
    166 ? Ss 0:00 /sbin/udevd --daemon
    287 ? Ss 0:00 /usr/sbin/syslogd -m 0 -s -s
    301 ? Ss 0:00 /usr/sbin/gpm -m /dev/input/mice -t imps2
    306 tty1 Ss 0:00 -bash
    315 tty1 S+ 0:00 xinit -- /usr/bin/Xorg -config /root/xorg.conf -nolisten tcp :0
    333 ? Sl 0:00 pdnsd -d
    367 tty2 S<sl+ 0:25 /usr/bin/Xorg :0 -config /root/xorg.conf -nolisten tcp :0
    380 tty1 S 0:00 /usr/local/bin/fvwm3
    381 tty1 S 0:00 /usr/local/libexec/fvwm3/1.1.2/FvwmMFL 7 4 none 0 8
    387 tty1 S 0:01 xterm -class UXTerm -u8 -fa Liberation Mono -fs 14 -g 100x25+36+20 -vb -sb -title UXTERM
    388 tty1 S 0:02 xterm -class UXTerm -u8 -fa Liberation Mono -fs 14 -g 100x25+41+714 -vb -sb -title UXTERM
    389 tty1 S 0:01 xterm -class UXTerm -u8 -fa Liberation Mono -fs 14 -g 100x25+1298+350 -vb -sb -title UXTERM
    399 pts/1 Ss 0:00 bash
    400 pts/0 Ss 0:00 bash
    401 pts/2 Ss+ 0:00 bash
    571 tty1 Sl 0:23 /usr/bin/palemoon
    8759 tty1 S 0:00 cooledit -font /usr/share/fonts/liberation-fonts/LiberationMono-Regular.ttf:15 -g 1140x780 -lines 40 -columns 120 /root/files/shellcmds
    27778 tty1 Sl 0:02 pan

    Ha, ha, ha, ha! You distro list must be 100x as long.

    Well, I do have a daemon for system logging (syslogd) and a daemon
    for network caching (pdnsd) but those are trivial.

    I understand EVERYTHING that happens on my system at ALL TIMES.

    You don't. You are a distro dog.
    --
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From DFS@nospam@dfs.com to comp.os.linux.advocacy on Sat Dec 13 12:18:31 2025
    From Newsgroup: comp.os.linux.advocacy

    On 12/13/2025 10:53 AM, Farley Flud wrote:

    I use my own init scripts which are
    derived and modified from Linux From Scratch:

    ie copied to the nth degree.

    What a computing virtuoso!


    > I understand EVERYTHING that happens on my system at ALL TIMES.

    The fuck you do. You've barely read a lick of the source code you
    blindly compile and install. You have NO IDEA what it's doing.

    Compared to what you lie-brag about here on cola for 9 years, you're a
    huge tech failure.


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Joel W. Crump@joelcrump@gmail.com to comp.os.linux.advocacy on Sat Dec 13 12:24:31 2025
    From Newsgroup: comp.os.linux.advocacy

    On 12/13/25 12:18 PM, DFS wrote:
    On 12/13/2025 10:53 AM, Farley Flud wrote:

    I use my own init scripts which are
    derived and modified from Linux From Scratch:

    ie copied to the nth degree.

    What a computing virtuoso!

    ; I understand EVERYTHING that happens on my system at ALL TIMES.

     The fuck you do.  You've barely read a lick of the source code you blindly compile and install.  You have NO IDEA what it's doing.

    Compared to what you lie-brag about here on cola for 9 years, you're a
    huge tech failure.


    He really should understand that not everyone wants this "Linux from
    scratch" concept. If Linux from scratch can't boot a full system, it's
    not meant for general use, Larry is a weirdo.
    --
    Joel W. Crump
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From =?UTF-8?Q?St=C3=A9phane?= CARPENTIER@sc@fiat-linux.fr to comp.os.linux.advocacy on Sat Dec 13 18:12:58 2025
    From Newsgroup: comp.os.linux.advocacy

    Le 13-12-2025, DFS <nospam@dfs.com> a écrit :
    On 12/13/2025 10:53 AM, Farley Flud wrote:

    I use my own init scripts which are
    derived and modified from Linux From Scratch:

    ie copied to the nth degree.

    You mean you really believe that it works on his computer?

    What a computing virtuoso!


    I understand EVERYTHING that happens on my system at ALL TIMES.

    The fuck you do. You've barely read a lick of the source code you
    blindly compile and install.

    Then you go further: do you really believe it compile on his computer?
    For the working part is one (hudge for him) step further.

    You have NO IDEA what it's doing.

    Of course. That's why nobody (not even him) can know for sure if that
    works as intended on his computer. And as he explained the lack of logs
    isn't an issue for a program, I strongly believe he removed every error
    message displayed to avoid annoying information.

    Compared to what you lie-brag about here on cola for 9 years, you're a
    huge tech failure.

    The most impressive thing about his bragging is he doesn't even realize
    how he proves he's wrong with every message he sends.
    --
    Si vous avez du temps à perdre :
    https://scarpet42.gitlab.io
    --- Synchronet 3.21a-Linux NewsLink 1.2