On Tue, Feb 11, 2014 at 11:07:08AM +0000, Jona Joachim wrote: > On 2014-02-09, Stuart Henderson <[email protected]> wrote: > > On 2014-02-08, Jona Joachim <[email protected]> wrote: > >> Hello, > >> I've been in need for yaifo for quite some time now, so I decided to > >> bring up some patches to make it work with -CURRENT. > > > > Seems like a good time to ask: with the new autoinstall(8) functionality, > > do you still need yaifo? > > > > Are there any small changes to the auto installer that would help the > > standard installer replace yaifo in more situations? > > I think yaifo is very useful for situations where the machine is in some > datacenter where you do not control the network infrastructure and don't > have local access. In this case, you do not control the dhcp server (if > there is one) and autoinstall cannot work. If autoinstall had the option > to read the config files from the local hard drive this could be > addressed. One of the advantages of yaifo is also that you can see in > real-time if things go wrong during the upgrade and correct the errors > (broken mirrors, changes to devices, etc.) autoinstall is definitely a > great feature, I haven't tried it out so far. > > Best regards, > Jona
Well auto-install would read /install.conf from '/' sitting in the ramdisk, it would be enough. Yes, one would need to build own ramdisk to have such file, then I think would be the same (I just guess - to inject own mbr with boot loading this ramdisk). In any case, reading /install.conf from '/' inside ramdisk would be great. I can just imagine one could send an usb stick for initial deployment to a client/customer, of just send him an url for raw image which could be deployed to disk. The latter configuration would be just done remotely or via a configuration manager... jirib
