From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: dann frazier <dannf@dannf.org>,
Debian HPPA Port List <debian-hppa@lists.debian.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: NTPL transition
Date: Fri, 05 Sep 2008 09:07:06 -0500 [thread overview]
Message-ID: <1220623626.3331.5.camel@localhost.localdomain> (raw)
In-Reply-To: <119aab440809050517v2d26e2f1nd2d3e5aa0efe14bd@mail.gmail.com>
On Fri, 2008-09-05 at 08:17 -0400, Carlos O'Donell wrote:
> On Thu, Sep 4, 2008 at 1:52 PM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > Can we go via an intermediate library that would coexist with current
> > glibc? Something like libc6-nptl, then we do the transitional update
> > with the tools and other libraries moving over to libc6-nptl, then the
> > final piece of the upgrade is libc6 going to nptl based libc6.1 and we
> > remove the transitional libc6-nptl? This type of flip will have to be
> > done via ld.so.conf magic, but it should be doable.
>
> No, due to library-to-library dependencies you have the same problem.
> You would either have to rebuild *all* the libraries or continue
> splitting each library into two packages lib and lib-nptl.
We are going to have to rebuild all the libraries, that's not an option
because of the ABI change.
The problem is not to avoid this, but to find a way of doing an online
upgrade. The real problem we have to avoid is breaking system tools
that are required to perform the upgrade in the intermediate steps. I
don't rule out that will require us to pull this trick with some
libraries in addition to libc, but I don't think it will be all of them.
Just doing libc will probably fix the majority of the issues, though.
James
next prev parent reply other threads:[~2008-09-05 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080904114551.GA18877@tilt.dandreoli.com>
2008-09-04 14:13 ` NTPL transition Carlos O'Donell
2008-09-04 15:23 ` dann frazier
2008-09-04 15:31 ` Carlos O'Donell
2008-09-04 16:04 ` dann frazier
2008-09-04 17:29 ` Carlos O'Donell
2008-09-04 17:49 ` dann frazier
2008-09-04 17:52 ` James Bottomley
2008-09-04 23:26 ` Domenico Andreoli
2008-09-05 12:17 ` Carlos O'Donell
2008-09-05 14:07 ` James Bottomley [this message]
2008-09-05 14:20 ` Kyle McMartin
2008-09-05 14:58 ` Carlos O'Donell
2008-09-04 23:22 ` Domenico Andreoli
2008-09-06 8:24 Petr Salinger
2008-09-06 15:31 ` Carlos O'Donell
2008-09-06 20:16 ` Petr Salinger
2008-09-06 21:36 ` Carlos O'Donell
2008-10-24 5:45 ` Carlos O'Donell
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=1220623626.3331.5.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=carlos@systemhalted.org \
--cc=dannf@dannf.org \
--cc=debian-hppa@lists.debian.org \
--cc=linux-parisc@vger.kernel.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