[uClibc] Re: The naming wars continue...

Denis Vlasenko vda at port.imtp.ilyichevsk.odessa.ua
Fri Oct 29 23:13:18 UTC 2004


> > > Setup:
> > > - 1 server
> > > - 1000 clients mounting /usr ro from the server
> > >   some of the clients run databases
> > > 
> > > How do you manage an upgrade to a new major version of the database 
> > > under /usr ?
> > 
> > Easy. I deploy new database package WITHOUT removing old one.
> > Clients still run old database package.
> > 
> > I let this setup run for a while, migrating clients
> > in small groups to new database as needed/when I have time.
> > 
> > When I feel I don't need ancient database anymore,
> > I remove it.
> 
> This requires a distribution to fully support installing multiple 
> versions of such packages at the same time.

This is easy. Harder part is to make it possible to *run* them
simultaneously.

> That's not completely impossible, but e.g. in Debian unstable as it is 
> today it would require a non-trivial amount of changes.
> 
> And you still need other pieces like the possibility to execute commands 
> on all clients for e.g. restarting services during a glibc upgrade.

Why do I need to execute anything on glibc update?
--
vda




More information about the uClibc mailing list