> Hello, Haaai
> > > vserver-clones with debian-newvserver.sh > > > .... configuring will take interactive input. Sure, mostly when it's about the mail-system configuration and the other daemons. As I said it's a question what you're using it for. If you want to provide vservers to other "customers" there is sure a need for a base-system "dpkg-reconfigure" or something like that. > For me the upgrading and administration > of many debian servers is most relevant. > > Again, things like mounting /bin "read only" for a vserver could > some times be usefull (more safe) but how would that work with > installing and upgrading? I wanted to be able to use the packaging system in the vservers and on the host-system. Something that could work is that with every upgrade of the "reference"-vserver the downloaded packages get automaticaly converted to "dummy"-packages and installed on the vservers. This way the vservers won't overwrite the hardlinked unified files and have up2date apt-DB and packages -> we don't need ro on binaries and the vservers could still install stuff with dpkg. Just an idea ;) Greets Joel Wiesmann -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Bitte l�cheln! Fotogalerie online mit GMX ohne eigene Homepage!
