From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: root@chaos.analogic.com,
Torrey Hoffman <torrey.hoffman@myrio.com>,
"'Kenneth Johansson'" <ken@canit.se>,
Jonathan Lundell <jlundell@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4 and 2GB swap partition limit
Date: Wed, 2 May 2001 16:31:01 +0200 [thread overview]
Message-ID: <20010502163101.A7174@gruyere.muc.suse.de> (raw)
In-Reply-To: <B65FF72654C9F944A02CF9CC22034CE22E1B9F@mail0.myrio.com> <Pine.LNX.3.95.1010430145555.15714A-100000@chaos.analogic.com> <15085.47104.75880.572242@pizda.ninka.net>
In-Reply-To: <15085.47104.75880.572242@pizda.ninka.net>; from davem@redhat.com on Mon, Apr 30, 2001 at 12:07:44PM -0700
On Mon, Apr 30, 2001 at 12:07:44PM -0700, David S. Miller wrote:
> Even more effective is:
>
> mv /wherever/exeimage /usr/bin/exeimage
>
> The kernel keeps around the contents of the old file while
> the executing process still runs.
>
> This is also basically how things like libc get installed.
> A single mv is not only preserves currently referenced contents,
> it is atomic.
But something must have been not working with it for mmaps/shlibs
(not executables); at least historically.
At least I remember that all hell broke lose when you tried to update
libc by cp'ing a new one to /lib/libc.so in the 1.2 days. cp should create a
new inode (it uses O_CREAT) so in theory it should be coherent by the inode
reference; but somehow it didn't use to work and random already running
programs started to segfault. This was long ago. I wonder if old
GNU cp used O_TRUNC instead of O_CREAT, or was there some other kernel bug
with mappings (hopefully long since fixed). Anybody remembers?
-Andi
next prev parent reply other threads:[~2001-05-02 14:32 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 18:45 2.4 and 2GB swap partition limit Torrey Hoffman
2001-04-30 19:04 ` Richard B. Johnson
2001-04-30 19:07 ` David S. Miller
2001-04-30 19:14 ` Richard B. Johnson
2001-04-30 21:04 ` Andreas Ferber
2001-05-02 14:31 ` Andi Kleen [this message]
2001-05-02 22:17 ` Andreas Dilger
2001-05-04 8:16 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-05-03 14:04 Ishikawa
2001-03-05 16:53 Andries.Brouwer
2001-03-04 22:04 Matt_Domsch
2001-03-05 8:58 ` Christoph Rohland
2001-03-05 14:30 ` Rik van Riel
2001-03-05 14:36 ` Rik van Riel
2001-03-05 14:52 ` Matti Aarnio
2001-03-05 13:30 ` Christoph Hellwig
2001-03-02 21:23 Matt_Domsch
2001-03-02 23:52 ` Kenneth Johansson
2001-03-03 6:14 ` William T Wilson
2001-03-03 11:14 ` Rogier Wolff
2001-03-08 13:05 ` Goswin Brederlow
2001-04-27 10:51 ` Xavier Bestel
2001-04-27 11:13 ` Rogier Wolff
2001-04-27 20:52 ` LA Walsh
2001-04-27 21:44 ` Rik van Riel
2001-04-27 22:06 ` Thomas Dodd
2001-04-27 22:40 ` Hugh Dickins
2001-04-27 22:40 ` Rik van Riel
2001-04-29 15:12 ` Ingo Oeser
2001-04-27 22:44 ` LA Walsh
2001-04-28 7:47 ` Rogier Wolff
2001-04-27 22:22 ` Wakko Warner
2001-04-28 13:17 ` Rogier Wolff
2001-04-28 13:37 ` Wakko Warner
2001-04-28 14:11 ` Rogier Wolff
2001-04-28 14:28 ` J . A . Magallon
2001-04-30 18:12 ` Alan Cox
2001-05-01 13:00 ` Stephen C. Tweedie
2001-05-01 16:14 ` Rogier Wolff
2001-05-01 16:35 ` Stephen C. Tweedie
2001-05-02 10:54 ` Rogier Wolff
2001-05-02 11:04 ` Stephen C. Tweedie
2001-05-02 12:49 ` Hugh Dickins
2001-05-02 13:43 ` Stephen C. Tweedie
2001-05-02 0:28 ` Rik van Riel
2001-05-02 0:34 ` David S. Miller
2001-05-02 0:43 ` Rik van Riel
2001-05-02 1:14 ` Roger Larsson
2001-05-02 1:30 ` Rik van Riel
2001-05-01 13:39 ` Christoph Rohland
2001-05-01 23:25 ` Rik van Riel
2001-04-28 18:04 ` Albert D. Cahalan
2001-04-28 21:23 ` Rogier Wolff
2001-04-29 1:43 ` Jonathan Lundell
2001-04-29 9:17 ` Kenneth Johansson
2001-04-28 18:21 ` David Lang
2001-04-28 21:25 ` Rogier Wolff
2001-04-30 18:14 ` Alan Cox
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=20010502163101.A7174@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=jlundell@pobox.com \
--cc=ken@canit.se \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=torrey.hoffman@myrio.com \
/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;
as well as URLs for NNTP newsgroup(s).