From hawk at tbi.univie.ac.at Wed Oct 1 07:09:18 2014 From: hawk at tbi.univie.ac.at (Richard Neuboeck) Date: Wed, 01 Oct 2014 09:09:18 +0200 Subject: Always use local disk for driveorder In-Reply-To: <5429235E.8000701@gmail.com> References: <5429235E.8000701@gmail.com> Message-ID: <542BA89E.8020108@tbi.univie.ac.at> Hi, I had a similar problem. As it has already been described one possible way is to use /dev/disk/by-path/pci-*-usb-* to check for USB devices. In my case I had to consider different partition layouts depending on the disks available so I created a pre-install script that checks which disks are usable for the installation, create a layout accordingly and include that again in the kickstart config (%include /tmp/partition-schema) http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_4._Pre-installation_Script For checking USB devices another way would be udevadm info --query=path --name=$dev | grep -q -e '/usb' In your pre install script you could i.e. check for the availability of an HBA and if one is present consider the size of the devices or the 'manufacture name' when probing the device to make your choice which device to use and which to ignore. I would imagine that the SAN disk is larger than an internal disk, or the manufacture is the one that provides the HBA, so this may be a criterion. -Richard -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From kevin.r.miller at lmco.com Thu Oct 2 16:35:31 2014 From: kevin.r.miller at lmco.com (Miller, Kevin R) Date: Thu, 2 Oct 2014 16:35:31 +0000 Subject: %includes issues Message-ID: <30FCA8027710C94EB0B33D8ACDC9248824F65E9F@HDXDSP33.us.lmco.com> I have an operational Cobbler kickstart environment that is working great. In addition I modified the kickstart file and have incorporated it into a DVD based kickstart. The changes that were required were to remove SNIPPET calls and change the "url" command to be "cdrom". I have pasted the kickstart files for each below. #######Cobbler version ############## %include /tmp/diskparam authconfig --enableshadow --passalgo=sha512 text firewall --disabled firstboot --disable keyboard us lang en_US url --url=$tree reboot %pre $SNIPPET('disk_choose') %end %packages $SNIPPET('my_pkgs') %end %post $SNIPPET('my_post') %end ############end cobbler version################### ##############DVD Version##################### %include /tmp/diskparam authconfig --enableshadow --passalgo=sha512 text firewall --disabled firstboot --disable keyboard us lang en_US cdrom reboot %pre %include '/mnt/stage2/ks/includes/disk_choose' %end %packages %include '/mnt/stage2/ks/includes/my_pkgs' %end %post %include '/mnt/stage2/ks/includes/my_post' %end ##########end DVD version##################### What I would like to is make a single kickstart file that could be used for both Cobbler/net based and DVD based installations. I added some logic to the %pre section to adjust but it doesn't seem to be working. Logic is listed below. The logic works when I test it outside of kickstart but the kickstart doesn't seem to be interpreting the $basepath variable. When I interrupt a kickstart using a ctl-f2 and look at /tmp/ks.cfg it just shows the base kickstart file and not an interpreted one. Any help would be appreciated. If any ideas on how to accomplish the same thing are out the please let me know. %pre #!/bin/bash if [ `/bin/grep cdrom /proc/cmdline | wc -l` -gt 0 ] then touch /tmp/yes_cdrom basepath=/mnt/stage2/ks/ else touch /tmp/no_cdrom basepath=http://10.0.0.100/ fi %include "${basepath}includes/disk_choose" -------------- next part -------------- An HTML attachment was scrubbed... URL: From spikewhitetx at gmail.com Sat Oct 4 21:50:39 2014 From: spikewhitetx at gmail.com (Spike White) Date: Sat, 4 Oct 2014 16:50:39 -0500 Subject: %include issues Message-ID: > What I would like to is make a single kickstart file that could be used for both Cobbler/net based and DVD based installations. I added > some logic to the %pre section to adjust but it doesn?t seem to be working. Logic is listed below. The logic works when I test it > outside of kickstart but the kickstart doesn?t seem to be interpreting the $basepath variable. When I interrupt a kickstart using a ctl-f2 > and look at /tmp/ks.cfg it just shows the base kickstart file and not an interpreted one. Any help would be appreciated. If any ideas on > how to accomplish the same thing are out the please let me know. > > %pre > #!/bin/bash > if [ `/bin/grep cdrom /proc/cmdline | wc -l` -gt 0 ] > then > touch /tmp/yes_cdrom > basepath=/mnt/stage2/ks/ > else > touch /tmp/no_cdrom > basepath=http://10.0.0.100/ > fi > %include "${basepath}includes/disk_choose" Don't think you can use %include in a %pre section. As this section is being parsed by /bin/bash. But you can accomplish the same effect by using bash-based syntax. [[ -f /tmp/yes_cdrom ]] && cat ${basepath}includes/disk_choose > /tmp/disk_choose || (cd /tmp; wget ${basepath}includes/disk_choose) then in your main ks.cfg section: %include /tmp/disk_choose Spike -------------- next part -------------- An HTML attachment was scrubbed... URL: From gczarcinski at gmail.com Sun Oct 26 17:24:56 2014 From: gczarcinski at gmail.com (Gene Czarcinski) Date: Sun, 26 Oct 2014 13:24:56 -0400 Subject: kickstart install with liveimg Message-ID: <544D2E68.6060506@gmail.com> Previously I asked about being able to run kickstart with liveinst. Earlier today I realized that I had asked the wrong question. The right wquestion is how to do a kickstart install where I specify liveimg to point to a previously built filesystem like one you get from a "live" iso. First, some background: 1. My disk layouts/partitioning separates my data from the system (software). 2. I backup my data. 3. If I need to reinstall a system, I install it. Of course, this covers when I am current running Fedora X and am installing Fedora X+1. I never install over a working system and I do not do upgrades. I use kickstart to define the system parameters, the package selection, *and* the partition layouts. 4. I test both the install and the restore processes to make sure they work. You cannot wait until you need them to find out they do not work. Using pre-tested kickstart files increases the likelyhood that everything works as expected. 5. When I install a system (the software) I want to have something stable. In the past this meant using the distribution dvd or something similar that I created using mock/pungi. 6. With Fedora 21 I sense that there is a movement to productize Fedora and use live installs so I decided to revist how I did an install. So, now my question is how do i use liveimg in a kickstart file and how do I boot that. Ideally, I would like to use something like Fedora-Live-Workstation*.iso, boot it up and be able top specify ks= on the boot cmdline where that kickstart file has something like liveimg --url=file://run/install/live Tried this and cannot get it to work. I also tried a different kickstart file where I specify liveimg --url=http://. This did not work either. I also tried that last case with bootup of a netinstall iso. This worked (sort of). It did the install and then crashed with a traceback. Before reporting anything, I want to understand how to do it (specify it) correctly so that it should work. Yes, this was all done with F21 Beta-RC1 and anaconda-21.48.12-1. Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brandon.Ess at atk.com Fri Oct 31 20:48:58 2014 From: Brandon.Ess at atk.com (Ess, Brandon) Date: Fri, 31 Oct 2014 20:48:58 +0000 Subject: RHEL 5/6/7 Kickstart Options Message-ID: <801C33F0E4A1B8418D4A213ED77C1B1F37F7E81D@mn05svcwem002.atk.com> Hello, I'm working on Kickstart scripts targeted towards RHEL 5/6/7 and I would like to make them all as portable and reusable as possible. I understand some options and flags were added in newer releases of Anaconda but I cannot find documentation stating which options were added in which Anaconda version. A "works with RHEL {version}" would also help. My current question is this, for package selection I would like to also install optional packages using the --optional parameter at %packages --optional but for a RHEL6 installs Anaconda throws the error "no such option: --optional" Is the --optional parameter not available for RHEL6 installs? ###################### # Package Selection # ###################### #Core Packages %packages --optional @core @base @Compatibility libraries @Desktop @Development tools @General Purpose Desktop @Server Platform Development @X Window System ntp Thanks, Brandon -------------- next part -------------- An HTML attachment was scrubbed... URL: From chavanpushpendra at gmail.com Fri Oct 31 22:47:13 2014 From: chavanpushpendra at gmail.com (Mr. Pushpendra Chavan) Date: Sat, 1 Nov 2014 04:17:13 +0530 Subject: RHEL 5/6/7 Kickstart Options In-Reply-To: <801C33F0E4A1B8418D4A213ED77C1B1F37F7E81D@mn05svcwem002.atk.com> References: <801C33F0E4A1B8418D4A213ED77C1B1F37F7E81D@mn05svcwem002.atk.com> Message-ID: Hello Brandon, You are actually doing it wrong. You should try the following way. *%packages at group1@group2 --nodefaults at group3 --optionalpackage1package2-package3* The option --optional shall be used with the package group not with %packages section. The same is available in Red Hat Enterprise Linux 6[1] and 7[2] as well. A link[3] from Fedora Documentation also explains about it. [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Installation_Guide/index.html#s1-kickstart2-packageselection ? ?[2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-packages ? ?[3] https://fedorahosted.org/revisor/wiki/KickstartPackageSelection? ?Regards,? ?Pushp? ?? ?endra? On Sat, Nov 1, 2014 at 2:18 AM, Ess, Brandon wrote: > Hello, > > > > I?m working on Kickstart scripts targeted towards RHEL 5/6/7 and I would > like to make them all as portable and reusable as possible. I understand > some options and flags were added in newer releases of Anaconda but I > cannot find documentation stating which options were added in which > Anaconda version. A ?works with RHEL {version}? would also help. > > > > My current question is this, for package selection I would like to also > install optional packages using the --optional parameter at *%packages > --optional *but for a RHEL6 installs Anaconda throws the error ?*no such > option: --optional*? > > > > Is the --optional parameter not available for RHEL6 installs? > > > > *######################* > > *# Package Selection #* > > *######################* > > > > *#Core Packages* > > *%packages --optional* > > *@core* > > *@base* > > *@Compatibility libraries* > > *@Desktop* > > *@Development tools* > > *@General Purpose Desktop* > > *@Server Platform Development* > > *@X Window System* > > *ntp* > > > > Thanks, > > > > Brandon > > > > _______________________________________________ > 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: