We have a DHCP/PXE server in a build environment, which is separate from our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL.
I'd like to keep the storage footprint to a minimum, if possible. Keeping a big directory of ISOs to loop-mount for kickstart profile distributions seems excessive, especially when DVD#1 exceeds 4GB now. Is there any way around this requirement for kickstarting?
2015-02-17 22:26 GMT+02:00 Eckert, Doug doug.eckert@dowjones.com:
We have a DHCP/PXE server in a build environment, which is separate from our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL.
I'd like to keep the storage footprint to a minimum, if possible. Keeping a big directory of ISOs to loop-mount for kickstart profile distributions seems excessive, especially when DVD#1 exceeds 4GB now. Is there any way around this requirement for kickstarting?
How about using centos/rhel minimal iso for kickstarting ?
Eero
On 2/17/2015 12:31 PM, Eero Volotinen wrote:
2015-02-17 22:26 GMT+02:00 Eckert, Dougdoug.eckert@dowjones.com:
We have a DHCP/PXE server in a build environment, which is separate from our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL.
I'd like to keep the storage footprint to a minimum, if possible. Keeping a big directory of ISOs to loop-mount for kickstart profile distributions seems excessive, especially when DVD#1 exceeds 4GB now. Is there any way around this requirement for kickstarting?
How about using centos/rhel minimal iso for kickstarting ?
indeed, thats what I do, and point at an nfs or http repository of the packages. the kickstart file contains all the configuration info for a particular setup.
Trying to use "minimal" ISOs
The 64-bit CEL 7.0 and 6.6 look ok so far. but when I try to set up the CEL 6.6 i386, but I get the following
- The initrd could not be found at the specified location: /var/distros/CentOS-6.6-i386/images/pxeboot/initrd.img
It does have the initrd.img file in .../isolinux, but for some reason, not in .../images/pxeboot
On Tue, Feb 17, 2015 at 3:36 PM, John R Pierce pierce@hogranch.com wrote:
On 2/17/2015 12:31 PM, Eero Volotinen wrote:
2015-02-17 22:26 GMT+02:00 Eckert, Dougdoug.eckert@dowjones.com:
We have a DHCP/PXE server in a build environment, which is separate from
our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk
based
as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL.
I'd like to keep the storage footprint to a minimum, if possible.
Keeping a
big directory of ISOs to loop-mount for kickstart profile distributions seems excessive, especially when DVD#1 exceeds 4GB now. Is there any way around this requirement for kickstarting?
How about using centos/rhel minimal iso for kickstarting ?
indeed, thats what I do, and point at an nfs or http repository of the packages. the kickstart file contains all the configuration info for a particular setup.
-- john r pierce 37N 122W somewhere on the middle of the left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
ISO pulled from
http://mirror.rackspace.com/CentOS/6.6/isos/i386/CentOS-6.6-i386-minimal.iso
# df -h /var/distros/CentOS-6.6-i386 Filesystem Size Used Avail Use% Mounted on /var/ISO/CentOS-6.6-i386-minimal.iso 339M 339M 0 100% /var/distros/CentOS-6.6-i386 # find /var/distros/CentOS-6.6-i386 -name initr* /var/distros/CentOS-6.6-i386/isolinux/initrd.img #
In fact, the /images is populated with
images/install.img images/TRANS.TBL images/updates.img
Nothing else. I can pull apart the ISO, create images/pxeboot, plop the vmlinuz & initrd.img file into place and create a new ISO, but it seems like it should already be there, no? The 64-bit "minimal" ISOs for CEL 6&7 from the same source have them in the right place...
I'd like to just ditch all the i386 stuff, but we do have some legacy systems that were built as such.
On Wed, Feb 18, 2015 at 2:49 PM, Eckert, Doug doug.eckert@dowjones.com wrote:
Trying to use "minimal" ISOs
The 64-bit CEL 7.0 and 6.6 look ok so far. but when I try to set up the CEL 6.6 i386, but I get the following
- The initrd could not be found at the specified location:
/var/distros/CentOS-6.6-i386/images/pxeboot/initrd.img
It does have the initrd.img file in .../isolinux, but for some reason, not in .../images/pxeboot
On Tue, Feb 17, 2015 at 3:36 PM, John R Pierce pierce@hogranch.com wrote:
On 2/17/2015 12:31 PM, Eero Volotinen wrote:
2015-02-17 22:26 GMT+02:00 Eckert, Dougdoug.eckert@dowjones.com:
We have a DHCP/PXE server in a build environment, which is separate from
our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk
based
as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL.
I'd like to keep the storage footprint to a minimum, if possible.
Keeping a
big directory of ISOs to loop-mount for kickstart profile distributions seems excessive, especially when DVD#1 exceeds 4GB now. Is there any
way
around this requirement for kickstarting?
How about using centos/rhel minimal iso for kickstarting ?
indeed, thats what I do, and point at an nfs or http repository of the packages. the kickstart file contains all the configuration info for a particular setup.
-- john r pierce 37N 122W somewhere on the middle of the left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
--
*Doug Eckert* *Technical Architect*
*Global Business Technology* *Dow Jones* | *A News Corporation Company* P.O. Box 300 | Princeton NJ 08543-0300 (W) 609.520.4993 (C) 732.666.3681 *Email: **doug.eckert@dowjones.com* alias@dowjones.com
Same is true for i386 6.5 and 6.4 minimal. I gave up after seeing the same thing on 3 ISOs, but it probably follows all the way down to 6.0.
On Wed, Feb 18, 2015 at 3:53 PM, Eckert, Doug doug.eckert@dowjones.com wrote:
ISO pulled from
http://mirror.rackspace.com/CentOS/6.6/isos/i386/CentOS-6.6-i386-minimal.iso
# df -h /var/distros/CentOS-6.6-i386 Filesystem Size Used Avail Use% Mounted on /var/ISO/CentOS-6.6-i386-minimal.iso 339M 339M 0 100% /var/distros/CentOS-6.6-i386 # find /var/distros/CentOS-6.6-i386 -name initr* /var/distros/CentOS-6.6-i386/isolinux/initrd.img #
In fact, the /images is populated with
images/install.img images/TRANS.TBL images/updates.img
Nothing else. I can pull apart the ISO, create images/pxeboot, plop the vmlinuz & initrd.img file into place and create a new ISO, but it seems like it should already be there, no? The 64-bit "minimal" ISOs for CEL 6&7 from the same source have them in the right place...
I'd like to just ditch all the i386 stuff, but we do have some legacy systems that were built as such.
On Wed, Feb 18, 2015 at 2:49 PM, Eckert, Doug doug.eckert@dowjones.com wrote:
Trying to use "minimal" ISOs
The 64-bit CEL 7.0 and 6.6 look ok so far. but when I try to set up the CEL 6.6 i386, but I get the following
- The initrd could not be found at the specified location:
/var/distros/CentOS-6.6-i386/images/pxeboot/initrd.img
It does have the initrd.img file in .../isolinux, but for some reason, not in .../images/pxeboot
On Tue, Feb 17, 2015 at 3:36 PM, John R Pierce pierce@hogranch.com wrote:
On 2/17/2015 12:31 PM, Eero Volotinen wrote:
2015-02-17 22:26 GMT+02:00 Eckert, Dougdoug.eckert@dowjones.com:
We have a DHCP/PXE server in a build environment, which is separate from
our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk
based
as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL.
I'd like to keep the storage footprint to a minimum, if possible.
Keeping a
big directory of ISOs to loop-mount for kickstart profile
distributions
seems excessive, especially when DVD#1 exceeds 4GB now. Is there any
way
around this requirement for kickstarting?
How about using centos/rhel minimal iso for kickstarting ?
indeed, thats what I do, and point at an nfs or http repository of the packages. the kickstart file contains all the configuration info for a particular setup.
-- john r pierce 37N 122W somewhere on the middle of the left coast
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
--
*Doug Eckert* *Technical Architect*
*Global Business Technology* *Dow Jones* | *A News Corporation Company* P.O. Box 300 | Princeton NJ 08543-0300 (W) 609.520.4993 (C) 732.666.3681 *Email: **doug.eckert@dowjones.com* alias@dowjones.com
--
*Doug Eckert* *Technical Architect*
*Global Business Technology* *Dow Jones* | *A News Corporation Company* P.O. Box 300 | Princeton NJ 08543-0300 (W) 609.520.4993 (C) 732.666.3681 *Email: **doug.eckert@dowjones.com* alias@dowjones.com
-
Eckert, Doug -
Eero Volotinen -
John R Pierce