--- Jane Dogalt <jdogalt(a)yahoo.com&gt; wrote: Actually, I wasn't thinking of this 10 minutes ago when I wrote this, but... With the above, you could also allow a checkbox on a real native anaconda(fedora/redhat) install, say "create livecd boot image", which would go ahead and do a completely normal install on a system, but then leave a bonus bootable iso, say /root/anaconda-livecd.iso, for the user. Thus, for the people on this list who have talked about using kadischi to create deployable read-only livecd's for particular systems (say a particular dell hardware configuration, to be used as an appliance/kiosk), they could just do a normal install on one instance of the system, and boom, there is your livecd. Or even, if the system has a cd burner, you could do the install, and burn the cd right away. Maybe just using temp space on an existing system partition (vfat even) to generate the install iso. Of course, thats not very far away from my earlier dogmeat post about using a generated livecd as a configure/build/test environment for more livecds. Which has a fair amount of synergy to merging the generic os installer with the generic livecd, ala mandriva one, and something like a project I did years ago which just cached("installed") the livecd image to an existing disk partition(think host vfat). My hunch is that the recently fired mandrake founders new secret project ulteo is probably a mix of some of the above. IMO it's the direction to go with livecds. That and using relayfs/unionfs+distributed network filesystems to do really incredibly cool stuff :) -jdog __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Jane Dogalt wrote: Kadischi already does this. Since Anaconda doesn't posses mksquashfs or mkzftree and mkisofs capabilities it would'nt be that difficult. Just use rootpath methods. This is discussed at the http://fedoraproject.org/wiki/Kadischi/Schedule * %livecd section in Kickstart for Anaconda. A whole seperate UI has been suggested: http://fedoraproject.org/wiki/Kadischi/Schedule I would imagine work could be done on a Kadischi UI in Python with GTK bindings and perhaps at the same time send patches to devs. If you are a member of the wiki or a contributor with wiki editing priviliges, you could create a sub item list under the Schedule page under the * create and integrate a fancy little GUI item in the Kadischi wiki.