linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dodd <steved@loth.demon.co.uk>
To: Matthew Vanecek <linuxguy@directlink.net>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Updates to /bin/bash
Date: Sat, 6 May 2000 18:02:11 +0100	[thread overview]
Message-ID: <20000506180210.A6381@loth.demon.co.uk> (raw)
In-Reply-To: <39121254.F7F71DAC@directlink.net>; from Matthew Vanecek on Thu, May 04, 2000 at 07:14:12PM -0500

[I don't seem to have the start of this thread..]

On Thu, May 04, 2000 at 07:14:12PM -0500, Matthew Vanecek wrote:

> Well, the executable is loaded into memory once started.  For the most
> part, you can overwrite the executable (or other file) on the disk, as
> long as you have permissions to do so. [..]

Err, no, the executable is paged in and out as required. Updating a running
executable simply means you must make sure to create a *different* inode
for the new version, instead of scribbling over the existing one, i.e.:

cp /mnt/foo/bar /bin/bar.new
rm /bin/bar
mv /bin/bar.new /bin/bar

When the last user of the old version goes away, the inode for it is deleted.
New users see the new version.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

  parent reply	other threads:[~2000-05-06 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-04 19:53 Mark_H_Johnson.RTS
2000-05-05  0:14 ` Matthew Vanecek
2000-05-05  7:14   ` Trond Myklebust
2000-05-06 13:15     ` Andrea Arcangeli
2000-05-06 17:02   ` Steve Dodd [this message]
2000-05-05 13:32 Mark_H_Johnson.RTS

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=20000506180210.A6381@loth.demon.co.uk \
    --to=steved@loth.demon.co.uk \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=linuxguy@directlink.net \
    /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