2009/2/2 Jeremy Katz <[email protected]>: > 1) Boot loader config > There are a couple of possibilities here... the simplest would just be > that we edit the syslinux.cfg and append more entries. A little bit > more complicated would be to just have a simple "top-level" syslinux.cfg > which uses CONFIG directives to load the additional config files. Third > would be a com32 module to iterate and set up the menu items > automatically. I lean towards the second, at least for at first. > > 2) How to know the new directory > There are multiple places scattered that have hard-coded looking for > LiveOS. There's the initrd, there's the livesys initscript and there's > livecd-iso-to-disk/liveusb-creator. While we could add a kernel command > line option[1] and go and change each of these to set it/respect it, it > feels like maybe the less general solution. Maybe it's just that we > should always have livelabel= available so that we can use it other > places ? I don't know. Open to other thoughts and suggestions. > > What do people think? Is this worth doing? Other ideas on > implementation? Anyone want to start whipping up any patches? > > Jeremy >
This is what I've done in the last 3-4 months. I even have onepsuse and rawhide on my usb-key. They are in separeted directories and both work fine. Editing syslinux.cfg is simple enough to make the changes, but an automated script will be better. Great idea. -- Fedora-livecd-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-livecd-list
