Vendy,
Thank you for replying. It appears that the interactive-defaults.ks is exactly what I needed.
Thanks!
Brian V.
On Fri, Dec 7, 2018 at 4:45 AM Vendula Poncova <vponcova@xxxxxxxxxx> wrote:
Hi Brian,
I think that you can modify the file
/usr/share/anaconda/interactive-defaults.ks. If a user doesn't provide
a kickstart file, the installer uses this one to set defaults for the
interactive mode.
Another way might be to use the Anaconda DBus API to modify the
installation settings. It might be an overkill for your use case and
the project is still in progress, but I just want to point out that
there is also this option. You can find a small tutorial for exploring
the Anaconda DBus API on Live OS at
https://fedoramagazine.org/whats-new-in-the-anaconda-installer-for-fedora-28/.
Hope it helps.
Vendy
On Mon, Nov 19, 2018 at 6:10 PM Brian Varney <bvarney@xxxxxxxxx> wrote:
>
> Hello,
>
> I see that kickstarting from liveinst is not supported. The only reason I wanted to use the kickstart is to provide a bootloader line to append kernel arguments (blacklisting some drivers). Is there another way to do this?
>
> I realize I could boot the netinstall iso and point that to a kickstart containing my liveimg. This is my fallback plan but I would much prefer to boot from my custom built liveimg and install it directly from there.
>
> This is with Fedora 29.
>
> Thanks for any suggestions.
> Brian V.
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
