#235 f26: remove rhgb by removing plymouth, fix UEFI %post errors
Merged 6 years ago by mohanboddu. Opened 6 years ago by dustymabe.
dustymabe/fedora-kickstarts dusty-f26  into  f26

file modified
-3
@@ -140,7 +140,4 @@ 

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

  truncate -s 0 /etc/resolv.conf

  

- # Disable rhgb/quiet: https://bugzilla.redhat.com/show_bug.cgi?id=510523

- sed -i 's/rhgb quiet//' /boot/grub2/grub.cfg

- 

  %end

file modified
+6 -4
@@ -81,6 +81,9 @@ 

  #-kbd

  -uboot-tools

  -kernel

+ # No need for plymouth. Also means anaconda won't put rhgb/quiet

+ # on kernel command line

+ -plymouth

  

  %end

  
@@ -232,7 +235,9 @@ 

  echo "Fixing SELinux contexts."

  touch /var/log/cron

  touch /var/log/boot.log

- /usr/sbin/fixfiles -R -a restore

+ # ignore return code because UEFI systems with vfat filesystems

+ # that don't support selinux will give us errors

+ /usr/sbin/fixfiles -R -a restore || true

  

  echo "Zeroing out empty space."

  # This forces the filesystem to reclaim space from deleted files
@@ -257,8 +262,5 @@ 

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

  truncate -s 0 /etc/resolv.conf

  

- # Disable rhgb/quiet: https://bugzilla.redhat.com/show_bug.cgi?id=510523

- sed -i 's/rhgb quiet//' /boot/grub2/grub.cfg

- 

  %end

  

  • atomic, cloud: remove rhgb by removing plymouth
  • cloud: fix errors that happen on UEFI systems

Seems sane to me, though I would say the correct fix for plymouth is removing it from comps at this point. Though that'd affect Fedora Server too.

Pull-Request has been merged by mohanboddu

6 years ago
Metadata