From spikewhitetx at gmail.com Wed Sep 2 16:51:16 2015 From: spikewhitetx at gmail.com (Spike White) Date: Wed, 2 Sep 2015 11:51:16 -0500 Subject: Ability to specify ks.cfg dynamically for RHEL7 static builds? Message-ID: All, As you know, in RHEL7 the anaconda was totally re-written. I understand why -- apparently the old anaconda was held together with spit and bailing wire. But for static builds, there were several nice features that missing in the new anaconda. Today, I'm asking about specifying your ks.cfg dynamically during your build. Previously in RHEL5 or RHEL6, when doing static builds, the server provisioners would load up 7 - 10 ks.cfg files on their virtual USB key. Name them ks-hostname1.cfg, ks-hostname2.cfg, etc. Then they'd attach this virtual USB key as a virtual disk to their virtual consoles (DRACs). The USB boot media specifies "ks.cfg" file as their ks.cfg file. Since the boot media didn't find that file on the USB key, it'd throw up a prompt requesting the name of the ks.cfg file. The prompt would have something like: /dev/sdd1:/ks.cfg And you'd overwrite that to be: /dev/sdd1:/ks-hostname1.cfg Then the build would then proceed unattended. By doing that, they could have one boot media copy per 10 - 20 builds. Now with RHEL7 and the new anaconda, all that is gone. If it doesn't find a file with the expected name, it no longer throws up a prompt. For static builds, they have to generate a boot media per new build. They have to drop down the ks.cfg file for this new server and call it "ks.cfg". That is, we specify in our initrd line: inst.ks=hd:LABEL=MINIBOOT:/ks.cfg If it doesn't find this, it bails. Is there a way to pop up a menu. Something like: inst.ks=hd:LABEL=MINIBOOT:/ask ??? I can't specify the inst.ks as so on a static build: inst.ks=http://webserver/ks-ip Because (on a static build) the server has to know its IP address, netmask, gateway and NIC device before it brings up the network. Spike -------------- next part -------------- An HTML attachment was scrubbed... URL: From eross at alcf.anl.gov Fri Sep 4 18:39:37 2015 From: eross at alcf.anl.gov (Eric Ross) Date: Fri, 4 Sep 2015 13:39:37 -0500 Subject: ignoredisk --only-use and zerombr Message-ID: <55E9E569.9010906@alcf.anl.gov> Does anyone happen to know if zerombr respects ignoredisk --only-use=/dev/foo, or if it is independent. That is, if I specify a disk first and then issue the zerombr command for example: //snip ignoredisk --only-use=/dev/sda zerombr //end snip will zerombr only operate against /dev/sda, or will it operate against anything it can? The description for zerombr states "If zerombr is specified, _any_ disks whose formatting is unrecognized are initialized", which leads me to believe it doesn't, but I would like to know for sure. Thanks in advance, --Eric