External/fedora-kickstarts
1
0
Fork 0
mirror of https://pagure.io/fedora-kickstarts.git synced 2024-12-22 05:35:26 +00:00
Code Issues Packages Projects Releases Wiki Activity
f25
fedora-kickstarts/fedora-arm-base.ks

94 lines
2.4 KiB
Plaintext
Raw Permalink Normal View History

add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
lang en_US.UTF-8
#keyboard us
Switch md5 to sha512. Fixes bug #1234068 This is pretty cosmetic as live and cloud images don't use passwords and they install with sha512 fine, but some people may use these kickstarts as a base for their spins, so we should use best practices.
2015-06-21 16:38:20 +00:00
auth --useshadow --passalgo=sha512
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
selinux --enforcing
firewall --enabled --service=mdns,ssh
setup extlinux bootloader on arm images
2013-08-27 04:10:33 +00:00
# configure extlinux bootloader
rhel6's ksflatten doesnt support --extlinux
2013-11-25 04:13:52 +00:00
bootloader extlinux
setup extlinux bootloader on arm images
2013-08-27 04:10:33 +00:00
Initial support for Raspberry Pi. We continue to support existing ARM images without any change to the process (except they have a small 30Mb partition at the begining of the image) but all exisiting documented processe work for image writing. The RPi is auto configured and a pure dd to the card, plug and boot.
2016-09-21 14:23:18 +00:00
part /boot/fw --size=30 --fstype vfat --asprimary
revert ext3 /boot for arm images The issue has been fixed upstream with improvements to ext4 support in u-boot 2016.11, in Fedora I backported these fixes to uboot-tools-2016.09.01-2.fc25 and they've now been verified and that release is now stable so we should be good to revert the ext3 partition workaround for F-25 GA.
2016-10-22 17:44:36 +00:00
part /boot --size=512 --fstype ext4 --asprimary
Initial support for Raspberry Pi. We continue to support existing ARM images without any change to the process (except they have a small 30Mb partition at the begining of the image) but all exisiting documented processe work for image writing. The RPi is auto configured and a pure dd to the card, plug and boot.
2016-09-21 14:23:18 +00:00
part swap --size=512 --fstype swap --asprimary
part / --size=3584 --fstype ext4 --asprimary
ARM: kickstart cleanups remove vfat kickstarts, we are going to use u-boot in raw space without needing two sets of images with different partitioning we can remove the seperate partitioning snippets and put the partitioning in base.
2014-05-06 17:31:06 +00:00
make sure we set first-boot to --reconfig this is to make sure that on first boot the images get configured by the end user. timezone set, root password set, user created.
2013-06-01 02:57:20 +00:00
# make sure that initial-setup runs and lets us do all the configuration bits
firstboot --reconfig
manipulate network service in %post (#1369794) Due to #1369794 , anaconda cannot currently manipulate sysv services in F25+. So to work around this, take 'network' out of the services lines in all kickstarts and instead manipulate it in the %post section, with chkconfig. Also remove rsyslog from the Atomic image services line because it doesn't appear to be included in the OStree tree at present and so attempting to enable the service breaks Atomic image compose, see e.g.: https://kojipkgs.fedoraproject.org//work/tasks/9022/15349022/oz-x86_64.log also correct the name of the ssh service in fedora-arm-base.ks; it's sshd not ssh.
2016-08-24 16:50:38 +00:00
services --enabled=sshd,NetworkManager,avahi-daemon,rsyslog,chronyd,initial-setup
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
Make it easier to handle branching Now the switch between using the rawhide repo and the normal repos can be done by just switching comment lines in one place (fedora-repo.ks). (Note that the repo lines in fedora-install.ks don't get changed for branching.)
2013-06-29 13:05:30 +00:00
%include fedora-repo.ks
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
%packages
@core
@standard
@hardware-support
@dial-up
kernel
use --extlinux on arm, add dracut-generic-config as a workaround for a dracut bug
2013-10-08 03:21:50 +00:00
dracut-config-generic
install new arm-tools group to pull in tools for booting arm systems. Signed-off-by: Dennis Gilmore <dennis@ausil.us>
2016-05-30 15:08:58 +00:00
# install tools needed to manage and boot arm systems
@arm-tools
add rng-tools to all ARM images as most arm HW has a HW rng
2016-09-07 14:31:36 +00:00
rng-tools
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
chrony
setup extlinux bootloader on arm images
2013-08-27 04:10:33 +00:00
extlinux-bootloader
Initial support for Raspberry Pi. We continue to support existing ARM images without any change to the process (except they have a small 30Mb partition at the begining of the image) but all exisiting documented processe work for image writing. The RPi is auto configured and a pure dd to the card, plug and boot.
2016-09-21 14:23:18 +00:00
bcm283x-firmware
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
initial-setup
Add initial-setup-gui for arm. Fixes bug #1049545
2014-01-08 22:23:23 +00:00
initial-setup-gui
add dracut-modules-growroot to arm images
2013-08-01 00:45:24 +00:00
#lets resize / on first boot
remove growroot in arm images to test 1109603
2014-07-16 09:28:48 +00:00
# dracut-modules-growroot
install u-boot binaries for systems where we need to ship it.
2013-06-08 13:58:01 +00:00
install dracut-config-generic on arm images to get a generic initramfs remove it in %post so updates get host only initramfs's
2013-10-17 02:58:04 +00:00
# remove this in %post
dracut-config-generic
make sure that all the livecds and arm images have glibc-all-langpacks installed Signed-off-by: Dennis Gilmore <dennis@ausil.us>
2016-02-29 20:21:30 +00:00
# make sure all the locales are available for inital0-setup and anaconda to work
glibc-all-langpacks
specify libcrypt packages in fedora-arm-base for RHBZ #1324623 This seems to be enough to work around yum's issues in dealing with the libcrypt/libcrypt-nss package split, at least it is for me.
2016-08-15 20:58:01 +00:00
# workaround for consequence of RHBZ #1324623: without this, with
# yum-based creation tools, compose fails due to conflict between
# libcrypt and libcrypt-nss. dnf does not seem to have the same
# issue, so this may be dropped when appliance-creator is ported
# to dnf.
libcrypt-nss
-libcrypt
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
%end
%post
Initial support for Raspberry Pi. We continue to support existing ARM images without any change to the process (except they have a small 30Mb partition at the begining of the image) but all exisiting documented processe work for image writing. The RPi is auto configured and a pure dd to the card, plug and boot.
2016-09-21 14:23:18 +00:00
# Setup Raspberry Pi firmware
cp -Pr /usr/share/bcm283x-firmware/* /boot/fw/
cp -P /usr/share/uboot/rpi_2/u-boot.bin /boot/fw/rpi2-u-boot.bin
cp -P /usr/share/uboot/rpi_3_32b/u-boot.bin /boot/fw/rpi3-u-boot.bin
sed -i '/vfat/ d' /etc/fstab
import the gpg key since live and cloud is
2013-12-12 10:15:28 +00:00
# work around for poor key import UI in PackageKit
rm -f /var/lib/rpm/__db*
releasever=$(rpm -q --qf '%{version}\n' fedora-release)
basearch=armhfp
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
clean up the text printed in teh arm disk logs
2015-01-27 20:24:34 +00:00
echo "Packages within this ARM disk image"
import the gpg key since live and cloud is
2013-12-12 10:15:28 +00:00
rpm -qa
# Note that running rpm recreates the rpm db files which aren't needed or wanted
rm -f /var/lib/rpm/__db*
Nuke random seed in install for ARM images too, the new instance should make it's own. Fixes bug #1314879
2016-03-05 17:44:00 +00:00
# remove random seed, the newly installed instance should make it's own
rm -f /var/lib/systemd/random-seed
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
# Because memory is scarce resource in most arm systems we are differing from the Fedora
# default of having /tmp on tmpfs.
echo "Disabling tmpfs for /tmp."
systemctl mask tmp.mount
use dnf, not all ARM images have yum
2016-02-16 18:31:07 +00:00
dnf -y remove dracut-config-generic
install dracut-config-generic on arm images to get a generic initramfs remove it in %post so updates get host only initramfs's
2013-10-17 02:58:04 +00:00
manipulate network service in %post (#1369794) Due to #1369794 , anaconda cannot currently manipulate sysv services in F25+. So to work around this, take 'network' out of the services lines in all kickstarts and instead manipulate it in the %post section, with chkconfig. Also remove rsyslog from the Atomic image services line because it doesn't appear to be included in the OStree tree at present and so attempting to enable the service breaks Atomic image compose, see e.g.: https://kojipkgs.fedoraproject.org//work/tasks/9022/15349022/oz-x86_64.log also correct the name of the ssh service in fedora-arm-base.ks; it's sshd not ssh.
2016-08-24 16:50:38 +00:00
# Disable network service here, as doing it in the services line
# fails due to RHBZ #1369794
/sbin/chkconfig network off
Remove machine-id on pre generated images so it's unique on each deployed device As referenced on the arm list [1] and as already being done on the docker image we should remove the unique /etc/machine-id file on compose artifacts to ensure it's regenerated and unique on each deployed host/device. This unifies the process across all base ks so it's inherited for each artifact. [1] https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/message/Q3YZVF5P2OLLPUJQ2LYZSTKWGGDIU6QO/ Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2016-09-13 07:55:44 +00:00
# Remove machine-id on pre generated images
rm -f /etc/machine-id
Touch the machine-id file So is seems that if you remove the machine-id file it won't regenerate the file but if you touch the file and leave it empty on boot it'll put a new machine-id in the empty file. So work around this bug ("feature"?) by touching the file so we don't have other issues in the process. We're track the outcome of this in RHBZ 1379800
2016-09-27 19:17:46 +00:00
touch /etc/machine-id
Remove machine-id on pre generated images so it's unique on each deployed device As referenced on the arm list [1] and as already being done on the docker image we should remove the unique /etc/machine-id file on compose artifacts to ensure it's regenerated and unique on each deployed host/device. This unifies the process across all base ks so it's inherited for each artifact. [1] https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org/message/Q3YZVF5P2OLLPUJQ2LYZSTKWGGDIU6QO/ Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
2016-09-13 07:55:44 +00:00
add arm kickstarts TODO: add other desktop spins
2013-05-28 06:44:45 +00:00
%end
Reference in New Issue Copy Permalink