There is clearly confusion being caused by users still thinking that they need separate BootCD and plnode.txt/floppy files, when they are using the Custom, all-in-one BootCD.

I have made some changes to the myplc/db-config that sends messages, and I will make a few other changes to the GUI to provide in-line hints about what to do or download. I think there may be other sources of information causing confusion.

 Also, the bootmanager, should look on the BootCD itself first, and ignore any other node configuration files it finds... Or not?

I've been collecting links relevant to current technologies for building custom bootcds or livecds. The following are those available for building custom fedora cds. It looks very promising and could be very interesting in terms of how the CD is designed. Do we go for dead-simple fetch from PLC bootscript, or Live-CD node that treats disk as soft-state? I think it will be interesting to reflect on both extremes in the design space and the trade-offs over time, in order to get the most valuable features in.

• http://www-128.ibm.com/developerworks/linux/library/l-fedora-livecd/
• http://people.redhat.com/davidz/livecd/i386/
• http://gitweb.freedesktop.org/?p=users/david/livecd-tools.git