Looks like it determines that I am a local filesystem not TFTPBOOT, but am not sure why? I don't seem to get as far as pulling the config file and get stuck on "directory /minimyth failed to mount"

Of course it failed to mount, it doesn't exist. Is there a way to force it to get the config from /TFTP or NFS using the BOOT_URL as a command line?

Well, you could try option 2 in the post a few ago.

Seriously, you are making this far too difficult for yourself. I strongly recommend that you go back thru your tftpboot directory and delete everything related to minimyth (you can leave all the gentoo/ubuntu stuff if you wish). Then follow Pablo's instructions (use the outline map I sent if it helps clarify some things) to set up MM. It really will be easier.

If you continue on your present path, I fear it will get worse. Many of the scripts Pablo includes assume a specific directory structure. You'll be fighting that all the way.

Seriously, you are making this far too difficult for yourself. I strongly recommend that you go back thru your tftpboot directory and delete everything related to minimyth (you can leave all the gentoo/ubuntu stuff if you wish). Then follow Pablo's instructions (use the outline map I sent if it helps clarify some things) to set up MM. It really will be easier.

I did do that. Or at least I think I did.

I played around somewhat yesterday, moving the NFS root directory to /tftpboot/pxeconfig, calling it nfs-minimyth instead of just minimyth etc etc.

Finally got further. My assumption was almost correct, probably because I'm testing this on machines with Linux it guessed that I wanted local storage rather than get my files from TFTP. In the end I added MM_MINIMYTH_BOOT_URL="http://oac/minimyth/" to my boot line and pointed it to a directory on my apache server. No I can go onwards..