Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #95569 > unrolled thread
| Started by | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| First post | 2026-11-12 20:13 +0000 |
| Last post | 2026-11-21 01:05 +0000 |
| Articles | 2 on this page of 22 — 13 participants |
Back to article view | Back to comp.os.linux.misc
Why macOS Will Never Be A High-Performance OS Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-12 20:13 +0000
Re: Why macOS Will Never Be A High-Performance OS Alan <nuh-uh@nope.com> - 2026-11-12 14:32 -0700
Re: Why macOS Will Never Be A High-Performance OS The Natural Philosopher <tnp@invalid.invalid> - 2026-11-13 10:35 +0000
Re: Why macOS Will Never Be A High-Performance OS CrudeSausage <crude@sausa.ge> - 2026-11-12 17:15 -0500
Re: Why macOS Will Never Be A High-Performance OS Richard Kettlewell <invalid@invalid.invalid> - 2026-11-13 19:24 +0000
Re: Why macOS Will Never Be A High-Performance OS Rich <rich@example.invalid> - 2026-11-14 04:02 +0000
Re: Why macOS Will Never Be A High-Performance OS The Natural Philosopher <tnp@invalid.invalid> - 2026-11-14 12:07 +0000
Re: Why macOS Will Never Be A High-Performance OS The Natural Philosopher <tnp@invalid.invalid> - 2026-11-14 12:06 +0000
Re: Why macOS Will Never Be A High-Performance OS WolfFan <akwolffan@zoho.com> - 2026-11-16 15:43 -0500
Re: Why macOS Will Never Be A High-Performance OS Nick Charles <none@none.none> - 2026-11-16 21:21 +0000
Re: Why macOS Will Never Be A High-Performance OS Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-18 04:43 +0000
Re: Why macOS Will Never Be A High-Performance OS Brock McNuggets <brock.mcnuggets@gmail.com> - 2026-11-17 21:52 -0700
Re: Why macOS Will Never Be A High-Performance OS Jason H <jason_hindle@yahoo.com> - 2026-11-20 21:40 +0000
Re: Why macOS Will Never Be A High-Performance OS Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-20 22:21 +0000
Re: Why macOS Will Never Be A High-Performance OS Paul <nospam@needed.invalid> - 2026-11-20 19:09 -0500
Re: Why macOS Will Never Be A High-Performance OS Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-21 00:36 +0000
Re: Why macOS Will Never Be A High-Performance OS ...w¡ñ§±¤ñ <winstonmvp@gmail.com> - 2026-11-20 18:36 -0700
Re: Why macOS Will Never Be A High-Performance OS Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-21 04:40 +0000
Re: Why macOS Will Never Be A High-Performance OS Paul <nospam@needed.invalid> - 2026-11-21 01:26 -0500
Re: Why macOS Will Never Be A High-Performance OS Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-11-21 08:19 +0000
Re: Why macOS Will Never Be A High-Performance OS Paul <nospam@needed.invalid> - 2026-11-21 06:12 -0500
Re: Why macOS Will Never Be A High-Performance OS rbowman <bowman@montana.com> - 2026-11-21 01:05 +0000
Page 2 of 2 — ← Prev page 1 [2]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2026-11-21 06:12 -0500 |
| Message-ID | <11drubr$r37$1@dont-email.me> |
| In reply to | #95821 |
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 get here, is a utility that harnesses PendMoves. You can
privately schedule a file for change-out at shutdown, or, you can
privately schedule a file to be deleted at shutdown. For example,
you could attempt to delete the pagefile.sys at shutdown.
https://web.archive.org/web/20150121163147/https://technet.microsoft.com/en-us/sysinternals/bb897556.aspx
The pendmoves.exe , shows what is queued for changes at shutdown.
pendmoves.exe # You can run this after movefile.exe is used, to see what is planned.
The movefile.exe , uses the mechanism, to replace an old file with a new file,
or to delete the old file instead.
usage: movefile [source] [dest]
Specifying an empty destination ("") deletes the source at boot.
movefile test.exe ""
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.
The shutdown juggling balls, and the startup juggling balls, allow partition
changes when the OS is "less active". That's how outright conflicts are corrected.
For example, say at shutdown, the pagefile.sys is busy, maybe at startup it is
not busy (until it is switched on).
Paul
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-11-21 01:05 +0000 |
| Message-ID | <nmc91uFt2b4U1@mid.individual.net> |
| In reply to | #95808 |
On Fri, 20 Nov 2026 22:21:41 -0000 (UTC), Lawrence D’Oliveiro wrote: > 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. https://azure.microsoft.com/en-us/products/azure-linux
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.os.linux.misc
csiph-web