I think the LiveCD is a waste of time. Étoilé, currently, is only interesting as a development environment, and a LiveCD is pretty useless for that - ideally we'd want a script in the environment that would update to the latests svn of everything, and that's going to need 4GB or so of RAM as an absolute minimum for a LiveCD.
I don't think using the LiveCD as a starting point for a VM really makes sense, because LiveCDs need lots of ugly hacks that aren't needed for a VM. David On 12 Feb 2011, at 22:13, Ryan Harter wrote: > I was acutally looking at getting the livecd scripts updated and working. I > figured a VM from there is trivial (convert the ISO to a vmdk). Would it be > more helpful for me to focus on a script to build an etoile-dev environment > from a known state (fresh Ubuntu install) like the ubuntu-install-etoile > script does? That's probably first step for a working live CD script anyway. > > I understand why the uchroot but the problem is that the scripts that are > being run are trying to access things outside of the chroot environment. For > instance, the runUchroot function copies the livecd-build script to live/edit > and then chroots to that directory. The first thing the livecd-build script > does is try to access the ubuntu-install-etoille script which is not > accessible from the chroot environment. > > I thought to fix this I'd just copy all of the things needed by > livecd-build.sh somewhere within that live/edit directory so that after we've > chrooted it is available to us. That sound like a good approach? > > Ryan > > On Feb 12, 2011 4:02 PM, "David Chisnall" <[email protected]> wrote: > > If you are looking at the LiveCD script, I think it runs in a chroot > > because it is intended to create and run everything inside the chroot and > > then copy everything from the chroot to a disk image. With the VM image, > > this is not important - the VM image itself is the chroot equivalent. > > > > David > > > > On 12 Feb 2011, at 21:58, Ryan Harter wrote: > > > >> The 64 was just because I was testing on my machine, not the chroot > >> environment. Ill dig deeper into the ffi options to see what I need. > >> > >> I've found a problem with the script. Its running the build script in the > >> chroot environment but trying to access files outside in the script. I was > >> thinking I'd write a script in the chroot area with the runtime vars > >> (ETOILE_USER_NAME, etc) and then when the chroot is entered by the script > >> just run that to export those variables. Had you had something else in > >> mind when you wrote it? > >> > >> Ryan > >> > >> On Feb 12, 2011 2:45 PM, "David Chisnall" <[email protected]> wrote: > >> _______________________________________________ > >> Etoile-dev mailing list > >> [email protected] > >> https://mail.gna.org/listinfo/etoile-dev > > > > > > -- Sent from my brain > > > > > > _______________________________________________ > > Etoile-dev mailing list > > [email protected] > > https://mail.gna.org/listinfo/etoile-dev > _______________________________________________ > Etoile-dev mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-dev -- Sent from my STANTEC-ZEBRA _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
