public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pawel Kraszewski <Gentoo@kraszewscy.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dumb question
Date: Wed, 11 Oct 2006 09:44:47 +0200	[thread overview]
Message-ID: <200610110944.47523.Gentoo@kraszewscy.net> (raw)
In-Reply-To: <452C714D.2030008@gt.rr.com>

Dnia środa, 11 października 2006 06:21, Anthony E. Caudel napisał:
> I have been using Gentoo for more than 2 years now and have always
> wondered (but never asked - That's the "dumb" part) how Gentoo manages
> to update a package that happens to be running at the time.
>
> Given that the old version (the one running) is deleted, how does it
> manage to keep standing if you just cut its legs off?
>
> I've never seen this discussed anywhere which probably means everyone
> else already knows and are probably thinking to themselves, "Dumb
> question."

Observe CAREFULLY sequence of operations during emerge. It doesn't remove old 
package and install new ones. It installs the new one over the old and then 
removes unnecessary remains.

It may overwrite file in use due to the way Unices handle file management. On 
Windows you can't delete open file. On Unix you can, and process keeping file 
open won't usually notice that. Moreover, as long as the file is open, its 
data isn't removed from disk. Once the process closes it, it is physically 
removed - not sooner.

So after overwriting file (library, application) currently running 
applications (having it open) will still have access to old version and each 
newly run application will use the new one.

Which in turn means - yes, you need to 'power cycle' application to use new 
libraries or new version of executable.

-- 
 Pawel Kraszewski
 www.kraszewscy.net

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-10-11  7:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11  4:21 [gentoo-user] Dumb question Anthony E. Caudel
2006-10-11  4:42 ` Troy Curtis Jr
2006-10-11  6:20   ` Nick Rout
2006-10-11 18:05     ` Thomas T. Veldhouse
2006-10-11 18:29       ` Neil Bothwick
2006-10-11  6:30   ` Anthony E. Caudel
2006-10-11  8:28     ` Neil Bothwick
2006-10-11  7:44 ` Pawel Kraszewski [this message]
2006-10-11 16:23 ` Daniel Barkalow
2006-10-11 17:43   ` Michael Sullivan
2006-10-12  7:28     ` Alan McKinnon
2006-10-12  6:17   ` Anthony E. Caudel
2006-10-12  6:22     ` Bo Ørsted Andresen
2006-10-12  6:42       ` PaulNM
2006-10-12  7:30         ` Alan McKinnon
2006-10-12 11:55         ` Boyd Stephen Smith Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200610110944.47523.Gentoo@kraszewscy.net \
    --to=gentoo@kraszewscy.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox