[CentOS-devel] os/ and kickstart/ seem identical on Centos 8?

Kaj Niemi

kajtzu at a51.org
Thu Sep 26 10:37:58 UTC 2019

Hi Fabian,

Thanks for the quick response. Turns out that we had never used "-H" when rsyncing previous releases either, works now... :>

Just to be clear, with the structure currently being:

[ etc .. ]

- kickstart/ will never be updated while os/ is constantly updated? Thus, os contains whatever updates within the current release?
- So is it fair to say that the old updates directory will not exist at all in CentOS 8 like it did in previous versions?
- Is there a particular reason for the fasttrack directory, then?
What will happen when there is a new RHEL8 release and a CentOS release is created (I invented the year/month in the example) - will there be a new top-level directory like below:

[ etc .. ]


-----Original Message-----
From: CentOS-devel <centos-devel-bounces at centos.org> On Behalf Of Fabian Arrotin
Sent: 26 September, 2019 12:08
To: centos-devel at centos.org
Subject: Re: [CentOS-devel] os/ and kickstart/ seem identical on Centos 8?

On 26/09/2019 10:06, Kaj Niemi wrote:
> Hi,
> Is it on purpose that under AppStream, BaseOS, PowerTools (but not under
> extras, fasttrack and centosplusplus) there is an os and a kickstart
> directory for each architecture? On a quick glance the directory layout
> and contents seem rather identical.
> Asking as "we" do a local mirror of releases and started wondering about
> the amount of disk space 8 takes.


kickstart is a snapshot of os at GA/release time.
So that permits people to deploy with exactly same content without
having a moving target, as BaseOS/AppStream will be including updates as
they land.

WRT disk space, hopefully, as explained on how to mirror correctly
(https://wiki.centos.org/HowTos/CreatePublicMirrors) , you use -H for
rsync, as we heavily use hardlinks in our trees so that it reduces space
and also used bandwidth to sync mirror content

Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | twitter: @arrfab

More information about the CentOS-devel mailing list