Re: Why mount -o remount,ro /usr (sometimes) fails after apt-get dist-upgrade?
* Colin Watson <cjwatson@debian.org> [11-11-2002 16:23]:
> > now i could be wrong (and feel free to correct me if i am), but i think
> > executing the file also counts as a reference to it in some way, so when
> > you delete the file and/or overwrite it with an upgrade, if the program
> > is running in memory it should be just fine and should be able to load in
> > pages that weren't already in memory, but as soon as it exits the file
> > is 'gone'. in the meantime that the program is running, subsequent
> > calls to exec/read that file will get the new file (or fail if it was
> > simply removed).
>
> You are correct. This is how it's possible for distributions like Debian
> to upgrade running programs.
OP mentioned some problems wrt to remounting file-systems. Although
the discussion that followed was very interesting, that issue and
even more so a solution, is unclear to me.
I had to reboot a system after a security upgrade to make /usr ro.
I messed up the installation at first (issueing commands with /usr
ro and /tmp noexec), so I decided to blame myself for the reboot,
while still feeling unease at the reminiscence of the "Restart
Computer (yes/no)" syndrome.
I will try to find the discussion that was mentionend, but would
appreciate any thoughts on this matter.
Bob
Reply to: