On Thu, Jan 05, 2006 at 11:06:15PM +0200, Adrian Vasile wrote:
> As i said, i'm new to vservers on linux... bsd jails i know with
> unionfs so that i would not rebuild the system again on each necesary
> update.
depending on the packaging system (or the lack of)
the unionfs might be the easier (maintainability
wise) approach (in your particular case)
> I was thinking of keeping all the core packages on the host in ro mode
> and only install particular packages based on necesity. This ideea is
> best described by slax livecd.
in a unification setup you would have to install
the updates in all guests, and re-unify them again
nevertheless the listed advantages still apply.
> I'm always open to new and better ideas, so, any links are welcome.
consider unification like hardlinks, with a twist
the stable release makes them immutable but still
unlinkable (for updates), the devel release adds
CoW (Copy on Write) link breaking, which makes them
as flexible as normal files ...
HTH,
Herbert
> Adrian
>
> Herbert Poetzl wrote:
>
> >On Wed, Jan 04, 2006 at 11:42:32PM +0200, Adrian Vasile wrote:
> >
> >
> >>Hi all,
> >>
> >>i'm just starting with the ideea of vserver and i was thinking if
> >>anyone could point me towards some info related to using (configuring)
> >>vserver with unionfs and maybe give some hardware requirements
> >>(memory, procs, space) needed to run a couple :)
> >>
> >>
> >
> >the probably strange question is, why would you want
> >to use unionfs, when you can have unifiation, which
> >usually suits the linux-vserver guest setup much
> >more than some overlay filesystem?
> >
> >typical advantages over unionfs:
> >
> >- less overhead for access and modification
> >- reduced cache usage (hardlinks)
> >- can be re-unified at any time
> >- does not require patches or modules
> >
> >HTH,
> >Herbert
> >
> >
> >
> >>ps:
> >>webber ~ # uname -a
> >>Linux webber 2.6.14-vs2.0.1-gentootest1 #1 SMP Wed Jan 4 18:41:47 EET
> >>2006 x86_64 Intel(R) Xeon(TM) CPU 3.20GHz GenuineIntel GNU/Linux
> >>with 400GB and 2GB ECC RAM, just finished building it
> >>_______________________________________________
> >>Vserver mailing list
> >>Vserver@list.linux-vserver.org
> >>http://list.linux-vserver.org/mailman/listinfo/vserver
> >>
> >>
>
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Received on Fri Jan 6 04:18:40 2006