This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: upgrade problem

Ben Collins <> writes:

> On Thu, Nov 09, 2000 at 09:09:38PM +0100, Frederic Lepied wrote:
> > Ben Collins <> writes:
> > 


> > > 
> > > Any ideas from the libc folk about this? :)
> > 
> > What I plan to do for Mandrake is keep the libnss from old glibc until
> > the reboot. For that I have to change the soname of the libnss of the
> > new glibc to avoid name clashes. WDYT ?
> I thought about that aswell. Some ideas that came to mind were making the
> NSS module name lookups check for the module names in this order:
> - Load module for service "foo"
>   - Try (where 2.2 is the major.minor of the libc being
>     used)
>   - Fallback to (the current check)
> This way I could keep the old modules around under their non-standard
> name. This could even be reversed if it checks for failure on the standard
> name, then falls back to the versioned name.
> We already have nameing scheme (too tight of a name,
> IMO), so what's one more symlink? :)

It's a good proposition but it doesn't work because the old glibc
doesn't use this scheme and will load the which points
to the new one...

That said, it can be done for the future...
Fred - May the source be with you

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]