[Docter60]

Thank you, Docter60. I'm working to add this functionality to Reanimator and I'm using your documentation to polish some configurations.

I have booted my Indy on network using a RBPi+Reanimator as NAS and I have some remarks/questions:
- I have used my Octane2 as server, like you, to generate share and client directories
- I prefer to generate the installation on the local disk and to use tar to backup and transfer to RBPi using scp, the generation over network is still slower
- Using a SD card on RBPi is very slow, and the SD card loses write cycles
- I'm working on booting Indy using bootp on RBPi but moving the storage to a NAS (a GNU/Linux thin client) to increase the general speed

Questions:
- Indy booted showing a simple window manager and I couldn't shut it down, a missing file error is displayed and I shutdown executing "shutdown -g0 -p -y", have you experimented the same problems?
- What are these lines used for? I think they are useless:
6.5.22  root=192.168.1.23:/srv/tftp/diskless/share/6.5.22 \
        sbin=192.168.1.23:/srv/tftp/diskless/share/6.5.22/sbin \
        swap=192.168.1.23:
5.3    root=192.168.1.23:/srv/tftp/diskless/share/5.3 \
        sbin=192.168.1.23:/srv/tftp/diskless/share/5.3/sbin \
        swap=192.168.1.23:



On shutdown:

Oh, replies. I don't check back here often, apologies.

For the first question, can't say I have had that exact problem. The first solution I attempted was actually what you described (local tree generation then transferring)!  Tar-ing everything kind of screwed up the files somehow for me...so that might be what's happening.

As for the second question, yeah they kind of are useless.  They're only useful if you plan on creating network classes for your machines.  Those lines are essentially just pasted over from the bootparams file generated by the mock server.