6 Commits

Author	SHA1	Message	Date
Dusty Mabe	fc0a635bc4	zero out resolv.conf during install ... Anaconda is writing an /etc/resolv.conf from the install environment. The system should start out with an empty file, otherwise cloud-init will try to use this information and may error: https://bugs.launchpad.net/cloud-init/+bug/1670052	2017-03-28 16:20:25 -04:00
Colin Walters	954957e609	atomic: Append GROWPART to d-s-s config ... Rather than truncating. This allows us to preserve any existing configuration (e.g. overlayfs by default).	2017-03-21 10:54:59 -04:00
Colin Walters	9912269d88	all: Correct path to /var/lib/systemd/random-seed ... At least for Atomic Host, AFAICS it isn't actually in the final image; not entirely sure why. But we should be using the right path here anyways. https://bugzilla.redhat.com/show_bug.cgi?id=1424404	2017-02-17 15:05:13 -05:00
Colin Walters	740a9b4969	atomic: Add workaround for bash	2016-09-01 16:54:58 -04:00
Adam Williamson	4af7364074	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 11:27:40 -06:00
Dennis Gilmore	27a0af11dd	remove cloud from atomic kickstarts and point at new repo location ... Signed-off-by: Dennis Gilmore <dennis@ausil.us>	2016-04-11 14:09:19 -05:00