This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: upgrade problem
Ben Collins <bcollins@debian.org> writes:
|> On Fri, Nov 10, 2000 at 12:05:33AM +0100, Andreas Schwab wrote:
|> > Frederic Lepied <flepied@mandrakesoft.com> writes:
|> >
|> > |> Ben Collins <bcollins@debian.org> writes:
|> > |>
|> > |> > >
|> > |> > > It's a good proposition but it doesn't work because the old glibc
|> > |> > > doesn't use this scheme and will load the libnss_foo.so.2 which points
|> > |> > > to the new one...
|> > |> > >
|> > |> > > That said, it can be done for the future...
|> > |> >
|> > |> > Exactly...
|> > |>
|> > |> So we have to change the sonames to be able to handle the upgrade...
|> >
|> > Let's face it: you just can't upgrade libc in a running system. The only
|> > option you have is to leave out all runtime links to shared libraries
|> > during install and create them only at the next reboot.
|>
|> Actually that's completely incorrect. Except for this NSS issue, there are
|> next to zero problems on upgrading libc in place. Debian has been doing it
|> for years now.
They were just lucky. It has never been guaranteed to work.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg