From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Wed 14 Aug 2002 - 21:22:38 BST
On Tue, 13 Aug 2002 09:39:15 -0500, Jon Bendtsen wrote
> Herbert Poetzl wrote:
> >
> > On Mon, Aug 12, 2002 at 09:31:04PM +0200, Jon Bendtsen wrote:
> > > > Cathy Sarisky wrote:
> > unification is a little more than just a hardlink.
> > it is a hardlink with additional immuteability
> > (except for removal ;) which means, you would not
> > be able to _change_ the file/link in the root server
> > until you remove the immutable flag or the file.
>
> even the root server has to do this ?? I thought the immutable flag
> was only used in the vservers.
The real thing about unification and the immutable flag is that you generally
don't care about those flags. You are not allowed to modify the file, but you
are allowed to unlink it without any trick. Since package update is done using
unlink/rename combination, this is transparent.
> > maybe it would be a good idea to add the vunify
> > functionality to the vrpm script as an option?
>
> Well, what about debian ? and slackware ?
At some point, vunify will support rpm and deb transparently, (vbuild also)
so unification will be available there. Slackware lacks packaging information
allowing to tell apart configuration and resource file. rpm and deb both provide
this information.
For slackware, we can use heuristic. For example, stuff in /usr may be unified.
Not sure. Sam has a solution which would work on slackware though (comparing
files)
---------------------------------------------------------
Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc