| 1 |
On Tue, 3 Jan 2012 18:54:27 +0000 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Tue, 03 Jan 2012 13:50:25 -0500 |
| 5 |
> Olivier Crête <tester@g.o> wrote: |
| 6 |
> > There is a good reason for that, because in-place upgrades are |
| 7 |
> > impossible to do safely (and RedHat customers don't accept weird |
| 8 |
> > breakages like Gentoo users do). For example, if you replace a |
| 9 |
> > library or even a resource file (like a .ui file for GtkBuilder), |
| 10 |
> > the only way to make it work is to make sure that no currently |
| 11 |
> > running application is using it. And that just can't happen with |
| 12 |
> > system libraries like glibc or system packages like udev or dbus. |
| 13 |
> > So the only safe way to upgrade those is to reboot. |
| 14 |
> |
| 15 |
> Uhm... Unix filesystems don't work that way; you can unlink an open |
| 16 |
> file and anything that has that file still opened will continue to |
| 17 |
> work. You're thinking of Windows; Unix supports in-place upgrades |
| 18 |
> just fine. |
| 19 |
|
| 20 |
Considering that all applications keep all files open just for the fun |
| 21 |
of it. |
| 22 |
|
| 23 |
-- |
| 24 |
Best regards, |
| 25 |
Michał Górny |
Archives