Bill wrote:
In message , Stef
writes
Probably create a new WIM-boot file as part of the update procedure.
Similar to what Linux does with initrd or initramfs when an
update/upgrade requires it. I see this on my Linux system usually
when a kernel load module gets updated. Totally transparent to the user.

See my earlier reply. My Linx tablet seems to have some drivers inside
the compressed file and some outside. I suspect that the machine
manufacturer will have to put together the update.

I'm not so much worried about who prepares the update,
as how the space part of it will be managed. If the
tablet has a 32GB flash chip, the first request that
installer is going to make, is a request for more
free space. So you'll have to move the movie collection
off the tablet.

They can easily make a Windows.old. But the existing
file system consists of the read-only WIM, plus a
persistent file system on top of it. When the new WIM
comes in, the scheme probably has no way to accommodate
a second WIM. Perhaps it will mean setting up two
file systems, which would not then be the same thing
as on a desktop. There could be an entirely
different set of symptoms, when a tablet upgrade
goes nuts. Imagine the mess and the lack of solutions.
Like, what are we going to tell the first tablet
user who comes here, and the upgrade failed, and
the tablet won't boot ? Where would you start ?
(You know they don't have a backup...) While the WIM-boot
is a clever idea, I still haven't heard the story
how it is maintainable.

Paul