From: "Anthony E. Caudel" <acaudel@gt.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dumb question
Date: Wed, 11 Oct 2006 01:30:59 -0500 [thread overview]
Message-ID: <452C8FA3.9050007@gt.rr.com> (raw)
In-Reply-To: <4148457f0610102142hea2c303ub1e29acc43d065fe@mail.gmail.com>
Troy Curtis Jr wrote:
> On 10/10/06, Anthony E. Caudel <acaudel@gt.rr.com> wrote:
>> 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."
>>
>> Tony
>> --
>> Those who would give up essential Liberty, to purchase a little temporary
>> Safety, deserve neither Liberty nor Safety.
>> -- Benjamin Franklin
>> --
>> gentoo-user@gentoo.org mailing list
>>
>>
>
> Simple and short answer is that at run-time the binary and libraries
> are loaded into memory and run from there. When you do the update it
> replaces the binary and/or libraries on disk, but you won't actually
> be running those updates until you restart the process. There may be
> other, more dynamic, cases that I am aware of, but that is the general
> gist of it.
>
> Troy
I suspected it might be memory. However I still find it difficult. If
I'm running KDE for example, it requires at least kdelibs which is a lot
to hold in memory.
Tony
--
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-11 6:36 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 [this message]
2006-10-11 8:28 ` Neil Bothwick
2006-10-11 7:44 ` Pawel Kraszewski
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=452C8FA3.9050007@gt.rr.com \
--to=acaudel@gt.rr.com \
--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