Sujet : Re: Distros specifically designed for children
De : tnp (at) *nospam* invalid.invalid (The Natural Philosopher)
Groupes : comp.os.linux.miscDate : 03. Jun 2025, 12:37:47
Autres entêtes
Organisation : A little, after lunch
Message-ID : <101mmqb$3uskc$7@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : Mozilla Thunderbird
On 03/06/2025 11:35, Marc Haber wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:
On 03/06/2025 10:01, Marc Haber wrote:
The Natural Philosopher <tnp@invalid.invalid> wrote:
e.g. We will make your default to be IPV6 enabled even though no one is
actually using it
>
There is nothing wrong with that. Nothing breaks when IPv6 gets
enabled.
>
I beg to differ. BIND9 broke for me entirely because it was looking to
connect via IPV6 to DNS servers that it couldn't reach,.
It should have tried IPv4 then. Since there are gazillion possible
misconfigurations that break these features of IPv6, more in-depth
debugging or analysis is not possible at this place. I apologize for
that.
Oh indeed. I am not going to blame IPV6 explicitly, its simply the result of innovation that the customer doesn't necessarily want or need, made the default by bright eyed bushy tailed coders with 'modern' ideas.
Or systemd.
>
No init script broke because there was another program invoking it.
>
Well yes, some did.
>
in my case IIRC NFS came up before wifi had established contact,
delaying boot for minutes.
>
Someone moved WIFI into userland and gave it a low startup priority
while NFS had not been given a systemd dependency that included wifi.
Misconfiguration of services is not systemd's fault. Things like that
happen.
But systemd made those service files necessary in the first place.
Its not a criticism of any piece of code per se, its simply the result of rushing through the new before the old has had a chance to adapt to it
Illustration:
One of our customers phones up...
'Your (its always ours when there was a problem) internet has stopped working'.
'Oh, remind what you have?'
'Its a Cisco router going through our ISDN system'
'Ah, you have an ISDN PABX, not a single ISDN 64 link then?.
'Yes'
'Has anything changed in the setup recently'
'Yes., the ISDN firmware was upgraded yesterday'...
You can guess the rest. ISDN was downgraded to the version that actually worked and I heard no more
Innovation, even with the best of intentions, often breaks existing setups in unexpected ways.
Which is why some of us here are so against innovation *for the sake of it*. 'Creeping featurism' in programs that used to work well. 'Way of the future' upgrades to operating system that render old hardware and software inoperable.
Software written by people who like to code, or do graphic design , not to make easily understandable ergonomic user interfaces, do extensive debugging, or write documentation.
Lazy, spoilt compSci BRATS.
Greetings
Marc
-- “The fundamental cause of the trouble in the modern world today is that the stupid are cocksure while the intelligent are full of doubt." - Bertrand Russell