On Tue, Jul 14, 2009 at 7:38 AM, Douglas McClendon<dmc.fedora@xxxxxxxxxxxxxxxxxxxxxx> wrote: > No, from a user experience perspective, a kexec 'warm' reboot is still a > reboot. I could be wrong about that, or my interpretation of what > kexec does (I've read about it often in LWN, but never knowingly used it). That's correct I believe, yes. > If so, one way to describe the major > benefit of my rebootless installer, is that you get to boot the livecd/usb > environment, *then use it as such*, and at your option, desire, and > convenience, decide to permanently install the LiveOS you have just been > using and configuring, to disk. And of course when done, just pop out the > livecd/usb, and your are done... and free to leave your system with a > continuingly increasing uptime :) Wait, so it's persisting any changes you made to the target drive? That sounds quite cool actually, and I misunderstood the original post. Concretely with your change, if I've connected to a wireless network with NetworkManager, that would get saved in the target drive's configuration in gconf and be there next time I boot? I know with the live images one problem we have is that data can sort of randomly disappear if you're running close to the memory limit; if we go with your architecture we should probably special-case things like ~/.gconf so say the Firefox http disk cache doesn't blow away your wireless config. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
