Jeremy Katz wrote:
On Tue, 2007-10-23 at 17:58 -0500, Douglas McClendon wrote:
TODO: since livecd-tools was added to the dev-spin, it seems like the
most obvious minimal QA that should be done is to boot an RC of the
dev-livecd, mount some tmpspace, and then run livecd-creator (with
--tmpdir) with --base-on pointing at /dev/live, to see if you can easily
perform some minimal respin. E.g. perhaps just kickstart that adds a
couple new packages, maybe adds a 3rd party repo, and changes the
isolinux splash. And as a second QA test, respin itself without the
base-on option.
Accepting patches :-) I think the biggest thing is being able to
(easily) hook in something automated to run as part of the live boot.
While it's easy enough to add something to run anaconda as Rahul asked
about, being able to run anything generically is a bit trickier.
Hmm. I wasn't talking about any patches in the above, unless of course
the QA shows that something doesn't work.
As for what you said, and Rahul- It sounded like he wanted something
akin to the traditional installer. I.e. anaconda fullscreen with no
windowmanager or desktop. Can you give an example or two of things that
would be supported in the generic case that you speak of? Are we
talking something crazy like a kernel cmdline of
"autorun='firefox file:///usr/share/doc/fedora/releasenotes'"
I'm just don't quite understand what you were getting at.
And I would love it if the dev-livecd could include qemu (space
impact?), so that the resulting livecd's could be virtually test booted
trivially.
The developer config includes the virtualization group and thus should
have qemu and kvm as well as virt-manager
cool. I was lazy and just did a grep qemu.
-dmc
--
Fedora-livecd-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
