On Fri, 2006-01-13 at 21:11 +0100, Michael Tautschnig wrote: > [...] > > > > $ ls /usr/lib/debootstrap/scripts/ > > breezy hoary.buildd sarge.buildd warty woody.buildd > > etch potato sarge.fakechroot warty.buildd > > hoary sarge sid woody > > > > I skimmed quickly at > > fai-server_2.9-multi-distribution:make-fai-nfsroot:call_debootstrap(). > > Since it looks to me similar to the version in the original fai I conckuded > > that it, too, > > will fail in the same way that I described above. I haven't actually tried > > it nor do I have > > much knoweldge in debootstrap internals. I might be totally wrong. > >
Right. I do not address this specific sid/unstable problem. You add some stuff to FAI debootstrapping and nfsroot creation functions which fixes problems with debian release names in a script, and adjust some calls to specific programs as needed for sid. But then you still have the problem that you can't rely on being able to produce a useful sid base image with a debootstrap as available in Debian stable. And if you (manually!) install the hottest and newest debootstrap version from sid, you can't be sure that this debootstrap version is still able to produce good sarge base images. This doesn't get easier when thinking of Ubuntu, or even RedHat support. That's why I propose to make a difference between the nfsroot and the base image and get the logic necessary to build other base images than the one the fai-server is currently running on out of FAI's core functions completely And I made an implementation of that idea. It has some technical issues as discussed on the fai developers mailing list, but the functionality is there. The additional fai-distributions package could be located in the debian volatile archives, so releases independent from debian releases could be done. Then we could support a new sid debootstrap as soon as it is available, and match other distribution's release cycles - for FAI-servers running nothing else but Debian stable. Henning -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
