<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Wed, Jun 19, 2019, at 14:11, Jeff Sheltren wrote:<br></div><blockquote type="cite" id="qt"><div dir="ltr"><div dir="ltr">On Wed, Jun 19, 2019 at 1:06 PM Brian Stinson <<a href="mailto:brian@bstinson.com">brian@bstinson.com</a>> wrote:<br></div><div class="qt-gmail_quote"><blockquote style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-color:rgb(204, 204, 204);border-left-style:solid;border-left-width:1px;padding-left:1ex;" class="qt-gmail_quote"><div>> RHEL has the 'kickstart' repo which is equivalent to the CentOS 'base' <br></div><div> > repo in that it never changes once released.<br></div><div> <br></div><div> @kbsingh: if we did something like this, would it solve your use-case? <br></div></blockquote><div><br></div><div>I have the same concern as KB, and I think this would be a fine solution. Just looking for some way to have a reproducible install from the repo.<br></div><div><br></div><div>-Jeff<br></div></div></div><div>_______________________________________________<br></div><div>CentOS-devel mailing list<br></div><div>CentOS-devel@centos.org<br></div><div>https://lists.centos.org/mailman/listinfo/centos-devel<br></div><div><br></div></blockquote><div><br></div><div>Operationally, this means we'd compose BaseOS by itself at a point-release time, hard-link that tree over to the 'kickstart' location on the masters, and then re-spin for 0-day updates.<br></div></body></html>