From clumens at redhat.com Fri Jun 3 15:08:25 2011 From: clumens at redhat.com (Chris Lumens) Date: Fri, 3 Jun 2011 11:08:25 -0400 Subject: need test cases Message-ID: <20110603150824.GL22129@exeter.usersys.redhat.com> I'm working on a major improvement to the kickstart file parser in pykickstart that will allow for you to define your own custom %sections. I think this will be really handy for various specialty purposes. Unfortunately, when I wrote pykickstart back in 2005 I didn't make it easy to do this so I'm having to almost completely rewrite one critical function. In order to make sure I don't screw up anything that was previously working, I'm adding test cases. As you may know, pykickstart already has a lot of test cases for the commands, but there are none for the parser itself. I'd like to change that. What I could use is a little imagination here. If you have a kickstart file that does anything interesting as far as %pre/%post/%traceback scripts, %includes, etc., I would like to see it and include it as a test case with your permission. I'm not really interested in the commands themselves, and I'm not especially interested in the contents of the scripts (that is, if you have some huge script that generates partitioning, it's not really helpful as a test for this). So, what do you have? - Chris From akn.shp at gmail.com Mon Jun 6 11:14:35 2011 From: akn.shp at gmail.com (Ashkan Shirpour) Date: Mon, 6 Jun 2011 15:44:35 +0430 Subject: Logging to a Remote System During the Installation Message-ID: Hello I am setting up a pxe installation server on Fedora 14. Using it I can install Fedora releases(12,13,14,15). I know that Anaconda can sends log messages during the installation to a remote server, but this works only during the installation of Fedora 12. When I want to install other above-mentioned releases, the server receives no log messages. I use similar configuration files for installation of all the releases. The only differences are the paths to installation repo and kickstart file. One of my kickstart files: install url --url="ftp://192.168.31.1/Fedora/12/i386" lang en_US.UTF-8 keyboard us network --bootproto=dhcp --device=eth0 --onboot=on authconfig --enableshadow --passalgo=sha512 --enablefingerprint firewall --service=ssh logging --host=192.168.31.1 --port=514 bootloader --location=mbr --driveorder=sda --append="rhgb quiet" And one of the boot options: /linux/fedora/12/i386/vmlinuz initrd=/linux/fedora/12/i386/initrd ks= ftp://192.168.31.1/ks12 What is wrong? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michael.Gliwinski at henderson-group.com Mon Jun 6 11:18:21 2011 From: Michael.Gliwinski at henderson-group.com (Michael Gliwinski) Date: Mon, 6 Jun 2011 12:18:21 +0100 Subject: need test cases In-Reply-To: <20110603150824.GL22129@exeter.usersys.redhat.com> References: <20110603150824.GL22129@exeter.usersys.redhat.com> Message-ID: <201106061218.22219.Michael.Gliwinski@henderson-group.com> On Friday 03 Jun 2011 16:08:25 Chris Lumens wrote: > What I could use is a little imagination here. If you have a kickstart > file that does anything interesting as far as %pre/%post/%traceback > scripts, %includes, etc., I would like to see it and include it as a > test case with your permission. I'm not really interested in the > commands themselves, and I'm not especially interested in the contents > of the scripts (that is, if you have some huge script that generates > partitioning, it's not really helpful as a test for this). > > So, what do you have? Not much left if you cut contents of the scripts out, here's mine (URLs, IPs and passwords substituted): # Kickstart config file generated by Spacewalk Config Management # Profile Label : centos-5-i386-testing # Date Created : 2011-03-14 11:55:32.0 install text network --bootproto static --device eth0 --ip 10.5.0.16 --netmask 255.255.0.0 --gateway 10.5.0.90 --nameserver 10.5.0.153,10.5.0.173 --hostname test04 url --url http://spacewalk.internal.example.com/ks/dist/centos-5.5-i386 lang en_GB.UTF-8 keyboard uk zerombr clearpart --all --initlabel bootloader --location mbr timezone --utc Europe/London auth --enablemd5 --enableshadow rootpw --iscrypted $1$xSM0PmxP$lK.i7J88n9EEh/u.c2vcF/ reboot skipx key --skip services --enabled=httpd,nfs,snmpd,ntpd --disabled=pcscd,smartd repo --name=vmware-tools-5-i686 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/vmware-tools-5-i686/centos-5.5-i386 repo --name=centos-5-updates-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/centos-5-updates-i386/centos-5.5-i386 repo --name=hgs-nonfree-5-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/hgs-nonfree-5-i386/centos-5.5-i386 repo --name=centos-5-extras-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/centos-5-extras-i386/centos-5.5-i386 repo --name=spacewalk-client-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/spacewalk-client-i386/centos-5.5-i386 repo --name=epel-5-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/epel-5-i386/centos-5.5-i386 repo --name=hgs-rebuids-5-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/hgs-rebuids-5-i386/centos-5.5-i386 repo --name=hgs-5-i386 --baseurl=http://spacewalk.internal.example.com/ks/dist/child/hgs-5-i386/centos-5.5-i386 part /boot --fstype=ext2 --size=200 --ondisk=sda --asprimary --label=boot part pv.01 --size=1024 --grow --ondisk=sda volgroup ct pv.01 logvol swap --fstype=swap --name=swapvol --vgname=ct --recommended logvol / --fstype=ext3 --name=rootvol --vgname=ct --size=1024 --grow %packages @ Base @core # Unneeded "default" packages from @base -NetworkManager -bluez-utils -cryptsetup-luks -irda-utils -ksh -mtools -pcmciautils -smartmontools -talk -tcsh -wireless-tools -ypbind # Needed optional packages from @base aide @editors @printing # Do some exceptions (not needed) from @printing: -hplip -system-config-printer # Only install mutt from @text-internet, others not needed mutt @ftp-server # From @mail-server; only needed to reconfigure sendmail sendmail-cf # From @system-tools openldap-clients # From ? ntp xinetd # VMWare Tools vmware-tools-nox # For Spacewalk registration rhn-setup # Packages required by Progress/OpenEdge java-1.6.0-openjdk oe-common %pre # pre_install_network_config generated code %pre --logfile /tmp/ks-pre.log.1 # resolv.conf setup %post --nochroot # copy logs %post --nochroot --interpreter /usr/bin/python # get Spacewalk re-activation keys %post --logfile /root/ks-rhn-post.log # install Spacewalk keys, prep and register # disable distribution default repositories # apply post-activation actions # post_install_network_config generated code %post --interpreter /usr/bin/python --logfile /root/ks-post.log.2 # yum config tweaks %post --logfile /root/ks-post.log.3 # resolv and FQDN setup # auth setup # sudoers setup # TSM service setup # Progress OpenEdge setup # Python path setup %post --interpreter /usr/bin/python --logfile /root/ks-post.log.4 # patch /etc/bashrc %post # koan environment setup # end of generated kickstart file -- Michael Gliwinski Henderson Group Information Services 9-11 Hightown Avenue, Newtownabby, BT36 4RT Phone: 028 9034 3319 ********************************************************************************************** The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to the email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients, any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing client engagement leter or contract. If you have received this email in error please notify support at henderson-group.com John Henderson (Holdings) Ltd Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern Ireland, BT36 4RT. Registered in Northern Ireland Registration Number NI010588 Vat No.: 814 6399 12 ********************************************************************************* From larry.brigman at gmail.com Mon Jun 6 13:47:13 2011 From: larry.brigman at gmail.com (Larry Brigman) Date: Mon, 6 Jun 2011 06:47:13 -0700 Subject: Logging to a Remote System During the Installation In-Reply-To: References: Message-ID: Add syslog=log_server_ipaddr On Jun 6, 2011 4:21 AM, "Ashkan Shirpour" wrote: Hello I am setting up a pxe installation server on Fedora 14. Using it I can install Fedora releases(12,13,14,15). I know that Anaconda can sends log messages during the installation to a remote server, but this works only during the installation of Fedora 12. When I want to install other above-mentioned releases, the server receives no log messages. I use similar configuration files for installation of all the releases. The only differences are the paths to installation repo and kickstart file. One of my kickstart files: install url --url="ftp://192.168.31.1/Fedora/12/i386" lang en_US.UTF-8 keyboard us network --bootproto=dhcp --device=eth0 --onboot=on authconfig --enableshadow --passalgo=sha512 --enablefingerprint firewall --service=ssh logging --host=192.168.31.1 --port=514 bootloader --location=mbr --driveorder=sda --append="rhgb quiet" And one of the boot options: /linux/fedora/12/i386/vmlinuz initrd=/linux/fedora/12/i386/initrd ks= ftp://192.168.31.1/ks12 What is wrong? Thanks _______________________________________________ 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 akn.shp at gmail.com Mon Jun 6 15:46:46 2011 From: akn.shp at gmail.com (Ashkan Shirpour) Date: Mon, 6 Jun 2011 20:16:46 +0430 Subject: Logging to a Remote System During the Installation In-Reply-To: References: Message-ID: Thanks, It works BUT only for Fedora 13, I am still cannot receive any log messages on the log server during the installation of Fedora 14 and 15. -------------- next part -------------- An HTML attachment was scrubbed... URL: From beyonddc.storage at gmail.com Wed Jun 8 15:57:19 2011 From: beyonddc.storage at gmail.com (Chun Tat David Chu) Date: Wed, 8 Jun 2011 11:57:19 -0400 Subject: Post-Installation scripts execution ordering Message-ID: Hi All, I have a kickstart file with multiple %post. The reason why I am doing so is because I have %post that is a bash script and I have another %post that is a Perl script. Does Anaconda executes %post in sequential order or in parallel with threads? What I want to accomplish is I want my %post bash script runs first then my %post Perl script. Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: From hbrown at divms.uiowa.edu Wed Jun 8 16:16:55 2011 From: hbrown at divms.uiowa.edu (Hugh Brown) Date: Wed, 08 Jun 2011 11:16:55 -0500 Subject: Post-Installation scripts execution ordering In-Reply-To: References: Message-ID: <4DEFA077.2000604@divms.uiowa.edu> On 06/08/2011 10:57 AM, Chun Tat David Chu wrote: > Hi All, > > I have a kickstart file with multiple %post. The reason why I am doing so > is because I have %post that is a bash script and I have another %post that > is a Perl script. > > Does Anaconda executes %post in sequential order or in parallel with > threads? > > What I want to accomplish is I want my %post bash script runs first then my > %post Perl script. > > Thanks, > > David It should be easy to test, have each script put a time stamp into a file and compare the time stamps. Depending on your kickstart set up, you can also have the bash script copy the perl script to the local system and then call it, or run it from an nfs share. Hugh From root at nachtmaus.us Wed Jun 8 16:32:15 2011 From: root at nachtmaus.us (root at nachtmaus.us) Date: Wed, 8 Jun 2011 16:32:15 +0000 Subject: Post-Installation scripts execution ordering In-Reply-To: References: Message-ID: <1770382331-1307550736-cardhu_decombobulator_blackberry.rim.net-1895212573-@b25.c5.bise6.blackberry> Can you embed the perl script within the shell script, or have the shell script exec the perl script at its end? Sent via BlackBerry from T-Mobile -----Original Message----- From: Chun Tat David Chu Sender: kickstart-list-bounces at redhat.com Date: Wed, 8 Jun 2011 11:57:19 To: Reply-To: Discussion list about Kickstart Subject: Post-Installation scripts execution ordering _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From clumens at redhat.com Wed Jun 8 16:58:17 2011 From: clumens at redhat.com (Chris Lumens) Date: Wed, 8 Jun 2011 12:58:17 -0400 Subject: Post-Installation scripts execution ordering In-Reply-To: References: Message-ID: <20110608165817.GV22129@exeter.usersys.redhat.com> > I have a kickstart file with multiple %post. The reason why I am doing so > is because I have %post that is a bash script and I have another %post that > is a Perl script. > > Does Anaconda executes %post in sequential order or in parallel with > threads? > > What I want to accomplish is I want my %post bash script runs first then my > %post Perl script. All %post scripts should be executed in the order they are encountered in the kickstart file. - Chris From Pablo.Iranzo at redhat.com Wed Jun 8 17:08:01 2011 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?utf-8?Q?G=C3=B3mez?=) Date: Wed, 8 Jun 2011 13:08:01 -0400 (EDT) Subject: Post-Installation scripts execution ordering In-Reply-To: <20110608165817.GV22129@exeter.usersys.redhat.com> Message-ID: ----- Mensaje original ----- > De: "Chris Lumens" > Para: kickstart-list at redhat.com > Enviados: Mi?rcoles, 8 de Junio 2011 18:58:17 > Asunto: Re: Post-Installation scripts execution ordering > > > I have a kickstart file with multiple %post. The reason why I am > > doing so > > is because I have %post that is a bash script and I have another > > %post that > > is a Perl script. > > > > Does Anaconda executes %post in sequential order or in parallel > > with > > threads? > > > > What I want to accomplish is I want my %post bash script runs first > > then my > > %post Perl script. > > All %post scripts should be executed in the order they are > encountered > in the kickstart file. It always did it that way on the ones I've... Regards Pablo From beyonddc.storage at gmail.com Wed Jun 8 19:15:44 2011 From: beyonddc.storage at gmail.com (Chun Tat David Chu) Date: Wed, 8 Jun 2011 15:15:44 -0400 Subject: Post-Installation scripts execution ordering In-Reply-To: <20110608165817.GV22129@exeter.usersys.redhat.com> References: <20110608165817.GV22129@exeter.usersys.redhat.com> Message-ID: Hi Chris, Yup, what you said is correct. I just tried it. Thanks, David On Wed, Jun 8, 2011 at 12:58 PM, Chris Lumens wrote: > > I have a kickstart file with multiple %post. The reason why I am doing > so > > is because I have %post that is a bash script and I have another %post > that > > is a Perl script. > > > > Does Anaconda executes %post in sequential order or in parallel with > > threads? > > > > What I want to accomplish is I want my %post bash script runs first then > my > > %post Perl script. > > All %post scripts should be executed in the order they are encountered > in the kickstart file. > > - Chris > > _______________________________________________ > 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 jwells at rackspace.com Tue Jun 14 19:17:14 2011 From: jwells at rackspace.com (Jeff Wells) Date: Tue, 14 Jun 2011 19:17:14 +0000 Subject: Issue using --percent with "logvol" in RHEL 6 kickstart file Message-ID: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> Issue: When kicking with percent-based partitions, the logical volume creation errors. logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90 Error: An error was encountered while activating your storage configuration lvcreate failed for vglocal00/log00: 11:30:57,333 ERROR: Unable to create new logical volume with no extents Bugfix: http://rhn.redhat.com/errata/RHBA-2011-0530.html Based on the bug report, it appears to be fixed in RHEL 6.1 but I am still getting the error. Has anyone else seen this or have a workaround? This is the partitioning scheme I am trying to accomplish: part /boot --fstype "ext3" --size=250 --asprimary part pv.01 --size=1 --grow --ondisk=sda volgroup vglocal00 pv.01 logvol swap --fstype swap --name=swap00 --vgname=vglocal00 --size=2048 logvol /tmp --fstype ext4 --name=tmp00 --vgname=vglocal00 --size=2048 logvol /var/log --fstype ext4 --name=log00 --vgname=vglocal00 --percent=10 logvol / --fstype ext4 --name=root00 --vgname=vglocal00 --percent=90 Thanks, -- Jeff Wells - Supervisor, RHCE OS Deployment Services | Kickstart & RPM Dev Rackspace.com Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com, and delete the original message. Your cooperation is appreciated. From jwells at rackspace.com Tue Jun 14 19:58:10 2011 From: jwells at rackspace.com (Jeff Wells) Date: Tue, 14 Jun 2011 19:58:10 +0000 Subject: Issue using --percent with "logvol" in RHEL 6 kickstart file In-Reply-To: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> References: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> Message-ID: I have tried adding the --size and --grow based on the the RHEL 6 documentation but still get the same error: part /boot --fstype "ext3" --size=250 --asprimary part pv.01 --size=1 --grow --ondisk=sda volgroup vglocal00 pv.01 logvol swap --fstype swap --name=swap00 --vgname=vglocal00 --size=2048 logvol /tmp --vgname=vglocal00 --size=2048 --name=tmp00 logvol /var/log --vgname=vglocal00 --fstype ext4 --size=1 --name=log00 --grow --percent=10 logvol / --vgname=vglocal00 --fstype ext4 --size=1 --name=root00 --grow --percent=90 On Jun 14, 2011, at 2:17 PM, Jeff Wells wrote: > Issue: > When kicking with percent-based partitions, the logical volume creation errors. > logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90 > > Error: > An error was encountered while activating your storage configuration > lvcreate failed for vglocal00/log00: 11:30:57,333 ERROR: Unable to create new logical volume with no extents > > Bugfix: > http://rhn.redhat.com/errata/RHBA-2011-0530.html > > Based on the bug report, it appears to be fixed in RHEL 6.1 but I am still getting the error. > > Has anyone else seen this or have a workaround? This is the partitioning scheme I am trying to accomplish: > > part /boot --fstype "ext3" --size=250 --asprimary > part pv.01 --size=1 --grow --ondisk=sda > volgroup vglocal00 pv.01 > logvol swap --fstype swap --name=swap00 --vgname=vglocal00 --size=2048 > logvol /tmp --fstype ext4 --name=tmp00 --vgname=vglocal00 --size=2048 > logvol /var/log --fstype ext4 --name=log00 --vgname=vglocal00 --percent=10 > logvol / --fstype ext4 --name=root00 --vgname=vglocal00 --percent=90 > > Thanks, > > -- > Jeff Wells - Supervisor, RHCE > OS Deployment Services | Kickstart & RPM Dev > Rackspace.com > > > > > Confidentiality Notice: This e-mail message (including any attached or > embedded documents) is intended for the exclusive and confidential use of the > individual or entity to which this message is addressed, and unless otherwise > expressly indicated, is confidential and privileged information of Rackspace. > Any dissemination, distribution or copying of the enclosed material is prohibited. > If you receive this transmission in error, please notify us immediately by e-mail > at abuse at rackspace.com, and delete the original message. > Your cooperation is appreciated. > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list This email may include confidential information. If you received it in error, please delete it. From Moray.Henderson at ict-software.org Thu Jun 16 08:38:02 2011 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 16 Jun 2011 09:38:02 +0100 Subject: Issue using --percent with "logvol" in RHEL 6 kickstart file In-Reply-To: References: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> Message-ID: <000701cc2c00$cd76f850$6864e8f0$@Henderson@ict-software.org> Jeff Wells wrote: > I have tried adding the --size and --grow based on the the RHEL 6 > documentation but still get the same error: > > part /boot --fstype "ext3" --size=250 --asprimary > part pv.01 --size=1 --grow --ondisk=sda > volgroup vglocal00 pv.01 > logvol swap --fstype swap --name=swap00 --vgname=vglocal00 -- > size=2048 > logvol /tmp --vgname=vglocal00 --size=2048 --name=tmp00 > logvol /var/log --vgname=vglocal00 --fstype ext4 --size=1 -- > name=log00 --grow --percent=10 > logvol / --vgname=vglocal00 --fstype ext4 --size=1 --name=root00 > --grow --percent=90 > > On Jun 14, 2011, at 2:17 PM, Jeff Wells wrote: > > Issue: > > When kicking with percent-based partitions, the logical volume > creation errors. > > logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90 > > > > Error: > > An error was encountered while activating your storage configuration > > lvcreate failed for vglocal00/log00: 11:30:57,333 ERROR: Unable to > create new logical volume with no extents How big is the disk you are installing to? What happens if you calculate the 10 and 90 percent yourself and put those numbers in the --size parameter instead of using --percent? Round your 10% up to the nearest extent-sized boundary. Work out the numbers for the smallest disk it is likely to encounter, and use --grow if it needs to be able to handle larger disks too. I found in RHEL 5 that kickstart's LV calculations would sometimes round a size down to 0 if I wasn't dividing the disk using exact extent-sized proportions. Moray. "To err is human; to purr, feline." From srobson at cadence.com Thu Jun 16 16:22:37 2011 From: srobson at cadence.com (Steve Robson) Date: Thu, 16 Jun 2011 17:22:37 +0100 Subject: Issue using --percent with "logvol" in RHEL 6 kickstart file In-Reply-To: References: Message-ID: <4DFA2DCD.5010701@cadence.com> kickstart-list-request at redhat.com wrote: > Jeff Wells wrote: >> > I have tried adding the --size and --grow based on the the RHEL 6 >> > documentation but still get the same error: >> > >> > part /boot --fstype "ext3" --size=250 --asprimary >> > part pv.01 --size=1 --grow --ondisk=sda >> > volgroup vglocal00 pv.01 >> > logvol swap --fstype swap --name=swap00 --vgname=vglocal00 -- >> > size=2048 >> > logvol /tmp --vgname=vglocal00 --size=2048 --name=tmp00 >> > logvol /var/log --vgname=vglocal00 --fstype ext4 --size=1 -- >> > name=log00 --grow --percent=10 >> > logvol / --vgname=vglocal00 --fstype ext4 --size=1 --name=root00 >> > --grow --percent=90 >> > >> > On Jun 14, 2011, at 2:17 PM, Jeff Wells wrote: >>> > > Issue: >>> > > When kicking with percent-based partitions, the logical volume >> > creation errors. >>> > > logvol / --vgname=myvg --size=1 --name=rootvol --grow --percent=90 >>> > > >>> > > Error: >>> > > An error was encountered while activating your storage configuration >>> > > lvcreate failed for vglocal00/log00: 11:30:57,333 ERROR: Unable to >> > create new logical volume with no extents It might be the order in which you have specified things. The on-line documentation* specifies the syntax as: logvol --vgname= --size= --name= and "fstype", "grow" and "percent" are all options. Try re-ordering things: part /boot --fstype "ext3" --size=250 --asprimary part pv.01 --size=1 --grow --ondisk=sda volgroup vglocal00 pv.01 logvol swap --vgname=vglocal00 --size=2048 --name=swap00 --fstype swap logvol /tmp --vgname=vglocal00 --size=2048 --name=tmp00 logvol /var/log --vgname=vglocal00 --size=1 --name=log00 --grow --percent=10 --fstype ext4 logvol / --vgname=vglocal00 --size=1 --name=root00 --grow --percent=90 --fstype ext4 -- Regards, Steve *http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html From clumens at redhat.com Mon Jun 20 13:58:19 2011 From: clumens at redhat.com (Chris Lumens) Date: Mon, 20 Jun 2011 09:58:19 -0400 Subject: Issue using --percent with "logvol" in RHEL 6 kickstart file In-Reply-To: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> References: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> Message-ID: <20110620135819.GB22129@exeter.usersys.redhat.com> > part /boot --fstype "ext3" --size=250 --asprimary > part pv.01 --size=1 --grow --ondisk=sda > volgroup vglocal00 pv.01 > logvol swap --fstype swap --name=swap00 --vgname=vglocal00 --size=2048 > logvol /tmp --fstype ext4 --name=tmp00 --vgname=vglocal00 --size=2048 > logvol /var/log --fstype ext4 --name=log00 --vgname=vglocal00 --percent=10 > logvol / --fstype ext4 --name=root00 --vgname=vglocal00 --percent=90 What happens if you specify pv.01 to be big enough to hold everything you're putting into it? part pv.01 --size=4096 --grow --ondisk=sda - Chris From jwells at rackspace.com Mon Jun 20 16:41:27 2011 From: jwells at rackspace.com (Jeff Wells) Date: Mon, 20 Jun 2011 16:41:27 +0000 Subject: Issue using --percent with "logvol" in RHEL 6 kickstart file In-Reply-To: <20110620135819.GB22129@exeter.usersys.redhat.com> References: <14177_1308079037_p5EJHBon015638_E90B420F-940C-40DC-A0E0-300118069E5F@rackspace.com> <20110620135819.GB22129@exeter.usersys.redhat.com> Message-ID: <5BE804AE-2424-4A8C-9D1C-C2352AC4ADAB@rackspace.com> Moving from 6.0 to 6.1 took care of it. Thanks guys, --Jeff On Jun 20, 2011, at 8:58 AM, Chris Lumens wrote: >> part /boot --fstype "ext3" --size=250 --asprimary >> part pv.01 --size=1 --grow --ondisk=sda >> volgroup vglocal00 pv.01 >> logvol swap --fstype swap --name=swap00 --vgname=vglocal00 --size=2048 >> logvol /tmp --fstype ext4 --name=tmp00 --vgname=vglocal00 --size=2048 >> logvol /var/log --fstype ext4 --name=log00 --vgname=vglocal00 --percent=10 >> logvol / --fstype ext4 --name=root00 --vgname=vglocal00 --percent=90 > > What happens if you specify pv.01 to be big enough to hold everything > you're putting into it? > > part pv.01 --size=4096 --grow --ondisk=sda > > - Chris > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From arnaubria at pic.es Thu Jun 30 15:42:36 2011 From: arnaubria at pic.es (Arnau Bria) Date: Thu, 30 Jun 2011 17:42:36 +0200 Subject: rh6 kickstart network device and /etc/sysconfig/network Message-ID: <20110630174236.6a6f59ec@lx-arnau.pic.es> Hi all, I've looked into list archives and did not find an exact reference to my problem, so I'd like to confirm if I have a real problem or not. *I don't know if this kickstart or rh6 installation problem, so sorry if this is not the proper list to ask so. I'm trying to install a new rh6 host with non default netwrok device (eth1): so, kickstart line looks like: network --bootproto=static --device=eth1 --gateway=X.X.X.X --hostname=hostname --ip=Y.Y.Y.Y --nameserver=Z.Z.Z.Z --netmask=255.255.255.128 --onboot=on and the host if installed successfully, but, when I check network conf, GATEWAY info is not written into /etc/sysconfig/network but into /etc/sysconfig/network-scripts/ifcfg-eth1 . is this a desired behaviour? is kickstart involved in this problem? Cheers, Arnau From Moray.Henderson at ict-software.org Thu Jun 30 16:35:52 2011 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Thu, 30 Jun 2011 17:35:52 +0100 Subject: rh6 kickstart network device and /etc/sysconfig/network In-Reply-To: <20110630174236.6a6f59ec@lx-arnau.pic.es> References: <20110630174236.6a6f59ec@lx-arnau.pic.es> Message-ID: <000001cc3743$c7eee340$57cca9c0$@Henderson@ict-software.org> Arnau Bria wrote: > Hi all, > > I've looked into list archives and did not find an exact reference to > my problem, so I'd like to confirm if I have a real problem or not. > > *I don't know if this kickstart or rh6 installation problem, so sorry > if this is not the proper list to ask so. > > > I'm trying to install a new rh6 host with non default netwrok > device (eth1): > > so, kickstart line looks like: > > network --bootproto=static --device=eth1 --gateway=X.X.X.X > --hostname=hostname --ip=Y.Y.Y.Y > --nameserver=Z.Z.Z.Z --netmask=255.255.255.128 > --onboot=on > > and the host if installed successfully, but, when I check network conf, > GATEWAY info is not written into /etc/sysconfig/network but > into /etc/sysconfig/network-scripts/ifcfg-eth1 . > > is this a desired behaviour? is kickstart involved in this problem? I've been poking around the network config in CentOS 5 recently. In that OS, specifying GATEWAY in the ifcfg-eth1 script should not be a problem (although possibly not exactly desired) - it scans those files as well when setting up the default route. Does it make a difference if you specify --gateway= before --device? (never tried that myself, so don't know if it's supposed to work). Moray. "To err is human; to purr, feline."