So the latest libdbus update fixes some vulnerabilities <https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()? The whole point of introducing poll() <https://manpages.debian.org/poll(2)> was to get around the fixed
limit on the number and range of file descriptors <https://manpages.debian.org/select(2)>, and this is a waste of time
on macOS anyway, because it still has to be implemented via select()??
That is so sad ...
So the latest libdbus update fixes some vulnerabilities <https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()? The whole point of introducing poll() <https://manpages.debian.org/poll(2)> was to get around the fixed
limit on the number and range of file descriptors <https://manpages.debian.org/select(2)>, and this is a waste of time
on macOS anyway, because it still has to be implemented via select()??
That is so sad ...
On 2026-11-12 13:13, Lawrence D?Oliveiro wrote:
So the latest libdbus update fixes some vulnerabilities
<https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>,
including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
ÿÿÿÿ On platforms where poll() is emulated using select() (in practice
ÿÿÿÿ this is believed to mean macOS and Interix), prevent a
ÿÿÿÿ denial-of-service in which the system bus would crash if file
ÿÿÿÿ descriptors above 1024 were polled, and harden it against
ÿÿÿÿ busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()? The whole point of introducing poll()
<https://manpages.debian.org/poll(2)> was to get around the fixed
limit on the number and range of file descriptors
<https://manpages.debian.org/select(2)>, and this is a waste of time
on macOS anyway, because it still has to be implemented via select()??
That is so sad ...
1. "this is believed to mean macOS". So they don't even know.
2. What practical impact does this have on the ACTUAL USE CASES for macOS?
So the latest libdbus update fixes some vulnerabilities <https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()?
That is so sad ...
Lawrence D?Oliveiro <ldo@nz.invalid> writes:
So the latest libdbus update fixes some vulnerabilities
<https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>,
including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in
practice this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()?
Why would you post that without checking? It does have poll().
https://github.com/apple-oss-distributions/xnu/blob/main/bsd/kern/sys_generic.c#L1681
That is so sad ...
Well, something is sad, but I don?t think it?s macOS, in this instance.
Lawrence D?Oliveiro <ldo@nz.invalid> writes:
So the latest libdbus update fixes some vulnerabilities
<https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>,
including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()?
Why would you post that without checking? It does have poll().
https://github.com/apple-oss-distributions/xnu/blob/main/bsd/kern/sys_generic.c#L1681
That is so sad ...
Well, something is sad, but I don?t think it?s macOS, in this instance.
Troll's never check the facts of the things they post that they hope
will rile some group members up. The point is to rile folks up, and
fact checking just gets in the way of that purpose.
Lawrence D?Oliveiro <ldo@nz.invalid> writes:
So the latest libdbus update fixes some vulnerabilities <https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()?
Why would you post that without checking?
It does have poll().
https://github.com/apple-oss-distributions/xnu/blob/main/bsd/kern/sys_generic.
c#L1681
That is so sad ...
Well, something is sad, but I don?t think it?s macOS, in this instance.
On Nov 13, 2026, Richard Kettlewell wrote
(in article <wwv5wy0cz69.fsf@LkoBDZeT.terraraq.uk>):
Lawrence D?Oliveiro <ldo@nz.invalid> writes:
So the latest libdbus update fixes some vulnerabilities
<https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, >>> including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()?
Why would you post that without checking?
because he?s a know-nothing troll.
So the latest libdbus update fixes some vulnerabilities <https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, including ones specific to various BSD derivatives. But I couldn't
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call,
it has to emulate it via select()? The whole point of introducing
poll() <https://manpages.debian.org/poll(2)> was to get around the
fixed limit on the number and range of file descriptors <https://manpages.debian.org/select(2)>, and this is a waste of
time on macOS anyway, because it still has to be implemented via
select()??
That is so sad ...
So the latest libdbus update fixes some vulnerabilities ><https://lists.freedesktop.org/archives/dbus/2026-November/018530.html>, >including ones specific to various BSD derivatives. But I couldn?t
quite believe my eyes when I read this:
On platforms where poll() is emulated using select() (in practice
this is believed to mean macOS and Interix), prevent a
denial-of-service in which the system bus would crash if file
descriptors above 1024 were polled, and harden it against
busy-looping if an invalid file descriptor was polled.
Really?? The macOS kernel does *not* provide a native poll() call, it
has to emulate it via select()? The whole point of introducing poll() ><https://manpages.debian.org/poll(2)> was to get around the fixed
limit on the number and range of file descriptors ><https://manpages.debian.org/select(2)>, and this is a waste of time
on macOS anyway, because it still has to be implemented via select()??
That is so sad ...
Apple ceded server computing, where this is far more likely to
become an issue, to Linux. They're simply not in that space anymore.
As business decisions go, it was a good one, and one that Microsoft
can't quite bring itself to make...
On Fri, 20 Nov 2026 21:40:23 -0000 (UTC), Jason H wrote:
Apple ceded server computing, where this is far more likely to
become an issue, to Linux. They're simply not in that space anymore.
As business decisions go, it was a good one, and one that Microsoft
can't quite bring itself to make...
Actually, Microsoft *is* doing the same sort of thing. Its cloud
service is predominantly Linux-based, and revenue from that is already several times that coming from the division that includes Windows and
Xbox and a few other lesser products and services.
If you look at the development of Windows Server, you can see the
on-prem version already taking a back seat to the cloud version. And
the cloud version is in turn completely outnumbered by the customers
using Linux.
Wonder why the quality of Windows updates seems to be deteriorating
lately? The simple fact is, the revenue coming from that is in
decline, and so investment back into that business declines with it.
On Fri, 11/20/2026 5:21 PM, Lawrence D?Oliveiro wrote:
Wonder why the quality of Windows updates seems to be deteriorating
lately? The simple fact is, the revenue coming from that is in
decline, and so investment back into that business declines with
it.
Um, the Windows Updates are currently augmented by Mythos or Fable
scans for exploits. The resulting 1000 or 1400 security patches,
are bound to have some impact on operations. This is a "hurry-up"
activity, before the Black Hats do their fuzzing and scans with
Mythos or Fable.
How the Windows Group operates has nothing to do with revenue
in a direct one-to-one relationship. It operates on the promise
that some day, it will be a larger source of income.
The Windows Desktop OS continues to exist as a sales vehicle.
The Windows Desktop OS continues to exist as a sales vehicle. It's
a platform for experiments. And for subscription income. When they
can come up with a compelling reason for a subscription.
Paul
Microsoft already has a subscription version of Windows(E3/E5).
In 2025 increased by 15%, though the exact quantity is not reported as
a stand-alone unit.
Wonder why the quality of Windows updates continues to decline? Why
patches often don?t fix problems properly, indeed they often create
new problems? Because the whole Windows business simply isn?t
profitable enough to justify much ongoing investment any more. And
it?s only going to get worse, not better:
Microsoft CFO Amy Hood said on the company?s earnings call that
she expects Windows OEM revenue to decline again next quarter,
around ?the mid 30s,? and a decline is expected to continue
throughout the 2027 financial year.
On Fri, 11/20/2026 11:40 PM, Lawrence D?Oliveiro wrote:
Wonder why the quality of Windows updates continues to decline? Why
patches often don?t fix problems properly, indeed they often create
new problems? Because the whole Windows business simply isn?t
profitable enough to justify much ongoing investment any more. And
it?s only going to get worse, not better:
Microsoft CFO Amy Hood said on the company?s earnings call that
she expects Windows OEM revenue to decline again next quarter,
around ?the mid 30s,? and a decline is expected to continue
throughout the 2027 financial year.
Intel's sales were off by about 22% or so.
It's not as if one company stands alone in being affected by the
Tulip Craze.
Patching is just as complicated in Windows, as in Linux. Ubuntu has
SNAP updates, async to other patching. Windows has App updates (I
got ten of them today), async to Patch Tuesday. Windows has multiple
streams, and things need just as much backpatching as Linux does.
Windows has at least a thousand packages that make up the OS.
And then you have the issue that Windows insists on ?locking? files
that are currently open by running processes, which is why system
updates almost always render the system unusable, and require a reboot afterwards.
On Fri, 20 Nov 2026 19:09:48 -0500, Paul wrote:
Um, the Windows Updates are currently augmented by Mythos or Fable
scans for exploits. The resulting 1000 or 1400 security patches,
are bound to have some impact on operations. This is a "hurry-up"
activity, before the Black Hats do their fuzzing and scans with
Mythos or Fable.
How is it that other groups, like the Linux developers, can fix this
sort of thing without introducing new problems?
Yet all too often these days, Microsoft has to rush out an ?emergency
update? to fix problems caused by their last update.
How is it that other groups, like the Linux developers, can fix this
sort of thing without introducing new problems? Yet all too often
these days, Microsoft has to rush out an ?emergency update? to fix
problems caused by their last update.
Wonder why the quality of Windows updates continues to decline? Why
patches often don?t fix problems properly, indeed they often create
new problems? Because the whole Windows business simply isn?t
profitable enough to justify much ongoing investment any more. And
it?s only going to get worse, not better:
Just think if Intel had spent more time on the x86 - the Motorola
68000 might have won. (Let's have a moment of silence here...)
On Sat, 11/21/2026 3:19 AM, Lawrence D?Oliveiro wrote:
And then you have the issue that Windows insists on ?locking? files
that are currently open by running processes, which is why system
updates almost always render the system unusable, and require a reboot
afterwards.
The OS has a feature called PendMoves.
When Windows Update does an installation, it can mark things that
are locked, by using a command similar to "movefile" and the new
file is kept in a queue for shutdown. Then, the juggling balls as
the OS is shutting down, offers an opportunity for freshly unlocked
files, to be replaced by the Windows Update ones.
What you might be seeing, is during Windows Update installation,
sometimes services are shut down and after "something" is done, they
are started again. The start sometimes fails, and this has
side-effects on the users session :-/ That means, from the hour that
Windows Update is installed, until the hour of the day where you
decide to reboot, some service may not be running. There is no
notification on the screen for this either.
Some of these things are not documented, so the information is only
by observation, which is not the best way to do things.
You might try a Claude question, and see if all the gory details of
Windows Update can be explained.
On 2026-11-21, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
Wonder why the quality of Windows updates continues to decline? Why
patches often don?t fix problems properly, indeed they often create
new problems? Because the whole Windows business simply isn?t
profitable enough to justify much ongoing investment any more.
It's been part of the Microsoft culture and philosophy since day
one: rush out cheap crap, as long as it's pretty. And, like
everything else, they didn't invent that philosophy either. Back in
the '60s "Made in Japan" was a bad joke - Japan and Hong Kong
produced tons of cheap crappy gadgets, and managed to survive
reasonably well, just as Microsoft is doing today.
On Fri, 11/20/2026 11:40 PM, Lawrence D?Oliveiro wrote:
Wonder why the quality of Windows updates continues to decline? Why
patches often don?t fix problems properly, indeed they often create
new problems? Because the whole Windows business simply isn?t
profitable enough to justify much ongoing investment any more. And
it?s only going to get worse, not better:
Microsoft CFO Amy Hood said on the company?s earnings call that
she expects Windows OEM revenue to decline again next quarter,
around ?the mid 30s,? and a decline is expected to continue
throughout the 2027 financial year.
Intel's sales were off by about 22% or so.
It's not as if one company stands alone in being
affected by the Tulip Craze.
That's what they want to ship now.; other8 GB used to be the sweet spot, today 12 GB and trending toward 16GB
*******...though the size of WinSxS doesn't necessary relate to resource loss
Patching is just as complicated in Windows, as in Linux.
Ubuntu has SNAP updates, async to other patching. Windows
has App updates (I got ten of them today), async to Patch Tuesday.
Windows has multiple streams, and things need just as much
backpatching as Linux does. Windows has at least a thousand
packages that make up the OS.
My Windows side-by-side folder
WinSxS
Size 16.4GB
Size on disk 9.81GB <=== and hard linked to "where they are used" on disk
124,061 files
A lot of those files are tiny, and live in the $MFT. But they're
all part of bookkeeping for the repository.
One App level package, can receive nine updates in one day.
Why is that ? Well, that's a labeling problem. There is no
room in the label, to indicate they're actually different versions
of the same thing. And all nine of them are getting patched.
And sometimes, they all get patched within the same minute!
It's rather busy in there.
Yes, it can get busy...
There's really nothing wrong with Intel chips.
As for OS ... something sorta/kinda "-IX" is
gonna be your best bet.
WHAT bullshit now inhabits the 'brain boxes'
in most autos ... can't even keep track.
Likely some won't even drive unless they can
get Big Brother tracking GPS signals.
It order to get max fuel economy EVERYTHING,
engine/ignition/transmission, are all tightly
integrated into the brain-box equation. No
brain-box, NOTHING works.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:20:54 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |