> > Unifying is for some people an issue, for others not. > > Absolutely. It's also a question for what they are using vserver. I use it > to have dedicated servers, others use it to try new distributions... > unifying doesn't make always sense.
Same here. > > And if you don't > > care about unifying to save space, the README.Debian of the Debian > > packages is more than enough to get going there. > > The debian-newvserver.sh assumes that there is a good connection to > the internet because it has to download the base packages at least once. > I described this way too to install a reference-server. But when you want to > install all vserver-clones with debian-newvserver.sh you always have to do > it manually because the configuring will take interactive input. I don't use the debian-newvserver.sh script at all. I used debootstrap (installation alternative 2 in the README.Debian file) to create a vserver template, which i tarred down. Installation is happening by untarring that in an empty directory. Job done. If i wanted to upgrade it to newer packages, i would have to untar that, chroot, run apt-get update && apt-get upgrade and tar it down again. Issue solved. > > The biggest problem is (just my 2 pence) getting started, how to run > > what distro in the vserver and understanding the concept and the > > limitations of vserver. Mostly i think we need a howto for each and > > every distribution in general (on the host, but mostly on the vserver > > side), because each distro has it's specialities. > > Ok. What we know for sure is that we need more detailed informations. Yep. Regards, Martin List-Petersen martin at list-petersen dot dk -- May Euell Gibbons eat your only copy of the manual!
signature.asc
Description: This is a digitally signed message part
