From smah at vmware.com Fri Apr 7 00:01:22 2006 From: smah at vmware.com (Stephen Mah) Date: Thu, 06 Apr 2006 17:01:22 -0700 Subject: part-include Message-ID: <4435ABD2.9000903@vmware.com> I have a %pre script that writes to /tmp/part-include depending on the hard drive layout. The file, part-include is successfully written, but kickstart seems to ignore it. I've tried putting, before the %pre section and in the %pre section. %include /tmp/part-include Where do you put this line? From phr at doc.ic.ac.uk Fri Apr 7 12:28:19 2006 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Fri, 7 Apr 2006 13:28:19 +0100 (BST) Subject: part-include In-Reply-To: <4435ABD2.9000903@vmware.com> References: <4435ABD2.9000903@vmware.com> Message-ID: On Thu, 6 Apr 2006, Stephen Mah wrote: > I have a %pre script that writes to /tmp/part-include depending on the hard > drive layout. > The file, part-include is successfully written, but kickstart seems to ignore > it. > > I've tried putting, before the %pre section and in the %pre section. > %include /tmp/part-include Which version of RHEL/Fedora? I know I had problems with %include in older releases. Cheers, Phil From lists.james at gmail.com Fri Apr 7 14:09:27 2006 From: lists.james at gmail.com (James Puellmann) Date: Fri, 07 Apr 2006 09:09:27 -0500 Subject: part-include In-Reply-To: References: <4435ABD2.9000903@vmware.com> Message-ID: <44367297.4020106@gmail.com> I've used %include for partitioning without any problems with RHEL ES 4 by putting the partition %include directive between the "mouse" and "bootloader" options. (before the %pre) and then doing this in the %pre: cat > /tmp/include << EOF zerombr yes clearpart --all partition /boot --fstype=ext3 --size=200 partition swap --size=2000 partition pv.01 --size=1000 --grow volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 --grow logvol /tmp --vgname=myvg --name=tmp --size=1024 EOF Philip Rowlands wrote: > On Thu, 6 Apr 2006, Stephen Mah wrote: > >> I have a %pre script that writes to /tmp/part-include depending on >> the hard drive layout. >> The file, part-include is successfully written, but kickstart seems >> to ignore it. >> >> I've tried putting, before the %pre section and in the %pre section. >> %include /tmp/part-include > > > Which version of RHEL/Fedora? I know I had problems with %include in > older releases. > > > Cheers, > Phil > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From Gordon.Keegan at FMR.COM Fri Apr 7 16:16:10 2006 From: Gordon.Keegan at FMR.COM (Keegan, Gordon) Date: Fri, 7 Apr 2006 12:16:10 -0400 Subject: part-include Message-ID: <942A778F73A72141889C1F53A8EAA1C502D3ECE0@MSGMMKCLM2WIN.DMN1.FMR.COM> Noticing that your address is "vmware.com", just in case you are trying to kickstart VMware ESX 2.x.x, it is based on an older version of anaconda that doesn't support the part-include functionality. You can have a %pre section, but the ks.cfg file won't get re-read to pick up a new partition layout. I haven't looked at it yet, but this should be fixed in ESX 3, which is based on RHEL 3. Gordon Keegan -----Original Message----- From: Stephen Mah [mailto:smah at vmware.com] Sent: Thursday, April 06, 2006 8:01 PM To: Discussion list about Kickstart Subject: part-include I have a %pre script that writes to /tmp/part-include depending on the hard drive layout. The file, part-include is successfully written, but kickstart seems to ignore it. I've tried putting, before the %pre section and in the %pre section. %include /tmp/part-include Where do you put this line? From smah at vmware.com Fri Apr 7 16:17:05 2006 From: smah at vmware.com (Stephen Mah) Date: Fri, 07 Apr 2006 09:17:05 -0700 Subject: part-include In-Reply-To: <44367297.4020106@gmail.com> References: <4435ABD2.9000903@vmware.com> <44367297.4020106@gmail.com> Message-ID: <44369081.80209@vmware.com> James, Thank You, that worked like a charm! steve James Puellmann wrote: > I've used %include for partitioning without any problems with RHEL ES > 4 by putting the partition %include directive between the "mouse" and > "bootloader" options. (before the %pre) and then doing this in the %pre: > > cat > /tmp/include << EOF > zerombr yes > clearpart --all > partition /boot --fstype=ext3 --size=200 > partition swap --size=2000 > partition pv.01 --size=1000 --grow > volgroup myvg pv.01 > logvol / --vgname=myvg --name=rootvol --size=1000 --grow > logvol /tmp --vgname=myvg --name=tmp --size=1024 > EOF > From Chip.Shabazian at bankofamerica.com Fri Apr 7 16:18:43 2006 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 07 Apr 2006 09:18:43 -0700 Subject: part-include Message-ID: I have successfully done this with RHEL 2.1, 3 and 4. The %include is actually the second to last item in my config section, just before reboot: %include /tmp/partinfo reboot And this is in my pre: # Determine how many drives we have set $(list-harddrives) let numd=$#/2 d1=$1 d2=$3 if [ $numd -ge 2 ] ; then cat << EOF >> /tmp/partinfo part pv.01 --size=1 --grow --fstype=ext3 --ondisk=$d1 volgroup volgrp01 pv.01 part pv.02 --size=1 --grow --fstype=ext3 --ondisk=$d2 volgroup volgrp02 pv.02 part / --fstype ext3 --size=10240 --ondisk=$d1 logvol /var --vgname=volgrp01 --size=8192 --name=var part /boot --fstype ext3 --size=256 --ondisk=$d1 logvol /home --vgname=volgrp02 --size=4096 --name=home logvol /tmp --vgname=volgrp01 --size=2048 --name=tmp part swap --recommended --ondisk=$d1 EOF else cat << EOF >> /tmp/partinfo part pv.01 --size=1 --grow --fstype=ext3 --ondisk=$d1 volgroup volgrp01 pv.01 part / --fstype ext3 --size=10240 --ondisk=$d1 logvol /var --vgname=volgrp01 --size=8192 --name=var part /boot --fstype ext3 --size=256 --ondisk=$d1 logvol /home --vgname=volgrp01 --size=4096 --name=home logvol /tmp --vgname=volgrp01 --size=2048 --name=tmp part swap --recommended --ondisk=$d1 EOF -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of James Puellmann Sent: Friday, April 07, 2006 7:09 AM To: Discussion list about Kickstart Subject: Re: part-include I've used %include for partitioning without any problems with RHEL ES 4 by putting the partition %include directive between the "mouse" and "bootloader" options. (before the %pre) and then doing this in the %pre: cat > /tmp/include << EOF zerombr yes clearpart --all partition /boot --fstype=ext3 --size=200 partition swap --size=2000 partition pv.01 --size=1000 --grow volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 --grow logvol /tmp --vgname=myvg --name=tmp --size=1024 EOF Philip Rowlands wrote: > On Thu, 6 Apr 2006, Stephen Mah wrote: > >> I have a %pre script that writes to /tmp/part-include depending on >> the hard drive layout. >> The file, part-include is successfully written, but kickstart seems >> to ignore it. >> >> I've tried putting, before the %pre section and in the %pre section. >> %include /tmp/part-include > > > Which version of RHEL/Fedora? I know I had problems with %include in > older releases. > > > Cheers, > Phil > > _______________________________________________ > 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 smah at vmware.com Fri Apr 7 16:19:02 2006 From: smah at vmware.com (Stephen Mah) Date: Fri, 07 Apr 2006 09:19:02 -0700 Subject: part-include In-Reply-To: <942A778F73A72141889C1F53A8EAA1C502D3ECE0@MSGMMKCLM2WIN.DMN1.FMR.COM> References: <942A778F73A72141889C1F53A8EAA1C502D3ECE0@MSGMMKCLM2WIN.DMN1.FMR.COM> Message-ID: <443690F6.9070201@vmware.com> It's RHEL4, but thank you for that bit of info. steve Keegan, Gordon wrote: > Noticing that your address is "vmware.com", just in case you are trying > to kickstart VMware ESX 2.x.x, it is based on an older version of > anaconda that doesn't support the part-include functionality. You can > have a %pre section, but the ks.cfg file won't get re-read to pick up a > new partition layout. I haven't looked at it yet, but this should be > fixed in ESX 3, which is based on RHEL 3. > > Gordon Keegan > > > -----Original Message----- > From: Stephen Mah [mailto:smah at vmware.com] > Sent: Thursday, April 06, 2006 8:01 PM > To: Discussion list about Kickstart > Subject: part-include > > > I have a %pre script that writes to /tmp/part-include depending on the > hard drive layout. > The file, part-include is successfully written, but kickstart seems to > ignore it. > > I've tried putting, before the %pre section and in the %pre section. > %include /tmp/part-include > > Where do you put this line? > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From cmadams at hiwaay.net Fri Apr 7 17:40:49 2006 From: cmadams at hiwaay.net (Chris Adams) Date: Fri, 7 Apr 2006 12:40:49 -0500 Subject: part-include In-Reply-To: <942A778F73A72141889C1F53A8EAA1C502D3ECE0@MSGMMKCLM2WIN.DMN1.FMR.COM> References: <942A778F73A72141889C1F53A8EAA1C502D3ECE0@MSGMMKCLM2WIN.DMN1.FMR.COM> Message-ID: <20060407174049.GC1207438@hiwaay.net> Once upon a time, Keegan, Gordon said: > Noticing that your address is "vmware.com", just in case you are trying > to kickstart VMware ESX 2.x.x, it is based on an older version of > anaconda that doesn't support the part-include functionality. You can > have a %pre section, but the ks.cfg file won't get re-read to pick up a > new partition layout. I haven't looked at it yet, but this should be > fixed in ESX 3, which is based on RHEL 3. I've been using %include for partition info since Red Hat Linux 8.0. -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. From nauman.yousuf at gmail.com Sat Apr 8 09:41:39 2006 From: nauman.yousuf at gmail.com (Nauman Yousuf) Date: Sat, 8 Apr 2006 14:41:39 +0500 Subject: (no subject) Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From nauman.yousuf at gmail.com Sat Apr 8 09:55:02 2006 From: nauman.yousuf at gmail.com (Nauman Yousuf) Date: Sat, 8 Apr 2006 14:55:02 +0500 Subject: Software Raid through kickstart Message-ID: Dear All I want to install REDHAT AS4 through kistart start i did it . with software raid here is my ks.cfg file install cdrom lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8 keyboard us xconfig --card "VESA driver (generic)" --videoram 7872 --hsync 32-60 --vsync 57-85 --resolution 800x600 --depth 16 --startx onboot --defaultdesktop gnome network --device eth0 --bootproto dhcp rootpw --iscrypted $1$LSN6y60M$2Hbmw61n99GQsf .YsxXkp0 firewall --enabled --port=22:tcp --port=80:tcp --port=21:tcp --port=25:tcp selinux --enforcing authconfig --enableshadow --enablemd5 timezone Asia/Karachi bootloader --location=partition --append="rhgb quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all part /boot --fstype "ext3" --size=500 --ondisk=sda part raid.28 --size=20000 --ondisk=sdb part raid.25 --size=20000 --ondisk=sda part raid.19 --size=20000 --ondisk=sdb part raid.17 --size=20000 --ondisk=sda part raid.37 --size=10000 --ondisk=sdb part raid.34 --size=10000 --ondisk=sda part raid.15 --size=10000 --ondisk=sdb part raid.14 --size=10000 --ondisk=sda part raid.12 --size=2000 --ondisk=sdb part raid.11 --size=2000 --ondisk=sda part /boot1 --fstype "ext3" --size=500 --ondisk=sdb --asprimary part raid.46 --size=100 --grow --ondisk=sdb part raid.43 --size=100 --grow --ondisk=sda raid swap --fstype swap --level=RAID1 raid.11 raid.12 raid /oracle --fstype ext3 --level=RAID1 raid.14 raid.15 raid /oradata --fstype ext3 --level=RAID1 raid.17 raid.19 raid /u --fstype ext3 --level=RAID1 raid.25 raid.28 raid /v --fstype ext3 --level=RAID1 raid.34 raid.37 raid / --fstype ext3 --level=RAID1 raid.43 raid.46 %packages @ admin-tools @ text-internet @ gnome-desktop @ dialup @ smb-server @ base-x @ web-server @ printing @ server-cfg mdadm grub kernel-smp e2fsprogs %post dd if=/dev/sda1 of=/dev/sdb1 first thing raid is built successfully but as soon redhat install it gets boot and afer boot it gives me error i make /boot on first drive /dev/sda1 and /boot1 on /dev/sdb1 for disk recovery if one disk fails it boots from 2 disk. but when i install it give me error that fstab has entry #LABEL=/boot1 /boot1 ext3 defaults 1 2 when i uncomnt it it gets boot seemlesly . secong my post command wont work id dd if=/dec/sda1 of=/dev/sdb1 to boot from 2 disk in case of 1 disk fails but it wont do dd after installation . i need one more thing i have oracle cds i want to do such thing taht after kickstart install my system with requird partitions it runs the dd command and ask for oracle cds. i have oracle in oracle.gzip format . it ask for cds and to install it what should i do for this. Any help would greatly appriciated. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From maheshvrts at gmail.com Sun Apr 9 08:21:27 2006 From: maheshvrts at gmail.com (Maheshwar Reddy Gaddam) Date: Sun, 9 Apr 2006 13:51:27 +0530 Subject: ignoring shared storage Message-ID: <7c6f57920604090121r5891135cpf5a1c6f3717e7945@mail.gmail.com> Hi, How we can ignore shared storage (ex; qla2300) with kickstart -installation (RHEL4 Update 3) Thanks & regards Maheshwar. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dxh at yahoo.com Sun Apr 9 23:02:47 2006 From: dxh at yahoo.com (Don Hoover) Date: Sun, 9 Apr 2006 16:02:47 -0700 (PDT) Subject: Kickstart-list Digest, Vol 26, Issue 3 In-Reply-To: <20060409160011.1D3607369B@hormel.redhat.com> Message-ID: <20060409230247.24612.qmail@web60715.mail.yahoo.com> > How we can ignore shared storage (ex; qla2300) with > kickstart -installation > (RHEL4 Update 3) > You can add the "latefcload" option to the "boot:" command you use to bootup, and the kernel will load fibre channel drivers last so your ide/scsi drives will always appear first. --- Don Hoover dxh at yahoo.com From k.georgiou at imperial.ac.uk Mon Apr 10 11:59:03 2006 From: k.georgiou at imperial.ac.uk (Kostas Georgiou) Date: Mon, 10 Apr 2006 12:59:03 +0100 Subject: Software Raid through kickstart In-Reply-To: References: Message-ID: <20060410115903.GA20028@imperial.ac.uk> On Sat, Apr 08, 2006 at 02:55:02PM +0500, Nauman Yousuf wrote: > Dear All > I want to install REDHAT AS4 through kistart start i did it . with software > raid > clearpart --all > part /boot --fstype "ext3" --size=500 --ondisk=sda > part /boot1 --fstype "ext3" --size=500 --ondisk=sdb --asprimary Any reason not to use raid as well? Something like this for example works for me. part raid.00 --size=256 --ondisk=sda --asprimary part raid.01 --size=256 --ondisk=sdb --asprimary raid /boot --fstype ext3 --level=RAID1 raid.00 raid.01 > > first thing raid is built successfully but as soon redhat install it gets > boot and afer boot it gives me error > i make /boot on first drive /dev/sda1 and /boot1 on /dev/sdb1 for disk > recovery if one disk fails it boots from 2 disk. > but when i install it give me error that fstab has entry > #LABEL=/boot1 /boot1 ext3 defaults 1 2 > when i uncomnt it it gets boot seemlesly . After the dd from sda1 to sdb1 the label in sdb1 is /boot and not /boot1 so it fails, you can use tune2fs -L /boot1 /dev/sdb1 after the dd to restore the label for example but it is a lot better IMHO to use software raid for /boot. Kostas From tmaria at cs.ucy.ac.cy Mon Apr 10 12:19:38 2006 From: tmaria at cs.ucy.ac.cy (Maria Tsiolakki) Date: Mon, 10 Apr 2006 15:19:38 +0300 Subject: FC5 x86_64 with ftp installation method Message-ID: <443A4D5A.8000604@cs.ucy.ac.cy> Hello all, I am trying to install FC5 , x86_64, with ftp method, but it fails. It seems that it has problem to find the base dir and stage2.img file. The path to the ftp server is something like pub/linux/fedora/core/5/x86_64/os/, but it complains. Has anyone try to install it using ftp method? Thank you in advance Maria From Roman.Lazarev at FMR.COM Mon Apr 10 13:38:51 2006 From: Roman.Lazarev at FMR.COM (Lazarev, Roman) Date: Mon, 10 Apr 2006 09:38:51 -0400 Subject: When was "include" directive introduced? Message-ID: <5904C6EA1AC43B418E30B3D6FA2647520246CD57@MSGMMKCLF2WIN.DMN1.FMR.COM> Hi ALL, I'm working on an ESX server from VMware which uses anaconda + Kickstart. However it's anaconda version is quite archaic - I can't figure out the version of anaconda. It has also been heavily hacked by folks from VMware. They say it is based on RH7.2 I mounted netstg1.img and did a grep on "include" in "usr/lib/anaconda" but that didn't turn up any good positives... Maybe it just isn't there? My question is: How long ago was "%include" directive introduced? Should I take it for granted? Thanks much, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christian.Rohrmeier at SCHERING.DE Mon Apr 10 13:44:11 2006 From: Christian.Rohrmeier at SCHERING.DE (Christian.Rohrmeier at SCHERING.DE) Date: Mon, 10 Apr 2006 15:44:11 +0200 Subject: When was "include" directive introduced? In-Reply-To: <5904C6EA1AC43B418E30B3D6FA2647520246CD57@MSGMMKCLF2WIN.DMN1.FMR.COM> Message-ID: Hi Roman, RHEL 2.1 (based on RH 7.3) doesn't support %include. Only RHEL 3 and 4 support it. I am guessing then that RH8 and newer also support it. I have to support RHEL 2.1, 3, and 4, and thus I unfortunately can't take %include for granted. My RHEL 2.1 KS files are a different than the rest. I generate them on-the-fly via a CGI script, so its not a big deal _now_, but it used to be a pain to always make exceptions for RHEL 2.1, where just nothing is standard and half the stuff you need missing. Cheers, -Christian _________________ Christian Rohrmeier Schering AG Corporate IT - Infrastructure and Services Computer Systems and Operations System Administration - Research and Development Tel +49 30 468 15794 Fax +49 30 468 95794 "Lazarev, Roman" To Sent by: kickstart-list-bo unces at redhat.com cc Subject 10.04.2006 15:38 When was "include" directive introduced? Please respond to Discussion list about Kickstart Hi ALL, I'm working on an ESX server from VMware which uses anaconda + Kickstart. However it's anaconda version is quite archaic - I can't figure out the version of anaconda. It has also been heavily hacked by folks from VMware. They say it is based on RH7.2 I mounted netstg1.img and did a grep on "include" in "usr/lib/anaconda" but that didn't turn up any good positives? Maybe it just isn't there? My question is: How long ago was "%include" directive introduced? Should I take it for granted? Thanks much, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Roman.Lazarev at FMR.COM Mon Apr 10 13:58:52 2006 From: Roman.Lazarev at FMR.COM (Lazarev, Roman) Date: Mon, 10 Apr 2006 09:58:52 -0400 Subject: When was "include" directive introduced? Message-ID: <5904C6EA1AC43B418E30B3D6FA2647520246CD58@MSGMMKCLF2WIN.DMN1.FMR.COM> Thank you Christian! You confirmed my suspicions! I was wondering if just including the following hack into usr/lib/anaconda/kickstart.py could solve the "%include" issue for RHEL21. scriptInterp = arg + elif args and args[0] == "%include": + if len(args) < 2: + raise RuntimeError, "Invalid %include line" + else: + # read in the included file and set our where appropriately + where = self.readKickstart(id, args[1], where = where) elif args and args[0] == "%packages": Thanks, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Christian.Rohrmeier at SCHERING.DE Sent: Monday, April 10, 2006 9:44 AM To: Discussion list about Kickstart Cc: kickstart-list at redhat.com; kickstart-list-bounces at redhat.com; anaconda-devel-list at redhat.com Subject: Re: When was "include" directive introduced? Hi Roman, RHEL 2.1 (based on RH 7.3) doesn't support %include. Only RHEL 3 and 4 support it. I am guessing then that RH8 and newer also support it. I have to support RHEL 2.1, 3, and 4, and thus I unfortunately can't take %include for granted. My RHEL 2.1 KS files are a different than the rest. I generate them on-the-fly via a CGI script, so its not a big deal _now_, but it used to be a pain to always make exceptions for RHEL 2.1, where just nothing is standard and half the stuff you need missing. Cheers, -Christian _________________ Christian Rohrmeier Schering AG Corporate IT - Infrastructure and Services Computer Systems and Operations System Administration - Research and Development Tel +49 30 468 15794 Fax +49 30 468 95794 "Lazarev, Roman" To Sent by: kickstart-list-bo unces at redhat.com cc Subject 10.04.2006 15:38 When was "include" directive introduced? Please respond to Discussion list about Kickstart Hi ALL, I'm working on an ESX server from VMware which uses anaconda + Kickstart. However it's anaconda version is quite archaic - I can't figure out the version of anaconda. It has also been heavily hacked by folks from VMware. They say it is based on RH7.2 I mounted netstg1.img and did a grep on "include" in "usr/lib/anaconda" but that didn't turn up any good positives... Maybe it just isn't there? My question is: How long ago was "%include" directive introduced? Should I take it for granted? Thanks much, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 _______________________________________________ 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 Roman.Lazarev at FMR.COM Mon Apr 10 15:10:57 2006 From: Roman.Lazarev at FMR.COM (Lazarev, Roman) Date: Mon, 10 Apr 2006 11:10:57 -0400 Subject: When was "include" directive introduced? Message-ID: <5904C6EA1AC43B418E30B3D6FA2647520246CD5A@MSGMMKCLF2WIN.DMN1.FMR.COM> That hack didn't work ;( However I got a bit closer. Notice a change in readKickstart arguments and in "if" I'm trying to ignore this section until all the items are processes in %pre section. + elif args and args[0] == "%include" and where != "pre":: + if len(args) < 2: + raise RuntimeError, "Invalid %include line" + else: + # read in the included file and set our where appropriately + where = self.readKickstart(id, args[1]) However "%pre" section hasn't been processed when this is called and I just get an IOError. Could somebody from the devel team suggest a code solution? Thanks, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: Lazarev, Roman Sent: Monday, April 10, 2006 9:59 AM To: 'Discussion list about Kickstart' Cc: kickstart-list-bounces at redhat.com; anaconda-devel-list at redhat.com Subject: RE: When was "include" directive introduced? Thank you Christian! You confirmed my suspicions! I was wondering if just including the following hack into usr/lib/anaconda/kickstart.py could solve the "%include" issue for RHEL21. scriptInterp = arg + elif args and args[0] == "%include": + if len(args) < 2: + raise RuntimeError, "Invalid %include line" + else: + # read in the included file and set our where appropriately + where = self.readKickstart(id, args[1], where = where) elif args and args[0] == "%packages": Thanks, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Christian.Rohrmeier at SCHERING.DE Sent: Monday, April 10, 2006 9:44 AM To: Discussion list about Kickstart Cc: kickstart-list at redhat.com; kickstart-list-bounces at redhat.com; anaconda-devel-list at redhat.com Subject: Re: When was "include" directive introduced? Hi Roman, RHEL 2.1 (based on RH 7.3) doesn't support %include. Only RHEL 3 and 4 support it. I am guessing then that RH8 and newer also support it. I have to support RHEL 2.1, 3, and 4, and thus I unfortunately can't take %include for granted. My RHEL 2.1 KS files are a different than the rest. I generate them on-the-fly via a CGI script, so its not a big deal _now_, but it used to be a pain to always make exceptions for RHEL 2.1, where just nothing is standard and half the stuff you need missing. Cheers, -Christian _________________ Christian Rohrmeier Schering AG Corporate IT - Infrastructure and Services Computer Systems and Operations System Administration - Research and Development Tel +49 30 468 15794 Fax +49 30 468 95794 "Lazarev, Roman" To Sent by: kickstart-list-bo unces at redhat.com cc Subject 10.04.2006 15:38 When was "include" directive introduced? Please respond to Discussion list about Kickstart Hi ALL, I'm working on an ESX server from VMware which uses anaconda + Kickstart. However it's anaconda version is quite archaic - I can't figure out the version of anaconda. It has also been heavily hacked by folks from VMware. They say it is based on RH7.2 I mounted netstg1.img and did a grep on "include" in "usr/lib/anaconda" but that didn't turn up any good positives... Maybe it just isn't there? My question is: How long ago was "%include" directive introduced? Should I take it for granted? Thanks much, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 _______________________________________________ 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 Christian.Rohrmeier at SCHERING.DE Mon Apr 10 14:18:05 2006 From: Christian.Rohrmeier at SCHERING.DE (Christian.Rohrmeier at SCHERING.DE) Date: Mon, 10 Apr 2006 16:18:05 +0200 Subject: When was "include" directive introduced? In-Reply-To: <5904C6EA1AC43B418E30B3D6FA2647520246CD58@MSGMMKCLF2WIN.DMN1.FMR.COM> Message-ID: Hi Roman, that looks decent. Have you tried it yet? I unfortunately can't modify anything because then I'd lose support from my Vendor. So, sadly I'm forced to use only what is supported with the standard tools that each verison of RHEL comes with. Cheers, Christian _________________ Christian Rohrmeier Schering AG Corporate IT - Infrastructure and Services Computer Systems and Operations System Administration - Research and Development Tel +49 30 468 15794 Fax +49 30 468 95794 "Lazarev, Roman" To Sent by: "Discussion list about Kickstart" kickstart-list-bo unces at redhat.com cc kickstart-list-bounces at redhat.com, anaconda-devel-list at redhat.com 10.04.2006 15:58 Subject RE: When was "include" directive introduced? Please respond to Discussion list about Kickstart Thank you Christian! You confirmed my suspicions! I was wondering if just including the following hack into usr/lib/anaconda/kickstart.py could solve the "%include" issue for RHEL21. scriptInterp = arg + elif args and args[0] == "%include": + if len(args) < 2: + raise RuntimeError, "Invalid %include line" + else: + # read in the included file and set our where appropriately + where = self.readKickstart(id, args[1], where = where) elif args and args[0] == "%packages": Thanks, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Christian.Rohrmeier at SCHERING.DE Sent: Monday, April 10, 2006 9:44 AM To: Discussion list about Kickstart Cc: kickstart-list at redhat.com; kickstart-list-bounces at redhat.com; anaconda-devel-list at redhat.com Subject: Re: When was "include" directive introduced? Hi Roman, RHEL 2.1 (based on RH 7.3) doesn't support %include. Only RHEL 3 and 4 support it. I am guessing then that RH8 and newer also support it. I have to support RHEL 2.1, 3, and 4, and thus I unfortunately can't take %include for granted. My RHEL 2.1 KS files are a different than the rest. I generate them on-the-fly via a CGI script, so its not a big deal _now_, but it used to be a pain to always make exceptions for RHEL 2.1, where just nothing is standard and half the stuff you need missing. Cheers, -Christian _________________ Christian Rohrmeier Schering AG Corporate IT - Infrastructure and Services Computer Systems and Operations System Administration - Research and Development Tel +49 30 468 15794 Fax +49 30 468 95794 "Lazarev, Roman" To Sent by: kickstart-list-bo unces at redhat.com cc Subject 10.04.2006 15:38 When was "include" directive introduced? Please respond to Discussion list about Kickstart Hi ALL, I'm working on an ESX server from VMware which uses anaconda + Kickstart. However it's anaconda version is quite archaic - I can't figure out the version of anaconda. It has also been heavily hacked by folks from VMware. They say it is based on RH7.2 I mounted netstg1.img and did a grep on "include" in "usr/lib/anaconda" but that didn't turn up any good positives... Maybe it just isn't there? My question is: How long ago was "%include" directive introduced? Should I take it for granted? Thanks much, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 _______________________________________________ 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 Roman.Lazarev at FMR.COM Mon Apr 10 18:46:37 2006 From: Roman.Lazarev at FMR.COM (Lazarev, Roman) Date: Mon, 10 Apr 2006 14:46:37 -0400 Subject: When was "include" directive introduced? Message-ID: <5904C6EA1AC43B418E30B3D6FA26475205F15F9E@MSGMMKCLF2WIN.DMN1.FMR.COM> Yeap, the "%include" that is added into ks.cfg to include files generated in the %pre section. I do realize that it is pretty old, but that's all I got right now ;) and we have a bit diff hardware, so I wanna do disk layout and vmkpcidivy with %include Regards, Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: patrickd at vmware.com [mailto:patrickd at vmware.com] Sent: Monday, April 10, 2006 2:40 PM To: Lazarev, Roman Cc: kickstart-list at redhat.com; anaconda-devel-list at redhat.com Subject: Re: When was "include" directive introduced? What version of ESX are you using? ESX 2.x is mostly based on RHAS2.1. It's pretty old stuff. By the "%include directive", do you mean when did anaconda kickstart start parsing it? --Patrick. On Mon, 10 Apr 2006, Lazarev, Roman wrote: > Hi ALL, > > I'm working on an ESX server from VMware which uses anaconda + > Kickstart. However it's anaconda version is quite archaic - I can't > figure out the version of anaconda. It has also been heavily hacked by > folks from VMware. They say it is based on RH7.2 I mounted netstg1.img > and did a grep on "include" in "usr/lib/anaconda" but that didn't turn > up any good positives... Maybe it just isn't there? > > My question is: How long ago was "%include" directive introduced? Should > I take it for granted? > > Thanks much, > > Roman Lazarev > Fidelity Investment Management Technology > 245 Summer Street V2E > Boston, MA 02210 > (617) 563-1173 > > From Roman.Lazarev at FMR.COM Mon Apr 10 19:00:08 2006 From: Roman.Lazarev at FMR.COM (Lazarev, Roman) Date: Mon, 10 Apr 2006 15:00:08 -0400 Subject: When was "include" directive introduced? Message-ID: <5904C6EA1AC43B418E30B3D6FA26475205EBF542@MSGMMKCLF2WIN.DMN1.FMR.COM> That could be a very-very good option, if it pans out. Thanks I'll look into it! Roman Lazarev Fidelity Investment Management Technology 245 Summer Street V2E Boston, MA 02210 (617) 563-1173 -----Original Message----- From: patrickd at vmware.com [mailto:patrickd at vmware.com] Sent: Monday, April 10, 2006 2:57 PM To: Lazarev, Roman Cc: kickstart-list at redhat.com; anaconda-devel-list at redhat.com Subject: RE: When was "include" directive introduced? On Mon, 10 Apr 2006, Lazarev, Roman wrote: > Yeap, the "%include" that is added into ks.cfg to include files > generated in the %pre section. I do realize that it is pretty old, but > that's all I got right now ;) and we have a bit diff hardware, so I > wanna do disk layout and vmkpcidivy with %include It's been a really long time (like 2 years) since I looked at that code. I think you can do the pcidivy with the kickstart command "vmpcidivy" and passing it some arguments like what the bus/slot/[function] numbers are for your hardware. Take a look in doVMPciDivy() in kickstart.py for all of the arguments. --Patrick. From nauman.yousuf at gmail.com Mon Apr 10 21:56:40 2006 From: nauman.yousuf at gmail.com (Nauman Yousuf) Date: Tue, 11 Apr 2006 02:56:40 +0500 Subject: Software Raid through kickstart In-Reply-To: <20060410115903.GA20028@imperial.ac.uk> References: <20060410115903.GA20028@imperial.ac.uk> Message-ID: here is my ks.cfg . I dont under why i use /boot as raid and if i add new disk would this boot be recover automatically my adadm or not. onne more thing i need your guidness i dont need swap as raid b/c it slows down my speed . Now i am doing swap on 1 disk and /sw as ext3 of same partition on sdb . now if disk 1 goes down i dont have swap on 2 disk . how i add that i need it to automate . secondly when i add new disk i copy 2 disk partiotions to new disk so i need swap to their . any solution is greatly appriciated. i dont want swap as raid. install cdrom lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8 keyboard us xconfig --card "VESA driver (generic)" --videoram 7872 --hsync 32-60 --vsync 57-85 --resolution 800x600 --depth 16 --startx onboot --defaultdesktop gnome network --device eth0 --bootproto dhcp rootpw --iscrypted $1$LSN6y60M$2Hbmw61n99GQsf.YsxXkp0 firewall --enabled --port=22:tcp --port=80:tcp --port=21:tcp --port=25:tcp selinux --enforcing authconfig --enableshadow --enablemd5 timezone Asia/Karachi bootloader --location=partition --append="rhgb quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all part /boot --fstype "ext3" --size=500 --ondisk=sda part raid.28 --size=20000 --ondisk=sdb part raid.25 --size=20000 --ondisk=sda part raid.19 --size=20000 --ondisk=sdb part raid.17 --size=20000 --ondisk=sda part raid.37 --size=10000 --ondisk=sdb part raid.34 --size=10000 --ondisk=sda part raid.15 --size=10000 --ondisk=sdb part raid.14 --size=10000 --ondisk=sda part raid.12 --size=2000 --ondisk=sdb part raid.11 --size=2000 --ondisk=sda part /boot1 --fstype "ext3" --size=500 --ondisk=sdb --asprimary part raid.46 --size=100 --grow --ondisk=sdb part raid.43 --size=100 --grow --ondisk=sda raid swap --fstype swap --level=RAID1 raid.11 raid.12 raid /oracle --fstype ext3 --level=RAID1 raid.14 raid.15 raid /oradata --fstype ext3 --level=RAID1 raid.17 raid.19 raid /u --fstype ext3 --level=RAID1 raid.25 raid.28 raid /v --fstype ext3 --level=RAID1 raid.34 raid.37 raid / --fstype ext3 --level=RAID1 raid.43 raid.46 %packages @ admin-tools @ text-internet @ gnome-desktop @ dialup @ smb-server @ base-x @ web-server @ printing @ server-cfg mdadm grub kernel-smp e2fsprogs %post dd if=/dev/sda1 of=/dev/sdb1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rspaulding at mail.arc.nasa.gov Thu Apr 13 01:01:45 2006 From: rspaulding at mail.arc.nasa.gov (Ryan C. Spaulding) Date: Wed, 12 Apr 2006 18:01:45 -0700 Subject: Adding drivers to kickstart initrd.img Message-ID: Hi All, I am attempting to install Redhat 4.0-3 onto some new hardware with a 3ware 9550SX SCSI RAID card. There seems to be some support in 4.0-3 release for the 3ware 9XXX series, but not for this latest rev of the card as the 3ware kernel module with 4.0-3 release will not work it. I have been able to manually install the latest 3ware driver during a CD install to get the OS loaded on the system, but when I go to boot the machine, it is unable to boot [ and we get a kernel panic ? or we get a message it can't find the system disk ? ]. Thank you, Ryan From error27 at gmail.com Thu Apr 13 21:40:58 2006 From: error27 at gmail.com (Dan Carpenter) Date: Thu, 13 Apr 2006 14:40:58 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: Message-ID: On 4/12/06, Ryan C. Spaulding wrote: > I am attempting to install Redhat 4.0-3 onto some new hardware with a > 3ware 9550SX SCSI RAID card. You'll need to use a driver disk for that. If you're using x86_64, I could send it to you... regards, dan carpenter From rspaulding at mail.arc.nasa.gov Fri Apr 14 06:41:50 2006 From: rspaulding at mail.arc.nasa.gov (Ryan C. Spaulding) Date: Thu, 13 Apr 2006 23:41:50 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: Message-ID: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> Hi Dan, Yes, I am installing on x86_64. Any help you can give would be appreciated. I think I tracked down the problem with the driver not loading. I have added the correct driver into the modules.cgz cpio that is is inside the initrd.img file under the isolinux directory on install disk 1. I noticed that when it bombs out that it is attempting to load another 3ware driver from some other modules.cgz file. I found another modules.cgz in stage2.img but when I mount stage2.img it is read only and I have been unsuccessful in producing a duplicate stage2.img with mkfs.cramfs. I think that a rebuild of anaconda could fix this problem but I could be totally going in the wrong direction. Thank you, Ryan On Apr 13, 2006, at 2:40 PM, Dan Carpenter wrote: > On 4/12/06, Ryan C. Spaulding wrote: >> I am attempting to install Redhat 4.0-3 onto some new hardware with a >> 3ware 9550SX SCSI RAID card. > > You'll need to use a driver disk for that. > > If you're using x86_64, I could send it to you... > > regards, > dan carpenter > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From error27 at gmail.com Fri Apr 14 08:02:06 2006 From: error27 at gmail.com (Dan Carpenter) Date: Fri, 14 Apr 2006 01:02:06 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> Message-ID: On 4/13/06, Ryan C. Spaulding wrote: > I think that a rebuild of anaconda could fix this problem but I > could be totally going in the wrong direction. > A little bit in the wrong direction, yes. I'll forward you the driver disk in a seperate email. `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` Boot from the CD and use "linux dd" to specify that there is a driver disk. You'll need a floppy or USB key or something. If you want to automate the package. 1) Download the anaconda source rpm 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv 3) make 4) apply this patch https://www.redhat.com/archives/anaconda-devel-list/2005-November/msg00018.html 5) cd loader2/ ; make loader 6-9) Unpack the initrd. Replace the old loader with the one you just created. Put the driver disk in the initrd as /dd.img. Pack it back up. Then it's automatic. Or you could just put the driver disk on the network I suppose but I don't recall the format for that... regards, dan carpenter From Axel.Thimm at ATrpms.net Fri Apr 14 11:59:31 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Fri, 14 Apr 2006 13:59:31 +0200 Subject: logvol --noformat on FC5 Message-ID: <20060414115931.GF1831@neu.nirvana> Hi, I'm trying to setup a kickstart file to reinstall FC5 on a hard disk while keeping a data partition intact. The data partition is in fact a logical volume to allow me to reshuffle PEs if neccessary. If I look at the anaconda.cfg that is created when I enter the setup manually in anaconda I see the following directives: #part /boot --fstype ext3 --onpart sda1 #part pv.2 --noformat --onpart sda2 #volgroup systemoctopus --pesize=32768 pv.2 #logvol /srv/atrpms.net/storage/octopus --noformat --fstype ext3 --name=data --vgname=systemoctopus --size=222272 #logvol / --fstype ext3 --name=root --vgname=systemoctopus --size=14976 #logvol swap --fstype swap --name=swap --vgname=systemoctopus --size=1984 But if I try to use them to automate the process the install results in | Error mounting device systemoctopus/data as | /srv/atrpms.net/storage/octopus: No such file or directory | | This most likely meas this partition has not been formated. | | Press OK to reboot your system. Am I doing something wrong, or should I file a bug? How can I achive what I want, e.g. have kickstart spare a logical volume? Thanks! -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From koreesmith at gmail.com Fri Apr 14 12:35:48 2006 From: koreesmith at gmail.com (Koree A. Smith) Date: Fri, 14 Apr 2006 07:35:48 -0500 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> Message-ID: <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> It's been a while since I've done it, but I used the instructions here: http://lists.us.dell.com/pipermail/linux-poweredge/2003-August/009343.html and adapted them into what I needed for the driver I was installing. The above document probably won't give you all of the answers, but it's a good start, and it didn't require me to rebuild anaconda. Koree On 4/14/06, Dan Carpenter wrote: > On 4/13/06, Ryan C. Spaulding wrote: > > I think that a rebuild of anaconda could fix this problem but I > > could be totally going in the wrong direction. > > > > A little bit in the wrong direction, yes. > > I'll forward you the driver disk in a seperate email. > `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` > Boot from the CD and use "linux dd" to specify that there is a driver > disk. You'll need a floppy or USB key or something. > > If you want to automate the package. > 1) Download the anaconda source rpm > 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv > 3) make > 4) apply this patch > https://www.redhat.com/archives/anaconda-devel-list/2005-November/msg00018.html > 5) cd loader2/ ; make loader > > 6-9) Unpack the initrd. Replace the old loader with the one you just > created. Put the driver disk in the initrd as /dd.img. Pack it back > up. > > Then it's automatic. Or you could just put the driver disk on the > network I suppose but I don't recall the format for that... > > regards, > dan carpenter > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Koree A. Smith -- Senior System Administrator EV1Servers.net From rspaulding at mail.arc.nasa.gov Fri Apr 14 15:11:31 2006 From: rspaulding at mail.arc.nasa.gov (Ryan C. Spaulding) Date: Fri, 14 Apr 2006 08:11:31 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> Message-ID: <0741A65E-1CFB-4E44-9C86-BC9E76655550@mail.arc.nasa.gov> Hi All, Thank you for the instructions. I was looking over the kickstart documentation again and it looks like it has been updated with 4.0 release 3. I am going to attempt using what looks like a new option called --driverdisk (with Dan's driver disk). Looks like I can specify a driver disk via ftp, http and nfs. I will let you all know how it goes. Thank you, Ryan On Apr 14, 2006, at 1:02 AM, Dan Carpenter wrote: > On 4/13/06, Ryan C. Spaulding wrote: >> I think that a rebuild of anaconda could fix this problem but I >> could be totally going in the wrong direction. >> > > A little bit in the wrong direction, yes. > > I'll forward you the driver disk in a seperate email. > `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` > Boot from the CD and use "linux dd" to specify that there is a driver > disk. You'll need a floppy or USB key or something. > > If you want to automate the package. > 1) Download the anaconda source rpm > 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv > 3) make > 4) apply this patch > https://www.redhat.com/archives/anaconda-devel-list/2005-November/ > msg00018.html > 5) cd loader2/ ; make loader > > 6-9) Unpack the initrd. Replace the old loader with the one you just > created. Put the driver disk in the initrd as /dd.img. Pack it back > up. > > Then it's automatic. Or you could just put the driver disk on the > network I suppose but I don't recall the format for that... > > regards, > dan carpenter > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From error27 at gmail.com Fri Apr 14 15:48:32 2006 From: error27 at gmail.com (Dan Carpenter) Date: Fri, 14 Apr 2006 08:48:32 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> Message-ID: On 4/14/06, Koree A. Smith wrote: > It's been a while since I've done it, but I used the instructions here: > > http://lists.us.dell.com/pipermail/linux-poweredge/2003-August/009343.html > That's just instructions on how to build a driver disk. I already built the driver disk and forwarded it... That was step 0. :P Rebuilding anaconda is optional but it helps if your going to load hundreds of systems or it needs to be completely automated for some reason... regards, dan carpenter From Chip.Shabazian at bankofamerica.com Fri Apr 14 16:12:32 2006 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 14 Apr 2006 09:12:32 -0700 Subject: Adding drivers to kickstart initrd.img Message-ID: You can use --driverdisk in a kickstart file, or dd= at the boot: prompt. This isn't a new option though, it's been there quite a while. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ryan C. Spaulding Sent: Friday, April 14, 2006 8:12 AM To: Discussion list about Kickstart Subject: Re: Adding drivers to kickstart initrd.img Hi All, Thank you for the instructions. I was looking over the kickstart documentation again and it looks like it has been updated with 4.0 release 3. I am going to attempt using what looks like a new option called --driverdisk (with Dan's driver disk). Looks like I can specify a driver disk via ftp, http and nfs. I will let you all know how it goes. Thank you, Ryan On Apr 14, 2006, at 1:02 AM, Dan Carpenter wrote: > On 4/13/06, Ryan C. Spaulding wrote: >> I think that a rebuild of anaconda could fix this problem but I could >> be totally going in the wrong direction. >> > > A little bit in the wrong direction, yes. > > I'll forward you the driver disk in a seperate email. > `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` Boot from the CD and use > "linux dd" to specify that there is a driver disk. You'll need a > floppy or USB key or something. > > If you want to automate the package. > 1) Download the anaconda source rpm > 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv > 3) make > 4) apply this patch > https://www.redhat.com/archives/anaconda-devel-list/2005-November/ > msg00018.html > 5) cd loader2/ ; make loader > > 6-9) Unpack the initrd. Replace the old loader with the one you just > created. Put the driver disk in the initrd as /dd.img. Pack it back > up. > > Then it's automatic. Or you could just put the driver disk on the > network I suppose but I don't recall the format for that... > > regards, > dan carpenter > > _______________________________________________ > 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 rspaulding at mail.arc.nasa.gov Fri Apr 14 16:20:01 2006 From: rspaulding at mail.arc.nasa.gov (Ryan C. Spaulding) Date: Fri, 14 Apr 2006 09:20:01 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: Message-ID: <7701F34D-2CEB-4A9C-94D2-1D4D3DC555E7@mail.arc.nasa.gov> I guess since I have never needed it before it's new to me :) Wait can I do dd= before I put in ks ks= ? On Apr 14, 2006, at 9:12 AM, Shabazian, Chip wrote: > You can use --driverdisk in a kickstart file, or dd= at the boot: > prompt. > > This isn't a new option though, it's been there quite a while. > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ryan C. > Spaulding > Sent: Friday, April 14, 2006 8:12 AM > To: Discussion list about Kickstart > Subject: Re: Adding drivers to kickstart initrd.img > > > Hi All, > > Thank you for the instructions. I was looking over the kickstart > documentation again and it looks like it has been updated with 4.0 > release 3. I am going to attempt using what looks like a new option > called --driverdisk (with Dan's driver disk). Looks like I can > specify a > driver disk via ftp, http and nfs. > > I will let you all know how it goes. > > Thank you, > > Ryan > > > > On Apr 14, 2006, at 1:02 AM, Dan Carpenter wrote: > >> On 4/13/06, Ryan C. Spaulding wrote: >>> I think that a rebuild of anaconda could fix this problem but I >>> could > >>> be totally going in the wrong direction. >>> >> >> A little bit in the wrong direction, yes. >> >> I'll forward you the driver disk in a seperate email. >> `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` Boot from the CD and use >> "linux dd" to specify that there is a driver disk. You'll need a >> floppy or USB key or something. >> >> If you want to automate the package. >> 1) Download the anaconda source rpm >> 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv >> 3) make >> 4) apply this patch >> https://www.redhat.com/archives/anaconda-devel-list/2005-November/ >> msg00018.html >> 5) cd loader2/ ; make loader >> >> 6-9) Unpack the initrd. Replace the old loader with the one you just >> created. Put the driver disk in the initrd as /dd.img. Pack it back >> up. >> >> Then it's automatic. Or you could just put the driver disk on the >> network I suppose but I don't recall the format for that... >> >> regards, >> dan carpenter >> >> _______________________________________________ >> 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 Chip.Shabazian at bankofamerica.com Fri Apr 14 16:28:47 2006 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 14 Apr 2006 09:28:47 -0700 Subject: Adding drivers to kickstart initrd.img Message-ID: You can put dd= anywhere on the line after boot: Order is not important. Putting dd= on the boot line will give you the exact same result as putting --driverdisk in the kickstart file. About the only time I can think that you would NEED to put it on the boot line would be if you were loading your ks.cfg via the network and needed a network driver that wasn't supported. Also, be aware of the 255 character limitation on the boot: line. This is the reason we have added it to the ks.cfg file and not to the boot: line -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ryan C. Spaulding Sent: Friday, April 14, 2006 9:20 AM To: Discussion list about Kickstart Subject: Re: Adding drivers to kickstart initrd.img I guess since I have never needed it before it's new to me :) Wait can I do dd= before I put in ks ks= ? On Apr 14, 2006, at 9:12 AM, Shabazian, Chip wrote: > You can use --driverdisk in a kickstart file, or dd= at the boot: > prompt. > > This isn't a new option though, it's been there quite a while. > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ryan C. > Spaulding > Sent: Friday, April 14, 2006 8:12 AM > To: Discussion list about Kickstart > Subject: Re: Adding drivers to kickstart initrd.img > > > Hi All, > > Thank you for the instructions. I was looking over the kickstart > documentation again and it looks like it has been updated with 4.0 > release 3. I am going to attempt using what looks like a new option > called --driverdisk (with Dan's driver disk). Looks like I can specify > a driver disk via ftp, http and nfs. > > I will let you all know how it goes. > > Thank you, > > Ryan > > > > On Apr 14, 2006, at 1:02 AM, Dan Carpenter wrote: > >> On 4/13/06, Ryan C. Spaulding wrote: >>> I think that a rebuild of anaconda could fix this problem but I >>> could > >>> be totally going in the wrong direction. >>> >> >> A little bit in the wrong direction, yes. >> >> I'll forward you the driver disk in a seperate email. >> `dd if=3w-9xxx-4u3-amd64.144 of=/dev/fd0` Boot from the CD and use >> "linux dd" to specify that there is a driver disk. You'll need a >> floppy or USB key or something. >> >> If you want to automate the package. >> 1) Download the anaconda source rpm >> 2) rpm2cpio anacond-src-foo-rpm | cpio -idmv >> 3) make >> 4) apply this patch >> https://www.redhat.com/archives/anaconda-devel-list/2005-November/ >> msg00018.html >> 5) cd loader2/ ; make loader >> >> 6-9) Unpack the initrd. Replace the old loader with the one you just >> created. Put the driver disk in the initrd as /dd.img. Pack it back >> up. >> >> Then it's automatic. Or you could just put the driver disk on the >> network I suppose but I don't recall the format for that... >> >> regards, >> dan carpenter >> >> _______________________________________________ >> 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 koreesmith at gmail.com Fri Apr 14 17:02:48 2006 From: koreesmith at gmail.com (Koree A. Smith) Date: Fri, 14 Apr 2006 12:02:48 -0500 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> Message-ID: <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Hmm. I helped create a rather large system that does completely automated and unattended installs without rebuilding anaconda. What does one gain from doing so? Koree On 4/14/06, Dan Carpenter wrote: > On 4/14/06, Koree A. Smith wrote: > > It's been a while since I've done it, but I used the instructions here: > > > > http://lists.us.dell.com/pipermail/linux-poweredge/2003-August/009343.html > > > > That's just instructions on how to build a driver disk. I already > built the driver disk and forwarded it... That was step 0. :P > > Rebuilding anaconda is optional but it helps if your going to load > hundreds of systems or it needs to be completely automated for some > reason... > > regards, > dan carpenter > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Koree A. Smith -- Senior System Administrator EV1Servers.net From cleve.cornelius at kroger.com Fri Apr 14 19:30:12 2006 From: cleve.cornelius at kroger.com (cleve.cornelius at kroger.com) Date: Fri, 14 Apr 2006 15:30:12 -0400 Subject: Cleve Cornelius/MIS/CORP/KrogerCo is out of the office. Message-ID: I will be out of the office starting Fri 04/14/2006 and will not return until Mon 04/17/2006. If this is an urgent matter please contact the NOC and they will page the on call engineer to assist you. From rspaulding at mail.arc.nasa.gov Fri Apr 14 22:09:53 2006 From: rspaulding at mail.arc.nasa.gov (Ryan C. Spaulding) Date: Fri, 14 Apr 2006 15:09:53 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: Hi All, I had to download the new driver from 3ware for the '-34' kernel that release 3 uses. All I had to do was add 'dd' to my kickstart line and put in the floppy. Thank you everyone for all of your help :) Thank you, Ryan On Apr 14, 2006, at 10:02 AM, Koree A. Smith wrote: > Hmm. I helped create a rather large system that does completely > automated and unattended installs without rebuilding anaconda. What > does one gain from doing so? > > Koree > > On 4/14/06, Dan Carpenter wrote: >> On 4/14/06, Koree A. Smith wrote: >>> It's been a while since I've done it, but I used the instructions >>> here: >>> >>> http://lists.us.dell.com/pipermail/linux-poweredge/2003-August/ >>> 009343.html >>> >> >> That's just instructions on how to build a driver disk. I already >> built the driver disk and forwarded it... That was step 0. :P >> >> Rebuilding anaconda is optional but it helps if your going to load >> hundreds of systems or it needs to be completely automated for some >> reason... >> >> regards, >> dan carpenter >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > > > -- > Koree A. Smith > -- > Senior System Administrator > EV1Servers.net > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From error27 at gmail.com Sat Apr 15 03:46:08 2006 From: error27 at gmail.com (Dan Carpenter) Date: Fri, 14 Apr 2006 20:46:08 -0700 Subject: Adding drivers to kickstart initrd.img In-Reply-To: <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: On 4/14/06, Koree A. Smith wrote: > Hmm. I helped create a rather large system that does completely > automated and unattended installs without rebuilding anaconda. What > does one gain from doing so? > > Koree > You're right of course. The network route is the correct way to go in many cases. My way is still kind of useful if you need a network driver disk and so you can't get it over the network... Etc. I have a bunch of configs like that so I eventually end up patching anaconda for each new redhat release. Plus the subject was about putting the drivers in the initrd and I was trying to spread some anaconda-recompiling-joy. ;P regards, dan carpenter From Axel.Thimm at ATrpms.net Sun Apr 16 22:43:12 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 17 Apr 2006 00:43:12 +0200 Subject: logvol --noformat on FC5 In-Reply-To: <20060414115931.GF1831@neu.nirvana> References: <20060414115931.GF1831@neu.nirvana> Message-ID: <20060416224312.GA7160@neu.nirvana> On Fri, Apr 14, 2006 at 01:59:31PM +0200, Axel Thimm wrote: > Hi, > > I'm trying to setup a kickstart file to reinstall FC5 on a hard disk > while keeping a data partition intact. The data partition is in fact a > logical volume to allow me to reshuffle PEs if neccessary. > > If I look at the anaconda.cfg that is created when I enter the setup > manually in anaconda I see the following directives: > > #part /boot --fstype ext3 --onpart sda1 > #part pv.2 --noformat --onpart sda2 > #volgroup systemoctopus --pesize=32768 pv.2 > #logvol /srv/atrpms.net/storage/octopus --noformat --fstype ext3 --name=data --vgname=systemoctopus --size=222272 > #logvol / --fstype ext3 --name=root --vgname=systemoctopus --size=14976 > #logvol swap --fstype swap --name=swap --vgname=systemoctopus --size=1984 > > But if I try to use them to automate the process the install results > in > > | Error mounting device systemoctopus/data as > | /srv/atrpms.net/storage/octopus: No such file or directory > | > | This most likely meas this partition has not been formated. > | > | Press OK to reboot your system. BTW: Even though there is this error message the data partition that was to be --noformat'ed is lost. Looks like anaconda wipes the whole volume group. > Am I doing something wrong, or should I file a bug? > > How can I achive what I want, e.g. have kickstart spare a logical > volume? > > Thanks! -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From Axel.Thimm at ATrpms.net Sun Apr 16 22:45:38 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 17 Apr 2006 00:45:38 +0200 Subject: No module named rhpxl.videocard on FC5 Message-ID: <20060416224538.GB7160@neu.nirvana> Hi, if I try to switch a kickstart install to text mode by adding the keyword text, the console gets garbled while python debug traces. Among others the relevant issue seems to be No module named rhpxl.videocard -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dan at half-asleep.com Sun Apr 16 23:40:33 2006 From: dan at half-asleep.com (Daniel Segall) Date: Sun, 16 Apr 2006 19:40:33 -0400 Subject: No module named rhpxl.videocard on FC5 In-Reply-To: <20060416224538.GB7160@neu.nirvana> References: <20060416224538.GB7160@neu.nirvana> Message-ID: <4442D5F1.4000205@half-asleep.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Axel Thimm wrote: > Hi, > > if I try to switch a kickstart install to text mode by adding the > keyword text, the console gets garbled while python debug > traces. Among others the relevant issue seems to be > > No module named rhpxl.videocard > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list This is a known issue: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185840 Either comment out the xconfig line in your kickstart, or do a graphical install. - -Dan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEQtXxKBx1bl6SFWURAmNXAJ4u6onJHohwuMhKVa1hNP9qxudFrwCcCxUl Iq88PnsWq5/AVW4IICFBl0w= =Sq0o -----END PGP SIGNATURE----- From Axel.Thimm at ATrpms.net Sun Apr 16 23:47:52 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 17 Apr 2006 01:47:52 +0200 Subject: logvol --noformat on FC5 In-Reply-To: <20060416224312.GA7160@neu.nirvana> References: <20060414115931.GF1831@neu.nirvana> <20060416224312.GA7160@neu.nirvana> Message-ID: <20060416234752.GA6228@neu.nirvana> On Mon, Apr 17, 2006 at 12:43:12AM +0200, Axel Thimm wrote: > On Fri, Apr 14, 2006 at 01:59:31PM +0200, Axel Thimm wrote: > > I'm trying to setup a kickstart file to reinstall FC5 on a hard disk > > while keeping a data partition intact. The data partition is in fact a > > logical volume to allow me to reshuffle PEs if neccessary. > > > > If I look at the anaconda.cfg that is created when I enter the setup > > manually in anaconda I see the following directives: > > > > #part /boot --fstype ext3 --onpart sda1 > > #part pv.2 --noformat --onpart sda2 > > #volgroup systemoctopus --pesize=32768 pv.2 > > #logvol /srv/atrpms.net/storage/octopus --noformat --fstype ext3 --name=data --vgname=systemoctopus --size=222272 > > #logvol / --fstype ext3 --name=root --vgname=systemoctopus --size=14976 > > #logvol swap --fstype swap --name=swap --vgname=systemoctopus --size=1984 > > > > But if I try to use them to automate the process the install results > > in > > > > | Error mounting device systemoctopus/data as > > | /srv/atrpms.net/storage/octopus: No such file or directory > > | > > | This most likely meas this partition has not been formated. > > | > > | Press OK to reboot your system. > > BTW: Even though there is this error message the data partition that > was to be --noformat'ed is lost. Looks like anaconda wipes the whole > volume group. Looks like the bug is in missing --noformat on the volgroup declaration as well as missing --useexisting on the logvol lines w/o the --noformat. E.g. the bug is in the creation of the anaconda.cfg file, not in the parsing. I'll file a bug as soon as bugzilla is up again. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From nauman.yousuf at gmail.com Mon Apr 17 10:29:15 2006 From: nauman.yousuf at gmail.com (Nauman Yousuf) Date: Mon, 17 Apr 2006 15:29:15 +0500 Subject: Adding drivers to kickstart initrd.img In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: hi All I am doing software raid on Redhat AS4 with SATA drives. I am using GRUB Both disks are bootable i checked it out one by one n system boots from any one installed disk. Prb is when i add new disk and run this script #!/bin/bash echo Please, new Drive for Drive 1 enter /dev/sda and for 2 Drive enter /dev/sdb read DRIVE echo "Drive is $DRIVE" if [ $DRIVE = "/dev/sdb" ];then {/sbin/sfdisk -d /dev/sda > $DRIVE.out /sbin/sfdisk $DRIVE < $DRIVE.out} else {/sbin/sfdisk -d /dev/sdb > $DRIVE.out /sbin/sfdisk $DRIVE < $DRIVE.out} fi /sbin/mdadm /dev/md0 --add ${DRIVE}6 /sbin/mdadm /dev/md1 --add ${DRIVE}2 /sbin/mdadm /dev/md2 --add ${DRIVE}8 /sbin/mdadm /dev/md3 --add ${DRIVE}5 /sbin/mdadm /dev/md4 --add ${DRIVE}3 /sbin/mdadm /dev/md5 --add ${DRIVE}7 /sbin/mdadm /dev/md6 --add ${DRIVE}1 it add the second disk in my case and add all the new disk with same partitions as we have with old raid and Raid is then resync too. i make /boot as raid , / , /usr , swap all are raid md's . Now when i boot from 2 disk it wont boot . what to do any idea . iTs really urgrent to do . Your help is highly appriciated. Regards On 4/15/06, Dan Carpenter wrote: > > On 4/14/06, Koree A. Smith wrote: > > Hmm. I helped create a rather large system that does completely > > automated and unattended installs without rebuilding anaconda. What > > does one gain from doing so? > > > > Koree > > > > You're right of course. The network route is the correct way to go in > many cases. > > My way is still kind of useful if you need a network driver disk and > so you can't get it over the network... Etc. I have a bunch of > configs like that so I eventually end up patching anaconda for each > new redhat release. > > Plus the subject was about putting the drivers in the initrd and I was > trying to spread some anaconda-recompiling-joy. ;P > > regards, > dan carpenter > > _______________________________________________ > 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 phr at doc.ic.ac.uk Mon Apr 17 12:41:25 2006 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Mon, 17 Apr 2006 13:41:25 +0100 (BST) Subject: MD drives not bootable In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: Please don't post HTML to mailing lists. Please don't start new questions on old threads. On Mon, 17 Apr 2006, Nauman Yousuf wrote: > #!/bin/bash > echo Please, new Drive for Drive 1 enter /dev/sda and for 2 Drive enter > /dev/sdb > read DRIVE > echo "Drive is $DRIVE" > if [ $DRIVE = "/dev/sdb" ];then > {/sbin/sfdisk -d /dev/sda > $DRIVE.out > /sbin/sfdisk $DRIVE < $DRIVE.out} This syntax is wrong; you should be seeing errors from bash. Try this: if [ $DRIVE = "/dev/sdb" ]; then { /sbin/sfdisk ... ; /sbin/sfdisk ... ; } fi The whitespace and semicolons are required for a group command using {}. Cheers, Phil From error27 at gmail.com Mon Apr 17 15:14:56 2006 From: error27 at gmail.com (Dan Carpenter) Date: Mon, 17 Apr 2006 08:14:56 -0700 Subject: MD drives not bootable In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: Also you need to install GRUB on each physical drive. http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/008898.html Read from the section: "Installing GRUB Onto Drives that have /boot Raid Partitions" regards, dan carpenter From E.Grochocki at coi.pw.edu.pl Mon Apr 17 15:32:04 2006 From: E.Grochocki at coi.pw.edu.pl (Emil Grochocki) Date: Mon, 17 Apr 2006 17:32:04 +0200 Subject: FC5 minimal Message-ID: <003c01c66234$14366b50$0b911dc2@venus> How install "core" (not "base") version of FC5. I append: %packages @core but anaconda still install "base" version :-( Best Regards Emil Grochocki From Axel.Thimm at ATrpms.net Mon Apr 17 16:36:55 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Mon, 17 Apr 2006 18:36:55 +0200 Subject: logvol --noformat on FC5 In-Reply-To: <20060416234752.GA6228@neu.nirvana> References: <20060414115931.GF1831@neu.nirvana> <20060416224312.GA7160@neu.nirvana> <20060416234752.GA6228@neu.nirvana> Message-ID: <20060417163655.GA23945@neu.nirvana> On Mon, Apr 17, 2006 at 01:47:52AM +0200, Axel Thimm wrote: > On Mon, Apr 17, 2006 at 12:43:12AM +0200, Axel Thimm wrote: > > On Fri, Apr 14, 2006 at 01:59:31PM +0200, Axel Thimm wrote: > > > I'm trying to setup a kickstart file to reinstall FC5 on a hard disk > > > while keeping a data partition intact. The data partition is in fact a > > > logical volume to allow me to reshuffle PEs if neccessary. > > > > > > If I look at the anaconda.cfg that is created when I enter the setup > > > manually in anaconda I see the following directives: > > > > > > #part /boot --fstype ext3 --onpart sda1 > > > #part pv.2 --noformat --onpart sda2 > > > #volgroup systemoctopus --pesize=32768 pv.2 > > > #logvol /srv/atrpms.net/storage/octopus --noformat --fstype ext3 --name=data --vgname=systemoctopus --size=222272 > > > #logvol / --fstype ext3 --name=root --vgname=systemoctopus --size=14976 > > > #logvol swap --fstype swap --name=swap --vgname=systemoctopus --size=1984 > > > > > > But if I try to use them to automate the process the install results > > > in > > > > > > | Error mounting device systemoctopus/data as > > > | /srv/atrpms.net/storage/octopus: No such file or directory > > > | > > > | This most likely meas this partition has not been formated. > > > | > > > | Press OK to reboot your system. > > > > BTW: Even though there is this error message the data partition that > > was to be --noformat'ed is lost. Looks like anaconda wipes the whole > > volume group. > > Looks like the bug is in missing --noformat on the volgroup > declaration as well as missing --useexisting on the logvol lines w/o > the --noformat. E.g. the bug is in the creation of the anaconda.cfg > file, not in the parsing. > > I'll file a bug as soon as bugzilla is up again. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189123 -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rspaulding at mail.arc.nasa.gov Mon Apr 17 16:45:50 2006 From: rspaulding at mail.arc.nasa.gov (Ryan C. Spaulding) Date: Mon, 17 Apr 2006 09:45:50 -0700 Subject: logvol --noformat on FC5 In-Reply-To: <20060416234752.GA6228@neu.nirvana> References: <20060414115931.GF1831@neu.nirvana> <20060416224312.GA7160@neu.nirvana> <20060416234752.GA6228@neu.nirvana> Message-ID: <07665D5D-F172-41D7-90A3-2D16F2D2CE6A@mail.arc.nasa.gov> Hi Axel, Can you send the bug number once you submit it? I think this will be a problem I will have to deal with in a few months when we have to upgrade a number of systems with LVM on them. Thank you, Ryan On Apr 16, 2006, at 4:47 PM, Axel Thimm wrote: > On Mon, Apr 17, 2006 at 12:43:12AM +0200, Axel Thimm wrote: >> On Fri, Apr 14, 2006 at 01:59:31PM +0200, Axel Thimm wrote: >>> I'm trying to setup a kickstart file to reinstall FC5 on a hard disk >>> while keeping a data partition intact. The data partition is in >>> fact a >>> logical volume to allow me to reshuffle PEs if neccessary. >>> >>> If I look at the anaconda.cfg that is created when I enter the setup >>> manually in anaconda I see the following directives: >>> >>> #part /boot --fstype ext3 --onpart sda1 >>> #part pv.2 --noformat --onpart sda2 >>> #volgroup systemoctopus --pesize=32768 pv.2 >>> #logvol /srv/atrpms.net/storage/octopus --noformat --fstype ext3 >>> --name=data --vgname=systemoctopus --size=222272 >>> #logvol / --fstype ext3 --name=root --vgname=systemoctopus -- >>> size=14976 >>> #logvol swap --fstype swap --name=swap --vgname=systemoctopus -- >>> size=1984 >>> >>> But if I try to use them to automate the process the install results >>> in >>> >>> | Error mounting device systemoctopus/data as >>> | /srv/atrpms.net/storage/octopus: No such file or directory >>> | >>> | This most likely meas this partition has not been formated. >>> | >>> | Press OK to reboot your system. >> >> BTW: Even though there is this error message the data partition that >> was to be --noformat'ed is lost. Looks like anaconda wipes the whole >> volume group. > > Looks like the bug is in missing --noformat on the volgroup > declaration as well as missing --useexisting on the logvol lines w/o > the --noformat. E.g. the bug is in the creation of the anaconda.cfg > file, not in the parsing. > > I'll file a bug as soon as bugzilla is up again. > -- > Axel.Thimm at ATrpms.net > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Chip.Shabazian at bankofamerica.com Mon Apr 17 17:37:19 2006 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 17 Apr 2006 10:37:19 -0700 Subject: FC5 minimal Message-ID: Try %packages --nobase Be aware however, that this usually results in a system that is unusable. You need to build back up from @base in order to get a good build. I have no idea what these packages might be for FC5. Chip -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Emil Grochocki Sent: Monday, April 17, 2006 8:32 AM To: kickstart-list at redhat.com Subject: FC5 minimal How install "core" (not "base") version of FC5. I append: %packages @core but anaconda still install "base" version :-( Best Regards Emil Grochocki _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From jkeating at j2solutions.net Mon Apr 17 17:43:57 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Mon, 17 Apr 2006 13:43:57 -0400 Subject: FC5 minimal In-Reply-To: References: Message-ID: <1145295837.3071.25.camel@ender> On Mon, 2006-04-17 at 10:37 -0700, Shabazian, Chip wrote: > Be aware however, that this usually results in a system that is > unusable. You need to build back up from @base in order to get a good > build. I have no idea what these packages might be for FC5. %packages --nobase @Core will give you a system that is usable, but has no yum, no lftp, no man pages, no a lot of stuff. You do get rpm, and thus python so thats good. It is usable, just difficult to add to it from there. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) 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: This is a digitally signed message part URL: From Chip.Shabazian at bankofamerica.com Mon Apr 17 17:59:16 2006 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 17 Apr 2006 10:59:16 -0700 Subject: No module named rhpxl.videocard on FC5 Message-ID: Not sure if this will help or not, but when I use text, I also have to use nofb in order to connect over the virtual console port on the HP DL servers. boot: text nofb yadda.yadda.yadda -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Daniel Segall Sent: Sunday, April 16, 2006 4:41 PM To: kickstart-list at redhat.com Subject: Re: No module named rhpxl.videocard on FC5 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Axel Thimm wrote: > Hi, > > if I try to switch a kickstart install to text mode by adding the > keyword text, the console gets garbled while python debug traces. > Among others the relevant issue seems to be > > No module named rhpxl.videocard > > > > ---------------------------------------------------------------------- > -- > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list This is a known issue: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185840 Either comment out the xconfig line in your kickstart, or do a graphical install. - -Dan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEQtXxKBx1bl6SFWURAmNXAJ4u6onJHohwuMhKVa1hNP9qxudFrwCcCxUl Iq88PnsWq5/AVW4IICFBl0w= =Sq0o -----END PGP SIGNATURE----- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From E.Grochocki at coi.pw.edu.pl Mon Apr 17 19:19:40 2006 From: E.Grochocki at coi.pw.edu.pl (Emil Grochocki) Date: Mon, 17 Apr 2006 21:19:40 +0200 Subject: FC5 minimal References: <1145295837.3071.25.camel@ender> Message-ID: <01cd01c66253$e017edb0$0b911dc2@venus> Subject: RE: FC5 minimal %packages --nobase @Core Great! Thx ! Best regards Emil Grochocki From wwan at sigma-rt.com Tue Apr 18 01:56:32 2006 From: wwan at sigma-rt.com (Wim Wan) Date: Tue, 18 Apr 2006 09:56:32 +0800 Subject: How can i add a my own custom RPM package??? Message-ID: <200604180956299685177@sigma-rt.com> Hi, I want to network-autoinstall CentOS, so I copy anything needed from CentOS CD1,CD2,CD3,CD4 to my $HTTPdocumentRoot/centos/ and I copy my Own custom RPM to $HTTPdocumentRoot/centos/CentOS/RPMS/.... and add wim to CentOS/base/comps.xml and /usr/lib/anaconda-runtime/genhdlist $HTTPdocumentRoot/centos/ and get two new files: hdlist, hdlist2 but, when I use ks.cfg to Install it, a Warnning "not all packages in hdlist had order tag" show on VC3(virtual console 3), and install stop and died??? Please help me! What is a whole way to add a custom RPM to CentOS install tree? Wim Wan 2006-04-18 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nauman.yousuf at gmail.com Tue Apr 18 09:35:59 2006 From: nauman.yousuf at gmail.com (Nauman Yousuf) Date: Tue, 18 Apr 2006 14:35:59 +0500 Subject: MD drives not bootable In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: i am doing this Dan grub> device (hd0) /dev/sdb grub> root (hd0.0) grub> setup (hd0) setup (hd0) give me segmentation fault . what i do else is ok but i cant copy grub on second disk as well i add new disk same issue is there too. On 4/17/06, Dan Carpenter wrote: > > Also you need to install GRUB on each physical drive. > > http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/008898.html > > Read from the section: "Installing GRUB Onto Drives that have /boot > Raid Partitions" > > regards, > dan carpenter > > _______________________________________________ > 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 psfales at lucent.com Tue Apr 18 15:17:11 2006 From: psfales at lucent.com (Peter Fales) Date: Tue, 18 Apr 2006 10:17:11 -0500 Subject: FC5 on low memory systems Message-ID: <20060418151711.GA5712@lucent.com> I'm having trouble getting an FC5 kickstart to work on a laptop with only 128M of memory. With part swap --recommended it creates a 128M swap file which I believe is not big enough. The install aborts about halfway through and since the system reboots at that point, it's hard to see if any errors occur. But, I'm guessing it's running out of space because if I use part swap --size 256 then the installation will complete successfully. But, that's not the right answer for systems with larger amounts of memory. What I'd really like is something like part --size MIN( 256, recommended ) or better, to have anaconda not create such a small swap partition in the first place. Any workarounds? Should this be a bug against anaconda? Thanks, -- Peter Fales Lucent Technologies Member of Technical Staff 2000 Lucent Lane Room: 1C-436 Naperville, IL 60566-7033 Email: psfales at lucent.com Phone: 630 979 8031 From Chip.Shabazian at bankofamerica.com Tue Apr 18 16:29:24 2006 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Tue, 18 Apr 2006 09:29:24 -0700 Subject: FC5 on low memory systems Message-ID: You could run whatever logic you want in the %pre section, and then simply %include the swap information in the command section. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Peter Fales Sent: Tuesday, April 18, 2006 8:17 AM To: Discussion list about Kickstart Subject: FC5 on low memory systems I'm having trouble getting an FC5 kickstart to work on a laptop with only 128M of memory. With part swap --recommended it creates a 128M swap file which I believe is not big enough. The install aborts about halfway through and since the system reboots at that point, it's hard to see if any errors occur. But, I'm guessing it's running out of space because if I use part swap --size 256 then the installation will complete successfully. But, that's not the right answer for systems with larger amounts of memory. What I'd really like is something like part --size MIN( 256, recommended ) or better, to have anaconda not create such a small swap partition in the first place. Any workarounds? Should this be a bug against anaconda? Thanks, -- Peter Fales Lucent Technologies Member of Technical Staff 2000 Lucent Lane Room: 1C-436 Naperville, IL 60566-7033 Email: psfales at lucent.com Phone: 630 979 8031 _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From error27 at gmail.com Tue Apr 18 20:22:31 2006 From: error27 at gmail.com (Dan Carpenter) Date: Tue, 18 Apr 2006 13:22:31 -0700 Subject: MD drives not bootable In-Reply-To: References: <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: On 4/18/06, Nauman Yousuf wrote: > /sbin/mdadm /dev/md0 --add ${DRIVE}6 > /sbin/mdadm /dev/md1 --add ${DRIVE}2 > /sbin/mdadm /dev/md2 --add ${DRIVE}8 > /sbin/mdadm /dev/md3 --add ${DRIVE}5 > /sbin/mdadm /dev/md4 --add ${DRIVE}3 > /sbin/mdadm /dev/md5 --add ${DRIVE}7 > /sbin/mdadm /dev/md6 --add ${DRIVE}1 Why are you adding them backwards? > grub> root (hd0.0) It's a ',' not '.' Is this your boot partition if you are setting it up as md6? regards, dan carpenter From nauman.yousuf at gmail.com Wed Apr 19 06:18:39 2006 From: nauman.yousuf at gmail.com (Nauman Yousuf) Date: Wed, 19 Apr 2006 11:18:39 +0500 Subject: MD drives not bootable In-Reply-To: References: <386138A7-207C-46C5-9E48-6EDEBF0D86A4@mail.arc.nasa.gov> <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: i am adding backward as its done by disk durid when i made my software raid so i just copy the partition table of one disk to new disk .. well its , its my writing mistake in mail i am getting segmentation fault. On 4/17/06, Dan Carpenter wrote: > > Also you need to install GRUB on each physical drive. > > http://lists.us.dell.com/pipermail/linux-poweredge/2003-July/008898.html > > Read from the section: "Installing GRUB Onto Drives that have /boot > Raid Partitions" > > regards, > dan carpenter > > _______________________________________________ > 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 error27 at gmail.com Wed Apr 19 15:58:44 2006 From: error27 at gmail.com (Dan Carpenter) Date: Wed, 19 Apr 2006 08:58:44 -0700 Subject: MD drives not bootable In-Reply-To: References: <676847c60604140535q7b344ea1wd552dd98fbeef080@mail.gmail.com> <676847c60604141002i43a40b1ub8a3d8b201d421e4@mail.gmail.com> Message-ID: On 4/18/06, Nauman Yousuf wrote: > i am adding backward as its done by disk durid when i made my software raid > so i just copy the partition table of one disk to new disk .. > That just sounds bizarre to me. What does your /etc/fstab look like? regards, dan carpenter From forltran at yahoo.com Wed Apr 19 16:36:20 2006 From: forltran at yahoo.com (Lambert Tran) Date: Wed, 19 Apr 2006 09:36:20 -0700 (PDT) Subject: How can i add a my own custom RPM package??? In-Reply-To: <200604180956299685177@sigma-rt.com> Message-ID: <20060419163620.26705.qmail@web82308.mail.mud.yahoo.com> Wim, What you need to do is to run genhdlist twice. The 1st one to get hdlists for pkgorder, run the pkgorder, then finally run the genhdlist again to get the hdlists. This has worked for me: # cd to the dir contains RedHat, isolinux... # run genhdlist 1st time /usr/lib/anaconda-runtime/genhdlist --withnumbers \ --hdlist $PWD/RedHat/base/hdlist $PWD # run pkgorder, this will create pkgorder file in cwd PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder \ $PWD/ i386 > pkgorder # run genhdlist again with the correct order: /usr/lib/anaconda-runtime/genhdlist --withnumbers \ --fileorder $PWD/pkgorder --hdlist $PWD/RedHat/base/hdlist $PWD -ltran --- Wim Wan wrote: > > Hi, > > I want to network-autoinstall CentOS, so I copy anything needed from CentOS > CD1,CD2,CD3,CD4 to my $HTTPdocumentRoot/centos/ > > and I copy my Own custom RPM to $HTTPdocumentRoot/centos/CentOS/RPMS/.... > > and add wim to CentOS/base/comps.xml > > and /usr/lib/anaconda-runtime/genhdlist $HTTPdocumentRoot/centos/ > > and get two new files: hdlist, hdlist2 > > but, when I use ks.cfg to Install it, a Warnning "not all packages in hdlist > had order tag" show on VC3(virtual console 3), and install stop and died??? > > Please help me! > What is a whole way to add a custom RPM to CentOS install tree? > > > > Wim Wan > 2006-04-18 > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mhammerton at gmail.com Wed Apr 19 23:21:43 2006 From: mhammerton at gmail.com (Mark Hammerton) Date: Wed, 19 Apr 2006 19:21:43 -0400 Subject: need help with boot cd Message-ID: <310b80f10604191621o73c2c5b6m99f81b9fcd97d3c2@mail.gmail.com> I am using red hat enterprise linux v4 and i want eveyrthing to fit on one CD to do a minimal install i finally created a boot cd that will boot up and it uses the ks.cfg file on the cd so it does a complete install with out me beiing there. however after i install it instructs me to reboot and when i go to reboot it doesnt come grub starts to load and but nothing is install except a few folders under the root directory but no files or any of the packages are install before i reboot i checked the red hat installation screen and go this off of it *not all packages in hdlist had order tag File descriptor 3 left open the file descriptor on list from 1 until 31 No volume groups found these ar eth errors that i see on the screen from. can anyone help me out as to what they think my problem may be. everything would be greatly appreciated -------------- next part -------------- An HTML attachment was scrubbed... URL: From wwan at sigma-rt.com Thu Apr 20 01:36:33 2006 From: wwan at sigma-rt.com (Wim Wan) Date: Thu, 20 Apr 2006 09:36:33 +0800 Subject: How can i add a my own custom RPM package??? References: <20060419163620.26705.qmail@web82308.mail.mud.yahoo.com> Message-ID: <200604200936321710076@sigma-rt.com> Hi All: I succeed follow this method~ Thanks! Wim Wan 2006-04-20 ???? Lambert Tran ????? 2006-04-20 00:45:51 ???? Discussion list about Kickstart ??? ??? Re: How can i add a my own custom RPM package??? Wim, What you need to do is to run genhdlist twice. The 1st one to get hdlists for pkgorder, run the pkgorder, then finally run the genhdlist again to get the hdlists. This has worked for me: # cd to the dir contains RedHat, isolinux... # run genhdlist 1st time /usr/lib/anaconda-runtime/genhdlist --withnumbers \ --hdlist $PWD/RedHat/base/hdlist $PWD # run pkgorder, this will create pkgorder file in cwd PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder \ $PWD/ i386 > pkgorder # run genhdlist again with the correct order: /usr/lib/anaconda-runtime/genhdlist --withnumbers \ --fileorder $PWD/pkgorder --hdlist $PWD/RedHat/base/hdlist $PWD -ltran --- Wim Wan wrote: > > Hi, > > I want to network-autoinstall CentOS, so I copy anything needed from CentOS > CD1,CD2,CD3,CD4 to my $HTTPdocumentRoot/centos/ > > and I copy my Own custom RPM to $HTTPdocumentRoot/centos/CentOS/RPMS/.... > > and add wim to CentOS/base/comps.xml > > and /usr/lib/anaconda-runtime/genhdlist $HTTPdocumentRoot/centos/ > > and get two new files: hdlist, hdlist2 > > but, when I use ks.cfg to Install it, a Warnning "not all packages in hdlist > had order tag" show on VC3(virtual console 3), and install stop and died??? > > Please help me! > What is a whole way to add a custom RPM to CentOS install tree? > > > > Wim Wan > 2006-04-18 > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 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 forltran at yahoo.com Thu Apr 20 01:56:57 2006 From: forltran at yahoo.com (Lambert Tran) Date: Wed, 19 Apr 2006 18:56:57 -0700 (PDT) Subject: need help with boot cd In-Reply-To: <310b80f10604191621o73c2c5b6m99f81b9fcd97d3c2@mail.gmail.com> Message-ID: <20060420015657.7990.qmail@web82303.mail.mud.yahoo.com> Looked like you have the same problem with package order. Please read my previous email about running genhlist twice for more info. You can email me directly if you have any question. If you do email me, then give me a sample of your ks.cfg file. -ltran --- Mark Hammerton wrote: > I am using red hat enterprise linux v4 and i want eveyrthing to fit on one > CD to do a minimal install > i finally created a boot cd that will boot up and it uses the ks.cfg file on > the cd so it does a complete install with out me beiing there. however after > i install it instructs me to reboot and when i go to reboot it doesnt come > grub starts to load and but nothing is install except a few folders under > the root directory but no files or any of the packages are install before i > reboot i checked the red hat installation screen and go this off of it > > *not all packages in hdlist had order tag > > > File descriptor 3 left open > > the file descriptor on list from 1 until 31 > > No volume groups found > > these ar eth errors that i see on the screen from. > > > > > can anyone help me out as to what they think my problem may be. > everything would be greatly appreciated > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mhammerton at gmail.com Thu Apr 20 18:13:57 2006 From: mhammerton at gmail.com (Mark Hammerton) Date: Thu, 20 Apr 2006 14:13:57 -0400 Subject: need help with boot cd In-Reply-To: <20060420015657.7990.qmail@web82303.mail.mud.yahoo.com> References: <310b80f10604191621o73c2c5b6m99f81b9fcd97d3c2@mail.gmail.com> <20060420015657.7990.qmail@web82303.mail.mud.yahoo.com> Message-ID: <310b80f10604201113m4e6ed835wa028726fbbf0d014@mail.gmail.com> hey i was trying wat you suggested to the other guy thanks. However i create my pkorder.txt this is the command i use PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder $PWD/ > pkgorder i use this command in the root directory were the cd is. I see you have something about pointing it to i386, but i dont have any i386 directories i am using the AMD64 RHEL v4. Also i know which packages i want from the installer however i want to know how can i accurately tell which rpms i need on the cd, i have my ks.cfgalready this is my kickstart file cat ks.cfg # Kickstart file automatically generated by anaconda. install cdrom lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8 keyboard us xconfig --card "ATI Mach64" --videoram 8192 --hsync 31.5-37.9 --vsync 50-70 --resolution 800x600 --depth 16 network --device eth0 --bootproto static --ip 0.0.0.0 --netmask 255.255.255.0 --gateway 65.243.100.1 --nameserver 24.244.141.3,24.244.141.4--hostname dsg11 network --device eth1 --onboot no --bootproto dhcp --hostname dsg11 rootpw --iscrypted $1$bdKsw5wV$zcds9Vi/PrwYj4IZRh072. firewall --enabled --port=22:tcp selinux --disabled authconfig --enableshadow --enablemd5 timezone America/Nassau bootloader --location=partition # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --drives=hda,hdc part raid.9 --size=100 --ondisk=hda --asprimary part raid.16 --size=100 --ondisk=hdc --asprimary part raid.13 --size=20480 --ondisk=hdc --asprimary part raid.11 --size=20480 --ondisk=hda --asprimary part raid.14 --size=1024 --ondisk=hdc --asprimary part raid.10 --size=1024 --ondisk=hda --asprimary part raid.15 --size=100 --grow --ondisk=hdc --asprimary part raid.12 --size=100 --grow --ondisk=hda --asprimary raid /boot --fstype ext3 --level=RAID1 raid.9 raid.16 raid swap --fstype swap --level=RAID1 raid.10 raid.14 raid / --fstype ext3 --level=RAID1 raid.11 raid.13 raid /home --fstype ext3 --level=RAID1 raid.12 raid.15 %packages @ mysql @ admin-tools @ editors @ emacs @ text-internet @ dns-server @ dialup @ ftp-server @ web-server @ mail-server @ server-cfg @ development-tools php-mysql kernel mdadm -sendmail-cf mod_auth_mysql postfix mysql-server kernel-devel squirrelmail e2fsprogs %post chkconfig httpd on chkconfig vsftpd on chkconfig mysqld on chkconfig named on chkconfig saslauthd on chkconfig cyrus-imapd on chkconfig cups off chkconfig isdn off chkconfig kudzu off chkconfig pcmcia off chkconfig sendmail off chkconfig postfix on chkconfig nfslock off chkconfig nfs off chkconfig portmap off chkconfig nfslock off chkconfig nfs off chkconfig portmap off chkconfig cyrus-imapd on /etc/init.d/cups stop /etc/init.d/nfslock stop /etc/init.d/nfs stop /etc/init.d/portmap stop /etc/init.d/cyrus-imapd start /etc/init.d/sendmail stop /etc/init.d/postfix start /etc/init.d/httpd start /etc/init.d/mysqld start /etc/init.d/vsftpd start /etc/init.d/named start /etc/init.d/saslauthd start /etc/init.d/cups stop /etc/init.d/nfslock stop /etc/init.d/nfs stop /etc/init.d/portmap stop /etc/init.d/cyrus-imapd start mysqladmin -u root password mysqlpa55 touch /var/spool/cron/root echo "0 3,9,15,21 * * * /usr/sbin/ntpdate -u 128.2.136.71" >> /var/spool/cron/root chmod 600 /var/spool/cron/root /etc/init.d/crond restart -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhammerton at gmail.com Thu Apr 20 19:40:28 2006 From: mhammerton at gmail.com (Mark Hammerton) Date: Thu, 20 Apr 2006 15:40:28 -0400 Subject: Stripping down red hat cds Message-ID: <310b80f10604201240s104649edsb15db64058b9428a@mail.gmail.com> I wanted to created a single RHEL v4 CD {down from 5cds} during the installation i know which packages i need however i want to know which rpms would i need to keep such as including and fixing dependeencies so i can do a base instal from one cd or one jump drive. I can show you the ks.cfg file so you can see which pacages i need -- my LAN is your LAN -------------- next part -------------- An HTML attachment was scrubbed... URL: From JBilder at bacons.com Thu Apr 20 20:52:09 2006 From: JBilder at bacons.com (Jeffry Bilder) Date: Thu, 20 Apr 2006 15:52:09 -0500 Subject: Problems with Partitioning Message-ID: Here is my current kickstart file for FC5: ## :: hard partitioning part /boot --asprimary --fstype="ext3" --ondisk=hda --size=75 part pv.00 --size=1 --grow --asprimary --ondisk=hda volgroup vgroot pv.00 logvol / --fstype="reiserfs" --name=root.fs --vgname=vgroot --size=1024 --grow logvol swap --name=swap.vol --vgname=vgroot -recommended It will start X and then error out telling me that "Could not allocate partitions as primary partitions". Any insight would be much appreciated. Thanks! - JB -------------- next part -------------- An HTML attachment was scrubbed... URL: From vlaurenz at advance.net Wed Apr 26 18:13:18 2006 From: vlaurenz at advance.net (Vito Laurenza) Date: Wed, 26 Apr 2006 14:13:18 -0400 Subject: RHEL4 Kickstart Partition Question In-Reply-To: References: Message-ID: <444FB83E.4080203@advance.net> Hello all, I am trying to specify the number of bytes per inode on a partion in my kickstart config. I am familiar with the mkfs.ext3 flag --bytes-per-inode. Is there a way to pass this flag through kickstart? I've noticed in my googling that in older versions of kickstart (as late as RH 8) there was a flag to the 'part' option (--bytes-per-inode=) which allowed this. It seems like this flag was removed in later versions of kickstart. Is there anyway that I can have this functionality with kickstart and RHEL4? Thanks in advance, Vito :::: Vito Laurenza :: Systems Administrator :: Advance Internet :: 201.793.1807 :: vlaurenz at advance.net From clumens at redhat.com Wed Apr 26 18:30:21 2006 From: clumens at redhat.com (Chris Lumens) Date: Wed, 26 Apr 2006 14:30:21 -0400 Subject: Problems with Partitioning In-Reply-To: References: Message-ID: <20060426183020.GC2985@exeter.boston.redhat.com> > It will start X and then error out telling me that "Could not allocate > partitions as primary partitions". Do you have any clearpart command? - Chris From phr at doc.ic.ac.uk Wed Apr 26 23:39:19 2006 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Thu, 27 Apr 2006 00:39:19 +0100 (BST) Subject: RHEL4 Kickstart Partition Question In-Reply-To: <444FB83E.4080203@advance.net> References: <444FB83E.4080203@advance.net> Message-ID: On Wed, 26 Apr 2006, Vito Laurenza wrote: > I am trying to specify the number of bytes per inode on a partion in > my kickstart config. I am familiar with the mkfs.ext3 flag > --bytes-per-inode. Is there a way to pass this flag through kickstart? > > I've noticed in my googling that in older versions of kickstart (as > late as RH 8) there was a flag to the 'part' option > (--bytes-per-inode=) which allowed this. It seems like this flag was > removed in later versions of kickstart. It was? Still there in my Fedora Core 4 docs: $ grep -A4 bytes-per /usr/share/doc/anaconda-10.2.1.5/kickstart-docs.txt --bytes-per-inode= Specifies the size of inodes on the filesystem to be made on the partition. Not all filesystems support this option, so it is silently ignored for those cases. Cheers, Phil From patchu1 at yahoo.com Fri Apr 28 01:57:23 2006 From: patchu1 at yahoo.com (Pat) Date: Thu, 27 Apr 2006 18:57:23 -0700 (PDT) Subject: Script which runs after first reboot only? Message-ID: <20060428015723.97135.qmail@web32505.mail.mud.yahoo.com> There are a few last steps I need to do to complete my automated system setup which can only be done AFTER a computer reboots when it completes an installation. If you are wondering the steps including installing an RPM and initial configuration of some system services. Where do I place this script so it only runs once after the first reboot? Thanks for any help! __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From jkeating at j2solutions.net Fri Apr 28 02:00:33 2006 From: jkeating at j2solutions.net (Jesse Keating) Date: Thu, 27 Apr 2006 22:00:33 -0400 Subject: Script which runs after first reboot only? In-Reply-To: <20060428015723.97135.qmail@web32505.mail.mud.yahoo.com> References: <20060428015723.97135.qmail@web32505.mail.mud.yahoo.com> Message-ID: <1146189633.3196.26.camel@ender> On Thu, 2006-04-27 at 18:57 -0700, Pat wrote: > > Where do I place this script so it only runs once > after the first reboot? Thanks for any help! > In %post, copy /etc/rc.local to /etc/rc.local.back, insert your script into the end of /etc/rc.local, add to the end of your script a move of /etc/rc.local.back to /etc/rc.local And you're done (; -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) 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: This is a digitally signed message part URL: From tibbs at math.uh.edu Fri Apr 28 02:01:51 2006 From: tibbs at math.uh.edu (Jason L Tibbitts III) Date: Thu, 27 Apr 2006 21:01:51 -0500 Subject: Script which runs after first reboot only? In-Reply-To: <20060428015723.97135.qmail@web32505.mail.mud.yahoo.com> (Pat's message of "Thu, 27 Apr 2006 18:57:23 -0700 (PDT)") References: <20060428015723.97135.qmail@web32505.mail.mud.yahoo.com> Message-ID: >>>>> "P" == Pat writes: P> There are a few last steps I need to do to complete my automated P> system setup which can only be done AFTER a computer reboots when P> it completes an installation. I do this; in %post I just stick the script in /math-firstboot and then stick this at the end of /etc/rc.d/rc.local: if [ -f /math-firstboot ]; then echo "First boot: doing initial setup" /math-firstboot& fi The last thing /math-firstboot does is delete itself. This isn't the prettiest way to do things, but it's worked for me for many releases now. - J< From patchu1 at yahoo.com Fri Apr 28 17:39:34 2006 From: patchu1 at yahoo.com (Pat) Date: Fri, 28 Apr 2006 10:39:34 -0700 (PDT) Subject: Script which runs after first reboot only? In-Reply-To: <20060428160011.CA8557367E@hormel.redhat.com> Message-ID: <20060428173934.62934.qmail@web32505.mail.mud.yahoo.com> Thanks for the replies. I wasn't clever enough to think of using the rc.local file in that fashion but once you guys mentioned it, it makes perfect sense. Thanks again! __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From robin-lists at robinbowes.com Sat Apr 29 19:05:52 2006 From: robin-lists at robinbowes.com (Robin Bowes) Date: Sat, 29 Apr 2006 20:05:52 +0100 Subject: FC5 minimal In-Reply-To: <1145295837.3071.25.camel@ender> References: <1145295837.3071.25.camel@ender> Message-ID: Jesse Keating wrote: > On Mon, 2006-04-17 at 10:37 -0700, Shabazian, Chip wrote: >> Be aware however, that this usually results in a system that is >> unusable. You need to build back up from @base in order to get a good >> build. I have no idea what these packages might be for FC5. > > %packages --nobase > @Core > > will give you a system that is usable, but has no yum, no lftp, no man > pages, no a lot of stuff. You do get rpm, and thus python so thats > good. It is usable, just difficult to add to it from there. I've been working on this today, and this post scratch my itch nicely! I use this: %packages --nobase --resolvedeps @Core yum openssh-server openssh-clients # list of other packages here This way I can add only just those packages I need and don't get all the other cruft that comes with the standard install and isn't needed on servers. Now, if I could only work out how to set LANG to en_GB.UTF-8 on installation ... R.