Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: dann frazier <dannf@dannf.org>
Cc: Carlos O'Donell <carlos@systemhalted.org>,
	Debian HPPA Port List <debian-hppa@lists.debian.org>,
	linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: NTPL transition
Date: Thu, 04 Sep 2008 12:52:44 -0500	[thread overview]
Message-ID: <1220550764.3276.45.camel@localhost.localdomain> (raw)
In-Reply-To: <20080904160407.GB24316@colo.lackof.org>

On Thu, 2008-09-04 at 10:04 -0600, dann frazier wrote:
> On Thu, Sep 04, 2008 at 11:31:52AM -0400, Carlos O'Donell wrote:
> > On Thu, Sep 4, 2008 at 11:23 AM, dann frazier <dannf@dannf.org> wrote:
> > > I've already done the initial bootstrapping and John Wright and I have
> > > a buildd actively rebuilding bits against sid. We're rsyncing the
> > > results out to here:
> > >  http://parisc-linux.org/~dannf/hppa-nptl-mirror/unstable/
> > >
> > > Suffice to say, the rebuild is going fairly smoothly. But, I wonder
> > > how we're going to transition systems over to an NPTL userspace. Does
> > > anyone have a plan for that?
> > 
> > Isn't this the responsibility of the package manager?
> > 
> > Why wouldn't apt-get dist-upgrade work?
> 
> We had a discussion about this on IRC, a while back, let me see if I
> can recap...
> 
> If we continue to use libc6 as the package name as we're currently
> doing, at some point libc will get upgraded to the NPTL interface and
> things will start crashing immediately. I asked if we could just do
> "whatever x86 did", and kyle said that we have a problem they didn't -
> our data nptl/lt data structures are incompatible.
> 
> We can deal with that to an extent by adding a second libc package,
> e.g., libc6.1. But, jejb pointed out that, since most libs depend on
> libc, we'll need to be able to have libs for both interfaces at the
> same time to support a transitional upgrade - and that implies an
> SONAME bump for every C library.
> 
> Hopefully there's an easier way, but I don't know of one.

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.

James



  parent reply	other threads:[~2008-09-04 17:52 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 [this message]
2008-09-04 23:26           ` Domenico Andreoli
2008-09-05 12:17           ` Carlos O'Donell
2008-09-05 14:07             ` James Bottomley
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=1220550764.3276.45.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