From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: install.sh is wrong with libc.so
Date: Wed, 15 Jan 2014 15:18:09 +0100 [thread overview]
Message-ID: <20140115141809.GH1685@port70.net> (raw)
In-Reply-To: <baf7b791-0c56-4cdb-b4a3-7961c4df3a2a@email.android.com>
* orc <orc@sibserver.ru> [2014-01-15 20:48:18 +0800]:
>
> I agree with that. For historical reasons it's not. But I expected musl will continue to use standard install program.
>
the standard install program is non-standard
and it happens to fail to solve the problem it was designed for:
atomic replacement of binaries so they can be used concurrently
during install without spurious failures
next prev parent reply other threads:[~2014-01-15 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 8:42 orc
2014-01-15 11:01 ` Laurent Bercot
2014-01-15 11:35 ` Christian Wiese
2014-01-15 11:52 ` orc
2014-01-15 12:58 ` Christian Wiese
2014-01-15 12:13 ` Szabolcs Nagy
2014-01-15 12:48 ` orc
2014-01-15 14:18 ` Szabolcs Nagy [this message]
2014-01-15 16:31 ` Rich Felker
2014-01-16 1:34 ` orc
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=20140115141809.GH1685@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).