Hi Holger, Please note that this new feature does not interfere with your approach of using the debootstrap build method and then running softupdate. Perhaps we can suggest these two methods as alternatives for building vservers in the documentation.
Far from being a "regression", each approach has its advantages and disadvantages; the approach of using the nfsroot (which, of course, becomes a somewhat figurative term) makes the build a single logical step, and ensures consistency if the intent is to prototype real host builds using vservers. A single FAI vserver can be used to serve network installs as well as installs on the host system, and does not require that FAI be installed on the host. It also allows cross-architecture builds on systems that support it, like i386 builds on amd64 hosts. As for the default paths being "obsolete", I am currently working on making this usable for the current stable release of debian before I move on to making it work with testing. I based it off FAI 2.10.1; and plan to re-base it off the latest 2.x release. Please bear in mind that I have been familiarizing myself with FAI along the way, and that now we have a working system (and the projects we are using this for - the .nz registry system and NZ Electoral Enrolment Centre offices - are in deployment phase), we are in a position to spend time to take our improvements and share them. Perhaps in the meantime you might have suggestions for detecting which version of FAI is installed, and selecting more appropriate default paths so that users won't have to override the package defaults. Holger Levsen wrote: > package: fai > version: 3.0 > > Hi, > > a dedicated build method for fai-enabled vservers now exists in vservers-svn: > http://svn.linux-vserver.org/viewvc.py/util-vserver/trunk/scripts/vserver-build.fai?view=markup > and will hopefully released in util-vserver .211 > > The needed changes in fai have been send to the mailinglist but not to the > BTS, they are here: > http://www.mail-archive.com/linux-fai%40rrz.uni-koeln.de/msg03756.html > > Currently the build method in vserver has the following problems: > > - obsolete old path for FAI_CONFIGDIR and FAI_NFSROOT as default > - relying on sams branch, doesnt work with fai 3.0 (I have no idea whats > exactly needed to make it work...) > - relying on the fai nfsroot to exist. I very often deploy vservers with fai > without using a nfsroot and just using softupdate. So this is kind of a > regression. > - possible more ;) > > Sam, I think you could greatly help if you could describe what changes are > _really_ needed in fai to make vserver-build.fai work... > > > regards, > Holger > > Log from the discussion on #vserver, which made me notice this: > -- Sam Vilain, Systems Architect, Catalyst IT (NZ) Ltd. phone: +64 4 499 2267 PGP ID: 0x66B25843 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
