From Joe_Wulf at yahoo.com Sun Jul 1 05:45:00 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Sun, 1 Jul 2007 01:45:00 -0400 Subject: How-to info needed for multiple instances of RH OS's and multiple unique versions {to be kickstarted} Message-ID: Hi. I'm a new member of the list, recently joined about a week ago. I could really use some help regarding kickstart. I have one physical system running FC6. It is set up as my kickstart/NFS/DNS/DHCP server. I've a second physical system, a PC with the VMware Workstation installed and running. I use it to boot/build 'play' virtual machines from the FC6 kickstart server. I've taken the /root/anaconda-ks.cfg file from the same FC6 system and am using it, along with all the other normal kickstart steps, to tailor a network-based build of FC6. I do basically understand how to do that, and can successfully build a Virtual Machine (under VMware Workstation v6.0 on a separate computer) with FC6. Great. Now I am cook'n. Next, I established many new directory names, unique for each OS, established them each/all basically the same as for FC6, into that same FC6 kickstart server. The list follows for each of the OS's I'm working with. RHEL WS3u0 x32 RHEL WS3u1 x32 RHEL WS3u2 x32 RHEL WS3u3 x32 RHEL WS3u4 x32 RHEL WS3u5 x32 RHEL WS3u6 x32 RHEL WS3u7 x32 RHEL WS3u8 x32 RHEL WS3u9 x32 {And conceivably back to the 2.1 versions, too} RHEL WS3u0 x64 RHEL WS3u1 x64 RHEL WS3u2 x64 RHEL WS3u3 x64 RHEL WS3u4 x64 RHEL WS3u5 x64 RHEL WS3u6 x64 RHEL WS3u7 x64 RHEL WS3u8 x64 RHEL WS3u9 x64 {And conceivably back to the 2.1 versions, too} RHEL WS4u0 x32 RHEL WS4u1 x32 RHEL WS4u2 x32 RHEL WS4u3 x32 RHEL WS4u4 x32 RHEL WS4u5 x32 RHEL WS4u0 x64 RHEL WS4u1 x64 RHEL WS4u2 x64 RHEL WS4u3 x64 RHEL WS4u4 x64 RHEL WS4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL ES3u0 x32 RHEL ES3u1 x32 RHEL ES3u2 x32 RHEL ES3u3 x32 RHEL ES3u4 x32 RHEL ES3u5 x32 RHEL ES3u6 x32 RHEL ES3u7 x32 RHEL ES3u8 x32 RHEL ES3u9 x32 {And conceivably back to the 2.1 versions} RHEL ES3u0 x64 RHEL ES3u1 x64 RHEL ES3u2 x64 RHEL ES3u3 x64 RHEL ES3u4 x64 RHEL ES3u5 x64 RHEL ES3u6 x64 RHEL ES3u7 x64 RHEL ES3u8 x64 RHEL ES3u9 x64 {And conceivably back to the 2.1 versions} RHEL ES4u0 x32 RHEL ES4u1 x32 RHEL ES4u2 x32 RHEL ES4u3 x32 RHEL ES4u4 x32 RHEL ES4u5 x32 RHEL ES4u0 x64 RHEL ES4u1 x64 RHEL ES4u2 x64 RHEL ES4u3 x64 RHEL ES4u4 x64 RHEL ES4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL AS3u0 x32 RHEL AS3u1 x32 RHEL AS3u2 x32 RHEL AS3u3 x32 RHEL AS3u4 x32 RHEL AS3u5 x32 RHEL AS3u6 x32 RHEL AS3u7 x32 RHEL AS3u8 x32 RHEL AS3u9 x32 {And conceivably back to the 2.1 versions} RHEL AS3u0 x64 RHEL AS3u1 x64 RHEL AS3u2 x64 RHEL AS3u3 x64 RHEL AS3u4 x64 RHEL AS3u5 x64 RHEL AS3u6 x64 RHEL AS3u7 x64 RHEL AS3u8 x64 RHEL AS3u9 x64 {And conceivably back to the 2.1 versions} RHEL AS4u0 x32 RHEL AS4u1 x32 RHEL AS4u2 x32 RHEL AS4u3 x32 RHEL AS4u4 x32 RHEL AS4u5 x32 RHEL AS4u0 x64 RHEL AS4u1 x64 RHEL AS4u2 x64 RHEL AS4u3 x64 RHEL AS4u4 x64 RHEL AS4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL AS5u0 x32 RHEL AS5u0 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx FC1 x32 FC2 x32 FC3 x32 FC4 x32 FC5 x32 FC6 x32 FC1 x64 FC2 x64 FC3 x64 FC4 x64 FC5 x64 FC6 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Fedora 7 x32 Fedora 7 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx These are all for the Intel architecture, as that is all I have available. I'd do other architectures too (zSeries, Itanium and S/390) if someone wishes to loan me the equipment for the next year or so. My question is this: How do I dynamically build OS-specific kickstart anaconda-ks.cfg files for EACH of them without having to waste tons of hours manually installing each one simply to get that one file out of it??? I would have thought the kickstart GUI would have had something to allow the operator to 'select' which OS from the multitudes possible, that it would now be looking at. If such a capability exists, I'm unable to find it. I seek to devote more of my time to developing/polishing the post-installation area(s) than basic OS building. I have the disk resources to support hosting all the native files for each of the OS's I've listed above. Additionally, I've the disk resources to support hosting each of the OS's as they get built, to include snapshots and checkpoints, within VMware virtual machines. I have all the ISO's for each them as well. I have a 64 bit Intel system for virtual building of OS's. I have a task which requires testing various capabilities against each of these OSs, and uniquely against each of the various update/releases, thus this is why I'm approaching kickstart from such a broad perspective. I'm simply unsure on how to properly go about it. So, how do I manage kickstart building for any OS I wish to pick, and have the resultant anaconda-ks.cfg file work correctly for the chosen OS, when I'm building tons of machines 'virtually'? Do the kickstart tools in existence today facilitate this (it doesn't seem like they do)? If not, what manual method is needed? Is there a resource or two on the net that would facilitate what I'm seeking to learn? Thank you very much in advance for your help. R, -Joe Wulf, CISSP, USN(RET) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Klaus.Steden at thomson.net Sun Jul 1 06:04:43 2007 From: Klaus.Steden at thomson.net (Steden Klaus) Date: Sun, 1 Jul 2007 02:04:43 -0400 Subject: How-to info needed for multiple instances of RH OS's and multipleunique versions {to be kickstarted} Message-ID: I did pretty much that using templates written as Perl include files that were sourced by a CGI that a modified Anaconda called using cmdline boot parameters. I wrote this up on the Fedora Wiki. You should be able to bundle all your network installers on a single USB key or CD using a separate subdir for each flavour although I had to add some tools to older installers to make them work with my script. Hth, Klaus ----- Original Message ----- From: kickstart-list-bounces at redhat.com To: kickstart-list at redhat.com Sent: Sat Jun 30 22:45:00 2007 Subject: How-to info needed for multiple instances of RH OS's and multipleunique versions {to be kickstarted} Hi. I'm a new member of the list, recently joined about a week ago. I could really use some help regarding kickstart. I have one physical system running FC6. It is set up as my kickstart/NFS/DNS/DHCP server. I've a second physical system, a PC with the VMware Workstation installed and running. I use it to boot/build 'play' virtual machines from the FC6 kickstart server. I've taken the /root/anaconda-ks.cfg file from the same FC6 system and am using it, along with all the other normal kickstart steps, to tailor a network-based build of FC6. I do basically understand how to do that, and can successfully build a Virtual Machine (under VMware Workstation v6.0 on a separate computer) with FC6. Great. Now I am cook'n. Next, I established many new directory names, unique for each OS, established them each/all basically the same as for FC6, into that same FC6 kickstart server. The list follows for each of the OS's I'm working with. RHEL WS3u0 x32 RHEL WS3u1 x32 RHEL WS3u2 x32 RHEL WS3u3 x32 RHEL WS3u4 x32 RHEL WS3u5 x32 RHEL WS3u6 x32 RHEL WS3u7 x32 RHEL WS3u8 x32 RHEL WS3u9 x32 {And conceivably back to the 2.1 versions, too} RHEL WS3u0 x64 RHEL WS3u1 x64 RHEL WS3u2 x64 RHEL WS3u3 x64 RHEL WS3u4 x64 RHEL WS3u5 x64 RHEL WS3u6 x64 RHEL WS3u7 x64 RHEL WS3u8 x64 RHEL WS3u9 x64 {And conceivably back to the 2.1 versions, too} RHEL WS4u0 x32 RHEL WS4u1 x32 RHEL WS4u2 x32 RHEL WS4u3 x32 RHEL WS4u4 x32 RHEL WS4u5 x32 RHEL WS4u0 x64 RHEL WS4u1 x64 RHEL WS4u2 x64 RHEL WS4u3 x64 RHEL WS4u4 x64 RHEL WS4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL ES3u0 x32 RHEL ES3u1 x32 RHEL ES3u2 x32 RHEL ES3u3 x32 RHEL ES3u4 x32 RHEL ES3u5 x32 RHEL ES3u6 x32 RHEL ES3u7 x32 RHEL ES3u8 x32 RHEL ES3u9 x32 {And conceivably back to the 2.1 versions} RHEL ES3u0 x64 RHEL ES3u1 x64 RHEL ES3u2 x64 RHEL ES3u3 x64 RHEL ES3u4 x64 RHEL ES3u5 x64 RHEL ES3u6 x64 RHEL ES3u7 x64 RHEL ES3u8 x64 RHEL ES3u9 x64 {And conceivably back to the 2.1 versions} RHEL ES4u0 x32 RHEL ES4u1 x32 RHEL ES4u2 x32 RHEL ES4u3 x32 RHEL ES4u4 x32 RHEL ES4u5 x32 RHEL ES4u0 x64 RHEL ES4u1 x64 RHEL ES4u2 x64 RHEL ES4u3 x64 RHEL ES4u4 x64 RHEL ES4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL AS3u0 x32 RHEL AS3u1 x32 RHEL AS3u2 x32 RHEL AS3u3 x32 RHEL AS3u4 x32 RHEL AS3u5 x32 RHEL AS3u6 x32 RHEL AS3u7 x32 RHEL AS3u8 x32 RHEL AS3u9 x32 {And conceivably back to the 2.1 versions} RHEL AS3u0 x64 RHEL AS3u1 x64 RHEL AS3u2 x64 RHEL AS3u3 x64 RHEL AS3u4 x64 RHEL AS3u5 x64 RHEL AS3u6 x64 RHEL AS3u7 x64 RHEL AS3u8 x64 RHEL AS3u9 x64 {And conceivably back to the 2.1 versions} RHEL AS4u0 x32 RHEL AS4u1 x32 RHEL AS4u2 x32 RHEL AS4u3 x32 RHEL AS4u4 x32 RHEL AS4u5 x32 RHEL AS4u0 x64 RHEL AS4u1 x64 RHEL AS4u2 x64 RHEL AS4u3 x64 RHEL AS4u4 x64 RHEL AS4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL AS5u0 x32 RHEL AS5u0 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx FC1 x32 FC2 x32 FC3 x32 FC4 x32 FC5 x32 FC6 x32 FC1 x64 FC2 x64 FC3 x64 FC4 x64 FC5 x64 FC6 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Fedora 7 x32 Fedora 7 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx These are all for the Intel architecture, as that is all I have available. I'd do other architectures too (zSeries, Itanium and S/390) if someone wishes to loan me the equipment for the next year or so. My question is this: How do I dynamically build OS-specific kickstart anaconda-ks.cfg files for EACH of them without having to waste tons of hours manually installing each one simply to get that one file out of it??? I would have thought the kickstart GUI would have had something to allow the operator to 'select' which OS from the multitudes possible, that it would now be looking at. If such a capability exists, I'm unable to find it. I seek to devote more of my time to developing/polishing the post-installation area(s) than basic OS building. I have the disk resources to support hosting all the native files for each of the OS's I've listed above. Additionally, I've the disk resources to support hosting each of the OS's as they get built, to include snapshots and checkpoints, within VMware virtual machines. I have all the ISO's for each them as well. I have a 64 bit Intel system for virtual building of OS's. I have a task which requires testing various capabilities against each of these OSs, and uniquely against each of the various update/releases, thus this is why I'm approaching kickstart from such a broad perspective. I'm simply unsure on how to properly go about it. So, how do I manage kickstart building for any OS I wish to pick, and have the resultant anaconda-ks.cfg file work correctly for the chosen OS, when I'm building tons of machines 'virtually'? Do the kickstart tools in existence today facilitate this (it doesn't seem like they do)? If not, what manual method is needed? Is there a resource or two on the net that would facilitate what I'm seeking to learn? Thank you very much in advance for your help. R, -Joe Wulf, CISSP, USN(RET) From lippold at gmail.com Sun Jul 1 12:39:16 2007 From: lippold at gmail.com (Aaron Lippold) Date: Sun, 1 Jul 2007 14:39:16 +0200 Subject: Using Perl in %post Message-ID: <39d2723b0707010539h21d8baedu4d5f202b2bac8200@mail.gmail.com> Hello, I am building a kickstart that is fairly simple but has many repetitive actions based on a large set of files. I have the file sets listed in a simple text file and wrote a perl script to simple open the file, read the line, parse the filename and output the needed command with the right chunks of the full filename in the right places. I did it in perl and not bash because I am not sure how to do it well in bash or sh etc. I would like to just run this script and or fuction right in mz .spec file. I cannot seem to find any data on if I can do this. Or can someone show me a quick bash code snip for doing something like : MYFILE CODE/SET1/File.txt ... install() open file MYFILE while (file) # a = CODE, b = SET1, c = File d = txt (a,b,c,d) = parse(line) instcmd -n ="b" -f = "c.d" end while # in the postun section cleandb() open file MYFILE while(file) (a,b,c,d) = parse(line) rmcmd -n = c end while This way I could just define the right fileset for each subpackage and I won't have to maintain a list of 100 or more identical opperations, just dump an ls into a file for setx-file-list.txt when I need to rebuild the rpms for an updated set of file. Thanks for any help, thoughts and education. Aaron From lippold at gmail.com Sun Jul 1 12:41:19 2007 From: lippold at gmail.com (Aaron Lippold) Date: Sun, 1 Jul 2007 14:41:19 +0200 Subject: Using Perl in %post In-Reply-To: <39d2723b0707010539h21d8baedu4d5f202b2bac8200@mail.gmail.com> References: <39d2723b0707010539h21d8baedu4d5f202b2bac8200@mail.gmail.com> Message-ID: <39d2723b0707010541p4470fbd3rb08b66dffea71c75@mail.gmail.com> Sorry, Wrong list :) On 7/1/07, Aaron Lippold wrote: > Hello, > > I am building a kickstart that is fairly simple but has many > repetitive actions based on a large set of files. > > I have the file sets listed in a simple text file and wrote a perl > script to simple open the file, read the line, parse the filename and > output the needed command with the right chunks of the full filename > in the right places. > > I did it in perl and not bash because I am not sure how to do it well > in bash or sh etc. > > I would like to just run this script and or fuction right in mz .spec > file. I cannot seem to find any data on if I can do this. Or can > someone show me a quick bash code snip for doing something like : > > MYFILE > CODE/SET1/File.txt > ... > > install() > open file MYFILE > while (file) > # a = CODE, b = SET1, c = File d = txt > (a,b,c,d) = parse(line) > instcmd -n ="b" -f = "c.d" > end while > > # in the postun section > cleandb() > open file MYFILE > while(file) > (a,b,c,d) = parse(line) > rmcmd -n = c > end while > > This way I could just define the right fileset for each subpackage and > I won't have to maintain a list of 100 or more identical opperations, > just dump an ls into a file for setx-file-list.txt when I need to > rebuild the rpms for an updated set of file. > > Thanks for any help, thoughts and education. > > Aaron > From redhat-list at xdroop.com Sun Jul 1 13:04:14 2007 From: redhat-list at xdroop.com (David Mackintosh) Date: Sun, 1 Jul 2007 09:04:14 -0400 Subject: How-to info needed for multiple instances of RH OS's and multiple unique versions {to be kickstarted} In-Reply-To: References: Message-ID: <20070701130414.GB2717@xdroop.com> On Sun, Jul 01, 2007 at 01:45:00AM -0400, Joe_Wulf wrote: > My question is this: > How do I dynamically build OS-specific kickstart anaconda-ks.cfg files for EACH > of them without having to waste > tons of hours manually installing each one simply to get that one file out of > it??? My method for handling this was to install the oldest one I could and then built a "generic" ks.cfg that could be quickly modified through a perl script or something. In my case all I have to change is the line which tells the installer where the source is: nfs --server $myserver --dir /export/kickstart/$REV This has worked for me -- I have basically carried the same ks.cfg file forward from a RedHat 8.0 installation, although I understand it won't work for RHEL 5.x since the @Everything package group has been removed. (Boo!) The second thing I did was to set up cobbler (http://cobbler.et.redhat.com/) which simplified a PXE-boot environment. The version I installed required that I built my own interactive menu to select the PXE profile to install, but I understand that later versions include this functionality. I have successfully PXE installed (currently... eight?) different versions of RedHat using this method, both real machines and VMware systems. -- /\oo/\ / /()\ \ David Mackintosh | dave at xdroop.com | http://www.xdroop.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From lippold at gmail.com Sun Jul 1 17:04:58 2007 From: lippold at gmail.com (Aaron Lippold) Date: Sun, 1 Jul 2007 19:04:58 +0200 Subject: How-to info needed for multiple instances of RH OS's and multiple unique versions {to be kickstarted} In-Reply-To: <20070701130414.GB2717@xdroop.com> References: <20070701130414.GB2717@xdroop.com> Message-ID: <39d2723b0707011004r2c10eac3m5c79c9de82ed4541@mail.gmail.com> You could also use cobber and its ks template system. http://cobbler.et.redhat.com On 7/1/07, David Mackintosh wrote: > On Sun, Jul 01, 2007 at 01:45:00AM -0400, Joe_Wulf wrote: > > > My question is this: > > How do I dynamically build OS-specific kickstart anaconda-ks.cfg files for EACH > > of them without having to waste > > tons of hours manually installing each one simply to get that one file out of > > it??? > > My method for handling this was to install the oldest one I could and then built > a "generic" ks.cfg that could be quickly modified through a perl script or something. > In my case all I have to change is the line which tells the installer where > the source is: > > nfs --server $myserver --dir /export/kickstart/$REV > > This has worked for me -- I have basically carried the same ks.cfg > file forward from a RedHat 8.0 installation, although I understand it > won't work for RHEL 5.x since the @Everything package group has been > removed. (Boo!) > > The second thing I did was to set up cobbler (http://cobbler.et.redhat.com/) > which simplified a PXE-boot environment. The version I installed > required that I built my own interactive menu to select the PXE > profile to install, but I understand that later versions include this > functionality. > > I have successfully PXE installed (currently... eight?) different > versions of RedHat using this method, both real machines and VMware > systems. > > -- > /\oo/\ > / /()\ \ David Mackintosh | > dave at xdroop.com | http://www.xdroop.com > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > From Chip.Shabazian at bankofamerica.com Mon Jul 2 07:56:20 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 02 Jul 2007 00:56:20 -0700 Subject: How-to info needed for multiple instances of RH OS's and multiple unique versions {to be kickstarted} In-Reply-To: Message-ID: Well, first of all, you can dispense with the WS/ES/AS redundancy. The only difference between them is what gets installed in package groups and the redhat-release rpm. For testing binary compatibility, you can simply test any of the WS/ES/AS versions. In fact, depending on your kickstart, it's possible you get the exact same build from each one (I do using our kickstart). I would probably just take my kickstart file, replace the install source with something unique such as INSTALL_SOURCE_HERE, then do a "for `ls /dir/of/your/install/trees`" loop using perl or sed to change the INSTALL_SOURCE_HERE to the proper directory name and create kickstart files for each release. You could then simply use ks=method:/path_to_kickstarts/release.cfg. It may be a bit simplistic, but it's quick and should work just fine. Any issues you run into can be fixed in the specific release kickstart file. Although Cobbler is an excellent tool (and I highly recommend it for anyone setting up a build infrastructure), it sounds like more setup than you need for this project. Chip ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Joe_Wulf Sent: Saturday, June 30, 2007 10:45 PM To: kickstart-list at redhat.com Subject: How-to info needed for multiple instances of RH OS's and multiple unique versions {to be kickstarted} Hi. I'm a new member of the list, recently joined about a week ago. I could really use some help regarding kickstart. I have one physical system running FC6. It is set up as my kickstart/NFS/DNS/DHCP server. I've a second physical system, a PC with the VMware Workstation installed and running. I use it to boot/build 'play' virtual machines from the FC6 kickstart server. I've taken the /root/anaconda-ks.cfg file from the same FC6 system and am using it, along with all the other normal kickstart steps, to tailor a network-based build of FC6. I do basically understand how to do that, and can successfully build a Virtual Machine (under VMware Workstation v6.0 on a separate computer) with FC6. Great. Now I am cook'n. Next, I established many new directory names, unique for each OS, established them each/all basically the same as for FC6, into that same FC6 kickstart server. The list follows for each of the OS's I'm working with. RHEL WS3u0 x32 RHEL WS3u1 x32 RHEL WS3u2 x32 RHEL WS3u3 x32 RHEL WS3u4 x32 RHEL WS3u5 x32 RHEL WS3u6 x32 RHEL WS3u7 x32 RHEL WS3u8 x32 RHEL WS3u9 x32 {And conceivably back to the 2.1 versions, too} RHEL WS3u0 x64 RHEL WS3u1 x64 RHEL WS3u2 x64 RHEL WS3u3 x64 RHEL WS3u4 x64 RHEL WS3u5 x64 RHEL WS3u6 x64 RHEL WS3u7 x64 RHEL WS3u8 x64 RHEL WS3u9 x64 {And conceivably back to the 2.1 versions, too} RHEL WS4u0 x32 RHEL WS4u1 x32 RHEL WS4u2 x32 RHEL WS4u3 x32 RHEL WS4u4 x32 RHEL WS4u5 x32 RHEL WS4u0 x64 RHEL WS4u1 x64 RHEL WS4u2 x64 RHEL WS4u3 x64 RHEL WS4u4 x64 RHEL WS4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL ES3u0 x32 RHEL ES3u1 x32 RHEL ES3u2 x32 RHEL ES3u3 x32 RHEL ES3u4 x32 RHEL ES3u5 x32 RHEL ES3u6 x32 RHEL ES3u7 x32 RHEL ES3u8 x32 RHEL ES3u9 x32 {And conceivably back to the 2.1 versions} RHEL ES3u0 x64 RHEL ES3u1 x64 RHEL ES3u2 x64 RHEL ES3u3 x64 RHEL ES3u4 x64 RHEL ES3u5 x64 RHEL ES3u6 x64 RHEL ES3u7 x64 RHEL ES3u8 x64 RHEL ES3u9 x64 {And conceivably back to the 2.1 versions} RHEL ES4u0 x32 RHEL ES4u1 x32 RHEL ES4u2 x32 RHEL ES4u3 x32 RHEL ES4u4 x32 RHEL ES4u5 x32 RHEL ES4u0 x64 RHEL ES4u1 x64 RHEL ES4u2 x64 RHEL ES4u3 x64 RHEL ES4u4 x64 RHEL ES4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL AS3u0 x32 RHEL AS3u1 x32 RHEL AS3u2 x32 RHEL AS3u3 x32 RHEL AS3u4 x32 RHEL AS3u5 x32 RHEL AS3u6 x32 RHEL AS3u7 x32 RHEL AS3u8 x32 RHEL AS3u9 x32 {And conceivably back to the 2.1 versions} RHEL AS3u0 x64 RHEL AS3u1 x64 RHEL AS3u2 x64 RHEL AS3u3 x64 RHEL AS3u4 x64 RHEL AS3u5 x64 RHEL AS3u6 x64 RHEL AS3u7 x64 RHEL AS3u8 x64 RHEL AS3u9 x64 {And conceivably back to the 2.1 versions} RHEL AS4u0 x32 RHEL AS4u1 x32 RHEL AS4u2 x32 RHEL AS4u3 x32 RHEL AS4u4 x32 RHEL AS4u5 x32 RHEL AS4u0 x64 RHEL AS4u1 x64 RHEL AS4u2 x64 RHEL AS4u3 x64 RHEL AS4u4 x64 RHEL AS4u5 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx RHEL AS5u0 x32 RHEL AS5u0 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx FC1 x32 FC2 x32 FC3 x32 FC4 x32 FC5 x32 FC6 x32 FC1 x64 FC2 x64 FC3 x64 FC4 x64 FC5 x64 FC6 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Fedora 7 x32 Fedora 7 x64 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx These are all for the Intel architecture, as that is all I have available. I'd do other architectures too (zSeries, Itanium and S/390) if someone wishes to loan me the equipment for the next year or so. My question is this: How do I dynamically build OS-specific kickstart anaconda-ks.cfg files for EACH of them without having to waste tons of hours manually installing each one simply to get that one file out of it??? I would have thought the kickstart GUI would have had something to allow the operator to 'select' which OS from the multitudes possible, that it would now be looking at. If such a capability exists, I'm unable to find it. I seek to devote more of my time to developing/polishing the post-installation area(s) than basic OS building. I have the disk resources to support hosting all the native files for each of the OS's I've listed above. Additionally, I've the disk resources to support hosting each of the OS's as they get built, to include snapshots and checkpoints, within VMware virtual machines. I have all the ISO's for each them as well. I have a 64 bit Intel system for virtual building of OS's. I have a task which requires testing various capabilities against each of these OSs, and uniquely against each of the various update/releases, thus this is why I'm approaching kickstart from such a broad perspective. I'm simply unsure on how to properly go about it. So, how do I manage kickstart building for any OS I wish to pick, and have the resultant anaconda-ks.cfg file work correctly for the chosen OS, when I'm building tons of machines 'virtually'? Do the kickstart tools in existence today facilitate this (it doesn't seem like they do)? If not, what manual method is needed? Is there a resource or two on the net that would facilitate what I'm seeking to learn? Thank you very much in advance for your help. R, -Joe Wulf, CISSP, USN(RET) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdehaan at redhat.com Mon Jul 2 16:04:36 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 02 Jul 2007 12:04:36 -0400 Subject: How-to info needed for multiple instances of RH OS's and multiple unique versions {to be kickstarted} In-Reply-To: References: Message-ID: <46892214.1040407@redhat.com> Shabazian, Chip wrote: > Well, first of all, you can dispense with the WS/ES/AS redundancy. +1. > The only difference between them is what gets installed in package > groups and the redhat-release rpm. For testing binary compatibility, > you can simply test any of the WS/ES/AS versions. In fact, depending > on your kickstart, it's possible you get the exact same build from > each one (I do using our kickstart). > > I would probably just take my kickstart file, replace the install > source with something unique such as INSTALL_SOURCE_HERE, then do a > "for `ls /dir/of/your/install/trees`" loop using perl or sed to change > the INSTALL_SOURCE_HERE to the proper directory name and create > kickstart files for each release. You could then simply use > ks=method:/path_to_kickstarts/release.cfg. > > It may be a bit simplistic, but it's quick and should work just fine. > Any issues you run into can be fixed in the specific release kickstart > file. > > Although Cobbler is an excellent tool (and I highly recommend it for > anyone setting up a build infrastructure), it sounds like more setup > than you need for this project. > Managing an large set of distros and then assigning kickstarts to them is kind of what I designed it for :). Regardless of the size of your setup, it still should be faster than making changes to /tftpboot and the kickstart files once set up -- and even that should only take a few minutes -- no scripting required. Back on the kickstart topic, it turns out that kickstarts for RHEL3/4/FC5 for base installs are reasonably the same, with the exception of the ability to specify yum repositories in the kickstart which is new in FC6/RHEL5, and the install key logic that is new in RHEL5. Cobbler uses Cheetah for this, so you can template out those specific parts based on what distro you are running. cobbler distro add --name=d1 --ksmeta="type=rhel4" cobbler distro add --name=d2 --ksmeta="type=rhel5" In the kickstart file .. blah ... #if $type == "rhel5" key --skip #end .. blah ... cobbler profile add --name=p1 --distro=d1 --kickstart=/path/to/same/ks.cfg cobbler profile add --name=p2 --distro=d2 --kickstart=/path/to/same/ks.cfg You can feed whatever variables you need into --ksmeta that you would want. > Chip > > ------------------------------------------------------------------------ > *From:* kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] *On Behalf Of *Joe_Wulf > *Sent:* Saturday, June 30, 2007 10:45 PM > *To:* kickstart-list at redhat.com > *Subject:* How-to info needed for multiple instances of RH OS's and > multiple unique versions {to be kickstarted} > > Hi. I'm a new member of the list, recently joined about a week ago. > I could really use some help regarding kickstart. > > I have one physical system running FC6. It is set up as my > kickstart/NFS/DNS/DHCP server. I've a second physical > system, a PC with the VMware Workstation installed and running. I use > it to boot/build 'play' virtual machines from the > FC6 kickstart server. > > I've taken the /root/anaconda-ks.cfg file from the same FC6 system and > am using it, along with all the other normal > kickstart steps, to tailor a network-based build of FC6. I do > basically understand how to do that, and can successfully > build a Virtual Machine (under VMware Workstation v6.0 on a separate > computer) with FC6. Great. Now I am cook'n. > > Next, I established many new directory names, unique for each > OS, established them each/all basically the same as for > FC6, into that same FC6 kickstart server. The list follows for each > of the OS's I'm working with. > > > RHEL WS3u0 x32 > RHEL WS3u1 x32 > RHEL WS3u2 x32 > RHEL WS3u3 x32 > RHEL WS3u4 x32 > RHEL WS3u5 x32 > RHEL WS3u6 x32 > RHEL WS3u7 x32 > RHEL WS3u8 x32 > RHEL WS3u9 x32 {And conceivably back to the 2.1 versions, too} > > > RHEL WS3u0 x64 > RHEL WS3u1 x64 > RHEL WS3u2 x64 > RHEL WS3u3 x64 > RHEL WS3u4 x64 > RHEL WS3u5 x64 > RHEL WS3u6 x64 > RHEL WS3u7 x64 > RHEL WS3u8 x64 > RHEL WS3u9 x64 {And conceivably back to the 2.1 versions, too} > > > RHEL WS4u0 x32 > RHEL WS4u1 x32 > RHEL WS4u2 x32 > RHEL WS4u3 x32 > RHEL WS4u4 x32 > RHEL WS4u5 x32 > > RHEL WS4u0 x64 > RHEL WS4u1 x64 > RHEL WS4u2 x64 > RHEL WS4u3 x64 > RHEL WS4u4 x64 > RHEL WS4u5 x64 > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > RHEL ES3u0 x32 > RHEL ES3u1 x32 > RHEL ES3u2 x32 > RHEL ES3u3 x32 > RHEL ES3u4 x32 > RHEL ES3u5 x32 > RHEL ES3u6 x32 > RHEL ES3u7 x32 > RHEL ES3u8 x32 > RHEL ES3u9 x32 {And conceivably back to the 2.1 versions} > > > RHEL ES3u0 x64 > RHEL ES3u1 x64 > RHEL ES3u2 x64 > RHEL ES3u3 x64 > RHEL ES3u4 x64 > RHEL ES3u5 x64 > RHEL ES3u6 x64 > RHEL ES3u7 x64 > RHEL ES3u8 x64 > RHEL ES3u9 x64 {And conceivably back to the 2.1 versions} > > > RHEL ES4u0 x32 > RHEL ES4u1 x32 > RHEL ES4u2 x32 > RHEL ES4u3 x32 > RHEL ES4u4 x32 > RHEL ES4u5 x32 > > RHEL ES4u0 x64 > RHEL ES4u1 x64 > RHEL ES4u2 x64 > RHEL ES4u3 x64 > RHEL ES4u4 x64 > RHEL ES4u5 x64 > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > RHEL AS3u0 x32 > RHEL AS3u1 x32 > RHEL AS3u2 x32 > RHEL AS3u3 x32 > RHEL AS3u4 x32 > RHEL AS3u5 x32 > RHEL AS3u6 x32 > RHEL AS3u7 x32 > RHEL AS3u8 x32 > RHEL AS3u9 x32 {And conceivably back to the 2.1 versions} > > > RHEL AS3u0 x64 > RHEL AS3u1 x64 > RHEL AS3u2 x64 > RHEL AS3u3 x64 > RHEL AS3u4 x64 > RHEL AS3u5 x64 > RHEL AS3u6 x64 > RHEL AS3u7 x64 > RHEL AS3u8 x64 > RHEL AS3u9 x64 {And conceivably back to the 2.1 versions} > > > > RHEL AS4u0 x32 > RHEL AS4u1 x32 > RHEL AS4u2 x32 > RHEL AS4u3 x32 > RHEL AS4u4 x32 > RHEL AS4u5 x32 > > RHEL AS4u0 x64 > RHEL AS4u1 x64 > RHEL AS4u2 x64 > RHEL AS4u3 x64 > RHEL AS4u4 x64 > RHEL AS4u5 x64 > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > RHEL AS5u0 x32 > RHEL AS5u0 x64 > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > FC1 x32 > FC2 x32 > FC3 x32 > FC4 x32 > FC5 x32 > FC6 x32 > > > FC1 x64 > FC2 x64 > FC3 x64 > FC4 x64 > FC5 x64 > FC6 x64 > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > Fedora 7 x32 > > Fedora 7 x64 > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > These are all for the Intel architecture, as that is all I have > available. I'd do other architectures too (zSeries, Itanium > and S/390) if someone wishes to loan me the equipment for the next > year or so. > > > *_My question is this_*: > How do I dynamically build OS-specific kickstart anaconda-ks.cfg files > for EACH of them without having to waste > tons of hours manually installing each one simply to get that one file > out of it??? I would have thought the kickstart > GUI would have had something to allow the operator to 'select' which > OS from the multitudes possible, that it would > now be looking at. If such a capability exists, I'm unable to find it. > > I seek to devote more of my time to developing/polishing the > post-installation area(s) than basic OS building. > > I have the disk resources to support hosting all the native files for > each of the OS's I've listed above. Additionally, > I've the disk resources to support hosting each of the OS's as they > get built, to include snapshots and checkpoints, > within VMware virtual machines. I have all the ISO's for each them as > well. I have a 64 bit Intel system for virtual > building of OS's. I have a task which requires testing various > capabilities against each of these OSs, and uniquely > against each of the various update/releases, thus this is why I'm > approaching kickstart from such a broad perspective. > I'm simply unsure on how to properly go about it. > > So, how do I manage kickstart building for any OS I wish to pick, and > have the resultant anaconda-ks.cfg file work > correctly for the chosen OS, when I'm building tons of machines > 'virtually'? Do the kickstart tools in existence today > facilitate this (it doesn't seem like they do)? If not, what manual > method is needed? Is there a resource or two on > the net that would facilitate what I'm seeking to learn? > > Thank you very much in advance for your help. > > R, > -Joe Wulf, CISSP, USN(RET) > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Matt.Fahrner at coat.com Mon Jul 2 17:19:34 2007 From: Matt.Fahrner at coat.com (Matt Fahrner) Date: Mon, 02 Jul 2007 13:19:34 -0400 Subject: Loading device firmware in kickstart In-Reply-To: <4684B4C2.2080408@zot.com> References: <4681298D.2010001@coat.com> <4681A579.1090508@herakles.homelinux.org> <4682736A.5080804@coat.com> <4684B4C2.2080408@zot.com> Message-ID: <468933A6.20603@coat.com> Thanks - I believe you are right from what I'm seeing. As I've struggled through this, it appears to simply be a generic i586 kernel... Thanks again, - Matt Chris Edillon wrote: > Matt Fahrner wrote: > >> Unfortunately I haven't done this for a while and FC6 is a bit of a >> learning curve. It used to be easier because you could just use the >> "BOOT" kernel config - I have no idea where this is pulled no (it >> appears perhaps to be a generic i586 kernel in "boot.iso" - at least >> generic i586 modules seem to work with it for versioning). >> > i believe that the BOOT kernel was used in RHEL3 and prior, > and that starting with RHEL4 the pxeboot kernel is the standard > RHEL4 single-processor kernel. > > chris > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- --------------------------------------------------------------------- Matt Fahrner 2 South Park St. Chief Systems Architect Willis House Burlington Coat Factory Warehouse Lebanon, N.H. 03766 Tel: (603) 448-4100 x5150 USA Fax: (603) 443-6190 Matt.Fahrner at COAT.COM --------------------------------------------------------------------- From Colin.Coe at woodside.com.au Fri Jul 6 01:25:43 2007 From: Colin.Coe at woodside.com.au (Coe, Colin C. (Unix Engineer)) Date: Fri, 6 Jul 2007 09:25:43 +0800 Subject: Anaconda 11.1.2.36 Message-ID: Hi all I'm in the process of looking at migrating my RedHat Satellite based RHEL3 kickstarts to RHEL5. Previously, I've always had a '%include /tmp/partition.cfg' and code in the %pre script to determine what '/tmp/partition.cfg' looks like. What I'm finding now is Anaconda/KickStart is complaining about /tmp/partition.cfg being missing before the %pre script has run. Any ideas on whats going on with this? Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chip.Shabazian at bankofamerica.com Fri Jul 6 17:27:49 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 06 Jul 2007 10:27:49 -0700 Subject: Anaconda 11.1.2.36 In-Reply-To: Message-ID: I'm using %include in my command section just fine. If you post your scripting, we can look for obvious errors, but the best thing to do would be to simply put: sleep 999999999 in your %pre and then open a terminal (alt-f2) and walk through the pre manually to see where it fails. Chip ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Coe, Colin C. (Unix Engineer) Sent: Thursday, July 05, 2007 6:26 PM To: Discussion list about Kickstart Subject: Anaconda 11.1.2.36 Hi all I'm in the process of looking at migrating my RedHat Satellite based RHEL3 kickstarts to RHEL5. Previously, I've always had a '%include /tmp/partition.cfg' and code in the %pre script to determine what '/tmp/partition.cfg' looks like. What I'm finding now is Anaconda/KickStart is complaining about /tmp/partition.cfg being missing before the %pre script has run. Any ideas on whats going on with this? Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chip.Shabazian at bankofamerica.com Fri Jul 6 18:13:13 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 06 Jul 2007 11:13:13 -0700 Subject: Kickstart Tips and Tricks In-Reply-To: Message-ID: All, As promised, I have finally completed the presentation for LinuxWorld and welcome feedback and corrections: http://www.shabazian.com/lw2007.pdf Thanks, and I hope it's useful to someone. Chip -------------- next part -------------- An HTML attachment was scrubbed... URL: From drkludge at cox.net Sun Jul 8 09:11:18 2007 From: drkludge at cox.net (Greg Morgan) Date: Sun, 08 Jul 2007 02:11:18 -0700 Subject: Kickstart Tips and Tricks In-Reply-To: References: Message-ID: <4690AA36.6010808@cox.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shabazian, Chip wrote: > All, > > As promised, I have finally completed the presentation for LinuxWorld > and welcome feedback and corrections: > > http://www.shabazian.com/lw2007.pdf > > Thanks, and I hope it's useful to someone. > > Chip > I am not sure how this will be presented. However, when I used xpdf to review the document, the code examples were "washed" out. I could see the code samples better, once I viewed the file at 200%. My monitor settings are 1280 by 1024. That setting may highlight a problem your presentation hall viewers will have. I would suggest using a bold fix text font for those sections of the document. Perhaps a font size adjustment would also help, if you can still fit you code segments on the same page. Your title says "Tips and Tricks". I don't get to hear you present so much of the "glue presentation" is missing for me as I review the document. When I blitzed through the document the first time, I was wondering what the difference between the main part and the appendices? That comes from a programmer looking at another alphabetic api looking document. With that being said, how can you set off your tip and trick sections so that I can focus on these? This may be an audience question for you. For people that have clicked themselves through several server installations, finding out about anaconda is a major tip. If you're going for the newbie crowd, then you may have hit the mark. If you're going for the advanced crowd, then covering more of the struggles that you see on the kickstart list would be helpful. At what level do your tips and tricks hit home? Since you are talking about imaging hard drives, is stateless linux worth putting in too http://fedoraproject.org/wiki/StatelessLinux or are these technologies that you have used? It is nice that B of A supports your efforts. Tell 'em thanks. HTH, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGkKo1xyxe5L6mr7IRAjrVAKCHIFbD3iQAxd6Ijv+H8ndC4G27aQCfX0io RSIb2WZ2Fgk+bJ+YXW1nP2E= =k5cW -----END PGP SIGNATURE----- From jim at rossberry.com Sun Jul 8 10:46:11 2007 From: jim at rossberry.com (Jim Wildman) Date: Sun, 8 Jul 2007 06:46:11 -0400 (EDT) Subject: Kickstart Tips and Tricks In-Reply-To: <4690AA36.6010808@cox.net> References: <4690AA36.6010808@cox.net> Message-ID: On Sun, 8 Jul 2007, Greg Morgan wrote: > I am not sure how this will be presented. However, when I used xpdf to > review the document, the code examples were "washed" out. I could see > the code samples better, once I viewed the file at 200%. My monitor > settings are 1280 by 1024. That setting may highlight a problem your > presentation hall viewers will have. I would suggest using a bold fix > text font for those sections of the document. Perhaps a font size > adjustment would also help, if you can still fit you code segments on > the same page. > I had the same problem using evince to view the document. ------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine From Colin.Coe at woodside.com.au Sun Jul 8 22:53:59 2007 From: Colin.Coe at woodside.com.au (Coe, Colin C. (Unix Engineer)) Date: Mon, 9 Jul 2007 06:53:59 +0800 Subject: Anaconda 11.1.2.36 In-Reply-To: Message-ID: Hi Yep, tried that, It fails with "/tmp/partition.cfg not found". The sleep at the top of the %pre script is not executed. Does the partition need to be provided prior to the %pre script nowdays? CC ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Saturday, 7 July 2007 1:28 AM To: Discussion list about Kickstart Subject: RE: Anaconda 11.1.2.36 I'm using %include in my command section just fine. If you post your scripting, we can look for obvious errors, but the best thing to do would be to simply put: sleep 999999999 in your %pre and then open a terminal (alt-f2) and walk through the pre manually to see where it fails. Chip ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Coe, Colin C. (Unix Engineer) Sent: Thursday, July 05, 2007 6:26 PM To: Discussion list about Kickstart Subject: Anaconda 11.1.2.36 Hi all I'm in the process of looking at migrating my RedHat Satellite based RHEL3 kickstarts to RHEL5. Previously, I've always had a '%include /tmp/partition.cfg' and code in the %pre script to determine what '/tmp/partition.cfg' looks like. What I'm finding now is Anaconda/KickStart is complaining about /tmp/partition.cfg being missing before the %pre script has run. Any ideas on whats going on with this? Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jb at smarterliving.com Mon Jul 9 02:01:18 2007 From: jb at smarterliving.com (JB Segal) Date: Sun, 08 Jul 2007 22:01:18 -0400 Subject: Automated generation of installed packages list? (RHEL5) Message-ID: <469196EE.60200@smarterliving.com> A somewhat more than cursory glance at the archives doesn't show the answer to this... At the end of a manually-configured install, where I spent a reasonable amount of time going through the available packages, picking those I wanted, and those I didn't, the only evidence of this left in the anaconda-ks.cfg is the wholly-insubstantial lines %packages @editors and that's IT. A) Would anyone like to guess whether this is a bug, a design lacuna, or a 'feature'? B) Is there any way to generate an appropriate ks.cfg based upon this system? While it seems that the KS docs have been revised and updated for RHEL5, at this hour on a Sunday, I'm not managing to find anything about reverse-engineering a package list, nor anything about why I should ever NEED to do that. Thanks for any help or suggestions you can give, JB From jason at rampaginggeek.com Mon Jul 9 02:18:01 2007 From: jason at rampaginggeek.com (Jason Edgecombe) Date: Sun, 08 Jul 2007 22:18:01 -0400 Subject: Automated generation of installed packages list? (RHEL5) In-Reply-To: <469196EE.60200@smarterliving.com> References: <469196EE.60200@smarterliving.com> Message-ID: <46919AD9.9090109@rampaginggeek.com> JB Segal wrote: > A somewhat more than cursory glance at the archives doesn't show the > answer to this... > At the end of a manually-configured install, where I spent a > reasonable amount of time > going through the available packages, picking those I wanted, and > those I didn't, the only > evidence of this left in the anaconda-ks.cfg is the > wholly-insubstantial lines > %packages > @editors > > and that's IT. > > A) Would anyone like to guess whether this is a bug, a design lacuna, > or a 'feature'? > B) Is there any way to generate an appropriate ks.cfg based upon this > system? > > While it seems that the KS docs have been revised and updated for > RHEL5, at this hour on > a Sunday, I'm not managing to find anything about reverse-engineering > a package list, nor > anything about why I should ever NEED to do that. > > Thanks for any help or suggestions you can give, run "rpm -qa" on the installed system. That will generate a package list for you. Jason From rvandolson at esri.com Mon Jul 9 15:09:01 2007 From: rvandolson at esri.com (Ray Van Dolson) Date: Mon, 9 Jul 2007 08:09:01 -0700 Subject: Kickstart Tips and Tricks In-Reply-To: References: <4690AA36.6010808@cox.net> Message-ID: <20070709150900.GA20897@esri.com> On Sun, Jul 08, 2007 at 06:46:11AM -0400, Jim Wildman wrote: > >I am not sure how this will be presented. However, when I used xpdf to > >review the document, the code examples were "washed" out. I could see > >the code samples better, once I viewed the file at 200%. My monitor > >settings are 1280 by 1024. That setting may highlight a problem your > >presentation hall viewers will have. I would suggest using a bold fix > >text font for those sections of the document. Perhaps a font size > >adjustment would also help, if you can still fit you code segments on > >the same page. > > > > I had the same problem using evince to view the document. Worked fine for me (FYI) on F7 with whatever is the default Document Viewer for PDF. :) Ray From Chip.Shabazian at bankofamerica.com Mon Jul 9 17:08:29 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 09 Jul 2007 10:08:29 -0700 Subject: Anaconda 11.1.2.36 In-Reply-To: Message-ID: I believe you will run into this when the %pre has a bash error in it somewhere. Either comment out the entire %pre (except for the sleep) or run it through kickstart-validator to see what it reports. ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Coe, Colin C. (Unix Engineer) Sent: Sunday, July 08, 2007 3:54 PM To: Discussion list about Kickstart Subject: RE: Anaconda 11.1.2.36 Hi Yep, tried that, It fails with "/tmp/partition.cfg not found". The sleep at the top of the %pre script is not executed. Does the partition need to be provided prior to the %pre script nowdays? CC ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Saturday, 7 July 2007 1:28 AM To: Discussion list about Kickstart Subject: RE: Anaconda 11.1.2.36 I'm using %include in my command section just fine. If you post your scripting, we can look for obvious errors, but the best thing to do would be to simply put: sleep 999999999 in your %pre and then open a terminal (alt-f2) and walk through the pre manually to see where it fails. Chip ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Coe, Colin C. (Unix Engineer) Sent: Thursday, July 05, 2007 6:26 PM To: Discussion list about Kickstart Subject: Anaconda 11.1.2.36 Hi all I'm in the process of looking at migrating my RedHat Satellite based RHEL3 kickstarts to RHEL5. Previously, I've always had a '%include /tmp/partition.cfg' and code in the %pre script to determine what '/tmp/partition.cfg' looks like. What I'm finding now is Anaconda/KickStart is complaining about /tmp/partition.cfg being missing before the %pre script has run. Any ideas on whats going on with this? Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jb at smarterliving.com Mon Jul 9 17:10:11 2007 From: jb at smarterliving.com (JB Segal) Date: Mon, 9 Jul 2007 13:10:11 -0400 Subject: Automated generation of installed packages list? (RHEL5) In-Reply-To: <46919AD9.9090109@rampaginggeek.com> References: <469196EE.60200@smarterliving.com> <46919AD9.9090109@rampaginggeek.com> Message-ID: <20070709171010.GO6001@smarterliving.com> Quoth Jason Edgecombe (jason at rampaginggeek.com): > JB Segal wrote: > >A somewhat more than cursory glance at the archives doesn't show the answer to this... > >At the end of a manually-configured install, where I spent a reasonable amount of time > >going through the available packages, picking those I wanted, and those I didn't, the only > >evidence of this left in the anaconda-ks.cfg is the wholly-insubstantial lines > >%packages > >@editors > > > >and that's IT. > > > >A) Would anyone like to guess whether this is a bug, a design lacuna, or a 'feature'? > >B) Is there any way to generate an appropriate ks.cfg based upon this system? > > > >While it seems that the KS docs have been revised and updated for RHEL5, at this hour on > >a Sunday, I'm not managing to find anything about reverse-engineering a package list, nor > >anything about why I should ever NEED to do that. > > > >Thanks for any help or suggestions you can give, > run "rpm -qa" on the installed system. That will generate a package list for you. > Yes. Sorry, I was more thinking of something in a default ks.cfg format, with the groups that are installed, and the modifications to those groups - for example, with RHEL4, I got the following in the autogenerated file: %packages --resolvedeps @ editors @ emacs @ system-tools @ dialup @ ftp-server @ emacs @ server-cfg @ development-tools kernel-smp -bluez-pin e2fsprogs lvm2 -httpd-manual -distcache -uucp -samba-client -x3270-x11 -php -cvs kernel-devel -rcs kernel-smp-devel -xdelta -valgrind -valgrind-callgrind and I was hoping for something more like that. (Actually, it's not impossible that some number of the '-package' lines were manually configured by me. I'm not certain anymore... but still, I know the '@ group' lines WEREN'T, and the fact that RHEL5 doesn't provide those I figure MUST be a bug.) I'll go digging through bugzilla today to see what's already been filed... From Chip.Shabazian at bankofamerica.com Mon Jul 9 17:32:34 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 09 Jul 2007 10:32:34 -0700 Subject: Kickstart Tips and Tricks In-Reply-To: <4690AA36.6010808@cox.net> Message-ID: Thanks for the input. I have just used Acrobat to view the file (it was created in OOo, saved as a .pdf, and "stacked" so that it was all one file). I'll see about making it xpdf friendly. The single .pdf file was for the LinuxWorld staff so that they had a single file to print and got it in the right order (this will be handed out in hard copy format to all who attend). The presentation will be just the slides in OOo so I won't have all the white space below and the washed out look won't be there. The main part of the presentation is what I will be showing during the presentation. The appendixes are simply there because I know that I've always wanted a nice printed copy of those options, and this was an opportunity to put it in paper form for people with Red Hat's blessing. As for audience, I really don't know unfortunately. Based on past tutorials I have attended at LinuxWorld, most assume no knowledge of the subject they are presenting unless it's called "Advanced so and so". With that in mind, I did lean towards newbies a bit. Also, I have 3 hours, so I figure I'll get through the slides in 2 hours and leave an hour to work on specific technical issues that attendees may have. All that said, once I get a feel for the crowd, I'll make changes as appropriate for the next LinuxWorld in Boston. That's the problem going in blind, I have NO idea what my target audience is going to be :( I'll mention stateless, it just didn't cross my mind! And yes, BofA has been great in giving me time, space, and corporate approval to build a kickstart infrastructure and be able to present back what I've learned. Thanks again! Chip -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Greg Morgan Sent: Sunday, July 08, 2007 2:11 AM To: Discussion list about Kickstart Subject: Re: Kickstart Tips and Tricks -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Shabazian, Chip wrote: > All, > > As promised, I have finally completed the presentation for LinuxWorld > and welcome feedback and corrections: > > http://www.shabazian.com/lw2007.pdf > > Thanks, and I hope it's useful to someone. > > Chip > I am not sure how this will be presented. However, when I used xpdf to review the document, the code examples were "washed" out. I could see the code samples better, once I viewed the file at 200%. My monitor settings are 1280 by 1024. That setting may highlight a problem your presentation hall viewers will have. I would suggest using a bold fix text font for those sections of the document. Perhaps a font size adjustment would also help, if you can still fit you code segments on the same page. Your title says "Tips and Tricks". I don't get to hear you present so much of the "glue presentation" is missing for me as I review the document. When I blitzed through the document the first time, I was wondering what the difference between the main part and the appendices? That comes from a programmer looking at another alphabetic api looking document. With that being said, how can you set off your tip and trick sections so that I can focus on these? This may be an audience question for you. For people that have clicked themselves through several server installations, finding out about anaconda is a major tip. If you're going for the newbie crowd, then you may have hit the mark. If you're going for the advanced crowd, then covering more of the struggles that you see on the kickstart list would be helpful. At what level do your tips and tricks hit home? Since you are talking about imaging hard drives, is stateless linux worth putting in too http://fedoraproject.org/wiki/StatelessLinux or are these technologies that you have used? It is nice that B of A supports your efforts. Tell 'em thanks. HTH, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGkKo1xyxe5L6mr7IRAjrVAKCHIFbD3iQAxd6Ijv+H8ndC4G27aQCfX0io RSIb2WZ2Fgk+bJ+YXW1nP2E= =k5cW -----END PGP SIGNATURE----- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From lippold at gmail.com Mon Jul 9 22:35:54 2007 From: lippold at gmail.com (Aaron Lippold) Date: Tue, 10 Jul 2007 00:35:54 +0200 Subject: Automated generation of installed packages list? (RHEL5) In-Reply-To: <20070709171010.GO6001@smarterliving.com> References: <469196EE.60200@smarterliving.com> <46919AD9.9090109@rampaginggeek.com> <20070709171010.GO6001@smarterliving.com> Message-ID: <39d2723b0707091535h1fdb255fo9d490694d0f71f9b@mail.gmail.com> Cross posting ... my bad but I thought for sure you guys would have already had to address this issue with Revisor.... given the output of rpm -qa can pykickstart work with the comps.xml file to create a 'grouped and minus' package list? Hi, I have been messing with Revisor - a FedoraCommunity project - and it uses pykickstart which may - using the comps.xml file be able to generate a list like that for you. Email the revisor list and see if anyone smart with the code could give you some quick python to do it. Aaron On 7/9/07, JB Segal wrote: > Quoth Jason Edgecombe (jason at rampaginggeek.com): > > JB Segal wrote: > > >A somewhat more than cursory glance at the archives doesn't show the answer to this... > > >At the end of a manually-configured install, where I spent a reasonable amount of time > > >going through the available packages, picking those I wanted, and those I didn't, the only > > >evidence of this left in the anaconda-ks.cfg is the wholly-insubstantial lines > > >%packages > > >@editors > > > > > >and that's IT. > > > > > >A) Would anyone like to guess whether this is a bug, a design lacuna, or a 'feature'? > > >B) Is there any way to generate an appropriate ks.cfg based upon this system? > > > > > >While it seems that the KS docs have been revised and updated for RHEL5, at this hour on > > >a Sunday, I'm not managing to find anything about reverse-engineering a package list, nor > > >anything about why I should ever NEED to do that. > > > > > >Thanks for any help or suggestions you can give, > > run "rpm -qa" on the installed system. That will generate a package list for you. > > > > Yes. Sorry, I was more thinking of something in a default ks.cfg format, > with the groups that are installed, and the modifications to those > groups - for example, with RHEL4, I got the following in the > autogenerated file: > > %packages --resolvedeps > @ editors > @ emacs > @ system-tools > @ dialup > @ ftp-server > @ emacs > @ server-cfg > @ development-tools > kernel-smp > -bluez-pin > e2fsprogs > lvm2 > -httpd-manual > -distcache > -uucp > -samba-client > -x3270-x11 > -php > -cvs > kernel-devel > -rcs > kernel-smp-devel > -xdelta > -valgrind > -valgrind-callgrind > > and I was hoping for something more like that. (Actually, it's not > impossible that some number of the '-package' lines were manually > configured by me. I'm not certain anymore... but still, I know the > '@ group' lines WEREN'T, and the fact that RHEL5 doesn't provide those I > figure MUST be a bug.) I'll go digging through bugzilla today to see > what's already been filed... > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From jb at smarterliving.com Tue Jul 10 18:11:51 2007 From: jb at smarterliving.com (JB Segal) Date: Tue, 10 Jul 2007 14:11:51 -0400 Subject: Automated generation of installed packages list? (RHEL5) In-Reply-To: <469196EE.60200@smarterliving.com> References: <469196EE.60200@smarterliving.com> Message-ID: <20070710181151.GQ6001@smarterliving.com> It seems to be a bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=227383 One that claims to be in QA, and I can but hope that r5u1 includes the fix. That said, a generating tool would be great anyway. I'll check out the one that was suggested yesterday in a bit. JB Quoth JB Segal (jb at smarterliving.com): > A somewhat more than cursory glance at the archives doesn't show the answer to this... > At the end of a manually-configured install, where I spent a reasonable amount of time > going through the available packages, picking those I wanted, and those I didn't, the only > evidence of this left in the anaconda-ks.cfg is the wholly-insubstantial lines > %packages > @editors > > and that's IT. > > A) Would anyone like to guess whether this is a bug, a design lacuna, or a 'feature'? > B) Is there any way to generate an appropriate ks.cfg based upon this system? > > While it seems that the KS docs have been revised and updated for RHEL5, at this hour on > a Sunday, I'm not managing to find anything about reverse-engineering a package list, nor > anything about why I should ever NEED to do that. > > Thanks for any help or suggestions you can give, > > JB > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- JB Segal 617-886-5575 www.smartertravel.com Systems/Network Admin. 465 Medford St. Ste 400 www.bookingbuddy.com Smarter Travel Media LLC Boston, MA 02129 www.tripmania.com From debian at herakles.homelinux.org Wed Jul 11 00:22:51 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 11 Jul 2007 08:22:51 +0800 Subject: Automated generation of installed packages list? (RHEL5) In-Reply-To: <469196EE.60200@smarterliving.com> References: <469196EE.60200@smarterliving.com> Message-ID: <469422DB.6030008@herakles.homelinux.org> JB Segal wrote: > A somewhat more than cursory glance at the archives doesn't show the > answer to this... > At the end of a manually-configured install, where I spent a reasonable > amount of time > going through the available packages, picking those I wanted, and those > I didn't, the only > evidence of this left in the anaconda-ks.cfg is the wholly-insubstantial > lines > %packages > @editors > > and that's IT. I installed a clone. I don't recall doing much package selection as I wanted to replicate my package selection from my nahant-clone out of FC3. My list looks better than my list: %packages @admin-tools @base @base-x @core @dialup @dns-server @editors @ftp-server @games @gnome-desktop @graphical-internet @graphics @java @kde-desktop @legacy-network-server @mail-server @network-server @news-server @office @printing @server-cfg @smb-server @sound-and-video @text-internet @web-server You can patch your list with rpm --qa >>anaconda-ks.cfg similar to Jason's suggestion. It's not as nice as Anaconda's doing it right, but it should be a satisfactory workaround while RH sorts out the bug report you're about to file. For anyone who's intesteded, the Summerfield technique of "upgrading" the cross-breed involved 1. Preparing a package list on nahant-clone with "rpm -qa --qf '%{name}\n' >packages" 2. Installing Tikanga-clone. 3. Configuring yum to install from the install source any other likely sources of packages such as atrpms. 4. Copying the package list 5. A loop like this: cat packages | while read p ; do yum -y install ${p};done which ran for quite some time and, to my delight, picked up such essentials as PINE. 6. Cloning users and groups from nahant-clone. 7. Copying /home > > A) Would anyone like to guess whether this is a bug, a design lacuna, or > a 'feature'? > B) Is there any way to generate an appropriate ks.cfg based upon this > system? > > While it seems that the KS docs have been revised and updated for RHEL5, > at this hour on > a Sunday, I'm not managing to find anything about reverse-engineering a > package list, nor > anything about why I should ever NEED to do that. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From robert at actual-systems.com Thu Jul 12 15:22:35 2007 From: robert at actual-systems.com (Robert J Lee) Date: Thu, 12 Jul 2007 16:22:35 +0100 Subject: Obscure errors configuring software in Kickstart %POST script Message-ID: <4696473B.9030300@actual-systems.com> Sorry if this is not strictly relevant, but I wanted to give this back to the community in some form. Since I've spent some time working this out, it might be useful to note that the permissions on the device files /dev/* are different between running an install and running a live system. If, for instance, you try to create a Postgresql database on Red Hat Enterprise 5 using "service postgres start" in a kickstart script, then it will create the pg_log directory but then fail. (Of course, the pg_log directory is left there so initdb will then refuse to create the database again, but that's by the by). The solution to this is to ensure that users other than root have whatever read/write access they need to the device files they are using. Many servers are shipped with databases and software pre-installed, and so it wouldn't surprise me if this affected other major software packages, any yet I couldn't find anything on the issue with a Google search. Maybe people are giving up and doing manual installs, or cloning disk images or something? Perhaps this could be made more prominent in the documentation? Anyway, I hope that helps someone. Getting an obscure error like "/dev/null: Permission denied" (when it was actually another device file causing the problem) isn't too easy to figure out. Robert J. Lee -- Robert Lee Java Programmer Actual Systems UK Ltd e: robert at actual-systems.com w: www.actual-systems.com t: +44 (0131) 538 8538 f: +44 (0131) 538 8539 Vat Registration No. 429422452 Registered in Scotland No. S211063 Registered Office: 9 Bankhead Drive, Edinburgh, United Kingdom,EH11 4EJ From mdehaan at redhat.com Thu Jul 12 15:54:08 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Thu, 12 Jul 2007 11:54:08 -0400 Subject: Obscure errors configuring software in Kickstart %POST script In-Reply-To: <4696473B.9030300@actual-systems.com> References: <4696473B.9030300@actual-systems.com> Message-ID: <46964EA0.6060607@redhat.com> Robert J Lee wrote: > Sorry if this is not strictly relevant, but I wanted to give this back > to the community in some form. > > Since I've spent some time working this out, it might be useful to note > that the permissions on the device files /dev/* are different between > running an install and running a live system. > > If, for instance, you try to create a Postgresql database on Red Hat > Enterprise 5 using "service postgres start" in a kickstart script, then > it will create the pg_log directory but then fail. (Of course, the > pg_log directory is left there so initdb will then refuse to create the > database again, but that's by the by). > > The solution to this is to ensure that users other than root have > whatever read/write access they need to the device files they are using. > > Many servers are shipped with databases and software pre-installed, and > so it wouldn't surprise me if this affected other major software > packages, any yet I couldn't find anything on the issue with a Google > search. > > Maybe people are giving up and doing manual installs, or cloning disk > images or something? Perhaps this could be made more prominent in the > documentation? > > Anyway, I hope that helps someone. Getting an obscure error like > "/dev/null: Permission denied" (when it was actually another device file > causing the problem) isn't too easy to figure out. > > Robert J. Lee > > Perhaps you should be configuring Postgres at firstboot, or otherwise just creating an init script that is installed in %post and then disables itself? Setting up databases in %post seems a bit heavy to me. --Michael From debian at herakles.homelinux.org Thu Jul 12 22:55:08 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 13 Jul 2007 06:55:08 +0800 Subject: Obscure errors configuring software in Kickstart %POST script In-Reply-To: <4696473B.9030300@actual-systems.com> References: <4696473B.9030300@actual-systems.com> Message-ID: <4696B14C.4060506@herakles.homelinux.org> Robert J Lee wrote: > Sorry if this is not strictly relevant, but I wanted to give this back > to the community in some form. > > Since I've spent some time working this out, it might be useful to note > that the permissions on the device files /dev/* are different between > running an install and running a live system. Given the arrival of udev and such, can't say I'm surprised. I'm with Michael: do it the first time the system boots after the install. That's when things are supposed to work. > > If, for instance, you try to create a Postgresql database on Red Hat > Enterprise 5 using "service postgres start" in a kickstart script, then > it will create the pg_log directory but then fail. (Of course, the > pg_log directory is left there so initdb will then refuse to create the > database again, but that's by the by). > > The solution to this is to ensure that users other than root have > whatever read/write access they need to the device files they are using. > > Many servers are shipped with databases and software pre-installed, and > so it wouldn't surprise me if this affected other major software > packages, any yet I couldn't find anything on the issue with a Google > search. > > Maybe people are giving up and doing manual installs, or cloning disk > images or something? Perhaps this could be made more prominent in the > documentation? > > Anyway, I hope that helps someone. Getting an obscure error like > "/dev/null: Permission denied" (when it was actually another device file > causing the problem) isn't too easy to figure out. > > Robert J. Lee > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From jaiber.john at gmail.com Wed Jul 18 09:40:49 2007 From: jaiber.john at gmail.com (jaiber john) Date: Wed, 18 Jul 2007 15:10:49 +0530 Subject: Inserting usb-storage module Message-ID: Is it possible to insert the usb-storage module during kickstart based RH5 install if it does not get automatically loaded? When I use a USB DVDROM drive to auto-install through kickstart, it stops by showing a "Driver not found. Please select the appropriate driver for the device message". Now I have to manually choose the USB Storage driver from the list and the installation goes on fine. Is there any way - kernel commandline or some entry in kickstart file to force loading usb-storage driver? Thanks, Jaiber John From thegabeman at gmail.com Wed Jul 18 09:55:02 2007 From: thegabeman at gmail.com (Gabrie) Date: Wed, 18 Jul 2007 11:55:02 +0200 Subject: Using variables in kickstart file Message-ID: Hi I'm going to install about 20 servers, which will be identical apart from hostname and IP address. To make changes in all ks files easier, I would like to start using one central batch file, that is being called from the ks.cfg file. Therefore I would like to use 2 variables containing IP and hostname. Ideally it would be something like this: ### Begin ks020.cfg VAR-IP = 10.0.0.20 VAR-HOST = vmesx020.mydomain.com network --device eth0 --bootproto static --ip $VAR-IP --netmask 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST %post # download central script lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg perl /tmp/central.cfg $VAR-IP $VAR-HOST ### End ks020.cfg In the central.cfg I would then be able to read the VAR-IP and VAR-HOST and use it for other configuration stuff. Who can tell me how to use variables in this way? I have the feeling there also is a difference between a variable in the first section (network section) and the post section???? Gabrie From lippold at gmail.com Wed Jul 18 13:07:24 2007 From: lippold at gmail.com (Aaron Lippold) Date: Wed, 18 Jul 2007 15:07:24 +0200 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: <39d2723b0707180607w7e0761e5pd03f5b0e7ab5bbce@mail.gmail.com> Hi, Checkout cobbler at : http://cobbler.et.redhat.com. It has ks templating. Using cobbler you could do exactly what you need very quickly. Aaron On 7/18/07, Gabrie wrote: > Hi > > I'm going to install about 20 servers, which will be identical apart > from hostname and IP address. To make changes in all ks files easier, > I would like to start using one central batch file, that is being > called from the ks.cfg file. Therefore I would like to use 2 variables > containing IP and hostname. > > Ideally it would be something like this: > > ### Begin ks020.cfg > VAR-IP = 10.0.0.20 > VAR-HOST = vmesx020.mydomain.com > > > > network --device eth0 --bootproto static --ip $VAR-IP --netmask > 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST > > > > %post > # download central script > lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg > > perl /tmp/central.cfg $VAR-IP $VAR-HOST > > ### End ks020.cfg > > > In the central.cfg I would then be able to read the VAR-IP and > VAR-HOST and use it for other configuration stuff. > > Who can tell me how to use variables in this way? I have the feeling > there also is a difference between a variable in the first section > (network section) and the post section???? > > Gabrie > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From Chip.Shabazian at bankofamerica.com Wed Jul 18 16:32:27 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 09:32:27 -0700 Subject: Using variables in kickstart file In-Reply-To: Message-ID: You could also add these variables to the boot: line and then pull them from /proc/cmdline in the %pre section. Just make sure you have 255 characters or less for that boot: line. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie Sent: Wednesday, July 18, 2007 2:55 AM To: Kickstart-list at redhat.com Subject: Using variables in kickstart file Hi I'm going to install about 20 servers, which will be identical apart from hostname and IP address. To make changes in all ks files easier, I would like to start using one central batch file, that is being called from the ks.cfg file. Therefore I would like to use 2 variables containing IP and hostname. Ideally it would be something like this: ### Begin ks020.cfg VAR-IP = 10.0.0.20 VAR-HOST = vmesx020.mydomain.com network --device eth0 --bootproto static --ip $VAR-IP --netmask 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST %post # download central script lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg perl /tmp/central.cfg $VAR-IP $VAR-HOST ### End ks020.cfg In the central.cfg I would then be able to read the VAR-IP and VAR-HOST and use it for other configuration stuff. Who can tell me how to use variables in this way? I have the feeling there also is a difference between a variable in the first section (network section) and the post section???? Gabrie _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From thegabeman at gmail.com Wed Jul 18 17:21:41 2007 From: thegabeman at gmail.com (Gabrie) Date: Wed, 18 Jul 2007 19:21:41 +0200 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: Would you have an example of that? I now set the variables in the %post section and then they are available in the scripts. But I can't use them in the "network" section. Gabrie On 7/18/07, Shabazian, Chip wrote: > You could also add these variables to the boot: line and then pull them > from /proc/cmdline in the %pre section. Just make sure you have 255 > characters or less for that boot: line. > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie > Sent: Wednesday, July 18, 2007 2:55 AM > To: Kickstart-list at redhat.com > Subject: Using variables in kickstart file > > Hi > > I'm going to install about 20 servers, which will be identical apart > from hostname and IP address. To make changes in all ks files easier, I > would like to start using one central batch file, that is being called > from the ks.cfg file. Therefore I would like to use 2 variables > containing IP and hostname. > > Ideally it would be something like this: > > ### Begin ks020.cfg > VAR-IP = 10.0.0.20 > VAR-HOST = vmesx020.mydomain.com > > > > network --device eth0 --bootproto static --ip $VAR-IP --netmask > 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST > > > > %post > # download central script > lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg > > perl /tmp/central.cfg $VAR-IP $VAR-HOST > > ### End ks020.cfg > > > In the central.cfg I would then be able to read the VAR-IP and VAR-HOST > and use it for other configuration stuff. > > Who can tell me how to use variables in this way? I have the feeling > there also is a difference between a variable in the first section > (network section) and the post section???? > > Gabrie > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From asheltz at us.ibm.com Wed Jul 18 18:00:19 2007 From: asheltz at us.ibm.com (Adam Sheltz) Date: Wed, 18 Jul 2007 12:00:19 -0600 Subject: Adam Sheltz is out of the office. Message-ID: I will be out of the office starting 07/13/2007 and will not return until 07/23/2007. I will respond to your message when I return, Matt Cheely will be my backup while I am away. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdehaan at redhat.com Wed Jul 18 18:13:01 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 18 Jul 2007 14:13:01 -0400 Subject: Using variables in kickstart file In-Reply-To: <39d2723b0707180607w7e0761e5pd03f5b0e7ab5bbce@mail.gmail.com> References: <39d2723b0707180607w7e0761e5pd03f5b0e7ab5bbce@mail.gmail.com> Message-ID: <469E582D.7090701@redhat.com> Aaron Lippold wrote: > Hi, > > Checkout cobbler at : http://cobbler.et.redhat.com. > > It has ks templating. > > Using cobbler you could do exactly what you need very quickly. > > Aaron > the cobbler example is just: cobbler system add --name=$mac_address --profile=$profile_name --ip=X --hostname=Y and in the kickstart you use $ip and $hostname. Additional arbitrary variables, including conditionals (if statements, etc) can be fed in through --ksmeta. > On 7/18/07, Gabrie wrote: >> Hi >> >> I'm going to install about 20 servers, which will be identical apart >> from hostname and IP address. To make changes in all ks files easier, >> I would like to start using one central batch file, that is being >> called from the ks.cfg file. Therefore I would like to use 2 variables >> containing IP and hostname. >> >> Ideally it would be something like this: >> >> ### Begin ks020.cfg >> VAR-IP = 10.0.0.20 >> VAR-HOST = vmesx020.mydomain.com >> >> >> >> network --device eth0 --bootproto static --ip $VAR-IP --netmask >> 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST >> >> >> >> %post >> # download central script >> lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg >> >> perl /tmp/central.cfg $VAR-IP $VAR-HOST >> >> ### End ks020.cfg >> >> >> In the central.cfg I would then be able to read the VAR-IP and >> VAR-HOST and use it for other configuration stuff. >> >> Who can tell me how to use variables in this way? I have the feeling >> there also is a difference between a variable in the first section >> (network section) and the post section???? >> >> Gabrie >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Chip.Shabazian at bankofamerica.com Wed Jul 18 18:15:07 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 11:15:07 -0700 Subject: Using variables in kickstart file In-Reply-To: Message-ID: in the command section, use %include /tmp/network in the %pre section, you create /tmp/network by reading /proc/cmdline and getting the settings you need. I suggest running through it manually to figure it out by putting sleep 9999999 in your %pre, or using a tool designed for this such as cobbler. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie Sent: Wednesday, July 18, 2007 10:22 AM To: Discussion list about Kickstart Subject: Re: Using variables in kickstart file Would you have an example of that? I now set the variables in the %post section and then they are available in the scripts. But I can't use them in the "network" section. Gabrie On 7/18/07, Shabazian, Chip wrote: > You could also add these variables to the boot: line and then pull > them from /proc/cmdline in the %pre section. Just make sure you have > 255 characters or less for that boot: line. > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie > Sent: Wednesday, July 18, 2007 2:55 AM > To: Kickstart-list at redhat.com > Subject: Using variables in kickstart file > > Hi > > I'm going to install about 20 servers, which will be identical apart > from hostname and IP address. To make changes in all ks files easier, > I would like to start using one central batch file, that is being > called from the ks.cfg file. Therefore I would like to use 2 variables > containing IP and hostname. > > Ideally it would be something like this: > > ### Begin ks020.cfg > VAR-IP = 10.0.0.20 > VAR-HOST = vmesx020.mydomain.com > > > > network --device eth0 --bootproto static --ip $VAR-IP --netmask > 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST > > > > %post > # download central script > lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg > > perl /tmp/central.cfg $VAR-IP $VAR-HOST > > ### End ks020.cfg > > > In the central.cfg I would then be able to read the VAR-IP and > VAR-HOST and use it for other configuration stuff. > > Who can tell me how to use variables in this way? I have the feeling > there also is a difference between a variable in the first section > (network section) and the post section???? > > Gabrie > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From ebrown at lanl.gov Wed Jul 18 19:10:09 2007 From: ebrown at lanl.gov (Ed Brown) Date: Wed, 18 Jul 2007 13:10:09 -0600 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: <469E6591.6090200@lanl.gov> Cobbler might be a bigger hammer than is needed, and PXE/DHCP isn't always an option, especially in distributed network environments. If you're installing the OS over the network (as opposed to cd's), and are able to burn/boot from cd to initiate the install, there's possibly not a simpler approach to kickstarting and static ip addressing than to make a boot cd with a custom syslinux.cfg file with the common boot parameters (method, ks, netmask, dns) and just provide the ip and gateway at the anaconda 'boot:' prompt. in your kickstart file: network --bootproto=static copy the isolinux/ directory from your distro edit isolinux/isolinux.cfg and create custom entry: label custom kernel vmlinuz append initrd=initrd.img text nofb dns=your.nameserver.ip netmask=255.255.255.0 ks= method= make a bootable iso: mkisofs -o boot.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -T -v isolinux/ burn cd: cdrecord boot.iso to install, boot from cd, and enter arguments at boot prompt boot: custom ip= gateway= Within %post, hostname is available like this: hostname=`grep HOSTNAME /etc/sysconfig/network |cut -d'=' -f2` Note that the hostname was not provided at kickstart time, it came from DNS. And I haven't tried it, but as Chip suggested, the ip, if you need it, should be available by processing /proc/cmdline, something like: ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` -Ed Gabrie wrote: > Would you have an example of that? > > I now set the variables in the %post section and then they are > available in the scripts. But I can't use them in the "network" > section. > > Gabrie > > > On 7/18/07, Shabazian, Chip wrote: >> You could also add these variables to the boot: line and then pull them >> from /proc/cmdline in the %pre section. Just make sure you have 255 >> characters or less for that boot: line. >> >> -----Original Message----- >> From: kickstart-list-bounces at redhat.com >> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie >> Sent: Wednesday, July 18, 2007 2:55 AM >> To: Kickstart-list at redhat.com >> Subject: Using variables in kickstart file >> >> Hi >> >> I'm going to install about 20 servers, which will be identical apart >> from hostname and IP address. To make changes in all ks files easier, I >> would like to start using one central batch file, that is being called >> from the ks.cfg file. Therefore I would like to use 2 variables >> containing IP and hostname. >> >> Ideally it would be something like this: >> >> ### Begin ks020.cfg >> VAR-IP = 10.0.0.20 >> VAR-HOST = vmesx020.mydomain.com >> >> >> >> network --device eth0 --bootproto static --ip $VAR-IP --netmask >> 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST >> >> >> >> %post >> # download central script >> lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg >> >> perl /tmp/central.cfg $VAR-IP $VAR-HOST >> >> ### End ks020.cfg >> >> >> In the central.cfg I would then be able to read the VAR-IP and VAR-HOST >> and use it for other configuration stuff. >> >> Who can tell me how to use variables in this way? I have the feeling >> there also is a difference between a variable in the first section >> (network section) and the post section???? >> >> Gabrie >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From mdehaan at redhat.com Wed Jul 18 19:47:16 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 18 Jul 2007 15:47:16 -0400 Subject: Using variables in kickstart file In-Reply-To: <469E6591.6090200@lanl.gov> References: <469E6591.6090200@lanl.gov> Message-ID: <469E6E44.1090807@redhat.com> Ed Brown wrote: > Cobbler might be a bigger hammer than is needed, and PXE/DHCP isn't > always an option, especially in distributed network environments. If > you're installing the OS over the network (as opposed to cd's), and > are able to burn/boot from cd to initiate the install, there's > possibly not a simpler approach to kickstarting and static ip > addressing than to make a boot cd with a custom syslinux.cfg file with > the common boot parameters (method, ks, netmask, dns) and just provide > the ip and gateway at the anaconda 'boot:' prompt. Slightly OT, but ... Adam Wolf contributed a fairly nice CGI to help with this recently ... http://feelslikeburning.com/projects/live-cd-restoring-with-cobbler/ You may want to mentally read "live CD" here as "restore disk". A modification of what he posted is in the upstream codebase now as "findks.cgi". Or, you can completely ignore that and still use cobbler and a restore disk, just hard coding the URLs. There's also a real live CD (buildable from the koan source checkout) that acts as a universal installer -- so from one Live CD, depending on the system MAC, it can install the correct distro for the system -- and the distro doesn't even have to match the distro of the media you are using. Over time, you can redefine what each system needs to get installed on it, and you'll never have to reburn that one CD as new distros get added or you change the OS that a certain machine should be running ... it just /knows/. Anyhow, this is useful because, just like in the restore disk boot scenario -- a lot of people don't have a PXE configuration -- and we can support that too. Anyhow, I disagree that Cobbler is too big of a hammer -- a hammer is a pretty simple tool, and it's designed to fulfill the needs of small setups just as much as the datacenter case -- for instance, in my office, PXE provisioning isn't viable because I don't own DHCP, but I can still use the other features. It's worth checking out and it only takes a few commands to get the above environment running from scratch -- and then you get full templating for it out of the box. I would definitely say using /all/ of Cobbler isn't worth it, but you don't have to use /all/ of it. If you just want to use it to maintain kickstarts and don't intend to use the PXE portions, that's fine. It also does Xen, QEMU/KVM (new), and reinstalling existing machines -- all things that you may also want templating for. So, in adopting something a bit more flexible now, you get options later. My main point is that it's /not/ just a PXE setup tool. Is that one of the primary uses? Sure. > > in your kickstart file: > network --bootproto=static > > copy the isolinux/ directory from your distro > edit isolinux/isolinux.cfg and create custom entry: > label custom > kernel vmlinuz > append initrd=initrd.img text nofb dns=your.nameserver.ip > netmask=255.255.255.0 ks= method= > > make a bootable iso: > mkisofs -o boot.iso -b isolinux.bin -c boot.cat -no-emul-boot > -boot-load-size 4 -boot-info-table -R -J -T -v isolinux/ > > burn cd: > cdrecord boot.iso > > to install, boot from cd, and enter arguments at boot prompt > boot: custom ip= gateway= > > Within %post, hostname is available like this: > hostname=`grep HOSTNAME /etc/sysconfig/network |cut -d'=' -f2` > Note that the hostname was not provided at kickstart time, it came > from DNS. > > And I haven't tried it, but as Chip suggested, the ip, if you need it, > should be available by processing /proc/cmdline, something like: > ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` > > -Ed > > > > Gabrie wrote: >> Would you have an example of that? >> >> I now set the variables in the %post section and then they are >> available in the scripts. But I can't use them in the "network" >> section. >> >> Gabrie >> >> >> On 7/18/07, Shabazian, Chip wrote: >>> You could also add these variables to the boot: line and then pull them >>> from /proc/cmdline in the %pre section. Just make sure you have 255 >>> characters or less for that boot: line. >>> >>> -----Original Message----- >>> From: kickstart-list-bounces at redhat.com >>> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie >>> Sent: Wednesday, July 18, 2007 2:55 AM >>> To: Kickstart-list at redhat.com >>> Subject: Using variables in kickstart file >>> >>> Hi >>> >>> I'm going to install about 20 servers, which will be identical apart >>> from hostname and IP address. To make changes in all ks files easier, I >>> would like to start using one central batch file, that is being called >>> from the ks.cfg file. Therefore I would like to use 2 variables >>> containing IP and hostname. >>> >>> Ideally it would be something like this: >>> >>> ### Begin ks020.cfg >>> VAR-IP = 10.0.0.20 >>> VAR-HOST = vmesx020.mydomain.com >>> >>> >>> >>> network --device eth0 --bootproto static --ip $VAR-IP --netmask >>> 255.255.255.0 -gateway 10.0.0.254 --hostname $VAR-HOST >>> >>> >>> >>> %post >>> # download central script >>> lwp-download http://10.0.0.1/scripts/central.cfg /tmp/central.cfg >>> >>> perl /tmp/central.cfg $VAR-IP $VAR-HOST >>> >>> ### End ks020.cfg >>> >>> >>> In the central.cfg I would then be able to read the VAR-IP and VAR-HOST >>> and use it for other configuration stuff. >>> >>> Who can tell me how to use variables in this way? I have the feeling >>> there also is a difference between a variable in the first section >>> (network section) and the post section???? >>> >>> Gabrie >>> >>> _______________________________________________ >>> Kickstart-list mailing list >>> Kickstart-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/kickstart-list >>> >>> _______________________________________________ >>> Kickstart-list mailing list >>> Kickstart-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/kickstart-list >>> >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From mdehaan at redhat.com Wed Jul 18 19:51:17 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 18 Jul 2007 15:51:17 -0400 Subject: Using variables in kickstart file In-Reply-To: <469E6E44.1090807@redhat.com> References: <469E6591.6090200@lanl.gov> <469E6E44.1090807@redhat.com> Message-ID: <469E6F35.90607@redhat.com> Michael DeHaan wrote: > > There's also a real live CD (buildable from the koan source checkout) Here's the info on that ... if anyone has further Q&A, stop by #cobbler on irc.freenode.net or post to the list... and, as always, patches/ideas/comments welcome. https://www.redhat.com/archives/et-mgmt-tools/2007-July/msg00084.html From thegabeman at gmail.com Wed Jul 18 20:38:00 2007 From: thegabeman at gmail.com (Gabrie) Date: Wed, 18 Jul 2007 22:38:00 +0200 Subject: Using variables in kickstart file In-Reply-To: <469E6591.6090200@lanl.gov> References: <469E6591.6090200@lanl.gov> Message-ID: > Within %post, hostname is available like this: > hostname=`grep HOSTNAME /etc/sysconfig/network |cut -d'=' -f2` > Note that the hostname was not provided at kickstart time, it came > from DNS. > > And I haven't tried it, but as Chip suggested, the ip, if you need it, > should be available by processing /proc/cmdline, something like: > ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` > > -Ed Hi thanks everyone for your replies. The cobbler tips I'm gonna try as a last resort. I'm now using a VMware appliance from http://www.rtfm-ed.co.uk/?cat=11 called the UDA. Its a simple pxe / dhcp server build on a minimal Fedora Core 5. I'm using it to roll-out VMware ESX servers. Because the webinterface on the UDA, it will be very easy for the admins to accept my concept and realy use it. If I had to let them edit all scripts on the command line, they won't accept it (it is a windows company). Therefore, I'm first gonna try to do things using the /proc/cmdline options. Which, as I'm lookin' at ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` is gonna give me quite a headache figuring out how this works :-) But then again, the result will great :-) So, if I get this right.... I can use /proc/cmdline to read the command line that kickstart has been called from and use the output in the kickstart file (network section)? Without using /proc/cmdline, I got this far: network ip=10.0.0.20 (by hand) %post ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 lwp-download http://webserver/centralscript.sh /tmp/centralscript.sh chmod a+x /tmp/centralscript.sh /tmp/centralscript.sh $ESXIP $ESXVMOTION And in centralscript.sh I can use them like $1 and $2. Which is an improvement, but if I'm able to use /proc/cmdline I would be the hero of my department :p Thanks everybode for the replies !!! Gabrie From jkeating at j2solutions.net Wed Jul 18 20:51:50 2007 From: jkeating at j2solutions.net (Jesse Keating) Date: Wed, 18 Jul 2007 16:51:50 -0400 Subject: Using variables in kickstart file In-Reply-To: References: <469E6591.6090200@lanl.gov> Message-ID: <20070718165150.443851d3@localhost.localdomain> On Wed, 18 Jul 2007 22:38:00 +0200 Gabrie wrote: > So, if I get this right.... I can use /proc/cmdline to read the > command line that kickstart has been called from and use the output in > the kickstart file (network section)? You can insert anything you want on the boot line, and that content will wind up being in /proc/cmdline, which you can parse in %pre to generate stubs to be %included elsewhere, or to use in %post or whatever. They sky (or the buffer) is the limit. -- Jesse Keating RHCE (jkeating.livejournal.com) Fedora Project (fedoraproject.org/wiki/JesseKeating) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Chip.Shabazian at bankofamerica.com Wed Jul 18 20:55:08 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 13:55:08 -0700 Subject: Using variables in kickstart file In-Reply-To: Message-ID: boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 %pre (and %post if needed) ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` Yea, Yea, Yea, there are more elegant ways to do this, but this should work for you Chip -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie Sent: Wednesday, July 18, 2007 1:38 PM To: Discussion list about Kickstart Subject: Re: Using variables in kickstart file > Within %post, hostname is available like this: > hostname=`grep HOSTNAME /etc/sysconfig/network |cut -d'=' -f2` Note > that the hostname was not provided at kickstart time, it came from > DNS. > > And I haven't tried it, but as Chip suggested, the ip, if you need it, > should be available by processing /proc/cmdline, something like: > ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` > > -Ed Hi thanks everyone for your replies. The cobbler tips I'm gonna try as a last resort. I'm now using a VMware appliance from http://www.rtfm-ed.co.uk/?cat=11 called the UDA. Its a simple pxe / dhcp server build on a minimal Fedora Core 5. I'm using it to roll-out VMware ESX servers. Because the webinterface on the UDA, it will be very easy for the admins to accept my concept and realy use it. If I had to let them edit all scripts on the command line, they won't accept it (it is a windows company). Therefore, I'm first gonna try to do things using the /proc/cmdline options. Which, as I'm lookin' at ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` is gonna give me quite a headache figuring out how this works :-) But then again, the result will great :-) So, if I get this right.... I can use /proc/cmdline to read the command line that kickstart has been called from and use the output in the kickstart file (network section)? Without using /proc/cmdline, I got this far: network ip=10.0.0.20 (by hand) %post ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 lwp-download http://webserver/centralscript.sh /tmp/centralscript.sh chmod a+x /tmp/centralscript.sh /tmp/centralscript.sh $ESXIP $ESXVMOTION And in centralscript.sh I can use them like $1 and $2. Which is an improvement, but if I'm able to use /proc/cmdline I would be the hero of my department :p Thanks everybode for the replies !!! Gabrie _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Chip.Shabazian at bankofamerica.com Wed Jul 18 21:01:01 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 14:01:01 -0700 Subject: Using variables in kickstart file In-Reply-To: Message-ID: oops. word wrap. Lets try this: %pre (and %post if needed) ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Wednesday, July 18, 2007 1:55 PM To: Discussion list about Kickstart Subject: RE: Using variables in kickstart file boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 %pre (and %post if needed) ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` Yea, Yea, Yea, there are more elegant ways to do this, but this should work for you Chip -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie Sent: Wednesday, July 18, 2007 1:38 PM To: Discussion list about Kickstart Subject: Re: Using variables in kickstart file > Within %post, hostname is available like this: > hostname=`grep HOSTNAME /etc/sysconfig/network |cut -d'=' -f2` Note > that the hostname was not provided at kickstart time, it came from > DNS. > > And I haven't tried it, but as Chip suggested, the ip, if you need it, > should be available by processing /proc/cmdline, something like: > ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` > > -Ed Hi thanks everyone for your replies. The cobbler tips I'm gonna try as a last resort. I'm now using a VMware appliance from http://www.rtfm-ed.co.uk/?cat=11 called the UDA. Its a simple pxe / dhcp server build on a minimal Fedora Core 5. I'm using it to roll-out VMware ESX servers. Because the webinterface on the UDA, it will be very easy for the admins to accept my concept and realy use it. If I had to let them edit all scripts on the command line, they won't accept it (it is a windows company). Therefore, I'm first gonna try to do things using the /proc/cmdline options. Which, as I'm lookin' at ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` is gonna give me quite a headache figuring out how this works :-) But then again, the result will great :-) So, if I get this right.... I can use /proc/cmdline to read the command line that kickstart has been called from and use the output in the kickstart file (network section)? Without using /proc/cmdline, I got this far: network ip=10.0.0.20 (by hand) %post ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 lwp-download http://webserver/centralscript.sh /tmp/centralscript.sh chmod a+x /tmp/centralscript.sh /tmp/centralscript.sh $ESXIP $ESXVMOTION And in centralscript.sh I can use them like $1 and $2. Which is an improvement, but if I'm able to use /proc/cmdline I would be the hero of my department :p Thanks everybode for the replies !!! Gabrie _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From thegabeman at gmail.com Wed Jul 18 21:16:40 2007 From: thegabeman at gmail.com (Gabrie) Date: Wed, 18 Jul 2007 23:16:40 +0200 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: On 7/18/07, Shabazian, Chip wrote: > boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 > > %pre (and %post if needed) > ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` > ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " > -f 1` > > Yea, Yea, Yea, there are more elegant ways to do this, but this should > work for you > Ok, thanks. But only in %pre and %post ???? So this will NOT work? %pre ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` # Network Configurations network --device eth0 --bootproto static --ip $ESXIP --netmask 255.255.255.0 Or in other words.... is the network-line part of the %pre section???? Gabrie From mdehaan at redhat.com Wed Jul 18 21:26:32 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 18 Jul 2007 17:26:32 -0400 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: <469E8588.7040206@redhat.com> Gabrie wrote: > On 7/18/07, Shabazian, Chip wrote: >> boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 >> >> %pre (and %post if needed) >> ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` >> ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " >> -f 1` >> >> Yea, Yea, Yea, there are more elegant ways to do this, but this should >> work for you >> > > Ok, thanks. > But only in %pre and %post ???? > > So this will NOT work? > > %pre > ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` > ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " > " -f 1` > > # Network Configurations > network --device eth0 --bootproto static --ip $ESXIP --netmask > 255.255.255.0 > > > Or in other words.... is the network-line part of the %pre section???? > > Gabrie > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list %pre and %post are essentially bash shell scripts, independent of the other lines Here's a clever snippet (also originated from Chip) that illustrates how to build part of your kickstart, on the fly, using %pre and %include... # lots of stuff here... # ... # .... %include /tmp/partinfo %pre # Determine how many drives we have set \$(list-harddrives) let numd=\$#/2 d1=\$1 d2=\$3 cat << EOF >> /tmp/partinfo part / --fstype ext3 --size=1024 --grow --ondisk=\$d1 --asprimary part swap --size=1024 --ondisk=\$d1 --asprimary #EOF In the above example, the pre script runs first, and generates a file in /tmp. That file is then inserted into the kickstart, containing instructions for drive setup. The same thing can be done in your case. From thegabeman at gmail.com Wed Jul 18 21:43:25 2007 From: thegabeman at gmail.com (Gabrie) Date: Wed, 18 Jul 2007 23:43:25 +0200 Subject: Using variables in kickstart file In-Reply-To: <469E8588.7040206@redhat.com> References: <469E8588.7040206@redhat.com> Message-ID: On 7/18/07, Michael DeHaan wrote: > %pre and %post are essentially bash shell scripts, independent of the > other lines > > Here's a clever snippet (also originated from Chip) that illustrates how > to build part of your kickstart, on the fly, using %pre and %include... > > # lots of stuff here... > # ... > # .... > %include /tmp/partinfo > > %pre > # Determine how many drives we have > set \$(list-harddrives) > let numd=\$#/2 > d1=\$1 > d2=\$3 > > cat << EOF >> /tmp/partinfo > part / --fstype ext3 --size=1024 --grow --ondisk=\$d1 --asprimary > part swap --size=1024 --ondisk=\$d1 --asprimary > #EOF > > In the above example, the pre script runs first, and generates a file in > /tmp. That file is then inserted into the kickstart, containing > instructions for drive setup. > The same thing can be done in your case. Sorry, I see what you want to explain, but I don't get the syntax..... because I don't understand when it is written and when read. Don't get how the files work together.... Gabrie From Chip.Shabazian at bankofamerica.com Wed Jul 18 21:49:17 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 14:49:17 -0700 Subject: Using variables in kickstart file In-Reply-To: Message-ID: You cannot use variables in the command section (I wish you could), only in %pre and %post. SO, you write the line you need for your network (or disk, timezone, whatever) and you use %include which IS available to you in the command section. Does that clarify it? -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie Sent: Wednesday, July 18, 2007 2:43 PM To: Discussion list about Kickstart Subject: Re: Using variables in kickstart file On 7/18/07, Michael DeHaan wrote: > %pre and %post are essentially bash shell scripts, independent of the > other lines > > Here's a clever snippet (also originated from Chip) that illustrates > how to build part of your kickstart, on the fly, using %pre and %include... > > # lots of stuff here... > # ... > # .... > %include /tmp/partinfo > > %pre > # Determine how many drives we have > set \$(list-harddrives) > let numd=\$#/2 > d1=\$1 > d2=\$3 > > cat << EOF >> /tmp/partinfo > part / --fstype ext3 --size=1024 --grow --ondisk=\$d1 --asprimary part > swap --size=1024 --ondisk=\$d1 --asprimary #EOF > > In the above example, the pre script runs first, and generates a file > in /tmp. That file is then inserted into the kickstart, containing > instructions for drive setup. > The same thing can be done in your case. Sorry, I see what you want to explain, but I don't get the syntax..... because I don't understand when it is written and when read. Don't get how the files work together.... Gabrie _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From ebrown at lanl.gov Wed Jul 18 21:50:25 2007 From: ebrown at lanl.gov (Ed Brown) Date: Wed, 18 Jul 2007 15:50:25 -0600 Subject: Using variables in kickstart file In-Reply-To: References: <469E6591.6090200@lanl.gov> Message-ID: <469E8B21.8020809@lanl.gov> Gabrie wrote: > So, if I get this right.... I can use /proc/cmdline to read the > command line that kickstart has been called from and use the output in > the kickstart file (network section)? No, you can't just use variables in the network line. And I don't believe that you will be able to insert or include or modify the network line parameters during %pre. Yes, this works for packages and partitioning, but I think it's too late for network parameters. Now I could be wrong, maybe that is not true for dhcp or cd-based installs. (You haven't said what your install method is, though you mentioned a dhcp server in passing.) -Ed From Chip.Shabazian at bankofamerica.com Wed Jul 18 21:51:53 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 14:51:53 -0700 Subject: Using variables in kickstart file In-Reply-To: <469E8B21.8020809@lanl.gov> Message-ID: We use %include /tmp/network every day, it works just fine. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ed Brown Sent: Wednesday, July 18, 2007 2:50 PM To: Discussion list about Kickstart Subject: Re: Using variables in kickstart file Gabrie wrote: > So, if I get this right.... I can use /proc/cmdline to read the > command line that kickstart has been called from and use the output in > the kickstart file (network section)? No, you can't just use variables in the network line. And I don't believe that you will be able to insert or include or modify the network line parameters during %pre. Yes, this works for packages and partitioning, but I think it's too late for network parameters. Now I could be wrong, maybe that is not true for dhcp or cd-based installs. (You haven't said what your install method is, though you mentioned a dhcp server in passing.) -Ed _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From thegabeman at gmail.com Wed Jul 18 22:02:50 2007 From: thegabeman at gmail.com (Gabrie) Date: Thu, 19 Jul 2007 00:02:50 +0200 Subject: Using variables in kickstart file In-Reply-To: References: <469E8B21.8020809@lanl.gov> Message-ID: Ok... let me give it a try. commandline: boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 Kickstart.cfg: # Regional Settings keyboard us lang en_US langsupport --default en_US timezone America/New_York # Installatition settings skipx mouse none firewall --disabled # Unencrypted root password: password rootpw --iscrypted $1$5a17$In5zYe6YsCty76AycpGaf/ reboot install url --url http://192.168.3.150/esx/esx301/ # network configuration %include /tmp/networkinfo # Partitioning clearpart --all --drives=cciss/c0d0 --initlabel part /boot --fstype ext3 --size 250 --ondisk=cciss/c0d0 part swap --size 1600 --ondisk=cciss/c0d0 part / --fstype ext3 --size 5120 --ondisk=cciss/c0d0 part /var --fstype ext3 --size 2048 --ondisk=cciss/c0d0 %pre # Read ESXIP and ESXVMOTION from commandline ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` # Now write them to file: cat << EOF >> /tmp/networkinfo # Network Configurations network --device eth0 --bootproto static --ip $ESXIP --netmask 255.255.255.0 #EOF Any good? Gabrie From Chip.Shabazian at bankofamerica.com Wed Jul 18 22:18:28 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 18 Jul 2007 15:18:28 -0700 Subject: Using variables in kickstart file In-Reply-To: Message-ID: I don't think #EOF will work, EOF has to be the first thing on the line. Also, *I* would put the comments before/after writing the file, not in the file itself: # Now write them to file: cat << EOF >> /tmp/networkinfo network --device eth0 --bootproto static --ip $ESXIP --netmask 255.255.255.0 EOF -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie Sent: Wednesday, July 18, 2007 3:03 PM To: Discussion list about Kickstart Subject: Re: Using variables in kickstart file Ok... let me give it a try. commandline: boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 Kickstart.cfg: # Regional Settings keyboard us lang en_US langsupport --default en_US timezone America/New_York # Installatition settings skipx mouse none firewall --disabled # Unencrypted root password: password rootpw --iscrypted $1$5a17$In5zYe6YsCty76AycpGaf/ reboot install url --url http://192.168.3.150/esx/esx301/ # network configuration %include /tmp/networkinfo # Partitioning clearpart --all --drives=cciss/c0d0 --initlabel part /boot --fstype ext3 --size 250 --ondisk=cciss/c0d0 part swap --size 1600 --ondisk=cciss/c0d0 part / --fstype ext3 --size 5120 --ondisk=cciss/c0d0 part /var --fstype ext3 --size 2048 --ondisk=cciss/c0d0 %pre # Read ESXIP and ESXVMOTION from commandline ESXIP=`awk -F "ESXIP=" '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` # Now write them to file: cat << EOF >> /tmp/networkinfo # Network Configurations network --device eth0 --bootproto static --ip $ESXIP --netmask 255.255.255.0 #EOF Any good? Gabrie _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From thegabeman at gmail.com Wed Jul 18 22:21:25 2007 From: thegabeman at gmail.com (Gabrie) Date: Thu, 19 Jul 2007 00:21:25 +0200 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: Will try all this at work tomorrow. Think I'm gonna make a VM that can do PXE boot first, because booting a HP DL585 takes forever :-) Again, many many thanks to all that helped !!! Realy great work !!! Thank you Gabrie On 7/19/07, Shabazian, Chip wrote: > I don't think #EOF will work, EOF has to be the first thing on the line. > Also, *I* would put the comments before/after writing the file, not in > the file itself: > > # Now write them to file: > cat << EOF >> /tmp/networkinfo > network --device eth0 --bootproto static --ip $ESXIP --netmask > 255.255.255.0 > EOF > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Gabrie > Sent: Wednesday, July 18, 2007 3:03 PM > To: Discussion list about Kickstart > Subject: Re: Using variables in kickstart file > > Ok... let me give it a try. > > > commandline: > boot: yadda yadda yadda ESXIP=10.0.0.20 ESXVMOTION=10.0.2.20 > > > Kickstart.cfg: > > # Regional Settings > keyboard us > lang en_US > langsupport --default en_US > timezone America/New_York > > # Installatition settings > skipx > mouse none > firewall --disabled > # Unencrypted root password: password > rootpw --iscrypted $1$5a17$In5zYe6YsCty76AycpGaf/ reboot install url > --url http://192.168.3.150/esx/esx301/ > > # network configuration > %include /tmp/networkinfo > > # Partitioning > clearpart --all --drives=cciss/c0d0 --initlabel part /boot --fstype ext3 > --size 250 --ondisk=cciss/c0d0 > part swap --size 1600 --ondisk=cciss/c0d0 > part / --fstype ext3 --size 5120 --ondisk=cciss/c0d0 part /var > --fstype ext3 --size 2048 --ondisk=cciss/c0d0 > > %pre > # Read ESXIP and ESXVMOTION from commandline ESXIP=`awk -F "ESXIP=" > '{print $2}' /proc/cmdline | cut -d " " -f 1` ESXVMOTION=`awk -F > "ESXVMOTION=" '{print $2}' /proc/cmdline | cut -d " " -f 1` > > # Now write them to file: > cat << EOF >> /tmp/networkinfo > > # Network Configurations > network --device eth0 --bootproto static --ip $ESXIP --netmask > 255.255.255.0 #EOF > > > > Any good? > Gabrie > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From ebrown at lanl.gov Wed Jul 18 22:26:19 2007 From: ebrown at lanl.gov (Ed Brown) Date: Wed, 18 Jul 2007 16:26:19 -0600 Subject: Using variables in kickstart file In-Reply-To: References: Message-ID: <469E938B.5090804@lanl.gov> Shabazian, Chip wrote: > We use %include /tmp/network every day, it works just fine. Thanks. My reservation about that was based on some old experiences, trying to modify network info on the fly for installs themselves using static ip addressing, and local kickstart files. -Ed From jce at zot.com Thu Jul 19 04:02:37 2007 From: jce at zot.com (Chris Edillon) Date: Thu, 19 Jul 2007 00:02:37 -0400 Subject: Using variables in kickstart file In-Reply-To: <469E8B21.8020809@lanl.gov> References: <469E6591.6090200@lanl.gov> <469E8B21.8020809@lanl.gov> Message-ID: <469EE25D.1040502@zot.com> Ed Brown wrote: > Gabrie wrote: >> So, if I get this right.... I can use /proc/cmdline to read the >> command line that kickstart has been called from and use the output in >> the kickstart file (network section)? > > No, you can't just use variables in the network line. > > And I don't believe that you will be able to insert or include or modify > the network line parameters during %pre. Yes, this works for packages > and partitioning, but I think it's too late for network parameters. Now > I could be wrong, maybe that is not true for dhcp or cd-based installs. > (You haven't said what your install method is, though you mentioned a > dhcp server in passing.) > as chip mentioned, this technique does work and is rather useful. i believe the only things that cannot be pulled in via %include are the line in the kickstart file which specifies either install or upgrade, the %packages line (but package lists can be %included), the %pre section, and the %post line (not sure if %post script text can be included or not). at some point or another i've used %include for almost every kickstart command as well as package lists or partial package lists (e.g. use %pre to determine machine architecture and install specific packages based on this). the install/upgrade lines or information in them cannot be created in a %pre script because anaconda has to locate the second stage image based on this information, and %pre runs after the second stage image has been loaded so it can take advantage of all the extra tools located there (sed, awk, perl, etc.). chris From thegabeman at gmail.com Thu Jul 19 13:08:34 2007 From: thegabeman at gmail.com (Gabrie) Date: Thu, 19 Jul 2007 15:08:34 +0200 Subject: Using variables in kickstart file In-Reply-To: <469EE25D.1040502@zot.com> References: <469E6591.6090200@lanl.gov> <469E8B21.8020809@lanl.gov> <469EE25D.1040502@zot.com> Message-ID: Hi Today playing with all the examples you gave me. Looks like awk is not available at that time during installation. Also can't find any tools to first download awk from my pxe-boot server. :-S Gabrie From jkeating at j2solutions.net Thu Jul 19 13:58:43 2007 From: jkeating at j2solutions.net (Jesse Keating) Date: Thu, 19 Jul 2007 09:58:43 -0400 Subject: Using variables in kickstart file In-Reply-To: References: <469E6591.6090200@lanl.gov> <469E8B21.8020809@lanl.gov> <469EE25D.1040502@zot.com> Message-ID: <20070719095843.7ddf7154@localhost.localdomain> On Thu, 19 Jul 2007 15:08:34 +0200 Gabrie wrote: > Today playing with all the examples you gave me. Looks like awk is not > available at that time during installation. > > Also can't find any tools to first download awk from my pxe-boot > server. :-S Use python instead. Python is there, and you can slurp up the contents of /proc/cmdline and process them as you need. -- Jesse Keating RHCE (jkeating.livejournal.com) Fedora Project (fedoraproject.org/wiki/JesseKeating) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From ebrown at lanl.gov Thu Jul 19 14:07:18 2007 From: ebrown at lanl.gov (Ed Brown) Date: Thu, 19 Jul 2007 08:07:18 -0600 Subject: Using variables in kickstart file In-Reply-To: <20070719095843.7ddf7154@localhost.localdomain> References: <469E6591.6090200@lanl.gov> <469E8B21.8020809@lanl.gov> <469EE25D.1040502@zot.com> <20070719095843.7ddf7154@localhost.localdomain> Message-ID: <469F7016.5090009@lanl.gov> > Use python instead. Or perl. You can substitute any parameter name you want from /proc/cmdline, in place of the string 'ip' in the example given earlier: ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print $1}'` ESXIP=`cat /proc/cmdline |perl -e 'if (<> =~ /\sESXIP=(.*?)\s/) {print $1}'` -Ed From jskohli at gmail.com Thu Jul 19 14:45:51 2007 From: jskohli at gmail.com (Jaswinder Singh Kohli) Date: Thu, 19 Jul 2007 20:15:51 +0530 Subject: unable to use kickstart file with pungi generated iso Message-ID: <27ecd4490707190745k34780d9bhc8e77581c5c1ed1b@mail.gmail.com> Hi, I am just unable to use the kickstart file which specifies the packages wiht the iso file generated by pungi. The same kickstart file works with the official Fedora 7 DVD but when i create a new DVD image by integrating the updates from the Update Tree,(from a local rsync'd repo) It spits out the some error by the yuminstall as if it is trying to get some header but was unsuccessful. I have attached all possible files, which may or may not point in the direction of the error. Any ideas what is going wrong. pungi command line = pungi --all-stages works out ok, gives me DVD image to play with. Thanks in advance. -- Regards JSK jskohli (AT) gmail (DOT) com ------------------------------------------ Vi Veri Veniversum Vivus Vici. (By the power of truth, I, while living, have conquered the universe.) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: anaconda_logs.tar.bz2 Type: application/x-bzip2 Size: 17163 bytes Desc: not available URL: From jkeating at j2solutions.net Thu Jul 19 15:04:56 2007 From: jkeating at j2solutions.net (Jesse Keating) Date: Thu, 19 Jul 2007 11:04:56 -0400 Subject: unable to use kickstart file with pungi generated iso In-Reply-To: <27ecd4490707190745k34780d9bhc8e77581c5c1ed1b@mail.gmail.com> References: <27ecd4490707190745k34780d9bhc8e77581c5c1ed1b@mail.gmail.com> Message-ID: <20070719110456.5baa6125@localhost.localdomain> On Thu, 19 Jul 2007 20:15:51 +0530 "Jaswinder Singh Kohli" wrote: > I am just unable to use the kickstart file which specifies the > packages wiht the iso file generated by pungi. > > The same kickstart file works with the official Fedora 7 DVD but when > i create a new DVD > image by integrating the updates from the Update Tree,(from a local > rsync'd repo) > > It spits out the some error by the yuminstall as if it is trying to > get some header but was > unsuccessful. > > I have attached all possible files, which may or may not point in the > direction of the error. > > Any ideas what is going wrong. > > pungi command line = pungi --all-stages > > works out ok, gives me DVD image to play with. This doesn't have much to do with pungi, other than you used it to create a tree with updated packages. There was a change to yum in how it dealt with package headers, and this led to there not being a headers directory created. This trips up anaconda, as it expects the old behavior of yum. Fear not, as this has been fixed in yum cvs, and I expect there to be a yum update for Fedora 7 soon that addresses this and some other issues. Another spin with pungi once the new yum is in place should resolve this. In the mean time, you could exclude the newer yum from your pungi tree and things should just work. -- Jesse Keating RHCE (jkeating.livejournal.com) Fedora Project (fedoraproject.org/wiki/JesseKeating) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From email at jasonkohles.com Thu Jul 19 15:49:13 2007 From: email at jasonkohles.com (Jason Kohles) Date: Thu, 19 Jul 2007 11:49:13 -0400 Subject: Using variables in kickstart file In-Reply-To: <469F7016.5090009@lanl.gov> References: <469E6591.6090200@lanl.gov> <469E8B21.8020809@lanl.gov> <469EE25D.1040502@zot.com> <20070719095843.7ddf7154@localhost.localdomain> <469F7016.5090009@lanl.gov> Message-ID: <2D6EFFD0-F3EB-41B0-BCCF-67A66877B970@jasonkohles.com> On Jul 19, 2007, at 10:07 AM, Ed Brown wrote: >> Use python instead. > > Or perl. You can substitute any parameter name you want from /proc/ > cmdline, in place of the string 'ip' in the example given earlier: > > ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print > $1}'` > > ESXIP=`cat /proc/cmdline |perl -e 'if (<> =~ /\sESXIP=(.*?)\s/) > {print $1}'` > Or you can use the -n option to perl, which makes it work quite a bit like awk anyway (see the perlrun man page)... ESXIP=`perl -ne '/ESXIP=(\S+)/ && print $1' /proc/cmdline` What I usually do though, is just exploit bash to do the whole thing. Stick this at the top of a %pre/%post script, and it will take anything of the form var=value from /proc/cmdline and turn it into a variable you can use directly... set -- `cat /proc/cmdline` for I in $*; do case "$I" in *=*) eval $I;; esac; done You can try it from the command line to see how it works... [root at dev1-mgmt-01 ~]# cat /proc/cmdline ro root=/dev/SystemVG/RootLV [root at dev1-mgmt-01 ~]# set -- `cat /proc/cmdline` [root at dev1-mgmt-01 ~]# for I in $*; do case "$I" in *=*) eval "$I";; esac; done [root at dev1-mgmt-01 ~]# echo $root /dev/SystemVG/RootLV -- Jason Kohles email at jasonkohles.com http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire From ahpook at gmail.com Thu Jul 19 17:47:34 2007 From: ahpook at gmail.com (Eric Sorenson) Date: Thu, 19 Jul 2007 10:47:34 -0700 Subject: Using variables in kickstart file In-Reply-To: <2D6EFFD0-F3EB-41B0-BCCF-67A66877B970@jasonkohles.com> References: <469E6591.6090200@lanl.gov> <469E8B21.8020809@lanl.gov> <469EE25D.1040502@zot.com> <20070719095843.7ddf7154@localhost.localdomain> <469F7016.5090009@lanl.gov> <2D6EFFD0-F3EB-41B0-BCCF-67A66877B970@jasonkohles.com> Message-ID: <80145c330707191047oc055710pec27ed5e7a7ff5ed@mail.gmail.com> That is a very clever trick. Saved for future reference. Thank you Jason. On 7/19/07, Jason Kohles wrote: > > On Jul 19, 2007, at 10:07 AM, Ed Brown wrote: > > >> Use python instead. > > > > Or perl. You can substitute any parameter name you want from /proc/ > > cmdline, in place of the string 'ip' in the example given earlier: > > > > ip=`cat /proc/cmdline |perl -e 'if (<> =~ /\sip=(.*?)\s/) {print > > $1}'` > > > > ESXIP=`cat /proc/cmdline |perl -e 'if (<> =~ /\sESXIP=(.*?)\s/) > > {print $1}'` > > > > Or you can use the -n option to perl, which makes it work quite a bit > like awk anyway (see the perlrun man page)... > > ESXIP=`perl -ne '/ESXIP=(\S+)/ && print $1' /proc/cmdline` > > > What I usually do though, is just exploit bash to do the whole > thing. Stick this at the top of a %pre/%post script, and it will > take anything of the form var=value from /proc/cmdline and turn it > into a variable you can use directly... > > set -- `cat /proc/cmdline` > for I in $*; do case "$I" in *=*) eval $I;; esac; done > > > You can try it from the command line to see how it works... > > [root at dev1-mgmt-01 ~]# cat /proc/cmdline > ro root=/dev/SystemVG/RootLV > [root at dev1-mgmt-01 ~]# set -- `cat /proc/cmdline` > [root at dev1-mgmt-01 ~]# for I in $*; do case "$I" in *=*) eval "$I";; > esac; done > [root at dev1-mgmt-01 ~]# echo $root > /dev/SystemVG/RootLV > > -- > Jason Kohles > email at jasonkohles.com > http://www.jasonkohles.com/ > "A witty saying proves nothing." -- Voltaire > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbird at me.dium.com Mon Jul 23 17:12:32 2007 From: jbird at me.dium.com (Jim Bird) Date: Mon, 23 Jul 2007 11:12:32 -0600 Subject: rhel5 and kickstart Message-ID: I've been using kickstart via http/pxe on our rhel4 servers for a while now and have recently created a rhel5 image on the same kickstart server. I've replaced the vmlinuz and initrd files and can't get it to work. It stops when it is looking for the .discinfo file in the disc1 directory of my rhel5 image repository (which isn't there). My rhel5 image is identical to the dvd image as provided by RedHat. Any ideas? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdehaan at redhat.com Mon Jul 23 17:22:15 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 23 Jul 2007 13:22:15 -0400 Subject: rhel5 and kickstart In-Reply-To: References: Message-ID: <46A4E3C7.1070809@redhat.com> Jim Bird wrote: > > I?ve been using kickstart via http/pxe on our rhel4 servers for a > while now and have recently created a rhel5 image on the same > kickstart server. I?ve replaced the vmlinuz and initrd files and can?t > get it to work. It stops when it is looking for the .discinfo file in > the disc1 directory of my rhel5 image repository (which isn?t there). > My rhel5 image is identical to the dvd image as provided by RedHat. > Any ideas? > > Thanks > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list What are you using for the source URL? RHEL5 is split into a few different repos, and (what I do in Cobbler anyway) is use the Server one for the main install tree and add the other repos with the "repo" kickstart directive, if you need to use them. (I think "VT" is one of those). This way the main install tree gets set up correctly and you can also get to the other repos as well, because RHEL5 Anaconda supports attaching to those other repositories in kickstart. So, I'm guessing that your install source probably isn't pointing at the right place. You could try tweaking it, or you could perhaps just use "cobbler import" and it will set that up automagically :) --Michael From jbird at me.dium.com Mon Jul 23 17:30:11 2007 From: jbird at me.dium.com (Jim Bird) Date: Mon, 23 Jul 2007 11:30:11 -0600 Subject: rhel5 and kickstart In-Reply-To: <46A4E3C7.1070809@redhat.com> References: <46A4E3C7.1070809@redhat.com> Message-ID: I'm actually using the root of the repository. So you're suggesting that I use root/VT? --JB What are you using for the source URL? RHEL5 is split into a few different repos, and (what I do in Cobbler anyway) is use the Server one for the main install tree and add the other repos with the "repo" kickstart directive, if you need to use them. (I think "VT" is one of those). This way the main install tree gets set up correctly and you can also get to the other repos as well, because RHEL5 Anaconda supports attaching to those other repositories in kickstart. So, I'm guessing that your install source probably isn't pointing at the right place. You could try tweaking it, or you could perhaps just use "cobbler import" and it will set that up automagically :) --Michael _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From ebrown at lanl.gov Mon Jul 23 17:34:49 2007 From: ebrown at lanl.gov (Ed Brown) Date: Mon, 23 Jul 2007 11:34:49 -0600 Subject: rhel5 and kickstart In-Reply-To: References: Message-ID: <46A4E6B9.5050107@lanl.gov> Jim Bird wrote: > I've been using kickstart via http/pxe on our rhel4 servers for a while > now and have recently created a rhel5 image on the same kickstart > server. I've replaced the vmlinuz and initrd files and can't get it to > work. It stops when it is looking for the .discinfo file in the disc1 > directory of my rhel5 image repository (which isn't there). My rhel5 > image is identical to the dvd image as provided by RedHat. Any ideas? For what it's worth, I also see a [much-too-long] delay during ftp installs, while anaconda tries and retries to find .discinfo. It's long enough to make you think things are hung, and start looking for a problem on alternate consoles, at which point you can see what is going on. But eventually it moves on to the next thing. Did you give it plenty of time? -Ed From jbird at me.dium.com Mon Jul 23 17:52:46 2007 From: jbird at me.dium.com (Jim Bird) Date: Mon, 23 Jul 2007 11:52:46 -0600 Subject: rhel5 and kickstart In-Reply-To: <46A4E6B9.5050107@lanl.gov> References: <46A4E6B9.5050107@lanl.gov> Message-ID: I believe that I've left it unattended for quite some time while trying to search for what may be wrong. I've even created bogus disc1-6 directories and placed the .discinfo file in there and it hangs on disc7... LOL For what it's worth, I also see a [much-too-long] delay during ftp installs, while anaconda tries and retries to find .discinfo. It's long enough to make you think things are hung, and start looking for a problem on alternate consoles, at which point you can see what is going on. But eventually it moves on to the next thing. Did you give it plenty of time? -Ed _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From mdehaan at redhat.com Mon Jul 23 18:15:36 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 23 Jul 2007 14:15:36 -0400 Subject: rhel5 and kickstart In-Reply-To: References: <46A4E3C7.1070809@redhat.com> Message-ID: <46A4F048.90308@redhat.com> Jim Bird wrote: > I'm actually using the root of the repository. So you're suggesting that > I use root/VT? > > --JB > > > Ok, it's been a while since I looked at the import code. You should still use the directory containing "images" for the kickstart URL parameter, but you may want to list the content in the other directories in the "repo" stanza lines. Actually Anaconda might be smart enough to do this for you automatically based on .discinfo. I would bet it is. That complexity does come up when wanting to set up the boot server for use in yum package installation (as a local mirror) post install. --Michael > > > What are you using for the source URL? > > RHEL5 is split into a few different repos, and (what I do in Cobbler > anyway) is use the Server one for the main install tree and add the > other repos with the "repo" kickstart > directive, if you need to use them. (I think "VT" is one of those). > > This way the main install tree gets set up correctly and you can also > get to the other repos as well, because RHEL5 Anaconda supports > attaching to those other repositories in kickstart. > > So, I'm guessing that your install source probably isn't pointing at the > > right place. You could try tweaking it, or you could perhaps just use > "cobbler import" and it will > set that up automagically :) > > --Michael > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From jbird at me.dium.com Mon Jul 23 18:54:07 2007 From: jbird at me.dium.com (Jim Bird) Date: Mon, 23 Jul 2007 12:54:07 -0600 Subject: rhel5 and kickstart In-Reply-To: <46A4F048.90308@redhat.com> References: <46A4E3C7.1070809@redhat.com> <46A4F048.90308@redhat.com> Message-ID: This is an excerpt from the http log file: [23/Jul/2007:12:34:23 -0600] "GET /chassis3/ks-d1c3s2.cfg HTTP/1.0" 200 5570 "-" "anaconda/11.1.2.36" [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/updates.img HTTP/1.0" 404 307 "-" "anaconda/11.1.2.36" [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/disc1/images/updates.img HTTP/1.0" 404 313 "-" "anaconda/11.1.2.36" [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/product.img HTTP/1.0" 404 307 "-" "anaconda/11.1.2.36" [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/disc1/images/product.img HTTP/1.0" 404 313 "-" "anaconda/11.1.2.36" [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/minstg2.img HTTP/1.0" 200 33587200 "-" "anaconda/11.1.2.36" [23/Jul/2007:12:35:25 -0600] "GET /rhel5image//disc1/.discinfo HTTP/1.1" 404 305 "-" "urlgrabber/3.1.0" It doesn't even look for the .discinfo file in the correct location. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Michael DeHaan Sent: Monday, July 23, 2007 12:16 PM To: Discussion list about Kickstart Subject: Re: rhel5 and kickstart Jim Bird wrote: > I'm actually using the root of the repository. So you're suggesting that > I use root/VT? > > --JB > > > Ok, it's been a while since I looked at the import code. You should still use the directory containing "images" for the kickstart URL parameter, but you may want to list the content in the other directories in the "repo" stanza lines. Actually Anaconda might be smart enough to do this for you automatically based on .discinfo. I would bet it is. That complexity does come up when wanting to set up the boot server for use in yum package installation (as a local mirror) post install. --Michael > > > What are you using for the source URL? > > RHEL5 is split into a few different repos, and (what I do in Cobbler > anyway) is use the Server one for the main install tree and add the > other repos with the "repo" kickstart > directive, if you need to use them. (I think "VT" is one of those). > > This way the main install tree gets set up correctly and you can also > get to the other repos as well, because RHEL5 Anaconda supports > attaching to those other repositories in kickstart. > > So, I'm guessing that your install source probably isn't pointing at the > > right place. You could try tweaking it, or you could perhaps just use > "cobbler import" and it will > set that up automagically :) > > --Michael > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From mdehaan at redhat.com Mon Jul 23 19:32:19 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 23 Jul 2007 15:32:19 -0400 Subject: rhel5 and kickstart In-Reply-To: References: <46A4E3C7.1070809@redhat.com> <46A4F048.90308@redhat.com> Message-ID: <46A50243.4060901@redhat.com> Jim Bird wrote: > This is an excerpt from the http log file: > > [23/Jul/2007:12:34:23 -0600] "GET /chassis3/ks-d1c3s2.cfg HTTP/1.0" 200 > 5570 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/updates.img > HTTP/1.0" 404 307 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/disc1/images/updates.img > HTTP/1.0" 404 313 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/product.img > HTTP/1.0" 404 307 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/disc1/images/product.img > HTTP/1.0" 404 313 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/minstg2.img > HTTP/1.0" 200 33587200 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:25 -0600] "GET /rhel5image//disc1/.discinfo > HTTP/1.1" 404 305 "-" "urlgrabber/3.1.0" > > > It doesn't even look for the .discinfo file in the correct location. > Is "/rhel5image" a copy of the DVD? If you are using various CD's copied into a single directory, that might be your problem. FYI ... cobbler import docs/howto: http://cobbler.et.redhat.com/cobbler-import.php From jbird at me.dium.com Mon Jul 23 19:44:26 2007 From: jbird at me.dium.com (Jim Bird) Date: Mon, 23 Jul 2007 13:44:26 -0600 Subject: rhel5 and kickstart In-Reply-To: <46A50243.4060901@redhat.com> References: <46A4E3C7.1070809@redhat.com> <46A4F048.90308@redhat.com> <46A50243.4060901@redhat.com> Message-ID: It's an exact copy of the DVD... -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Michael DeHaan Sent: Monday, July 23, 2007 1:32 PM To: Discussion list about Kickstart Subject: Re: rhel5 and kickstart Jim Bird wrote: > This is an excerpt from the http log file: > > [23/Jul/2007:12:34:23 -0600] "GET /chassis3/ks-d1c3s2.cfg HTTP/1.0" 200 > 5570 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/updates.img > HTTP/1.0" 404 307 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/disc1/images/updates.img > HTTP/1.0" 404 313 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/product.img > HTTP/1.0" 404 307 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/disc1/images/product.img > HTTP/1.0" 404 313 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:13 -0600] "GET /rhel5image/images/minstg2.img > HTTP/1.0" 200 33587200 "-" "anaconda/11.1.2.36" > [23/Jul/2007:12:35:25 -0600] "GET /rhel5image//disc1/.discinfo > HTTP/1.1" 404 305 "-" "urlgrabber/3.1.0" > > > It doesn't even look for the .discinfo file in the correct location. > Is "/rhel5image" a copy of the DVD? If you are using various CD's copied into a single directory, that might be your problem. FYI ... cobbler import docs/howto: http://cobbler.et.redhat.com/cobbler-import.php _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From lbhella at yahoo.com Tue Jul 24 16:53:46 2007 From: lbhella at yahoo.com (Lakhvir Bhella) Date: Tue, 24 Jul 2007 09:53:46 -0700 (PDT) Subject: deslecting xen virtualization group in kickstart Message-ID: <487376.96330.qm@web50502.mail.re2.yahoo.com> I am doing Rhel 5 client install via kickstart but I don't want to include Virtualization package group in the install. I do want all other package groups. Right now, I use @ everything for packages but this installs all packages. How can the Virtualization package group can be ignored in kickstart file. ____________________________________________________________________________________ Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 From lbhella at yahoo.com Tue Jul 24 16:56:03 2007 From: lbhella at yahoo.com (Lakhvir Bhella) Date: Tue, 24 Jul 2007 09:56:03 -0700 (PDT) Subject: installation number Message-ID: <733576.54728.qm@web50506.mail.re2.yahoo.com> How would I add installation number in kickstart file? Right now, I get prompted to enter the number or skip it. I would like to add in the installation number in kickstart file so that all the packages gets installed. ____________________________________________________________________________________ Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting From mdehaan at redhat.com Tue Jul 24 17:32:17 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Tue, 24 Jul 2007 13:32:17 -0400 Subject: deslecting xen virtualization group in kickstart In-Reply-To: <487376.96330.qm@web50502.mail.re2.yahoo.com> References: <487376.96330.qm@web50502.mail.re2.yahoo.com> Message-ID: <46A637A1.7040503@redhat.com> Lakhvir Bhella wrote: > I am doing Rhel 5 client install via kickstart but I > don't want to include Virtualization package group in > the install. I do want all other package groups. > Right now, I use @ everything for packages but this > installs all packages. > How can the Virtualization package group can be > ignored in kickstart file. > > > > ____________________________________________________________________________________ > Sick sense of humor? Visit Yahoo! TV's > Comedy with an Edge to see what's on, when. > http://tv.yahoo.com/collections/222 > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > Use @base and add packages from there. yum install system-config-kickstart and it use that, and it will give you quite a few ideas. From mdehaan at redhat.com Tue Jul 24 17:40:09 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Tue, 24 Jul 2007 13:40:09 -0400 Subject: installation number In-Reply-To: <733576.54728.qm@web50506.mail.re2.yahoo.com> References: <733576.54728.qm@web50506.mail.re2.yahoo.com> Message-ID: <46A63979.9010605@redhat.com> Lakhvir Bhella wrote: > How would I add installation number in kickstart file? > Right now, I get prompted to enter the number or skip > it. I would like to add in the installation number in > kickstart file so that all the packages gets > installed. > > > > ____________________________________________________________________________________ > Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. > http://smallbusiness.yahoo.com/webhosting > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > It works like "key 8675309". To avoid specifying a installation number, you can use "key --skip" --Michael From kanarip at kanarip.com Wed Jul 25 12:34:55 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 25 Jul 2007 14:34:55 +0200 Subject: deslecting xen virtualization group in kickstart In-Reply-To: <46A637A1.7040503@redhat.com> References: <487376.96330.qm@web50502.mail.re2.yahoo.com> <46A637A1.7040503@redhat.com> Message-ID: <46A7436F.4070709@kanarip.com> Michael DeHaan wrote: > Lakhvir Bhella wrote: >> I am doing Rhel 5 client install via kickstart but I >> don't want to include Virtualization package group in >> the install. I do want all other package groups. Right now, I use @ >> everything for packages but this >> installs all packages. How can the Virtualization package group can be >> ignored in kickstart file. >> > > Use @base and add packages from there. > > yum install system-config-kickstart and it use that, and it will give > you quite a few ideas. > Wasn't @Everything removed from RHEL5 anyway? Kind regards, Jeroen van Meeuwen -kanarip From jos at xos.nl Wed Jul 25 12:39:32 2007 From: jos at xos.nl (Jos Vos) Date: Wed, 25 Jul 2007 14:39:32 +0200 Subject: deslecting xen virtualization group in kickstart In-Reply-To: <46A7436F.4070709@kanarip.com>; from kanarip@kanarip.com on Wed, Jul 25, 2007 at 02:34:55PM +0200 References: <487376.96330.qm@web50502.mail.re2.yahoo.com> <46A637A1.7040503@redhat.com> <46A7436F.4070709@kanarip.com> Message-ID: <20070725143932.B11444@xos037.xos.nl> On Wed, Jul 25, 2007 at 02:34:55PM +0200, Jeroen van Meeuwen wrote: > Wasn't @Everything removed from RHEL5 anyway? Not completely... it was removed from the user interface, but in kickstart it can still be specified, although it is deprecated (see the warning on one of the consoles ;-)) and you should use "*" instead (having exactly the same semantics). -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From thegabeman at gmail.com Wed Jul 25 13:01:47 2007 From: thegabeman at gmail.com (Gabrie) Date: Wed, 25 Jul 2007 15:01:47 +0200 Subject: How to transfer variable from one section to another Message-ID: Hi I'm pulling my hear out here. Thanks to your help, I managed to read a variable from the command line and can use it in the %pre section. Write it to /tmp/networkconfig and include it in the network section. Unfortunately, in the %post section it gets lost. In the post section I want to call a batch and past variables: /tmp/esx-install.sh ${var1} But by that time ${var1} is lost. So I tried to first create a new file in the %pre section: cat << EOF1 >> /call-script.sh /tmp/esx-install.sh 10.0.0.${ESXIP} 10.0.2.${ESXIP} EOF1 chmod a+x /call-script.sh Which indeed did write the file call-script.sh and it contained: /tmp/esx-install.sh 10.0.0.49 10.0.2.49 Lookin' good. Unfortunately, when running the %post section, the script /call-script.sh can't be found. Probably because after the %pre section the whole file system is reloaded after formatting the disk. Which is logical I think. Is there a place I could put this script, so I can find it in the post section? Or should I do this in an other way? Gabrie From ebrown at lanl.gov Wed Jul 25 14:31:17 2007 From: ebrown at lanl.gov (Ed Brown) Date: Wed, 25 Jul 2007 08:31:17 -0600 Subject: How to transfer variable from one section to another In-Reply-To: References: Message-ID: <46A75EB5.3030601@lanl.gov> Gabrie wrote: > cat << EOF1 >> /call-script.sh > Is there a place I could put this script, so I can find it in the post > section? Or should I do this in an other way? One way to handle this is to use two %post sections, the first not chroot-ed, and copy the script to somewhere under /mnt/sysimage, which is the root of the chroot-ed environment (newly installed filesystem): %post --nochroot cp /call-script.sh /mnt/sysimage/call-script.sh %post ... -Ed From linuxsemi at gmail.com Wed Jul 25 17:25:24 2007 From: linuxsemi at gmail.com (semi linux) Date: Wed, 25 Jul 2007 10:25:24 -0700 Subject: List of kickstart directives? Message-ID: The latest thing I can find is a RH9 reference... Does an up to date (F7) list of kickstart directives exist or is it undocumented? I just tried using my FC4 kickstart with F7 (foolhearty, I know) and, without surprise, it didn't work... I wanted a reference of all the directives and options to help get me on the right path w/o using the GUI tool. - G. From Chip.Shabazian at bankofamerica.com Wed Jul 25 17:28:53 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 25 Jul 2007 10:28:53 -0700 Subject: List of kickstart directives? In-Reply-To: Message-ID: https://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installatio n_Guide-en-US/pt-install-advanced-deployment.html -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of semi linux Sent: Wednesday, July 25, 2007 10:25 AM To: kickstart-list at redhat.com Subject: List of kickstart directives? The latest thing I can find is a RH9 reference... Does an up to date (F7) list of kickstart directives exist or is it undocumented? I just tried using my FC4 kickstart with F7 (foolhearty, I know) and, without surprise, it didn't work... I wanted a reference of all the directives and options to help get me on the right path w/o using the GUI tool. - G. _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From mdehaan at redhat.com Wed Jul 25 17:32:23 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 25 Jul 2007 13:32:23 -0400 Subject: List of kickstart directives? In-Reply-To: References: Message-ID: <46A78927.60107@redhat.com> semi linux wrote: > The latest thing I can find is a RH9 reference... > > Does an up to date (F7) list of kickstart directives exist or is it > undocumented? > > I just tried using my FC4 kickstart with F7 (foolhearty, I know) and, > without surprise, it didn't work... > > I wanted a reference of all the directives and options to help get me > on the right path w/o using the GUI tool. > > - G. Here's the RHEL 5 guide ... which is basically the same as F7 minus the installation key stuff. http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html The F7 guide is largely a pointer to system-config-kickstart http://docs.fedoraproject.org/install-guide/f7/en_US/sn-automating-installation.html From Matt.Fahrner at coat.com Wed Jul 25 17:39:26 2007 From: Matt.Fahrner at coat.com (Matt Fahrner) Date: Wed, 25 Jul 2007 13:39:26 -0400 Subject: List of kickstart directives? In-Reply-To: References: Message-ID: <46A78ACE.3080406@coat.com> What I did is looked at the Red Hat Enterprise Linux 5 Install Guide: http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/Installation_Guide.pdf It should roughly track Fedora... - Matt semi linux wrote: > The latest thing I can find is a RH9 reference... > > Does an up to date (F7) list of kickstart directives exist or is it > undocumented? > > I just tried using my FC4 kickstart with F7 (foolhearty, I know) and, > without surprise, it didn't work... > > I wanted a reference of all the directives and options to help get me > on the right path w/o using the GUI tool. > > - G. > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- --------------------------------------------------------------------- Matt Fahrner 2 South Park St. Chief Systems Architect Willis House Burlington Coat Factory Warehouse Lebanon, N.H. 03766 Tel: (603) 448-4100 x5150 USA Fax: (603) 443-6190 Matt.Fahrner at COAT.COM --------------------------------------------------------------------- From linuxsemi at gmail.com Wed Jul 25 23:42:46 2007 From: linuxsemi at gmail.com (semi linux) Date: Wed, 25 Jul 2007 16:42:46 -0700 Subject: kickstart + fstab/swap trouble (WAS: List of kickstart directives?) Message-ID: Thanks guys... just finished reading it all, I should be able use these as great references... One more question though, is there any way to restrict anaconda from writing an fstab with LABEL=blah style entires? Eg: LABEL=/ / ext3 defaults 1 1 LABEL=SWAP-sda2 swap swap defaults 0 0 would be: /dev/sda1 / ext3 defaults 1 1 /dev/sda2 swap swap defaults 0 0 The reason I ask is that when using FC4, sometimes anaconda really messes things up trying to label swap... - G. On 7/25/07, Matt Fahrner wrote: > What I did is looked at the Red Hat Enterprise Linux 5 Install Guide: > > http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/en-US/Installation_Guide.pdf > > It should roughly track Fedora... > > - Matt > > semi linux wrote: > > The latest thing I can find is a RH9 reference... > > > > Does an up to date (F7) list of kickstart directives exist or is it > > undocumented? > > > > I just tried using my FC4 kickstart with F7 (foolhearty, I know) and, > > without surprise, it didn't work... > > > > I wanted a reference of all the directives and options to help get me > > on the right path w/o using the GUI tool. > > > > - G. > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > -- > --------------------------------------------------------------------- > Matt Fahrner 2 South Park St. > Chief Systems Architect Willis House > Burlington Coat Factory Warehouse Lebanon, N.H. 03766 > Tel: (603) 448-4100 x5150 USA > Fax: (603) 443-6190 Matt.Fahrner at COAT.COM > --------------------------------------------------------------------- > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From thegabeman at gmail.com Thu Jul 26 08:45:37 2007 From: thegabeman at gmail.com (Gabrie) Date: Thu, 26 Jul 2007 10:45:37 +0200 Subject: How to transfer variable from one section to another In-Reply-To: <46A75EB5.3030601@lanl.gov> References: <46A75EB5.3030601@lanl.gov> Message-ID: Thanks !!! Worked excellent. Finally I finished my automatic scripting procedure :-) On 7/25/07, Ed Brown wrote: > Gabrie wrote: > > > cat << EOF1 >> /call-script.sh > > > Is there a place I could put this script, so I can find it in the post > > section? Or should I do this in an other way? > > One way to handle this is to use two %post sections, the first not > chroot-ed, and copy the script to somewhere under /mnt/sysimage, which > is the root of the chroot-ed environment (newly installed filesystem): > > %post --nochroot > cp /call-script.sh /mnt/sysimage/call-script.sh > > %post > ... > > > > -Ed > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From peter at bosgraaf.org Thu Jul 26 10:39:13 2007 From: peter at bosgraaf.org (Peter Bosgraaf) Date: Thu, 26 Jul 2007 12:39:13 +0200 Subject: Fedora 7 kickstart problem Message-ID: <46A879D1.9080005@bosgraaf.org> Hi, First let me apologize for cross-posting. I'm having big troubles with F7 kickstarting with software raid and the updates repository. I filed a anaconda bug report some time ago, but i'm not sure it belongs there. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=249265 Are there others having similar problems? Best regards, Peter From tv at solnet.ch Mon Jul 30 06:54:42 2007 From: tv at solnet.ch (Thomas Vogt) Date: Mon, 30 Jul 2007 08:54:42 +0200 Subject: more arping like checks in fedora7? Message-ID: <46AD8B32.4060304@solnet.ch> Hi I use kickstart for fedora 4-6 and it works very well. Since we have a proxy arp in front of all machines I had to remove all the arping checks in /etc/sysconfig/network-scripts/ifup-eth (line 245,248). This is necessary because the proxy arp always gives answers for any arp requests. Without removing the arping fedora can't set the static ip. With fedora7 this doesn't work any more. I still have removed the arping check in /etc/sysconfig/network-scripts/ifup-eth but the interface eth0 does not set the static ip adress after a reboot. It works fine if i set it via console with "ifconfig eth0 1.2.3.5 netmask 255.255.255.0" and "route add default gw 1.2.3.4" but not if I start|restart it via network the default network script in init.d. Are there any other checks in fedora7 to protect the system from a network conflict? Regards, Thomas Vogt From Joe_Wulf at yahoo.com Mon Jul 30 13:38:35 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Mon, 30 Jul 2007 09:38:35 -0400 Subject: How to setup a kickstart server in Fedora 7 Message-ID: I've been attempting to use my notes for establishing a kickstart server, yet within Fedora 7 I'm not finding so of what I am used to seeing---must be ignorance on my part. I don't see the xinetd.d (maybe don't need it) but I also don't see where/how to get tftp up and running. In RHEL AS4, for example, I'd utilize a copy of the "/usr/lib/syslinux/pxelinux.0" file, but it seems that Fedora 7 doesn't have such a file for copying into /tftpboot/linuxinstall. Also, my small network has a Linksys router that normally serves of DHCP, will I have to disable that to get no dhcp server conflicts with the Fedora7 kickstart server? While I'm at it, do you know of any other gotcha's for employing Fedora 7 as a kickstart server? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: not available URL: From jkeating at j2solutions.net Mon Jul 30 15:35:00 2007 From: jkeating at j2solutions.net (Jesse Keating) Date: Mon, 30 Jul 2007 11:35:00 -0400 Subject: How to setup a kickstart server in Fedora 7 In-Reply-To: References: Message-ID: <20070730113500.059fc212@localhost.localdomain> On Mon, 30 Jul 2007 09:38:35 -0400 "Joe_Wulf" wrote: > In RHEL AS4, for example, I'd utilize a copy of the > "/usr/lib/syslinux/pxelinux.0" file, but it seems that > Fedora 7 doesn't have such a file for copying > into /tftpboot/linuxinstall. You can ask yum to install the package that provides the file for you: yum install /usr/lib/syslinux/pxelinux.0 It comes from the syslinux package. -- Jesse Keating RHCE (jkeating.livejournal.com) Fedora Project (fedoraproject.org/wiki/JesseKeating) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mdehaan at redhat.com Mon Jul 30 15:55:05 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 30 Jul 2007 11:55:05 -0400 Subject: How to setup a kickstart server in Fedora 7 In-Reply-To: References: Message-ID: <46AE09D9.3020008@redhat.com> Joe_Wulf wrote: > I've been attempting to use my notes for establishing a kickstart > server, yet within Fedora 7 I'm not finding > so of what I am used to seeing---must be ignorance on my part. I > don't see the xinetd.d (maybe don't > need it) but I also don't see where/how to get tftp up and running. yum install cobbler ? :) There's really not a compelling reason for setting this up and maintaining all of this manually if you don't have to. > > Also, my small network has a Linksys router that normally serves of > DHCP, will I have to disable that > to get no dhcp server conflicts with the Fedora7 kickstart server? You can edit your DHCP configuration on your router (if doable) to point to your TFTP server -- running a second DHCP server on the TFTP server is not required. This is the "next-server" parameter in ISC dhcp. > > While I'm at it, do you know of any other gotcha's for employing > Fedora 7 as a kickstart server? Nope :) > > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > > www.prosync.com > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From lfarkas at bppiac.hu Tue Jul 31 15:13:25 2007 From: lfarkas at bppiac.hu (Farkas Levente) Date: Tue, 31 Jul 2007 17:13:25 +0200 Subject: how to exclude package from repo Message-ID: <46AF5195.4060607@bppiac.hu> hi, is there any way to exclude package or assign priority to repository in kickstart file? with yum one can exclude packages from a repo or with yum-protect or yum-priority i can assign priority among repos (in conf file). who can i do it in a kickstart file? eg. i'd like to install kmod-xfs from centosplus repo during kickstart, but unfortunately centosplus repo also contains a modified kernel while i wanna use the base kernel. so with yum i can protect or give higher priority to base and updates and in this case kernel not updated from centos plus, but kmod-xfs can be used. of if i can exclude=kernel* from centosplus that's another solution. but none of the above work with kickstart. is there any way to solve my problem? thanks in advance. -- Levente "Si vis pacem para bellum!" From callahant at tessco.com Tue Jul 31 15:29:05 2007 From: callahant at tessco.com (Thomas Callahan) Date: Tue, 31 Jul 2007 11:29:05 -0400 Subject: how to exclude package from repo In-Reply-To: <46AF5195.4060607@bppiac.hu> Message-ID: Put a minus in front of the package name under %packages in your ks file. That excludes that package from being installed. Ie -kde -firefox X11 wireshark Thanks, Tom Callahan On 7/31/07 11:13 AM, "Farkas Levente" wrote: > hi, > is there any way to exclude package or assign priority to repository in > kickstart file? with yum one can exclude packages from a repo or with > yum-protect or yum-priority i can assign priority among repos (in conf > file). who can i do it in a kickstart file? eg. i'd like to install > kmod-xfs from centosplus repo during kickstart, but unfortunately > centosplus repo also contains a modified kernel while i wanna use the > base kernel. so with yum i can protect or give higher priority to base > and updates and in this case kernel not updated from centos plus, but > kmod-xfs can be used. of if i can exclude=kernel* from centosplus that's > another solution. but none of the above work with kickstart. > is there any way to solve my problem? > thanks in advance. > > -- > Levente "Si vis pacem para bellum!" > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lfarkas at bppiac.hu Tue Jul 31 15:55:51 2007 From: lfarkas at bppiac.hu (Farkas Levente) Date: Tue, 31 Jul 2007 17:55:51 +0200 Subject: how to exclude package from repo In-Reply-To: References: Message-ID: <46AF5B87.3000900@bppiac.hu> read my mail!:-) a package from a _given_ repo! Thomas Callahan wrote: > Put a minus in front of the package name under %packages in your ks > file. That excludes that package from being installed. > > Ie > > -kde > -firefox > X11 > wireshark > > Thanks, > Tom Callahan > > > On 7/31/07 11:13 AM, "Farkas Levente" wrote: > > hi, > is there any way to exclude package or assign priority to repository in > kickstart file? with yum one can exclude packages from a repo or with > yum-protect or yum-priority i can assign priority among repos (in conf > file). who can i do it in a kickstart file? eg. i'd like to install > kmod-xfs from centosplus repo during kickstart, but unfortunately > centosplus repo also contains a modified kernel while i wanna use the > base kernel. so with yum i can protect or give higher priority to base > and updates and in this case kernel not updated from centos plus, but > kmod-xfs can be used. of if i can exclude=kernel* from centosplus that's > another solution. but none of the above work with kickstart. > is there any way to solve my problem? > thanks in advance. > > -- > Levente "Si vis pacem para bellum!" > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Levente "Si vis pacem para bellum!" From ebrown at lanl.gov Tue Jul 31 16:09:02 2007 From: ebrown at lanl.gov (Ed Brown) Date: Tue, 31 Jul 2007 10:09:02 -0600 Subject: how to exclude package from repo In-Reply-To: <46AF5195.4060607@bppiac.hu> References: <46AF5195.4060607@bppiac.hu> Message-ID: <46AF5E9E.6090304@lanl.gov> Farkas Levente wrote: > hi, > is there any way to exclude package or assign priority to repository in > kickstart file? with yum one can exclude packages from a repo or with > yum-protect or yum-priority i can assign priority among repos (in conf > file). who can i do it in a kickstart file? eg. i'd like to install > kmod-xfs from centosplus repo during kickstart, but unfortunately > centosplus repo also contains a modified kernel while i wanna use the > base kernel. so with yum i can protect or give higher priority to base > and updates and in this case kernel not updated from centos plus, but > kmod-xfs can be used. of if i can exclude=kernel* from centosplus that's > another solution. but none of the above work with kickstart. > is there any way to solve my problem? > thanks in advance. It's true, ASFAIK, that you can't modify the yum configuration for repositories added in kickstart with the --repos option, and used for %packages. An alternative would be to create the configuration with 'here' docs in %post, and then install the package. Something like: %post ... cat <>/etc/yum.repos.d/centosplus [centosplus] name=CentOSplus baseurl=http://... exclude=kernel* enabled=0 XYZ yum --enable-repo=centosplus install kmod-xfs ... -Ed From dhageman at eecs.ku.edu Tue Jul 31 19:34:56 2007 From: dhageman at eecs.ku.edu (David Hageman) Date: Tue, 31 Jul 2007 14:34:56 -0500 (CDT) Subject: Fedora 7 Kickstart / Stage2 Issue Message-ID: I have been using kickstart to setup our computer labs for the last several releases of Fedora. I thought while I had some time, that I would implement a cobbler setup and roll out Fedora 7. I am running into an issue with kickstarting Fedora 7. I use the boot.iso to create a bootable CD which from the command line type in my kickstart command: ks=http:// Anaconda starts up, grabs an IP address, grabs the kickstart file and at this point attempts to re-initialize the interface using DHCP. The system queries via DHCP several times before it gives up and attempts to retrieve stage2 which fails ... I am at a loss because I watch the DHCP server logs and it sees all the queries and responds to each one. It is like anaconda is ignoring the responses. I have looked at the mailing list for previous problems and solutions and have even set portfast on the port in question, but it failed to help me. I have also set various other options such as noipv6 ksdevice=link loglevel=debug without any success. Anyone have any ideas on this? -- ========================================================= David Hageman Linux/Network Administrator Department of Electrical Engineering and Computer Science University of Kansas 3042 Eaton Hall (785) 864.3923 dhageman at eecs.ku.edu ========================================================= From Chip.Shabazian at bankofamerica.com Tue Jul 31 19:52:23 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Tue, 31 Jul 2007 12:52:23 -0700 Subject: Fedora 7 Kickstart / Stage2 Issue In-Reply-To: Message-ID: try using noipv6 nicdelay=50 linksleep=50 eth0_ethtool="autoneg=on speed=1000 duplex=full" Of course, adjust the ethtool line as appropriate for interface, speed, etc. Let us know if this works for you. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of David Hageman Sent: Tuesday, July 31, 2007 12:35 PM To: kickstart-list at redhat.com Subject: Fedora 7 Kickstart / Stage2 Issue I have been using kickstart to setup our computer labs for the last several releases of Fedora. I thought while I had some time, that I would implement a cobbler setup and roll out Fedora 7. I am running into an issue with kickstarting Fedora 7. I use the boot.iso to create a bootable CD which from the command line type in my kickstart command: ks=http:// Anaconda starts up, grabs an IP address, grabs the kickstart file and at this point attempts to re-initialize the interface using DHCP. The system queries via DHCP several times before it gives up and attempts to retrieve stage2 which fails ... I am at a loss because I watch the DHCP server logs and it sees all the queries and responds to each one. It is like anaconda is ignoring the responses. I have looked at the mailing list for previous problems and solutions and have even set portfast on the port in question, but it failed to help me. I have also set various other options such as noipv6 ksdevice=link loglevel=debug without any success. Anyone have any ideas on this? -- ========================================================= David Hageman Linux/Network Administrator Department of Electrical Engineering and Computer Science University of Kansas 3042 Eaton Hall (785) 864.3923 dhageman at eecs.ku.edu ========================================================= _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From dhageman at eecs.ku.edu Tue Jul 31 20:29:39 2007 From: dhageman at eecs.ku.edu (David Hageman) Date: Tue, 31 Jul 2007 15:29:39 -0500 (CDT) Subject: Fedora 7 Kickstart / Stage2 Issue In-Reply-To: References: Message-ID: On Tue, 31 Jul 2007, Shabazian, Chip wrote: > try using > > noipv6 nicdelay=50 linksleep=50 eth0_ethtool="autoneg=on speed=1000 > duplex=full" > > Of course, adjust the ethtool line as appropriate for interface, speed, > etc. > > Let us know if this works for you. Unfortunately, it did not seem to help. It should also be noted that I did not notice any extended delay when applying nicdelay=50 and linksleep=50. I played around various combinations of each option and was unable to get any new results. Any other ideas? I do appreciate your help! -- ========================================================= David Hageman Linux/Network Administrator Department of Electrical Engineering and Computer Science University of Kansas 3042 Eaton Hall (785) 864.3923 dhageman at eecs.ku.edu ========================================================= From Chip.Shabazian at bankofamerica.com Tue Jul 31 20:34:37 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Tue, 31 Jul 2007 13:34:37 -0700 Subject: Fedora 7 Kickstart / Stage2 Issue In-Reply-To: Message-ID: What happens if you retry the connection from the console? Does it then go through? -----Original Message----- From: David Hageman [mailto:dhageman at eecs.ku.edu] Sent: Tuesday, July 31, 2007 1:30 PM To: Shabazian, Chip Cc: David Hageman; Discussion list about Kickstart Subject: RE: Fedora 7 Kickstart / Stage2 Issue On Tue, 31 Jul 2007, Shabazian, Chip wrote: > try using > > noipv6 nicdelay=50 linksleep=50 eth0_ethtool="autoneg=on speed=1000 > duplex=full" > > Of course, adjust the ethtool line as appropriate for interface, > speed, etc. > > Let us know if this works for you. Unfortunately, it did not seem to help. It should also be noted that I did not notice any extended delay when applying nicdelay=50 and linksleep=50. I played around various combinations of each option and was unable to get any new results. Any other ideas? I do appreciate your help! -- ========================================================= David Hageman Linux/Network Administrator Department of Electrical Engineering and Computer Science University of Kansas 3042 Eaton Hall (785) 864.3923 dhageman at eecs.ku.edu ========================================================= From dhageman at eecs.ku.edu Tue Jul 31 20:52:57 2007 From: dhageman at eecs.ku.edu (David Hageman) Date: Tue, 31 Jul 2007 15:52:57 -0500 (CDT) Subject: Fedora 7 Kickstart / Stage2 Issue In-Reply-To: References: Message-ID: On Tue, 31 Jul 2007, Shabazian, Chip wrote: > > What happens if you retry the connection from the console? Does it then > go through? > Unfortunately, the console doesn't come available until after Stage2 is retrieved and unpacked. :-( That is the part that makes this a bit more difficult. -- ========================================================= David Hageman Linux/Network Administrator Department of Electrical Engineering and Computer Science University of Kansas 3042 Eaton Hall (785) 864.3923 dhageman at eecs.ku.edu ========================================================= From kernel at linuxace.com Tue Jul 31 21:41:03 2007 From: kernel at linuxace.com (Phil Oester) Date: Tue, 31 Jul 2007 14:41:03 -0700 Subject: Fedora 7 Kickstart / Stage2 Issue In-Reply-To: References: Message-ID: <20070731214103.GA27063@linuxace.com> On Tue, Jul 31, 2007 at 02:34:56PM -0500, David Hageman wrote: > > I have been using kickstart to setup our computer labs for the last > several releases of Fedora. I thought while I had some time, that I would > implement a cobbler setup and roll out Fedora 7. > > I am running into an issue with kickstarting Fedora 7. > > I use the boot.iso to create a bootable CD which from the command line > type in my kickstart command: ks=http:// > > Anaconda starts up, grabs an IP address, grabs the kickstart file and at > this point attempts to re-initialize the interface using DHCP. The system > queries via DHCP several times before it gives up and attempts to retrieve > stage2 which fails ... > > I am at a loss because I watch the DHCP server logs and it sees all the > queries and responds to each one. It is like anaconda is ignoring the > responses. > > I have looked at the mailing list for previous problems and solutions and > have even set portfast on the port in question, but it failed to help me. > > I have also set various other options such as noipv6 ksdevice=link > loglevel=debug without any success. > > Anyone have any ideas on this? Did you query bugzilla? http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241783 Phil From dhageman at eecs.ku.edu Tue Jul 31 21:55:05 2007 From: dhageman at eecs.ku.edu (David Hageman) Date: Tue, 31 Jul 2007 16:55:05 -0500 (CDT) Subject: Fedora 7 Kickstart / Stage2 Issue In-Reply-To: <20070731214103.GA27063@linuxace.com> References: <20070731214103.GA27063@linuxace.com> Message-ID: On Tue, 31 Jul 2007, Phil Oester wrote: > > Did you query bugzilla? > > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241783 > > Phil > Indeed I did, but apparently my search terms weren't correct. It is using the e1000 ... so this must be it. Hhmm... I guess I will try Chris Adam's files and see if they work for me. Thanks! -- ========================================================= David Hageman Linux/Network Administrator Department of Electrical Engineering and Computer Science University of Kansas 3042 Eaton Hall (785) 864.3923 dhageman at eecs.ku.edu =========================================================