"Flame away!"

Posted Mar 30, 2011 18:39 UTC (Wed) by vrfy (guest, #13362)
In reply to: "Flame away!" by cesarb
Parent article: Introducing /run

That will happen, sure. Actually, the installer of a system should do that today already.

It's just not entirely trivial to change that on the running system during a package update, but we will get there.

"Flame away!"

Posted Apr 1, 2011 3:45 UTC (Fri) by elanthis (guest, #6227) [Link] (1 responses)

It's not trivial (or even possible) to do a lot of things on a package update on a running system. It's utterly impossible to safely remove or replace an ABI-unstable shared library that is dynamically loaded by running applications, for instance. The only way to do that safely is to queue up the change until the next reboot, and then shuffle the files around then.

There's a _reason_ Windows requires a reboot for many updates.

(Windows fails in that it used to just require a reboot for everything out of laziness, which made it incredibly annoying to update all those things for which a reboot was totally unnecessary. It's a lot better about that these days. Many application vendors still demand reboots after their app installs, but those are generally ignorable and are not Windows' fault.)

"Flame away!"

Posted Apr 2, 2011 12:28 UTC (Sat) by kleptog (subscriber, #1183) [Link]

Umm, couldn't you just provide the new libraries under a new name? There is a question of when to delete the old files, but that's why having parallel installs of different versions is a good idea.