Path: news.eternal-september.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Terje Mathisen <terje.mathisen@tmsw.no>
Newsgroups: comp.arch
Subject: Re: Byte ordering
Date: Wed, 16 Oct 2024 07:36:29 +0200
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <venjcu$23p27$1@dont-email.me>
References: <vekb2f$1co97$6@dont-email.me>
 <memo.20241015184006.19028o@jgd.cix.co.uk>
 <ogvtgjhh4eujri9p7biok6c14qd9mv40v3@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 16 Oct 2024 07:36:30 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="25f7728f3d93acce23696a2b8d2bbf01";
	logging-data="2221127"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18shKa0o8PA1FICqiPtkpsbmzlFRe5l2vcwYB3OMvrrCQ=="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Firefox/91.0 SeaMonkey/2.53.19
Cancel-Lock: sha1:b3L0YqtNtwIvSAu9Ndup5K68Grw=
In-Reply-To: <ogvtgjhh4eujri9p7biok6c14qd9mv40v3@4ax.com>

George Neuner wrote:
> On Tue, 15 Oct 2024 18:40 +0100 (BST), jgd@cix.co.uk (John Dallman)
> wrote:
> 
>> In article <vekb2f$1co97$6@dont-email.me>, ldo@nz.invalid (Lawrence
>> D'Oliveiro) wrote:
>>
>>> On the other hand, some stubborn holdouts are still fond of
>>> microkernels -- you just have to say the whole idea is pointless,
>>> and they come out of the woodwork in a futile attempt to disagree
>>
>> The idea is impractical, not pointless. A hybrid kernel gives most of the
>> advantages of a microkernel to its developers, and avoids the need for
>> lots of context switches. It doesn't let you easily replace low-level OS
>> components, but not many people actually want that.
> 
> Actually, I think there are a whole lot of people who can't afford
> non-stop server hardware but would greatly appreciate not having to
> waste time with a shutdown/reboot every time some OS component gets
> updated.
> 
> YMMV.

This is _exactly_ (one of) the problem(s) cloud infrastructure solves: 
As soon as you have more than a single instance of a particular 
server/service, then you replace them in groups so that the service sees 
zero downtime even though all the servers have been updated/replaced.

Terje

-- 
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"