Sujet : Re: Dimdows Decay Syndrome Continues
De : nospam (at) *nospam* needed.invalid (Paul)
Groupes : comp.os.linux.advocacy alt.comp.os.windows-11Date : 09. Feb 2025, 03:18:17
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vo9399$ae00$1@dont-email.me>
References : 1 2 3 4 5 6 7
User-Agent : Ratcatcher/2.0.0.25 (Windows/20130802)
On Sat, 2/8/2025 9:05 AM, CrudeSausage wrote:
On 2025-02-08 1:36 a.m., Lawrence D'Oliveiro wrote:
On Fri, 7 Feb 2025 20:29:39 -0500, CrudeSausage wrote:
>
On 2025-02-07 4:34 p.m., Lawrence D'Oliveiro wrote:
>
And today, Microsoft’s own experts have no clear idea what Windows is
doing any more. Why do you think it needs to reboot about five times
just to do an OS install?
>
I have to admit those reboots are a nuisance. Of course, Fedora rebooted
pretty often too.
>
There are ways to minimize that. Doesn’t RHEL support kexec, which allows
the old Linux kernel to pass control to the new one without actually
disrupting the userland?
I don't know, it might. Like I said, you don't have to reboot but they recommend it. We expect that kind of behaviour from Windows, so it's not that cumbersome when it happens in Linux too.
Your personal policy may depend on your machine.
On a server with ECC and the background scrubber engaged,
you might laugh at reboots as "unnecessary" and "bourgeois".
On a desktop system where the RAM is protected by nothing,
rebooting is a good way of refreshing the RAM image.
Even if computers had static RAM instead of dynamic RAM,
the bus signal integrity means the error rate is not zero.
With static RAM, the memory might be a tiny bit more
resistant to cosmic ray events.
Paul
Dimdows Decay Syndrome Continues
Re: The Dominance Of Linux (was Re: Dimdows Decay Syndrome Continues)
