Jon Steer wrote: > I would like to customize the kickstart file that anaconda uses during > a liveinst install of my liveCD. There is no kickstart. It copies the installed (ext3 file)system right from the livecd onto the disk. Alternately you can launch anaconda yourself with a kickstart, assuming it defines the appropriately visable network repos. I've had thoughts about kickstart applied the filesystem copy method. It might be doable with code similar to what livecd-creator uses for it's "base-on-iso" codepath. The only benefit there, is that it wouldn't hit the network for packages already installed on the iso. -dmc > The kickstart file that is used for the install, is not the same > kickstart file that was used to create the LiveCD. > > A cursory inspection of anaconda doesn't yield any clues about how > that kickstart is created, or where it comes from. > > > Any pointers? > thanks, > jon > > -- Fedora-livecd-list mailing list Fedora-livecd-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list

You can actually feed liveinst a kickstart by adding a $1 to the end of the line in liveinst where it invokes anaconda... then you can do liveinst --kickstart=somefile.cfg and it passes the --kickstart= part to anaconda.. If have not tried to feed it packages this way, but partitioning, network, password, %post, etc work fine... Thanks, Mfk -----Original Message----- From: fedora-livecd-list-bounces(a)redhat.com [mailto:fedora-livecd-list-bounces@redhat.com] On Behalf Of Jon Steer Sent: Wednesday, August 22, 2007 10:08 PM To: fedora-livecd-list(a)redhat.com Subject: Re: [Fedora-livecd-list] liveinst ,where does it get it's kickstart file from? When I use liveinst, I get grub options that are different than what was on the original liveCD. For example, the original LiveCD had selinux off and no X, the installed version had both. I am using the stock anaconda and livecd tools, so perhaps I am missing some of the patches that would correct this? jon On 8/22/07, Douglas McClendon <dmc.fedora(a)filteredperception.org&gt; wrote: > Jon Steer wrote: > > I would like to customize the kickstart file that anaconda uses during > > a liveinst install of my liveCD. > > There is no kickstart. It copies the installed (ext3 file)system right > from the livecd onto the disk. > > Alternately you can launch anaconda yourself with a kickstart, assuming > it defines the appropriately visable network repos. > > I've had thoughts about kickstart applied the filesystem copy method. > It might be doable with code similar to what livecd-creator uses for > it's "base-on-iso" codepath. The only benefit there, is that it > wouldn't hit the network for packages already installed on the iso. > > -dmc > > > The kickstart file that is used for the install, is not the same > > kickstart file that was used to create the LiveCD. > > > > A cursory inspection of anaconda doesn't yield any clues about how > > that kickstart is created, or where it comes from. > > > > > > Any pointers? > > thanks, > > jon > > > > > > -- > Fedora-livecd-list mailing list > Fedora-livecd-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-livecd-list > -- "Whereever you go, there you are" -- Fedora-livecd-list mailing list Fedora-livecd-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list -- Fedora-livecd-list mailing list Fedora-livecd-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list

When I use liveinst, I get grub options that are different than what was on the original liveCD. For example, the original LiveCD had selinux off and no X, the installed version had both. I am using the stock anaconda and livecd tools, so perhaps I am missing some of the patches that would correct this?