Red Hat Bugzilla – Bug 1005223
New kickstart files are needed on the partner's ftp server
Last modified: 2016-07-05 14:30:36 EDT
Created attachment 794722 [details]
Description of problem:
I've updated and attached the kickstart files that can be used to install RHEL 5 and RHEL 6 systems under test and RHEL 6 test servers. Could you put them on the FTP site for us? We'd like to store them in this directory
and use symlinks to keep things neat for users. Here's how I'd like to symlink the files:
- rhel6-server-20130905.ks should be symlinked to rhel6-server.ks
- rhel5-x86_64-client-20130905.ks should be symlinked to rhel5-x86_64-client.ks
- rhel5-i386-client-20130905.ks should be symlinked to rhel5-i386-client.ks
- rhel6-x86_64-client-20130905.ks should be symlinked to rhel6-x86_64-client.ks
- rhel6-i386-client-20130905.ks should be symlinked to rhel6-i386-client.ks
Version-Release number of selected component (if applicable):
Steps to Reproduce:
We also pack kickstart files into the hwcert-client rpm (installed under /usr/share/hwcert/kickstart). Should these new files go there as well?
Also, should they be divided by version (1.5 vs. 1.6)? Perhaps all of them should go into the hwcert-server rpm and be installed under /var/www/hwcert/kickstart?
(In reply to Greg Nichols from comment #1)
> We also pack kickstart files into the hwcert-client rpm (installed under
> /usr/share/hwcert/kickstart). Should these new files go there as well?
> Also, should they be divided by version (1.5 vs. 1.6)? Perhaps all of them
> should go into the hwcert-server rpm and be installed under
I second the latter; I think they could all live in the hwcert-server package together.
I'm wondering if we want to even ship them in the RPM file. If we need to make updates to the kickstarts, we'd have to roll new versions of the RPM files, which entails QA etc. If they were only on the FTP server, we could change them any time we wanted to. That being said, I'm not really sure why we'd need to update them between releases of the hwcert packages.