#401 Use custom kickstart for Initial Setup
Closed 5 years ago by pbrobinson. Opened 5 years ago by m4rtink.
m4rtink/fedora-kickstarts f28-use_custom_ks_for_initial_setup  into  f28

file modified
+22
@@ -118,4 +118,26 @@ 

  # https://bugs.launchpad.net/cloud-init/+bug/1670052

  truncate -s 0 /etc/resolv.conf

  

+ # use custom kickstart for Initial Setup

+ # (Initial Setup prefers initial-setup-ks.cfg

+ #  to the anaconda-ks-cfg file generated during

+ #  installation by Anaconda if both are found.)

+ cat > /root/initial-setup-ks.cfg << EOF

+ # Fedora IoT kickstart for Initial Setup

+ #

+ # Created by fedora-iot.ks maintained in:

+ # https://pagure.io/fedora-kickstarts

+ 

+ # initial language/keyboard/timezone presets

+ lang en_US.UTF-8

+ keyboard us

+ timezone --utc Etc/UTC

+ # root should be locked by default but user

+ # can override this by setting a new root

+ # password in Initial Setup

+ rootpw --lock --iscrypted locked

+ # we always want to run Initial Setup in reconfig mode

+ firstboot --reconfig --enable

+ EOF

+ 

  %end

This way we have full control over how Initial Setup is started
and we will also no longer run into issues with image builders
potentially generating kickstarts Initial Setup can't parse.

Is this still wanted/needed? Perhaps against f30/f29? Can you refile if so?

It's a hack, we'll revisit in f29/30 if necessary but I'd prefer a proper upstream packaged fix.

Pull-Request has been closed by pbrobinson

5 years ago
Metadata