From dag at wieers.com Wed Oct 1 11:57:25 2008 From: dag at wieers.com (Dag Wieers) Date: Wed, 1 Oct 2008 13:57:25 +0200 (CEST) Subject: Forcing a disk rescan after %pre Message-ID: Hi, We are integrating some pre-install scripts. One of the things we have now is that in the %pre phase the HW RAID controller is tested for "Virtual disks" and if none are found it will create a RAID config depending on the number of disks found. The problem is that even when we created the RAID, restarted the RAID driver and created the device node (fdisk -l shows the new disk). Anaconda does not know about the new disk, likely because the scan for disks happened before. I found a file /tmp/scsidisks and also rewrite that file, but still Anaconda does not update its view of the system after the %pre. Does someone know how we can make Anaconda understand that we created a disk in the %pre ? -- -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] From debian at herakles.homelinux.org Thu Oct 2 01:22:48 2008 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 02 Oct 2008 09:22:48 +0800 Subject: Forcing a disk rescan after %pre In-Reply-To: References: Message-ID: <48E42268.3050401@herakles.homelinux.org> Dag Wieers wrote: > Hi, > > We are integrating some pre-install scripts. One of the things we have > now is that in the %pre phase the HW RAID controller is tested for > "Virtual disks" and if none are found it will create a RAID config > depending on the number of disks found. > > The problem is that even when we created the RAID, restarted the RAID > driver and created the device node (fdisk -l shows the new disk). > Anaconda does not know about the new disk, likely because the scan for > disks happened before. > > I found a file /tmp/scsidisks and also rewrite that file, but still > Anaconda does not update its view of the system after the %pre. > > Does someone know how we can make Anaconda understand that we created a > disk in the %pre ? I'm a little puzzled. Years ago (RHL 7.x I think) I used to initialise disks in %pre with various incantations of dd and fdisk (one can pipe commands into fdisk). That worked fine, and I'm pretty sure I created new partitions. fdisk forces partition tables to be reread. Of course, it's possible anaconda has been broken since then:-) -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From pmalinowskieu at yahoo.co.uk Thu Oct 2 08:04:29 2008 From: pmalinowskieu at yahoo.co.uk (Paul Malinowski) Date: Thu, 2 Oct 2008 08:04:29 +0000 (GMT) Subject: Forcing a disk rescan after %pre Message-ID: <605867.90423.qm@web23105.mail.ird.yahoo.com> Try to use partprobe to re-read available disks/partitions. I'm not sure is it available when %pre script runs, but anaconda does that somehow during the partitioning section so I guess it's possible. In the worst case scenario I would add reboot at the end of creation of raid config in the %pre script - so that it would reboot if change in config occured. I know that its rather a nasty hack, not a proper solution, but please keep in mind that anaconda has some limits. Good luck! Paul Malinowski ----- Original Message ---- From: John Summerfield To: Discussion list about Kickstart Sent: Thursday, 2 October, 2008 2:22:48 Subject: Re: Forcing a disk rescan after %pre Dag Wieers wrote: > Hi, > > We are integrating some pre-install scripts. One of the things we have > now is that in the %pre phase the HW RAID controller is tested for > "Virtual disks" and if none are found it will create a RAID config > depending on the number of disks found. > > The problem is that even when we created the RAID, restarted the RAID > driver and created the device node (fdisk -l shows the new disk). > Anaconda does not know about the new disk, likely because the scan for > disks happened before. > > I found a file /tmp/scsidisks and also rewrite that file, but still > Anaconda does not update its view of the system after the %pre. > > Does someone know how we can make Anaconda understand that we created a > disk in the %pre ? I'm a little puzzled. Years ago (RHL 7.x I think) I used to initialise disks in %pre with various incantations of dd and fdisk (one can pipe commands into fdisk). That worked fine, and I'm pretty sure I created new partitions. fdisk forces partition tables to be reread. Of course, it's possible anaconda has been broken since then:-) -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) _______________________________________________ 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 dag at wieers.com Thu Oct 2 11:11:04 2008 From: dag at wieers.com (Dag Wieers) Date: Thu, 2 Oct 2008 13:11:04 +0200 (CEST) Subject: Forcing a disk rescan after %pre In-Reply-To: <48E42268.3050401@herakles.homelinux.org> References: <48E42268.3050401@herakles.homelinux.org> Message-ID: On Thu, 2 Oct 2008, John Summerfield wrote: > Dag Wieers wrote: >> We are integrating some pre-install scripts. One of the things we have now >> is that in the %pre phase the HW RAID controller is tested for "Virtual >> disks" and if none are found it will create a RAID config depending on the >> number of disks found. >> >> The problem is that even when we created the RAID, restarted the RAID >> driver and created the device node (fdisk -l shows the new disk). Anaconda >> does not know about the new disk, likely because the scan for disks >> happened before. >> >> I found a file /tmp/scsidisks and also rewrite that file, but still >> Anaconda does not update its view of the system after the %pre. >> >> Does someone know how we can make Anaconda understand that we created a >> disk in the %pre ? > > I'm a little puzzled. Years ago (RHL 7.x I think) I used to initialise disks > in %pre with various incantations of dd and fdisk (one can pipe commands into > fdisk). That worked fine, and I'm pretty sure I created new partitions. fdisk > forces partition tables to be reread. > > Of course, it's possible anaconda has been broken since then:-) This is not partitioning disks. This is in fact creating a /dev/sda where previously there was no local disk in the %pre. -- -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] From dag at wieers.com Thu Oct 2 11:13:05 2008 From: dag at wieers.com (Dag Wieers) Date: Thu, 2 Oct 2008 13:13:05 +0200 (CEST) Subject: Forcing a disk rescan after %pre In-Reply-To: <605867.90423.qm@web23105.mail.ird.yahoo.com> References: <605867.90423.qm@web23105.mail.ird.yahoo.com> Message-ID: On Thu, 2 Oct 2008, Paul Malinowski wrote: > Try to use partprobe to re-read available disks/partitions. I'm not > sure is it available when %pre script runs, but anaconda does that > somehow during the partitioning section so I guess it's possible. In the > worst case scenario I would add reboot at the end of creation of raid > config in the %pre script - so that it would reboot if change in config > occured. I know that its rather a nasty hack, not a proper solution, but > please keep in mind that anaconda has some limits. The reboot is what I am planning to do, but I prefer to look first at a better option instead of settling for this because I don't know better :-) I fear that anaconda's data-structure is not updated and the scan for disks has already happened before the %pre. Because after my RAID scripts has run, I do have /dev/sda available to the system, but anaconda behaves as if there were no disks found. -- -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] From Pablo.Iranzo at redhat.com Thu Oct 2 11:18:39 2008 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?ISO-8859-1?Q?G=F3mez?=) Date: Thu, 02 Oct 2008 13:18:39 +0200 Subject: Forcing a disk rescan after %pre In-Reply-To: References: <605867.90423.qm@web23105.mail.ird.yahoo.com> Message-ID: <1222946319.5905.140.camel@iranzo.users.redhat.com> Dag, I think that I was able to detect MD devices created after %pre (on VT2), so would be an option to create an MD device over your newly created sda ? Regards Pablo El jue, 02-10-2008 a las 13:13 +0200, Dag Wieers escribi?: > On Thu, 2 Oct 2008, Paul Malinowski wrote: > > > Try to use partprobe to re-read available disks/partitions. I'm not > > sure is it available when %pre script runs, but anaconda does that > > somehow during the partitioning section so I guess it's possible. In the > > worst case scenario I would add reboot at the end of creation of raid > > config in the %pre script - so that it would reboot if change in config > > occured. I know that its rather a nasty hack, not a proper solution, but > > please keep in mind that anaconda has some limits. > > The reboot is what I am planning to do, but I prefer to look first at a > better option instead of settling for this because I don't know better :-) > > I fear that anaconda's data-structure is not updated and the scan for > disks has already happened before the %pre. Because after my RAID scripts > has run, I do have /dev/sda available to the system, but anaconda behaves > as if there were no disks found. > -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Esta parte del mensaje est? firmada digitalmente URL: From lists at zadevalov.com Thu Oct 2 13:46:15 2008 From: lists at zadevalov.com (Eugeny Zadevalov) Date: Thu, 02 Oct 2008 16:46:15 +0300 Subject: Forcing a disk rescan after %pre In-Reply-To: References: <605867.90423.qm@web23105.mail.ird.yahoo.com> Message-ID: <48E4D0A7.3060507@zadevalov.com> Dag Wieers wrote: > On Thu, 2 Oct 2008, Paul Malinowski wrote: > >> Try to use partprobe to re-read available disks/partitions. I'm not >> sure is it available when %pre script runs, but anaconda does that >> somehow during the partitioning section so I guess it's possible. In >> the worst case scenario I would add reboot at the end of creation of >> raid config in the %pre script - so that it would reboot if change in >> config occured. I know that its rather a nasty hack, not a proper >> solution, but please keep in mind that anaconda has some limits. > > The reboot is what I am planning to do, but I prefer to look first at a > better option instead of settling for this because I don't know better :-) > > I fear that anaconda's data-structure is not updated and the scan for > disks has already happened before the %pre. Because after my RAID > scripts has run, I do have /dev/sda available to the system, but > anaconda behaves as if there were no disks found. > Dag, if you're using "--onbiosdisk=XX" in your "part" anaconda commands that's the case. Avoid it and switch to "$(list-harddrives)"+"--ondisk=" method. Hope that helps, Thanks! From KMcDonald at egenera.com Fri Oct 3 15:15:00 2008 From: KMcDonald at egenera.com (Kyle McDonald) Date: Fri, 03 Oct 2008 11:15:00 -0400 Subject: Can anyone tell me what this KS stacktrace means? Message-ID: <48E636F4.1000805@Egenera.COM> Hi. Shortly after the kickstart has finished booting I get this: Running anaconda, the Red Hat Enterprise Linux Server system installer - please wait... Traceback (most recent call last): File "/usr/bin/anaconda", line 737, in ? vncksdata = setVNCFromKickstart(opts) File "/usr/bin/anaconda", line 274, in setVNCFromKickstart ksparser.readKickstart(opts.ksfile) File "/usr/lib/python2.4/site-packages/pykickstart/parser.py", line 1146, in readKickstart raise KickstartParseError, formatErrorMsg(lineno) pykickstart.parser.KickstartParseError: There was a problem reading from line 9 of the kickstart file install exited abnormally [1/1] line 9 of the kickstart file is: %include /tmp/ks.include /tmp/ks.include is generated by the %pre section. Everything looks fine, anyone with more experience have any ideas? -Kyle From rigg0022 at umn.edu Fri Oct 3 15:59:32 2008 From: rigg0022 at umn.edu (Ben Riggs) Date: Fri, 03 Oct 2008 10:59:32 -0500 Subject: Can anyone tell me what this KS stacktrace means? In-Reply-To: <48E636F4.1000805@Egenera.COM> References: <48E636F4.1000805@Egenera.COM> Message-ID: <48E64164.4090700@umn.edu> What is in /tmp/ks.include? Kyle McDonald wrote: > Hi. > > Shortly after the kickstart has finished booting I get this: > > Running anaconda, the Red Hat Enterprise Linux Server system installer - > please wait... > Traceback (most recent call last): > File "/usr/bin/anaconda", line 737, in ? > vncksdata = setVNCFromKickstart(opts) > File "/usr/bin/anaconda", line 274, in setVNCFromKickstart > ksparser.readKickstart(opts.ksfile) > File "/usr/lib/python2.4/site-packages/pykickstart/parser.py", line > 1146, in readKickstart > raise KickstartParseError, formatErrorMsg(lineno) > pykickstart.parser.KickstartParseError: There was a problem reading from > line 9 of the kickstart file > install exited abnormally [1/1] > > line 9 of the kickstart file is: > > %include /tmp/ks.include > > /tmp/ks.include is generated by the %pre section. > > Everything looks fine, anyone with more experience have any ideas? > > -Kyle > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Matthew.Richards at contentkeeper.com Fri Oct 10 06:46:12 2008 From: Matthew.Richards at contentkeeper.com (Matthew Richards) Date: Fri, 10 Oct 2008 17:46:12 +1100 Subject: Device naming for hd:: when installing off a USB HD Message-ID: Hi Charles, I am working on a solution to the same issue as well. Have you had any luck with this one :-) My main goal is to be able to do a kickstart install from USB without having the user prompted (after they start the install of course) for an install source method. > > Would it work to copy ks.cfg onto the local hard drive (which *isn't* > changing names between boots), have a %pre that generates an appropriate > harddrive stanza, and %include that? My initial attempt at solving this involved an approach similar to the one you mentioned, thus: 1) Give my USB installer a custom file system label. 2) Write a %pre script that identifies the USB install device by looking for the custom fs label with e2label, then writes the appropriate kickstart method= and ignoredisks= options to /tmp/ks-include 3) Finally add %include /tmp/ks-include to the start of my kickstart file. The problem with this approach is that the loader (init in Stage1 actually) needs to know the install method before the %pre scripts are run. It's a sort of chicken and egg situation. I have explored/considered some alternatives (below). I think what Pablo is suggesting is one of the simplest solutions to this problem, and by coincidence I had the exact same solution proposed to me earlier today :) Other solutions I've explored/considered: (1) Use the latest Anaconda to install CentOS 5.2. The latest Anaconda supports specification of harddrive install source via file system label, e.g. method=hd:LABEL="MyLabel1":/iso. This would allow identification of the correct USB HDD no matter which device node it was assigned. The problem is, apparently coz I haven't tried this yet, is that the latest anaconda has deps that would be too complex to resolve see comments here http://lists.centos.org/pipermail/centos-devel/2008-May/002747.html (2) Hack the CentOS 5 version of Anaconda to support specification of the harddrive install method via fs label. We found that we may be able to do this by hacking the devMakeInode function in anaconda-11.1.2.113/isys/devnodes.c and add a code block at the top to convert fs labels to device nodes. Problem is that you need to use code from e2label to read in and parse the file system super block from your local HDDs until you find the right one, then you need to use code from mknod (or perhaps an Anaconda equivalent) to set up the dev nodes as they are not set up under /dev at the time. It goes on from there, and frankly i'm not sure its worth it. (3) Apparently someone wrote a patch to Anaconda that allows specification of multiple kickstart files (ks.cfg). I haven't had much luck in tracking this down, tho I've not really tried that hard yet. I'm told this works by getting Anaconda to search for each ks file specified until it find one, so you'd specify on the command line ks=sda1/ks.cfg ks=sdb1/ks.cfg etc and Anaconda would match the USB drive that had your ks file and install source. (4) Create a Stage0 initrd that contained the actual Anaconda Stage1 initrd. This is a nice idea suggested to me by Niels de Vos that I've been playing with. You can read more about it here https://www.redhat.com/archives/anaconda-devel-list/2008-October/msg00008.html Well, good luck with the USB install. Regards, Matt ----------------------- Original Message ----------------------- * From: Pablo Iranzo G?mez * To: Discussion list about Kickstart * Subject: Re: Device naming for hd:: when installing off a USB HD * Date: Tue, 09 Sep 2008 08:36:19 +0000 Hi Charles El mar, 09-09-2008 a las 03:24 -0500, Charles Duffy escribi?: > Howdy, all. > > I'm trying to install CentOS 5 off an external USB device. The conflict > here is that the system I'm installing on has other USB storage devices > built-in, and the boot order between them is inconsistent. > This means that even if I scan the current list of device names and > labels and then kexec into the installer after observing how my initial > kernel names them, I have only a 50/50 chance of the device names used > for ks=hd::/ks.cfg and method=hd::/ being valid. > > > What's the Right Way to resolve this issue? LiveUSB's use a UUID=????-???? that identifies the root filesystem to boot > > Would it work to copy ks.cfg onto the local hard drive (which *isn't* > changing names between boots), have a %pre that generates an appropriate > harddrive stanza, and %include that? What I did to resolve this issue is to create a LiveUSB using livecd-tools from EPEL, and then inside the disk created a small script that searched for the hard drive to partition, give it boot files 'syslinux' and then reboot, so the system starts from that hard drive and perform an installation with the correct devices placed there. The problem with mixing both scsi, usb drives is that you'll never know what are your drive names going to be on the next system... so UUID could work but... will need tweaks as afaik anaconda checks for device name. Probably you could hack anaconda to run a custom script than looks for the correct path, and passes it to 'real' anaconda... Regards Pablo -- From Pablo.Iranzo at redhat.com Fri Oct 10 06:55:25 2008 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?ISO-8859-1?Q?G=F3mez?=) Date: Fri, 10 Oct 2008 08:55:25 +0200 Subject: Device naming for hd:: when installing off a USB HD In-Reply-To: References: Message-ID: <1223621725.32148.9.camel@iranzo.users.redhat.com> Hi Matthew What I did is to create a LiveUSB (using livecd-tools from EPEL on RHEL5) that triggers a minimal system that partitions hard drive, copies install ISO image, kernel, initrd and kickstart give that partition 'bootable' status with syslinux and then, restarts, so the system at next boot, uses hdd to do the install.. The problem with USB devices is that sometimes it's sda, sdb, whatever, depending on target system devices/buses ;). This method has allowed to use the same kickstart for a USB stick, a reinstall from hdd partition or a DVD... Regards Pablo El vie, 10-10-2008 a las 17:46 +1100, Matthew Richards escribi?: > Hi Charles, > > I am working on a solution to the same issue as well. Have you had any luck > with this one :-) > > My main goal is to be able to do a kickstart install from USB without having > the user prompted (after > they start the install of course) for an install source method. > > > > > Would it work to copy ks.cfg onto the local hard drive (which *isn't* > > changing names between boots), have a %pre that generates an appropriate > > harddrive stanza, and %include that? > > My initial attempt at solving this involved an approach similar to the one you > mentioned, thus: > > 1) Give my USB installer a custom file system label. > 2) Write a %pre script that identifies the USB install device by looking for > the custom fs label with e2label, > then writes the appropriate kickstart method= and ignoredisks= options to > /tmp/ks-include > 3) Finally add %include /tmp/ks-include to the start of my kickstart file. > > The problem with this approach is that the loader (init in Stage1 actually) > needs to know the install method > before the %pre scripts are run. It's a sort of chicken and egg situation. > > I have explored/considered some alternatives (below). I think what Pablo is > suggesting is one of the simplest > solutions to this problem, and by coincidence I had the exact same solution > proposed to me earlier today :) > > Other solutions I've explored/considered: > > (1) Use the latest Anaconda to install CentOS 5.2. > > The latest Anaconda supports specification of harddrive install source via file > system label, e.g. > method=hd:LABEL="MyLabel1":/iso. This would allow identification of the correct > USB HDD no matter which > device node it was assigned. > > The problem is, apparently coz I haven't tried this yet, is that the latest > anaconda has deps that would be too > complex to resolve see comments here > http://lists.centos.org/pipermail/centos-devel/2008-May/002747.html > > (2) Hack the CentOS 5 version of Anaconda to support specification of the > harddrive install method via fs label. > > We found that we may be able to do this by hacking the devMakeInode function in > anaconda-11.1.2.113/isys/devnodes.c and add a code block at the top to convert > fs labels to device nodes. > Problem is that you need to use code from e2label to read in and parse the file > system super block from your > local HDDs until you find the right one, then you need to use code from mknod > (or perhaps an Anaconda > equivalent) to set up the dev nodes as they are not set up under /dev at the > time. > > It goes on from there, and frankly i'm not sure its worth it. > > (3) Apparently someone wrote a patch to Anaconda that allows specification of > multiple kickstart files (ks.cfg). > > I haven't had much luck in tracking this down, tho I've not really tried that > hard yet. I'm told this works by > getting Anaconda to search for each ks file specified until it find one, so > you'd specify on the command line > ks=sda1/ks.cfg ks=sdb1/ks.cfg etc and Anaconda would match the USB drive that > had your ks file and install > source. > > (4) Create a Stage0 initrd that contained the actual Anaconda Stage1 initrd. > > This is a nice idea suggested to me by Niels de Vos that I've been playing > with. You can read more about it here > https://www.redhat.com/archives/anaconda-devel-list/2008-October/msg00008.html > > Well, good luck with the USB install. > > Regards, > Matt > > > > > ----------------------- Original Message ----------------------- > > * From: Pablo Iranzo Gmez > * To: Discussion list about Kickstart > * Subject: Re: Device naming for hd:: when installing off a USB > HD > * Date: Tue, 09 Sep 2008 08:36:19 +0000 > > > Hi Charles > > > El mar, 09-09-2008 a las 03:24 -0500, Charles Duffy escribi: > > Howdy, all. > > > > I'm trying to install CentOS 5 off an external USB device. The conflict > > here is that the system I'm installing on has other USB storage devices > > built-in, and the boot order between them is inconsistent. > > > This means that even if I scan the current list of device names and > > labels and then kexec into the installer after observing how my initial > > kernel names them, I have only a 50/50 chance of the device names used > > for ks=hd::/ks.cfg and method=hd::/ being valid. > > > > > > What's the Right Way to resolve this issue? > > > LiveUSB's use a UUID=????-???? that identifies the root filesystem to > boot > > > > > Would it work to copy ks.cfg onto the local hard drive (which *isn't* > > changing names between boots), have a %pre that generates an appropriate > > harddrive stanza, and %include that? > > What I did to resolve this issue is to create a LiveUSB using > livecd-tools from EPEL, and then inside the disk created a small script > that searched for the hard drive to partition, give it boot files > 'syslinux' and then reboot, so the system starts from that hard drive > and perform an installation with the correct devices placed there. > > The problem with mixing both scsi, usb drives is that you'll never know > what are your drive names going to be on the next system... so UUID > could work but... will need tweaks as afaik anaconda checks for device > name. > > Probably you could hack anaconda to run a custom script than looks for > the correct path, and passes it to 'real' anaconda... > > Regards > Pablo > > -- > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Esta parte del mensaje est? firmada digitalmente URL: From gbailey at terremark.com Tue Oct 14 15:38:47 2008 From: gbailey at terremark.com (Glenn Bailey) Date: Tue, 14 Oct 2008 10:38:47 -0500 Subject: part function Message-ID: <005AB96F733E674B89550DDAE730CB4A4BF556EE20@daa20725exc001.drtn.corp> What's the default behvaiour for the 'part' function when --ondisk is left out? I'm wanting to do something similar to this in my kickstarts, but make it available on other devices that don't have the cciss device: clearpart --all part /boot --fstype ext3 --size=250 --asprimary --ondisk=cciss/c0d0 part pv.100000 --noformat --size=1 --grow --ondisk=cciss/c0d0 volgroup vg0 --pesize=32768 pv.100000 logvol swap --fstype swap --name=lv_swap --vgname=vg0 --size=4096 logvol /var/log --fstype ext3 --name=lv_log --vgname=vg0 --size=4096 logvol / --fstype ext3 --name=lv_root --vgname=vg0 --size=2048 --grow If I just take out the --ondisk will it default to the first disk? Or will I need to execute a script in the %pre section? glenn - terremark worldwide From piranzo at redhat.com Tue Oct 14 15:52:48 2008 From: piranzo at redhat.com (=?utf-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Tue, 14 Oct 2008 11:52:48 -0400 (EDT) Subject: part function In-Reply-To: <005AB96F733E674B89550DDAE730CB4A4BF556EE20@daa20725exc001.drtn.corp> Message-ID: <12618928.18611223999563348.JavaMail.iranzo@Deneb.no-ip.org> Hi Glenn ----- "Glenn Bailey" escribi?: > What's the default behvaiour for the 'part' function when --ondisk is > left out? I'm wanting to do something similar to this in my > kickstarts, > but make it available on other devices that don't have the cciss > device: If you left it empty, anaconda will put the partitions wherever it finds a right place, what I do is to use a small script to force them on first hard drive detected on the system with: %include /tmp/part-include and then a %pre script like: %pre set $(list-harddrives) let numd=$#/2 # Number harddrives d1=$1 # first device S1=$2 # first device size (and so on) echo "part /boot --fstype ext3 --size=100 --onpart=$PARTBOOT" >> /tmp/part-include echo "part pv.100000 --size=1 --grow --onpart=$PARTVOL" >> /tmp/part-include echo "volgroup vg0 --pesize=32768 pv.100000" >> /tmp/part-include and the rest of rour logvols. Regards Pablo > > clearpart --all > part /boot --fstype ext3 --size=250 --asprimary --ondisk=cciss/c0d0 > part pv.100000 --noformat --size=1 --grow --ondisk=cciss/c0d0 > volgroup vg0 --pesize=32768 pv.100000 > logvol swap --fstype swap --name=lv_swap --vgname=vg0 --size=4096 > logvol /var/log --fstype ext3 --name=lv_log --vgname=vg0 --size=4096 > logvol / --fstype ext3 --name=lv_root --vgname=vg0 --size=2048 --grow > > If I just take out the --ondisk will it default to the first disk? Or > will I need to execute a script in the %pre section? > > glenn - terremark worldwide > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain From rob at lazzurs.net Tue Oct 14 15:51:53 2008 From: rob at lazzurs.net (Robert Lazzurs) Date: Tue, 14 Oct 2008 16:51:53 +0100 Subject: Install that previously worked now failing Message-ID: <1220a920810140851r44459ea8k1a95d220b03ed474@mail.gmail.com> Hello, I have an install here that I did have previously working with this hardware and mirror setup however that is now failing for some unknown reason. Below is the trace I got back from anaconda, if anyone has any ideas please let me know :) 15:01:55 INFO : Running kickstart %%traceback script(s) 15:01:55 INFO : All kickstart %%traceback script(s) have been run 15:01:55 CRITICAL: Traceback (most recent call first): File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, in comparePoEVR (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, in __eq__ if comparePoEVR(self, other) == 0 and self.arch == other.arch and self.name == other.name: File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in resolveVersions elif sameName == None: File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in installAllKmods rAvaModules = resolveVersions(avaModules) File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in postresolve_hook newKernels + installedKernels) File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, in run func(conduitcls(self, self.base, conf, **kwargs)) File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, in buildTransaction self.plugins.run('postresolve', rescode=rescode, restring=restring) File "/usr/lib/anaconda/yuminstall.py", line 1267, in doPostSelection (code, msgs) = self.ayum.buildTransaction() File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection return anaconda.backend.doPostSelection(anaconda) File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext self.moveStep() File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep self.gotoNext() File "/usr/lib/anaconda/text.py", line 539, in run (step, instance) = anaconda.dispatch.currentStep() File "/usr/bin/anaconda", line 982, in ? anaconda.intf.run(anaconda) AttributeError: 'NoneType' object has no attribute 'epoch' Thanks again :) From rob at lazzurs.net Tue Oct 14 15:55:38 2008 From: rob at lazzurs.net (Robert Lazzurs) Date: Tue, 14 Oct 2008 16:55:38 +0100 Subject: Install that previously worked now failing In-Reply-To: <1220a920810140851r44459ea8k1a95d220b03ed474@mail.gmail.com> References: <1220a920810140851r44459ea8k1a95d220b03ed474@mail.gmail.com> Message-ID: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs wrote: > Hello, > > I have an install here that I did have previously working with this > hardware and mirror setup however that is now failing for some unknown > reason. Below is the trace I got back from anaconda, if anyone has > any ideas please let me know :) > > 15:01:55 INFO : Running kickstart %%traceback script(s) > 15:01:55 INFO : All kickstart %%traceback script(s) have been run > 15:01:55 CRITICAL: Traceback (most recent call first): > File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, in > comparePoEVR > (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) > File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, in __eq__ > if comparePoEVR(self, other) == 0 and self.arch == other.arch and > self.name == other.name: > File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in resolveVersions > elif sameName == None: > File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in installAllKmods > rAvaModules = resolveVersions(avaModules) > File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in postresolve_hook > newKernels + installedKernels) > File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, in run > func(conduitcls(self, self.base, conf, **kwargs)) > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, > in buildTransaction > self.plugins.run('postresolve', rescode=rescode, restring=restring) > File "/usr/lib/anaconda/yuminstall.py", line 1267, in doPostSelection > (code, msgs) = self.ayum.buildTransaction() > File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection > return anaconda.backend.doPostSelection(anaconda) > File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep > rc = stepFunc(self.anaconda) > File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext > self.moveStep() > File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep > self.gotoNext() > File "/usr/lib/anaconda/text.py", line 539, in run > (step, instance) = anaconda.dispatch.currentStep() > File "/usr/bin/anaconda", line 982, in ? > anaconda.intf.run(anaconda) > AttributeError: 'NoneType' object has no attribute 'epoch' > > > Thanks again :) Sorry for replying to my own post however I figured that I should include more information This is an install with a fairly standard kickstart file (that has not changed) being generated from Cobbler. Cobbler has just had the RHEL 5.1 dvd reimported into it and this kickstart template tested with the new import and this also fails, where it had previously worked The install is on to a Dell PowerEdge 1950 III. If anyone requires any more information about this please let me know, if I find a solution I will post back to the list. Take care. From piranzo at redhat.com Tue Oct 14 15:59:13 2008 From: piranzo at redhat.com (=?utf-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Tue, 14 Oct 2008 11:59:13 -0400 (EDT) Subject: Install that previously worked now failing In-Reply-To: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> Message-ID: <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> Can you post your cobbler rendered kickstart to have a look on it? Regards Pablo ----- "Robert Lazzurs" escribi?: > On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs > wrote: > > Hello, > > > > I have an install here that I did have previously working with this > > hardware and mirror setup however that is now failing for some > unknown > > reason. Below is the trace I got back from anaconda, if anyone has > > any ideas please let me know :) > > > > 15:01:55 INFO : Running kickstart %%traceback script(s) > > 15:01:55 INFO : All kickstart %%traceback script(s) have been > run > > 15:01:55 CRITICAL: Traceback (most recent call first): > > File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, > in > > comparePoEVR > > (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) > > File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, > in __eq__ > > if comparePoEVR(self, other) == 0 and self.arch == other.arch > and > > self.name == other.name: > > File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in > resolveVersions > > elif sameName == None: > > File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in > installAllKmods > > rAvaModules = resolveVersions(avaModules) > > File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in > postresolve_hook > > newKernels + installedKernels) > > File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, > in run > > func(conduitcls(self, self.base, conf, **kwargs)) > > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, > > in buildTransaction > > self.plugins.run('postresolve', rescode=rescode, > restring=restring) > > File "/usr/lib/anaconda/yuminstall.py", line 1267, in > doPostSelection > > (code, msgs) = self.ayum.buildTransaction() > > File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection > > return anaconda.backend.doPostSelection(anaconda) > > File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep > > rc = stepFunc(self.anaconda) > > File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext > > self.moveStep() > > File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep > > self.gotoNext() > > File "/usr/lib/anaconda/text.py", line 539, in run > > (step, instance) = anaconda.dispatch.currentStep() > > File "/usr/bin/anaconda", line 982, in ? > > anaconda.intf.run(anaconda) > > AttributeError: 'NoneType' object has no attribute 'epoch' > > > > > > Thanks again :) > > Sorry for replying to my own post however I figured that I should > include more information > > This is an install with a fairly standard kickstart file (that has > not > changed) being generated from Cobbler. Cobbler has just had the RHEL > 5.1 dvd reimported into it and this kickstart template tested with > the > new import and this also fails, where it had previously worked > > The install is on to a Dell PowerEdge 1950 III. > > If anyone requires any more information about this please let me > know, > if I find a solution I will post back to the list. > > Take care. > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain From gbailey at terremark.com Tue Oct 14 16:02:28 2008 From: gbailey at terremark.com (Glenn Bailey) Date: Tue, 14 Oct 2008 11:02:28 -0500 Subject: part function In-Reply-To: <12618928.18611223999563348.JavaMail.iranzo@Deneb.no-ip.org> References: <005AB96F733E674B89550DDAE730CB4A4BF556EE20@daa20725exc001.drtn.corp> <12618928.18611223999563348.JavaMail.iranzo@Deneb.no-ip.org> Message-ID: <005AB96F733E674B89550DDAE730CB4A4BF556EE28@daa20725exc001.drtn.corp> > If you left it empty, anaconda will put the partitions > wherever it finds a right place, what I do is to use a small > script to force them on first hard drive detected on the system with: That helps, thnx! glenn - terremark From rob at lazzurs.net Wed Oct 15 11:49:07 2008 From: rob at lazzurs.net (Robert Lazzurs) Date: Wed, 15 Oct 2008 12:49:07 +0100 Subject: Install that previously worked now failing In-Reply-To: <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> References: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> Message-ID: <1220a920810150449p254c8d1idc5af537b02b0150@mail.gmail.com> Hello, of course, it is an attachment to this email. Thanks again. On Tue, Oct 14, 2008 at 16:59, Pablo Iranzo G?mez wrote: > Can you post your cobbler rendered kickstart to have a look on it? > > Regards > Pablo > > > ----- "Robert Lazzurs" escribi?: > >> On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs >> wrote: >> > Hello, >> > >> > I have an install here that I did have previously working with this >> > hardware and mirror setup however that is now failing for some >> unknown >> > reason. Below is the trace I got back from anaconda, if anyone has >> > any ideas please let me know :) >> > >> > 15:01:55 INFO : Running kickstart %%traceback script(s) >> > 15:01:55 INFO : All kickstart %%traceback script(s) have been >> run >> > 15:01:55 CRITICAL: Traceback (most recent call first): >> > File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, >> in >> > comparePoEVR >> > (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) >> > File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, >> in __eq__ >> > if comparePoEVR(self, other) == 0 and self.arch == other.arch >> and >> > self.name == other.name: >> > File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in >> resolveVersions >> > elif sameName == None: >> > File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in >> installAllKmods >> > rAvaModules = resolveVersions(avaModules) >> > File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in >> postresolve_hook >> > newKernels + installedKernels) >> > File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, >> in run >> > func(conduitcls(self, self.base, conf, **kwargs)) >> > File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, >> > in buildTransaction >> > self.plugins.run('postresolve', rescode=rescode, >> restring=restring) >> > File "/usr/lib/anaconda/yuminstall.py", line 1267, in >> doPostSelection >> > (code, msgs) = self.ayum.buildTransaction() >> > File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection >> > return anaconda.backend.doPostSelection(anaconda) >> > File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep >> > rc = stepFunc(self.anaconda) >> > File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext >> > self.moveStep() >> > File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep >> > self.gotoNext() >> > File "/usr/lib/anaconda/text.py", line 539, in run >> > (step, instance) = anaconda.dispatch.currentStep() >> > File "/usr/bin/anaconda", line 982, in ? >> > anaconda.intf.run(anaconda) >> > AttributeError: 'NoneType' object has no attribute 'epoch' >> > >> > >> > Thanks again :) >> >> Sorry for replying to my own post however I figured that I should >> include more information >> >> This is an install with a fairly standard kickstart file (that has >> not >> changed) being generated from Cobbler. Cobbler has just had the RHEL >> 5.1 dvd reimported into it and this kickstart template tested with >> the >> new import and this also fails, where it had previously worked >> >> The install is on to a Dell PowerEdge 1950 III. >> >> If anyone requires any more information about this please let me >> know, >> if I find a solution I will post back to the list. >> >> Take care. >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > -- > Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) > RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain > Phone: +34 645 01 01 49 (CET/CEST) > GnuPG KeyID: 0xFAD3CF0D > > -- > Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 > Directores: Michael Cunningham, Charlie Peters y David Owens > Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a > Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- A non-text attachment was scrubbed... Name: marble3 Type: application/octet-stream Size: 3512 bytes Desc: not available URL: From mdehaan at redhat.com Wed Oct 15 14:57:58 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 15 Oct 2008 10:57:58 -0400 Subject: Install that previously worked now failing In-Reply-To: <1220a920810150449p254c8d1idc5af537b02b0150@mail.gmail.com> References: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> <1220a920810150449p254c8d1idc5af537b02b0150@mail.gmail.com> Message-ID: <48F604F6.7070504@redhat.com> Robert Lazzurs wrote: > Hello, of course, it is an attachment to this email. > > Thanks again. > > On Tue, Oct 14, 2008 at 16:59, Pablo Iranzo G?mez wrote: > >> Can you post your cobbler rendered kickstart to have a look on it? >> >> Regards >> Pablo >> >> >> ----- "Robert Lazzurs" escribi?: >> >> >>> On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs >>> wrote: >>> >>>> Hello, >>>> >>>> I have an install here that I did have previously working with this >>>> hardware and mirror setup however that is now failing for some >>>> >>> unknown >>> >>>> reason. Below is the trace I got back from anaconda, if anyone has >>>> any ideas please let me know :) >>>> >>>> 15:01:55 INFO : Running kickstart %%traceback script(s) >>>> 15:01:55 INFO : All kickstart %%traceback script(s) have been >>>> >>> run >>> >>>> 15:01:55 CRITICAL: Traceback (most recent call first): >>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, >>>> >>> in >>> >>>> comparePoEVR >>>> (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) >>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, >>>> >>> in __eq__ >>> >>>> if comparePoEVR(self, other) == 0 and self.arch == other.arch >>>> >>> and >>> >>>> self.name == other.name: >>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in >>>> >>> resolveVersions >>> >>>> elif sameName == None: >>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in >>>> >>> installAllKmods >>> >>>> rAvaModules = resolveVersions(avaModules) >>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in >>>> >>> postresolve_hook >>> >>>> newKernels + installedKernels) >>>> File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, >>>> >>> in run >>> >>>> func(conduitcls(self, self.base, conf, **kwargs)) >>>> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, >>>> in buildTransaction >>>> self.plugins.run('postresolve', rescode=rescode, >>>> >>> restring=restring) >>> >>>> File "/usr/lib/anaconda/yuminstall.py", line 1267, in >>>> >>> doPostSelection >>> >>>> (code, msgs) = self.ayum.buildTransaction() >>>> File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection >>>> return anaconda.backend.doPostSelection(anaconda) >>>> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep >>>> rc = stepFunc(self.anaconda) >>>> File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext >>>> self.moveStep() >>>> File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep >>>> self.gotoNext() >>>> File "/usr/lib/anaconda/text.py", line 539, in run >>>> (step, instance) = anaconda.dispatch.currentStep() >>>> File "/usr/bin/anaconda", line 982, in ? >>>> anaconda.intf.run(anaconda) >>>> AttributeError: 'NoneType' object has no attribute 'epoch' >>>> >>>> >>>> Thanks again :) >>>> >>> Sorry for replying to my own post however I figured that I should >>> include more information >>> >>> This is an install with a fairly standard kickstart file (that has >>> not >>> changed) being generated from Cobbler. Cobbler has just had the RHEL >>> 5.1 dvd reimported into it and this kickstart template tested with >>> the >>> new import and this also fails, where it had previously worked >>> >>> The install is on to a Dell PowerEdge 1950 III. >>> >>> If anyone requires any more information about this please let me >>> know, >>> if I find a solution I will post back to the list. >>> >>> Take care. >>> >>> _______________________________________________ >>> Kickstart-list mailing list >>> Kickstart-list at redhat.com >>> https://www.redhat.com/mailman/listinfo/kickstart-list >>> >> -- >> Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) >> RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain >> Phone: +34 645 01 01 49 (CET/CEST) >> GnuPG KeyID: 0xFAD3CF0D >> >> -- >> Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 >> Directores: Michael Cunningham, Charlie Peters y David Owens >> Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a >> Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain >> >> >> _______________________________________________ >> 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 Cobbler runs through a copy of the DVD tree and identifies the varies "split" repos and runs createrepo on them. Having duplicates in the file shouldn't itself be a problem for yum, the theory was that createrepo might have munged the repo, but seeing this was an Anaconda traceback I was hoping someone might have better insight as to how a "None" could get in there. --Michael From rob at lazzurs.net Wed Oct 15 15:15:50 2008 From: rob at lazzurs.net (Robert Lazzurs) Date: Wed, 15 Oct 2008 16:15:50 +0100 Subject: Install that previously worked now failing In-Reply-To: <48F604F6.7070504@redhat.com> References: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> <1220a920810150449p254c8d1idc5af537b02b0150@mail.gmail.com> <48F604F6.7070504@redhat.com> Message-ID: <1220a920810150815mf8a1d81w5dde1476f407d068@mail.gmail.com> On Wed, Oct 15, 2008 at 15:57, Michael DeHaan wrote: > Robert Lazzurs wrote: >> >> Hello, of course, it is an attachment to this email. >> >> Thanks again. >> >> On Tue, Oct 14, 2008 at 16:59, Pablo Iranzo G?mez >> wrote: >> >>> >>> Can you post your cobbler rendered kickstart to have a look on it? >>> >>> Regards >>> Pablo >>> >>> >>> ----- "Robert Lazzurs" escribi?: >>> >>> >>>> >>>> On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs >>>> wrote: >>>> >>>>> >>>>> Hello, >>>>> >>>>> I have an install here that I did have previously working with this >>>>> hardware and mirror setup however that is now failing for some >>>>> >>>> >>>> unknown >>>> >>>>> >>>>> reason. Below is the trace I got back from anaconda, if anyone has >>>>> any ideas please let me know :) >>>>> >>>>> 15:01:55 INFO : Running kickstart %%traceback script(s) >>>>> 15:01:55 INFO : All kickstart %%traceback script(s) have been >>>>> >>>> >>>> run >>>> >>>>> >>>>> 15:01:55 CRITICAL: Traceback (most recent call first): >>>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, >>>>> >>>> >>>> in >>>> >>>>> >>>>> comparePoEVR >>>>> (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) >>>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, >>>>> >>>> >>>> in __eq__ >>>> >>>>> >>>>> if comparePoEVR(self, other) == 0 and self.arch == other.arch >>>>> >>>> >>>> and >>>> >>>>> >>>>> self.name == other.name: >>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in >>>>> >>>> >>>> resolveVersions >>>> >>>>> >>>>> elif sameName == None: >>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in >>>>> >>>> >>>> installAllKmods >>>> >>>>> >>>>> rAvaModules = resolveVersions(avaModules) >>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in >>>>> >>>> >>>> postresolve_hook >>>> >>>>> >>>>> newKernels + installedKernels) >>>>> File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, >>>>> >>>> >>>> in run >>>> >>>>> >>>>> func(conduitcls(self, self.base, conf, **kwargs)) >>>>> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, >>>>> in buildTransaction >>>>> self.plugins.run('postresolve', rescode=rescode, >>>>> >>>> >>>> restring=restring) >>>> >>>>> >>>>> File "/usr/lib/anaconda/yuminstall.py", line 1267, in >>>>> >>>> >>>> doPostSelection >>>> >>>>> >>>>> (code, msgs) = self.ayum.buildTransaction() >>>>> File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection >>>>> return anaconda.backend.doPostSelection(anaconda) >>>>> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep >>>>> rc = stepFunc(self.anaconda) >>>>> File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext >>>>> self.moveStep() >>>>> File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep >>>>> self.gotoNext() >>>>> File "/usr/lib/anaconda/text.py", line 539, in run >>>>> (step, instance) = anaconda.dispatch.currentStep() >>>>> File "/usr/bin/anaconda", line 982, in ? >>>>> anaconda.intf.run(anaconda) >>>>> AttributeError: 'NoneType' object has no attribute 'epoch' >>>>> >>>>> >>>>> Thanks again :) >>>>> >>>> >>>> Sorry for replying to my own post however I figured that I should >>>> include more information >>>> >>>> This is an install with a fairly standard kickstart file (that has >>>> not >>>> changed) being generated from Cobbler. Cobbler has just had the RHEL >>>> 5.1 dvd reimported into it and this kickstart template tested with >>>> the >>>> new import and this also fails, where it had previously worked >>>> >>>> The install is on to a Dell PowerEdge 1950 III. >>>> >>>> If anyone requires any more information about this please let me >>>> know, >>>> if I find a solution I will post back to the list. >>>> >>>> Take care. > > Cobbler runs through a copy of the DVD tree and identifies the varies > "split" repos and runs createrepo on them. > > Having duplicates in the file shouldn't itself be a problem for yum, the > theory was that createrepo might have munged the repo, but seeing this was > an Anaconda traceback I was hoping someone might have better insight as to > how a "None" could get in there. Hello everyone, As discussed with Michael on IRC we have found the issue to be with the duplicate repo lines. My kickstart template for cobbler currently has the following line $yum_repo_stanza Which was producing this repo --name=source-1 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/VT repo --name=source-2 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/ClusterStorage repo --name=source-3 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/Cluster repo --name=source-4 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/Server repo --name=source-5 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/VT repo --name=source-6 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/ClusterStorage repo --name=source-7 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/Cluster repo --name=source-8 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/Server So due to the duplication above anaconda was failing and producing the traceback in the original email. Removing the duplicates and manually adding this to the kickstart fixed the issue. repo --name=source-1 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/VT repo --name=source-2 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/ClusterStorage repo --name=source-3 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/Cluster repo --name=source-4 --baseurl=http://10.107.1.111/cobbler/ks_mirror/redhat-5.1-x86_64/Server I hope this post helps anyone with a similar issue. Thanks again for the help everyone, take care. From rob at lazzurs.net Wed Oct 15 15:21:44 2008 From: rob at lazzurs.net (Robert Lazzurs) Date: Wed, 15 Oct 2008 16:21:44 +0100 Subject: Install that previously worked now failing In-Reply-To: <1220a920810150815mf8a1d81w5dde1476f407d068@mail.gmail.com> References: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> <1220a920810150449p254c8d1idc5af537b02b0150@mail.gmail.com> <48F604F6.7070504@redhat.com> <1220a920810150815mf8a1d81w5dde1476f407d068@mail.gmail.com> Message-ID: <1220a920810150821x4ffedeedn2c25e432e45de673@mail.gmail.com> On Wed, Oct 15, 2008 at 16:15, Robert Lazzurs wrote: > On Wed, Oct 15, 2008 at 15:57, Michael DeHaan wrote: >> Robert Lazzurs wrote: >>> >>> Hello, of course, it is an attachment to this email. >>> >>> Thanks again. >>> >>> On Tue, Oct 14, 2008 at 16:59, Pablo Iranzo G?mez >>> wrote: >>> >>>> >>>> Can you post your cobbler rendered kickstart to have a look on it? >>>> >>>> Regards >>>> Pablo >>>> >>>> >>>> ----- "Robert Lazzurs" escribi?: >>>> >>>> >>>>> >>>>> On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs >>>>> wrote: >>>>> >>>>>> >>>>>> Hello, >>>>>> >>>>>> I have an install here that I did have previously working with this >>>>>> hardware and mirror setup however that is now failing for some >>>>>> >>>>> >>>>> unknown >>>>> >>>>>> >>>>>> reason. Below is the trace I got back from anaconda, if anyone has >>>>>> any ideas please let me know :) >>>>>> >>>>>> 15:01:55 INFO : Running kickstart %%traceback script(s) >>>>>> 15:01:55 INFO : All kickstart %%traceback script(s) have been >>>>>> >>>>> >>>>> run >>>>> >>>>>> >>>>>> 15:01:55 CRITICAL: Traceback (most recent call first): >>>>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, >>>>>> >>>>> >>>>> in >>>>> >>>>>> >>>>>> comparePoEVR >>>>>> (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) >>>>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, >>>>>> >>>>> >>>>> in __eq__ >>>>> >>>>>> >>>>>> if comparePoEVR(self, other) == 0 and self.arch == other.arch >>>>>> >>>>> >>>>> and >>>>> >>>>>> >>>>>> self.name == other.name: >>>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in >>>>>> >>>>> >>>>> resolveVersions >>>>> >>>>>> >>>>>> elif sameName == None: >>>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in >>>>>> >>>>> >>>>> installAllKmods >>>>> >>>>>> >>>>>> rAvaModules = resolveVersions(avaModules) >>>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in >>>>>> >>>>> >>>>> postresolve_hook >>>>> >>>>>> >>>>>> newKernels + installedKernels) >>>>>> File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, >>>>>> >>>>> >>>>> in run >>>>> >>>>>> >>>>>> func(conduitcls(self, self.base, conf, **kwargs)) >>>>>> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, >>>>>> in buildTransaction >>>>>> self.plugins.run('postresolve', rescode=rescode, >>>>>> >>>>> >>>>> restring=restring) >>>>> >>>>>> >>>>>> File "/usr/lib/anaconda/yuminstall.py", line 1267, in >>>>>> >>>>> >>>>> doPostSelection >>>>> >>>>>> >>>>>> (code, msgs) = self.ayum.buildTransaction() >>>>>> File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection >>>>>> return anaconda.backend.doPostSelection(anaconda) >>>>>> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep >>>>>> rc = stepFunc(self.anaconda) >>>>>> File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext >>>>>> self.moveStep() >>>>>> File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep >>>>>> self.gotoNext() >>>>>> File "/usr/lib/anaconda/text.py", line 539, in run >>>>>> (step, instance) = anaconda.dispatch.currentStep() >>>>>> File "/usr/bin/anaconda", line 982, in ? >>>>>> anaconda.intf.run(anaconda) >>>>>> AttributeError: 'NoneType' object has no attribute 'epoch' >>>>>> >>>>>> >>>>>> Thanks again :) >>>>>> >>>>> >>>>> Sorry for replying to my own post however I figured that I should >>>>> include more information >>>>> >>>>> This is an install with a fairly standard kickstart file (that has >>>>> not >>>>> changed) being generated from Cobbler. Cobbler has just had the RHEL >>>>> 5.1 dvd reimported into it and this kickstart template tested with >>>>> the >>>>> new import and this also fails, where it had previously worked >>>>> >>>>> The install is on to a Dell PowerEdge 1950 III. >>>>> >>>>> If anyone requires any more information about this please let me >>>>> know, >>>>> if I find a solution I will post back to the list. >>>>> >>>>> Take care. >> >> Cobbler runs through a copy of the DVD tree and identifies the varies >> "split" repos and runs createrepo on them. >> >> Having duplicates in the file shouldn't itself be a problem for yum, the >> theory was that createrepo might have munged the repo, but seeing this was >> an Anaconda traceback I was hoping someone might have better insight as to >> how a "None" could get in there. > > Hello everyone, > > As discussed with Michael on IRC we have found the issue to be with > the duplicate repo lines. My kickstart template for cobbler currently > has the following line Hello, Michael has confirmed that this is caused by a bug in cobbler that will be fixed soon. Anyone who is having this issue should watch the cobbler mailing list for a patch coming soon. Take care. From mdehaan at redhat.com Wed Oct 15 15:52:40 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 15 Oct 2008 11:52:40 -0400 Subject: Install that previously worked now failing In-Reply-To: <1220a920810150821x4ffedeedn2c25e432e45de673@mail.gmail.com> References: <1220a920810140855n19f9af3fm32e55a27d9580f19@mail.gmail.com> <17689996.18811223999950138.JavaMail.iranzo@Deneb.no-ip.org> <1220a920810150449p254c8d1idc5af537b02b0150@mail.gmail.com> <48F604F6.7070504@redhat.com> <1220a920810150815mf8a1d81w5dde1476f407d068@mail.gmail.com> <1220a920810150821x4ffedeedn2c25e432e45de673@mail.gmail.com> Message-ID: <48F611C8.10008@redhat.com> Robert Lazzurs wrote: > On Wed, Oct 15, 2008 at 16:15, Robert Lazzurs wrote: > >> On Wed, Oct 15, 2008 at 15:57, Michael DeHaan wrote: >> >>> Robert Lazzurs wrote: >>> >>>> Hello, of course, it is an attachment to this email. >>>> >>>> Thanks again. >>>> >>>> On Tue, Oct 14, 2008 at 16:59, Pablo Iranzo G?mez >>>> wrote: >>>> >>>> >>>>> Can you post your cobbler rendered kickstart to have a look on it? >>>>> >>>>> Regards >>>>> Pablo >>>>> >>>>> >>>>> ----- "Robert Lazzurs" escribi?: >>>>> >>>>> >>>>> >>>>>> On Tue, Oct 14, 2008 at 16:51, Robert Lazzurs >>>>>> wrote: >>>>>> >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I have an install here that I did have previously working with this >>>>>>> hardware and mirror setup however that is now failing for some >>>>>>> >>>>>>> >>>>>> unknown >>>>>> >>>>>> >>>>>>> reason. Below is the trace I got back from anaconda, if anyone has >>>>>>> any ideas please let me know :) >>>>>>> >>>>>>> 15:01:55 INFO : Running kickstart %%traceback script(s) >>>>>>> 15:01:55 INFO : All kickstart %%traceback script(s) have been >>>>>>> >>>>>>> >>>>>> run >>>>>> >>>>>> >>>>>>> 15:01:55 CRITICAL: Traceback (most recent call first): >>>>>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 35, >>>>>>> >>>>>>> >>>>>> in >>>>>> >>>>>> >>>>>>> comparePoEVR >>>>>>> (e2, v2, r2) = (po2.epoch, po2.ver, po2.rel) >>>>>>> File "/usr/lib/python2.4/site-packages/yum/packages.py", line 191, >>>>>>> >>>>>>> >>>>>> in __eq__ >>>>>> >>>>>> >>>>>>> if comparePoEVR(self, other) == 0 and self.arch == other.arch >>>>>>> >>>>>>> >>>>>> and >>>>>> >>>>>> >>>>>>> self.name == other.name: >>>>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 151, in >>>>>>> >>>>>>> >>>>>> resolveVersions >>>>>> >>>>>> >>>>>>> elif sameName == None: >>>>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 222, in >>>>>>> >>>>>>> >>>>>> installAllKmods >>>>>> >>>>>> >>>>>>> rAvaModules = resolveVersions(avaModules) >>>>>>> File "/usr/lib/yum-plugins/fedorakmod.py", line 276, in >>>>>>> >>>>>>> >>>>>> postresolve_hook >>>>>> >>>>>> >>>>>>> newKernels + installedKernels) >>>>>>> File "/usr/lib/python2.4/site-packages/yum/plugins.py", line 153, >>>>>>> >>>>>>> >>>>>> in run >>>>>> >>>>>> >>>>>>> func(conduitcls(self, self.base, conf, **kwargs)) >>>>>>> File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 442, >>>>>>> in buildTransaction >>>>>>> self.plugins.run('postresolve', rescode=rescode, >>>>>>> >>>>>>> >>>>>> restring=restring) >>>>>> >>>>>> >>>>>>> File "/usr/lib/anaconda/yuminstall.py", line 1267, in >>>>>>> >>>>>>> >>>>>> doPostSelection >>>>>> >>>>>> >>>>>>> (code, msgs) = self.ayum.buildTransaction() >>>>>>> File "/usr/lib/anaconda/backend.py", line 177, in doPostSelection >>>>>>> return anaconda.backend.doPostSelection(anaconda) >>>>>>> File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep >>>>>>> rc = stepFunc(self.anaconda) >>>>>>> File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext >>>>>>> self.moveStep() >>>>>>> File "/usr/lib/anaconda/dispatch.py", line 223, in currentStep >>>>>>> self.gotoNext() >>>>>>> File "/usr/lib/anaconda/text.py", line 539, in run >>>>>>> (step, instance) = anaconda.dispatch.currentStep() >>>>>>> File "/usr/bin/anaconda", line 982, in ? >>>>>>> anaconda.intf.run(anaconda) >>>>>>> AttributeError: 'NoneType' object has no attribute 'epoch' >>>>>>> >>>>>>> >>>>>>> Thanks again :) >>>>>>> >>>>>>> >>>>>> Sorry for replying to my own post however I figured that I should >>>>>> include more information >>>>>> >>>>>> This is an install with a fairly standard kickstart file (that has >>>>>> not >>>>>> changed) being generated from Cobbler. Cobbler has just had the RHEL >>>>>> 5.1 dvd reimported into it and this kickstart template tested with >>>>>> the >>>>>> new import and this also fails, where it had previously worked >>>>>> >>>>>> The install is on to a Dell PowerEdge 1950 III. >>>>>> >>>>>> If anyone requires any more information about this please let me >>>>>> know, >>>>>> if I find a solution I will post back to the list. >>>>>> >>>>>> Take care. >>>>>> >>> Cobbler runs through a copy of the DVD tree and identifies the varies >>> "split" repos and runs createrepo on them. >>> >>> Having duplicates in the file shouldn't itself be a problem for yum, the >>> theory was that createrepo might have munged the repo, but seeing this was >>> an Anaconda traceback I was hoping someone might have better insight as to >>> how a "None" could get in there. >>> >> Hello everyone, >> >> As discussed with Michael on IRC we have found the issue to be with >> the duplicate repo lines. My kickstart template for cobbler currently >> has the following line >> > > > > Hello, > > Michael has confirmed that this is caused by a bug in cobbler that > will be fixed soon. Anyone who is having this issue should watch the > cobbler mailing list for a patch coming soon. > > Take care. > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > Right, the theory is that multiple repo definitions to the same URL /do/ break Anaconda in certain situations, so we're going to add some basic checks to make sure that doesn't happen. --Michael From muksyed at stanford.edu Thu Oct 16 20:28:57 2008 From: muksyed at stanford.edu (Mukarram Syed) Date: Thu, 16 Oct 2008 13:28:57 -0700 Subject: Suggestions for a better kickstart infrastructure Message-ID: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> Hi We would like to upgrade our Kickstart infrastructure to make it better and I am looking for some suggestions. What we have is a menu based Kickstart infrastructure on running Oracle Enterprise Linux 4 (EL4), where you have the boot.msg file and the corresponding default file all installed from the system-config-netboot rpm. Then I have the tftp server, the webserver serving the ks.cfg files, RPM's etc. And then I have the post install script that run in the %post section of the ks.cfg file which mounts the NFS partitions where I have all my post-install scripts and files. We have been using this Kickstart infrastructure for about a year and a half now and it's been serving our purpose, but the menus have become a lot larger than it was and now when I pxeboot the client the menu scrolls off the screen and there is no way to do a page-up/page-down to see what's on top/bottom. We have tried to trim down the menu but now since our infrastructure has gotten a lot larger it's difficult. Then when we want to have both EL4 and EL5 it would be difficult as well. I have heard of "cobbler" but I would like some suggestions as to which is the best alternative to this menu based Kickstart that I am using here. Also this Kickstart infrastructure that I have here seems to be a basic one and we are ready to explore some advanced methods of Kickstarting our servers Any suggestions would be appreciated. Thanks # mukarram -------------- next part -------------- An HTML attachment was scrubbed... URL: From bjs at redhat.com Thu Oct 16 20:41:12 2008 From: bjs at redhat.com (Bryan J Smith) Date: Thu, 16 Oct 2008 16:41:12 -0400 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> Message-ID: <1224189673.10074.44.camel@localhost.localdomain> On Thu, 2008-10-16 at 13:28 -0700, Mukarram Syed wrote: > We have been using this Kickstart infrastructure for about a year and > a half now and it?s been serving our purpose, but the menus have > become a lot larger than it was and now when I pxeboot the client the > menu scrolls off the screen and there is no way to do a > page-up/page-down to see what?s on top/bottom. This is clearly a PXELinux configuration detail, not so much a Kickstart one. Is there any reason why you're not using it's option for nested menus? PXELinux has had that option for a long time, and some of the latest versions improve it much better. > We have tried to trim down the menu but now since our infrastructure > has gotten a lot larger it?s difficult. Then when we want to have > both EL4 and EL5 it would be difficult as well. Again, is there any reason you can't use nested menus in PXELinux? You can put your EL4 entries in one file, EL5 in another, utilities in yet another, etc... and have the "default" be the top menu that goes into each. Again, this has little to do with Kickstart, and more to do with PXELinux -- or whatever tool you're using to set it up. I've even used nexted PXELinux menus for Solaris Jumpstart and Windows PE as well. > I have heard of ?cobbler? but I would like some suggestions as to > which is the best alternative to this menu based Kickstart that I am > using here. Cobbler (including Koan) is an advanced provisioning tool. If you're building an infrastructure, it's basically the bomb (i.e., learn it). It's one of Red Hat's emerging technologies. > Also this Kickstart infrastructure that I have here seems to be a > basic one and we are ready to explore some advanced methods of > Kickstarting our servers Specifics? Red Hat has many emerging technologies (ET). Cobbler/Koan for provisioning, Puppet for configuration management, etc... If you're building an infrastructure, it's very useful to do so. -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From masaiah.p at gmail.com Fri Oct 17 04:25:28 2008 From: masaiah.p at gmail.com (masaiah kannan) Date: Fri, 17 Oct 2008 09:55:28 +0530 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> Message-ID: <55d950a10810162125j5d6124ady6fba656168a8720e@mail.gmail.com> Hi, i want create Kickstart DVD give me instructions from the top to bottom. i do not have any experiance on this please do the need full. Regards, Masaiah. On 10/17/08, Mukarram Syed wrote: > > Hi > > We would like to upgrade our Kickstart infrastructure to make it better and > I am looking for some suggestions. > > > > What we have is a menu based Kickstart infrastructure on running Oracle > Enterprise Linux 4 (EL4), where you have the boot.msg file and the > corresponding default file all installed from the system-config-netboot > rpm. Then I have the tftp server, the webserver serving the ks.cfg files, > RPM's etc. > > And then I have the post install script that run in the %post section of > the ks.cfg file which mounts the NFS partitions where I have all my > post-install scripts and files. > > > > We have been using this Kickstart infrastructure for about a year and a > half now and it's been serving our purpose, but the menus have become a lot > larger than it was and now when I pxeboot the client the menu scrolls off > the screen and there is no way to do a page-up/page-down to see what's on > top/bottom. > > We have tried to trim down the menu but now since our infrastructure has > gotten a lot larger it's difficult. Then when we want to have both EL4 and > EL5 it would be difficult as well. > > > > I have heard of "cobbler" but I would like some suggestions as to which is > the best alternative to this menu based Kickstart that I am using here. > > Also this Kickstart infrastructure that I have here seems to be a basic one > and we are ready to explore some advanced methods of Kickstarting our > servers > > > > Any suggestions would be appreciated. > > > > Thanks > > > > # mukarram > > > > _______________________________________________ > 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 debian at herakles.homelinux.org Fri Oct 17 07:32:34 2008 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 17 Oct 2008 15:32:34 +0800 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <55d950a10810162125j5d6124ady6fba656168a8720e@mail.gmail.com> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <55d950a10810162125j5d6124ady6fba656168a8720e@mail.gmail.com> Message-ID: <48F83F92.8050806@herakles.homelinux.org> masaiah kannan wrote: > Hi, > > i want create Kickstart DVD give me instructions from the top to > bottom. > i do not have any experiance on this please do the need full. > Really! You've made no effort to help yourself, and you want someone else to handfeed you? Every step you need is well documented, it's not hard to find. You must be joking. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From muksyed at stanford.edu Fri Oct 17 17:20:25 2008 From: muksyed at stanford.edu (Mukarram Syed) Date: Fri, 17 Oct 2008 10:20:25 -0700 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <1224189673.10074.44.camel@localhost.localdomain> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <1224189673.10074.44.camel@localhost.localdomain> Message-ID: <007101c9307c$a50bed30$f11d42ab@stanford.edu> Hi Bryan. I didn't know that you could have submenus in pxelinux. Thanks for the info. However I am more interesting in implementing Cobbler/Koan/Puppet and I am reading the docs on how to implement. Thanks much for the feedback. # mukarram -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Bryan J Smith Sent: Thursday, October 16, 2008 1:41 PM To: Discussion list about Kickstart Subject: Re: Suggestions for a better kickstart infrastructure On Thu, 2008-10-16 at 13:28 -0700, Mukarram Syed wrote: > We have been using this Kickstart infrastructure for about a year and > a half now and it's been serving our purpose, but the menus have > become a lot larger than it was and now when I pxeboot the client the > menu scrolls off the screen and there is no way to do a > page-up/page-down to see what's on top/bottom. This is clearly a PXELinux configuration detail, not so much a Kickstart one. Is there any reason why you're not using it's option for nested menus? PXELinux has had that option for a long time, and some of the latest versions improve it much better. > We have tried to trim down the menu but now since our infrastructure > has gotten a lot larger it's difficult. Then when we want to have > both EL4 and EL5 it would be difficult as well. Again, is there any reason you can't use nested menus in PXELinux? You can put your EL4 entries in one file, EL5 in another, utilities in yet another, etc... and have the "default" be the top menu that goes into each. Again, this has little to do with Kickstart, and more to do with PXELinux -- or whatever tool you're using to set it up. I've even used nexted PXELinux menus for Solaris Jumpstart and Windows PE as well. > I have heard of "cobbler" but I would like some suggestions as to > which is the best alternative to this menu based Kickstart that I am > using here. Cobbler (including Koan) is an advanced provisioning tool. If you're building an infrastructure, it's basically the bomb (i.e., learn it). It's one of Red Hat's emerging technologies. > Also this Kickstart infrastructure that I have here seems to be a > basic one and we are ready to explore some advanced methods of > Kickstarting our servers Specifics? Red Hat has many emerging technologies (ET). Cobbler/Koan for provisioning, Puppet for configuration management, etc... If you're building an infrastructure, it's very useful to do so. -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From mdehaan at redhat.com Fri Oct 17 21:48:50 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Fri, 17 Oct 2008 17:48:50 -0400 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <1224189673.10074.44.camel@localhost.localdomain> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <1224189673.10074.44.camel@localhost.localdomain> Message-ID: <48F90842.1050505@redhat.com> > Specifics? > > Red Hat has many emerging technologies (ET). Cobbler/Koan for > provisioning, Puppet for configuration management, etc... If you're > building an infrastructure, it's very useful to do so. > FYI -- Puppet is from Reductive Labs, not Red Hat. That doesn't mean it's not a good tool :) From bjs at redhat.com Fri Oct 17 22:21:56 2008 From: bjs at redhat.com (Bryan J Smith) Date: Fri, 17 Oct 2008 18:21:56 -0400 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <48F90842.1050505@redhat.com> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <1224189673.10074.44.camel@localhost.localdomain> <48F90842.1050505@redhat.com> Message-ID: <1224282116.5826.15.camel@localhost.localdomain> On Fri, 2008-10-17 at 17:48 -0400, Michael DeHaan wrote: > FYI -- Puppet is from Reductive Labs, not Red Hat. That doesn't mean > it's not a good tool :) Understood, but we list it in our ET site as a component. But thanx for properly attributing the maintainers when I did not. ;) -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From saagar.palace at gmail.com Sat Oct 18 08:27:30 2008 From: saagar.palace at gmail.com (saagar shrivastava) Date: Sat, 18 Oct 2008 13:57:30 +0530 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <1224282116.5826.15.camel@localhost.localdomain> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <1224189673.10074.44.camel@localhost.localdomain> <48F90842.1050505@redhat.com> <1224282116.5826.15.camel@localhost.localdomain> Message-ID: <106076a20810180127tb350411k69df9febaad2aabd@mail.gmail.com> Guys, My company wanted me to configure a server which can handle remote OS installation. For all the OS's we use. I've configured PXE on RHEL 5. And I'm able to Install all the Unix based OS's. OS we're using are: RHEL 3 AS RHEL 4 AS RHEL 5 Fedora Suse Windows XP Windows Server 2003 But I'm stucked with MicroSoft OS's. Can anybody help me please? Thanks, Saagar On Sat, Oct 18, 2008 at 3:51 AM, Bryan J Smith wrote: > On Fri, 2008-10-17 at 17:48 -0400, Michael DeHaan wrote: > > FYI -- Puppet is from Reductive Labs, not Red Hat. That doesn't mean > > it's not a good tool :) > > Understood, but we list it in our ET site as a component. > But thanx for properly attributing the maintainers when I did not. ;) > > > -- > Bryan J Smith - Senior Consultant - Red Hat GPS SE US > mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) > mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) > ----------------------------------------------------- > For every dollar you spend on Red Hat solutions, you > not only fund the leading community development re- > source, but you receive the #1 IT industry leader in > corporate value. http://www.redhat.com/promo/vendor/ > > > _______________________________________________ > 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 masaiah.p at gmail.com Mon Oct 20 04:38:54 2008 From: masaiah.p at gmail.com (masaiah kannan) Date: Mon, 20 Oct 2008 10:08:54 +0530 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <48F83F92.8050806@herakles.homelinux.org> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <55d950a10810162125j5d6124ady6fba656168a8720e@mail.gmail.com> <48F83F92.8050806@herakles.homelinux.org> Message-ID: <55d950a10810192138r308fd97fld6299c49a5d9282c@mail.gmail.com> john, I am not joking really i want to make a DVD help me if u can....... regards, Masaiah On 10/17/08, John Summerfield wrote: > > masaiah kannan wrote: > >> Hi, >> >> i want create start.shgive me instructions from the top to >> bottom. >> i do not have any experiance on this please do the need full. >> >> > Really! > You've made no effort to help yourself, and you want someone else to > handfeed you? > > Every step you need is well documented, it's not hard to find. > > You must be joking. > > -- > > Cheers > john > > -- spambait > 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html > http://support.microsoft.com/kb/555375 > > You cannot reply off-list:-) > > _______________________________________________ > 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 mdehaan at redhat.com Mon Oct 20 15:09:04 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Mon, 20 Oct 2008 11:09:04 -0400 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <106076a20810180127tb350411k69df9febaad2aabd@mail.gmail.com> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <1224189673.10074.44.camel@localhost.localdomain> <48F90842.1050505@redhat.com> <1224282116.5826.15.camel@localhost.localdomain> <106076a20810180127tb350411k69df9febaad2aabd@mail.gmail.com> Message-ID: <48FC9F10.7090507@redhat.com> saagar shrivastava wrote: > Guys, > > My company wanted me to configure a server which can handle remote OS > installation. For all the OS's we use. > > I've configured PXE on RHEL 5. And I'm able to Install all the Unix > based OS's. OS we're using are: > > RHEL 3 AS > RHEL 4 AS > RHEL 5 > Fedora > Suse > Windows XP > Windows Server 2003 > > But I'm stucked with MicroSoft OS's. Can anybody help me please? This isn't the list for that, unfortunately. That should be obvious from the "@redhat.com" at the end of it :) One solution is to look at virtualizing all of your Windows installations on top of Linux, using Cobbler with "cobbler image add" and koan to deploy Windows ISOs prepared with SysPrep on top of Linux KVM hosts. --Michael From bjs at redhat.com Mon Oct 20 15:42:35 2008 From: bjs at redhat.com (Bryan J Smith) Date: Mon, 20 Oct 2008 11:42:35 -0400 Subject: Suggestions for a better kickstart infrastructure In-Reply-To: <106076a20810180127tb350411k69df9febaad2aabd@mail.gmail.com> References: <000001c92fcd$d15e0210$f11d42ab@stanford.edu> <1224189673.10074.44.camel@localhost.localdomain> <48F90842.1050505@redhat.com> <1224282116.5826.15.camel@localhost.localdomain> <106076a20810180127tb350411k69df9febaad2aabd@mail.gmail.com> Message-ID: <1224517355.12811.15.camel@localhost.localdomain> On Sat, 2008-10-18 at 13:57 +0530, saagar shrivastava wrote: > Guys, > My company wanted me to configure a server which can handle remote OS > installation. For all the OS's we use. > I've configured PXE on RHEL 5. And I'm able to Install all the Unix > based OS's. OS we're using are: > RHEL 3 AS > RHEL 4 AS > RHEL 5 > Fedora > Suse > Windows XP > Windows Server 2003 > But I'm stucked with MicroSoft OS's. Can anybody help me please? PXELinux can solve any network booting problem, just like SYSLinux/ISOLinux can solve any disk booting problem, etc... Unfortunately some OSes are far bigger problems than others. ;) Best advice I can give you ... Don't bother this list, or even Peter Anvin's SYSLinux, etc... list for that matter, with Windows booting issues. Anvin is probably one of the biggest examples of "no good deed goes unpunished" as he is regularly bombarded (many times not-so-nicely) because his system is so damn useful for any and all OSes on the PC. PXELinux can provide the infrastructure. The problem are the OS boot limitations, something that no Linux or even ISO/PXE/SYSLinux list can address. Hit a Microsoft News group for more assistance, or various, independent resources. I will give you a few concepts to start, but please do _not_ follow-up on this list. ;) - You can use a PXE/SYSLinux COM32 object to boot a floppy or other disk option, such as various 3rd party recovery solutions. - You can use PXE/ISOLinux to boot an ISO image or other ISO9660 option, such as a WinPE ISO image, which is not easy to create (long story) Again, although many corporations use a PXELinux infrastructure because it are more flexible than Remote Installation Services (RIS), you have to be ready to hack things to get them to work as you want. Don't bother Linux lists with these details. Go consult with other Microsoft professionals on the appropriate lists. -- Bryan J Smith - Senior Consultant - Red Hat GPS SE US mailto:bjs at redhat.com +1 (407) 489-7013 (Mobile) mailto:b.j.smith at ieee.org (non-RH/ext to Blackberry) ----------------------------------------------------- For every dollar you spend on Red Hat solutions, you not only fund the leading community development re- source, but you receive the #1 IT industry leader in corporate value. http://www.redhat.com/promo/vendor/ From jason.gnu at gmail.com Mon Oct 27 09:02:26 2008 From: jason.gnu at gmail.com (jason zhang) Date: Mon, 27 Oct 2008 17:02:26 +0800 Subject: add a prompt screen to let user confirm disk partition operation Message-ID: hi, does anyone know how can I add a custom screen to prompt user to confirm the disk operations(they will lose their disk data) when perform a kickstart auto-installation. It's just need add some magic in %pre scripts, Eg. use pyhon and import gui library used by anaconda, or I have to make some anaconda customization for adding a custom screen? Best Regards, Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From astrand at cendio.se Mon Oct 27 09:07:21 2008 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Mon, 27 Oct 2008 10:07:21 +0100 (CET) Subject: add a prompt screen to let user confirm disk partition operation In-Reply-To: References: Message-ID: > > does anyone know how can I add a custom screen to prompt user to confirm the > disk operations(they will lose their disk data) when perform a kickstart > auto-installation. It's just need add some magic in %pre scripts, Eg. use This is what we are doing in TLCOS (ThinLinc Client OS): In ks.cfg: %pre /mnt/runtime/confirm-erase %end confirm-erase looks like: #!/usr/bin/python # -*-mode: python; coding: UTF-8 -*- # # Copyright 2002-2008 Cendio AB. # For more information, see http://www.cendio.com # FIXME: Determine current VT to switch back to VT = 8 import os import sys import snack import time import fcntl import termios pid = os.fork() if pid != 0: os.wait() os._exit(0) os.system("chvt %d" % VT) fd = os.open("/dev/tty%d" % VT, os.O_RDWR) os.dup2(fd, 0) os.dup2(fd, 1) os.dup2(fd, 2) sys.stdin = os.fdopen(0, "r") sys.stdout = os.fdopen(1, "w") sys.stderr = os.fdopen(2, "w") os.setsid() fcntl.ioctl(fd, termios.TIOCSCTTY, 1) screen = snack.SnackScreen() if "reboot" == snack.ButtonChoiceWindow(screen, "WARNING", "WARNING! All data on your hard disk will be DELETED!", buttons=["reboot", "continue"]): os.system("reboot") while 1: time.sleep(10) screen.finish() os.system("chvt %d" % 1) Regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From pgroven at 2wire.com Tue Oct 28 00:42:14 2008 From: pgroven at 2wire.com (Phillip Groven) Date: Mon, 27 Oct 2008 17:42:14 -0700 Subject: cmdline ignored Message-ID: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D6@phxexch01.corp.2wire.com> I am trying to kickstart redhat 5.2 64 bit We have used this %pre script for years and had have no issues. I am trying to kickstart an HP DL365 G5 but does not like this script The kickstart machine is running Redhat 4.5 This %pre script worked fine on a G4 with red hat 5.1. The kickstart always comes up with a GUI to partition the drives %pre NEWDEV=`sed 's/.*rootdev=\([^ $]*\).*/\1/' < /proc/cmdline` echo "##" echo "## newdev = $NEWDEV" if test "$NEWDEV" = "cciss" ; then DEVICE1="--ondisk cciss/c0d0" elif test "$NEWDEV" = "ida" ; then DEVICE1="--ondisk ida/c0d0" elif test "$NEWDEV" = "hd" ; then DEVICE1="--ondisk hda" elif test "$NEWDEV" = "sd" ; then DEVICE1="--ondisk sda" else DEVICE1="" fi echo "## kickstart configured with $DEVICE1" cat > /tmp/parts.ks < From Pablo.Iranzo at redhat.com Tue Oct 28 07:19:18 2008 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?ISO-8859-1?Q?G=F3mez?=) Date: Tue, 28 Oct 2008 07:19:18 +0000 Subject: cmdline ignored In-Reply-To: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D6@phxexch01.corp.2wire.com> References: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D6@phxexch01.corp.2wire.com> Message-ID: <1225178358.7797.9.camel@iranzo.users.redhat.com> Try with something like: %pre set $(list-harddrives) let numd=$#/2 # harddrive number d1=$1 # 1st device S1=$2 # 1st device size and so on DISCO=$d1 echo "clearpart --drives=$DISCO --all --initlabel" >> /tmp/part-include echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" >> /tmp/part-include echo "part pv.100000 --size=1 --grow --ondisk=$DISCO" >> /tmp/part-include echo "volgroup VG --pesize=32768 pv.100000" >> /tmp/part-include echo "logvol swap --fstype swap --name=Swap --vgname=VG --size=2047" >> /tmp/part-include echo "logvol / --fstype ext3 --name=root --vgname=VG --size=1024" >> /tmp/part-include echo "logvol /home --fstype ext3 --size=1024 --name=home --vgname=VG" >> /tmp/part-include echo "logvol /tmp --fstype ext3 --size=1024 --name=tmp --vgname=VG" >> /tmp/part-include echo "logvol /usr --fstype ext3 --size=3000 --name=usr --vgname=VG" >> /tmp/part-include echo "logvol /opt --fstype ext3 --size=12000 --name=opt --vgname=VG" >> /tmp/part-include echo "part /opt/iso --fstype vfat --size=8000 --ondisk=$DISCO" >> /tmp/part-include Regards Pablo El lun, 27-10-2008 a las 17:42 -0700, Phillip Groven escribi?: > I am trying to kickstart redhat 5.2 64 bit > > We have used this %pre script for years and had have no issues. > > I am trying to kickstart an HP DL365 G5 but does not like this script > > The kickstart machine is running Redhat 4.5 > > This %pre script worked fine on a G4 with red hat 5.1. > > The kickstart always comes up with a GUI to partition the drives > > %pre > NEWDEV=`sed 's/.*rootdev=\([^ $]*\).*/\1/' < /proc/cmdline` > echo "##" > echo "## newdev = $NEWDEV" > > if test "$NEWDEV" = "cciss" ; then > DEVICE1="--ondisk cciss/c0d0" > elif test "$NEWDEV" = "ida" ; then > DEVICE1="--ondisk ida/c0d0" > elif test "$NEWDEV" = "hd" ; then > DEVICE1="--ondisk hda" > elif test "$NEWDEV" = "sd" ; then > DEVICE1="--ondisk sda" > else > DEVICE1="" > fi > echo "## kickstart configured with $DEVICE1" > > cat > /tmp/parts.ks < clearpart --all --initlabel > part /boot --fstype "ext3" --size=128 --asprimary $DEVICE1 > part swap --size=2048 $DEVICE1 > part / --fstype "ext3" --size=512 --grow --asprimary $DEVICE1 > > EOPARTS > > > > I have tried this fix but it did not resolve the issue > > http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=1121516&prodTypeId=15351&prodSeriesId=1121516&objectID=c01430330 > > > > > > > > > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Esta parte del mensaje est? firmada digitalmente URL: From pgroven at 2wire.com Tue Oct 28 18:26:49 2008 From: pgroven at 2wire.com (Phillip Groven) Date: Tue, 28 Oct 2008 11:26:49 -0700 Subject: cmdline ignored In-Reply-To: <1225178358.7797.9.camel@iranzo.users.redhat.com> References: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D6@phxexch01.corp.2wire.com> <1225178358.7797.9.camel@iranzo.users.redhat.com> Message-ID: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D9@phxexch01.corp.2wire.com> I tried this but it the kickstart still comes up with a text-GUI page to configure the drives I am not sure why -----Original Message----- From: Pablo Iranzo G?mez [mailto:Pablo.Iranzo at redhat.com] Sent: Tuesday, October 28, 2008 12:19 AM To: Discussion list about Kickstart Subject: Re: cmdline ignored Try with something like: %pre set $(list-harddrives) let numd=$#/2 # harddrive number d1=$1 # 1st device S1=$2 # 1st device size and so on DISCO=$d1 echo "clearpart --drives=$DISCO --all --initlabel" >> /tmp/part-include echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" >> /tmp/part-include echo "part pv.100000 --size=1 --grow --ondisk=$DISCO" >> /tmp/part-include echo "volgroup VG --pesize=32768 pv.100000" >> /tmp/part-include echo "logvol swap --fstype swap --name=Swap --vgname=VG --size=2047" >> /tmp/part-include echo "logvol / --fstype ext3 --name=root --vgname=VG --size=1024" >> /tmp/part-include echo "logvol /home --fstype ext3 --size=1024 --name=home --vgname=VG" >> /tmp/part-include echo "logvol /tmp --fstype ext3 --size=1024 --name=tmp --vgname=VG" >> /tmp/part-include echo "logvol /usr --fstype ext3 --size=3000 --name=usr --vgname=VG" >> /tmp/part-include echo "logvol /opt --fstype ext3 --size=12000 --name=opt --vgname=VG" >> /tmp/part-include echo "part /opt/iso --fstype vfat --size=8000 --ondisk=$DISCO" >> /tmp/part-include Regards Pablo El lun, 27-10-2008 a las 17:42 -0700, Phillip Groven escribi?: > I am trying to kickstart redhat 5.2 64 bit > > We have used this %pre script for years and had have no issues. > > I am trying to kickstart an HP DL365 G5 but does not like this script > > The kickstart machine is running Redhat 4.5 > > This %pre script worked fine on a G4 with red hat 5.1. > > The kickstart always comes up with a GUI to partition the drives > > %pre > NEWDEV=`sed 's/.*rootdev=\([^ $]*\).*/\1/' < /proc/cmdline` > echo "##" > echo "## newdev = $NEWDEV" > > if test "$NEWDEV" = "cciss" ; then > DEVICE1="--ondisk cciss/c0d0" > elif test "$NEWDEV" = "ida" ; then > DEVICE1="--ondisk ida/c0d0" > elif test "$NEWDEV" = "hd" ; then > DEVICE1="--ondisk hda" > elif test "$NEWDEV" = "sd" ; then > DEVICE1="--ondisk sda" > else > DEVICE1="" > fi > echo "## kickstart configured with $DEVICE1" > > cat > /tmp/parts.ks < clearpart --all --initlabel > part /boot --fstype "ext3" --size=128 --asprimary $DEVICE1 > part swap --size=2048 $DEVICE1 > part / --fstype "ext3" --size=512 --grow --asprimary $DEVICE1 > > EOPARTS > > > > I have tried this fix but it did not resolve the issue > > http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=1121516&prodTypeId=15351&prodSeriesId=1121516&objectID=c01430330 > > > > > > > > > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid - C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain -------------- next part -------------- An HTML attachment was scrubbed... URL: From Pablo.Iranzo at redhat.com Tue Oct 28 18:30:12 2008 From: Pablo.Iranzo at redhat.com (=?UTF-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Tue, 28 Oct 2008 19:30:12 +0100 (CET) Subject: cmdline ignored In-Reply-To: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D9@phxexch01.corp.2wire.com> References: <299E8BB0D5475E4FABB162E7DCA1BBE902E289D6@phxexch01.corp.2wire.com> <1225178358.7797.9.camel@iranzo.users.redhat.com> <299E8BB0D5475E4FABB162E7DCA1BBE902E289D9@phxexch01.corp.2wire.com> Message-ID: On Tue, 28 Oct 2008, Phillip Groven wrote: > I tried this but it the kickstart still comes up with a text-GUI page to configure the drives > > I am not sure why What information did you get at your /tmp/part-include (or your file name), as well as anaconda.log ? Regards Pablo > > > > -----Original Message----- > From: Pablo Iranzo G?mez [mailto:Pablo.Iranzo at redhat.com] > Sent: Tuesday, October 28, 2008 12:19 AM > To: Discussion list about Kickstart > Subject: Re: cmdline ignored > > > > Try with something like: > > %pre > > set $(list-harddrives) > > let numd=$#/2 # harddrive number > > d1=$1 # 1st device > > S1=$2 # 1st device size and so on > > > > DISCO=$d1 > > > > echo "clearpart --drives=$DISCO --all --initlabel" >> /tmp/part-include > > echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" >> /tmp/part-include > > echo "part pv.100000 --size=1 --grow --ondisk=$DISCO" >> /tmp/part-include > > echo "volgroup VG --pesize=32768 pv.100000" >> /tmp/part-include > > echo "logvol swap --fstype swap --name=Swap --vgname=VG --size=2047" >> /tmp/part-include > > echo "logvol / --fstype ext3 --name=root --vgname=VG --size=1024" >> /tmp/part-include > > echo "logvol /home --fstype ext3 --size=1024 --name=home --vgname=VG" >> /tmp/part-include > > echo "logvol /tmp --fstype ext3 --size=1024 --name=tmp --vgname=VG" >> /tmp/part-include > > echo "logvol /usr --fstype ext3 --size=3000 --name=usr --vgname=VG" >> /tmp/part-include > > echo "logvol /opt --fstype ext3 --size=12000 --name=opt --vgname=VG" >> /tmp/part-include > > echo "part /opt/iso --fstype vfat --size=8000 --ondisk=$DISCO" >> /tmp/part-include > > > > > > Regards > > Pablo > > > > > > > > > > El lun, 27-10-2008 a las 17:42 -0700, Phillip Groven escribi?: > >> I am trying to kickstart redhat 5.2 64 bit > >> > >> We have used this %pre script for years and had have no issues. > >> > >> I am trying to kickstart an HP DL365 G5 but does not like this script > >> > >> The kickstart machine is running Redhat 4.5 > >> > >> This %pre script worked fine on a G4 with red hat 5.1. > >> > >> The kickstart always comes up with a GUI to partition the drives > >> > >> %pre > >> NEWDEV=`sed 's/.*rootdev=\([^ $]*\).*/\1/' < /proc/cmdline` > >> echo "##" > >> echo "## newdev = $NEWDEV" > >> > >> if test "$NEWDEV" = "cciss" ; then > >> DEVICE1="--ondisk cciss/c0d0" > >> elif test "$NEWDEV" = "ida" ; then > >> DEVICE1="--ondisk ida/c0d0" > >> elif test "$NEWDEV" = "hd" ; then > >> DEVICE1="--ondisk hda" > >> elif test "$NEWDEV" = "sd" ; then > >> DEVICE1="--ondisk sda" > >> else > >> DEVICE1="" > >> fi > >> echo "## kickstart configured with $DEVICE1" > >> > >> cat > /tmp/parts.ks < >> clearpart --all --initlabel > >> part /boot --fstype "ext3" --size=128 --asprimary $DEVICE1 > >> part swap --size=2048 $DEVICE1 > >> part / --fstype "ext3" --size=512 --grow --asprimary $DEVICE1 > >> > >> EOPARTS > >> > >> > >> > >> I have tried this fix but it did not resolve the issue > >> > >> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=1121516&prodTypeId=15351&prodSeriesId=1121516&objectID=c01430330 > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> Kickstart-list mailing list > >> Kickstart-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > -- Pablo Iranzo G??mez (http://Alufis35.uv.es/~iranzo/) (PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp) -- Postulado de Boling sobre la Ley de Murphy: Si se encuentra bien, no se preocupe. Se le pasar?? From jason.gnu at gmail.com Thu Oct 30 08:10:52 2008 From: jason.gnu at gmail.com (jason zhang) Date: Thu, 30 Oct 2008 16:10:52 +0800 Subject: add a prompt screen to let user confirm disk partition operation In-Reply-To: References: Message-ID: Peter, I've tested the code you offered, seems it can not stop anaconda doing partition erase while the your code promote the user to confirm, that means if user don't select 'reboot' action at the VT8 screen before anaconda keep processing 'package dependency check' then perform partition and disk format at VT6, the user still will face data loss risk. Any trick to suspend anaconda to wait user indeed do a confirmation? BR, Kevin On Mon, Oct 27, 2008 at 5:07 PM, Peter ?strand wrote: > > > > does anyone know how can I add a custom screen to prompt user to confirm > the > > disk operations(they will lose their disk data) when perform a kickstart > > auto-installation. It's just need add some magic in %pre scripts, Eg. use > > This is what we are doing in TLCOS (ThinLinc Client OS): > > In ks.cfg: > > %pre > /mnt/runtime/confirm-erase > %end > > confirm-erase looks like: > > #!/usr/bin/python > # -*-mode: python; coding: UTF-8 -*- > # > # Copyright 2002-2008 Cendio AB. > # For more information, see http://www.cendio.com > > # FIXME: Determine current VT to switch back to > > VT = 8 > import os > import sys > import snack > import time > import fcntl > import termios > > pid = os.fork() > if pid != 0: > os.wait() > os._exit(0) > os.system("chvt %d" % VT) > fd = os.open("/dev/tty%d" % VT, os.O_RDWR) > os.dup2(fd, 0) > os.dup2(fd, 1) > os.dup2(fd, 2) > sys.stdin = os.fdopen(0, "r") > sys.stdout = os.fdopen(1, "w") > sys.stderr = os.fdopen(2, "w") > os.setsid() > fcntl.ioctl(fd, termios.TIOCSCTTY, 1) > screen = snack.SnackScreen() > if "reboot" == snack.ButtonChoiceWindow(screen, "WARNING", > "WARNING! All data on your hard disk will be DELETED!", > buttons=["reboot", "continue"]): > os.system("reboot") > while 1: time.sleep(10) > screen.finish() > os.system("chvt %d" % 1) > > > Regards, > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > _______________________________________________ > 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 jason.gnu at gmail.com Thu Oct 30 08:10:52 2008 From: jason.gnu at gmail.com (jason zhang) Date: Thu, 30 Oct 2008 16:10:52 +0800 Subject: add a prompt screen to let user confirm disk partition operation In-Reply-To: References: Message-ID: Peter, I've tested the code you offered, seems it can not stop anaconda doing partition erase while the your code promote the user to confirm, that means if user don't select 'reboot' action at the VT8 screen before anaconda keep processing 'package dependency check' then perform partition and disk format at VT6, the user still will face data loss risk. Any trick to suspend anaconda to wait user indeed do a confirmation? BR, Kevin On Mon, Oct 27, 2008 at 5:07 PM, Peter ?strand wrote: > > > > does anyone know how can I add a custom screen to prompt user to confirm > the > > disk operations(they will lose their disk data) when perform a kickstart > > auto-installation. It's just need add some magic in %pre scripts, Eg. use > > This is what we are doing in TLCOS (ThinLinc Client OS): > > In ks.cfg: > > %pre > /mnt/runtime/confirm-erase > %end > > confirm-erase looks like: > > #!/usr/bin/python > # -*-mode: python; coding: UTF-8 -*- > # > # Copyright 2002-2008 Cendio AB. > # For more information, see http://www.cendio.com > > # FIXME: Determine current VT to switch back to > > VT = 8 > import os > import sys > import snack > import time > import fcntl > import termios > > pid = os.fork() > if pid != 0: > os.wait() > os._exit(0) > os.system("chvt %d" % VT) > fd = os.open("/dev/tty%d" % VT, os.O_RDWR) > os.dup2(fd, 0) > os.dup2(fd, 1) > os.dup2(fd, 2) > sys.stdin = os.fdopen(0, "r") > sys.stdout = os.fdopen(1, "w") > sys.stderr = os.fdopen(2, "w") > os.setsid() > fcntl.ioctl(fd, termios.TIOCSCTTY, 1) > screen = snack.SnackScreen() > if "reboot" == snack.ButtonChoiceWindow(screen, "WARNING", > "WARNING! All data on your hard disk will be DELETED!", > buttons=["reboot", "continue"]): > os.system("reboot") > while 1: time.sleep(10) > screen.finish() > os.system("chvt %d" % 1) > > > Regards, > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > _______________________________________________ > 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 astrand at cendio.se Thu Oct 30 13:49:43 2008 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Thu, 30 Oct 2008 14:49:43 +0100 (CET) Subject: add a prompt screen to let user confirm disk partition operation In-Reply-To: References: Message-ID: That's strange; Anaconda should halt until the %pre script is finished. You are sure you haven't added a '&' by mistake, or something like that? Or, it might depend on the Anaconda version; we are using Fedora 8. Regards, Peter ?strand On Thu, 30 Oct 2008, jason zhang wrote: > Peter, > I've tested the code you offered, seems it can not stop anaconda doing > partition erase while the your code promote the user to confirm, that means > if user don't select 'reboot' action at the VT8 screen before anaconda keep > processing 'package dependency check' then perform partition and disk > format at VT6, the user still will face data loss risk. Any trick to suspend > anaconda to wait user indeed do a confirmation? > > BR, > Kevin > > On Mon, Oct 27, 2008 at 5:07 PM, Peter ?strand wrote: > > > > > > > does anyone know how can I add a custom screen to prompt user to confirm > > the > > > disk operations(they will lose their disk data) when perform a kickstart > > > auto-installation. It's just need add some magic in %pre scripts, Eg. use > > > > This is what we are doing in TLCOS (ThinLinc Client OS): > > > > In ks.cfg: > > > > %pre > > /mnt/runtime/confirm-erase > > %end > > > > confirm-erase looks like: > > > > #!/usr/bin/python > > # -*-mode: python; coding: UTF-8 -*- > > # > > # Copyright 2002-2008 Cendio AB. > > # For more information, see http://www.cendio.com > > > > # FIXME: Determine current VT to switch back to > > > > VT = 8 > > import os > > import sys > > import snack > > import time > > import fcntl > > import termios > > > > pid = os.fork() > > if pid != 0: > > os.wait() > > os._exit(0) > > os.system("chvt %d" % VT) > > fd = os.open("/dev/tty%d" % VT, os.O_RDWR) > > os.dup2(fd, 0) > > os.dup2(fd, 1) > > os.dup2(fd, 2) > > sys.stdin = os.fdopen(0, "r") > > sys.stdout = os.fdopen(1, "w") > > sys.stderr = os.fdopen(2, "w") > > os.setsid() > > fcntl.ioctl(fd, termios.TIOCSCTTY, 1) > > screen = snack.SnackScreen() > > if "reboot" == snack.ButtonChoiceWindow(screen, "WARNING", > > "WARNING! All data on your hard disk will be DELETED!", > > buttons=["reboot", "continue"]): > > os.system("reboot") > > while 1: time.sleep(10) > > screen.finish() > > os.system("chvt %d" % 1) > > > > > > Regards, > > --- > > Peter ?strand ThinLinc Chief Developer > > Cendio AB http://www.cendio.com > > Wallenbergs gata 4 > > 583 30 Link?ping Phone: +46-13-21 46 00 > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.com Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Pablo.Iranzo at redhat.com Fri Oct 31 07:54:15 2008 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?ISO-8859-1?Q?G=F3mez?=) Date: Fri, 31 Oct 2008 08:54:15 +0100 Subject: FW: Kickstart-list Digest, Vol 56, Issue 14 In-Reply-To: <299E8BB0D5475E4FABB162E7DCA1BBE902E28A06@phxexch01.corp.2wire.com> References: <299E8BB0D5475E4FABB162E7DCA1BBE902E28A06@phxexch01.corp.2wire.com> Message-ID: <1225439655.25006.26.camel@iranzo.users.redhat.com> Send me a copy of your full ks to have a look on it. Regards Pablo El jue, 30-10-2008 a las 10:10 -0700, Phillip Groven escribi?: > > > I tried your partitioning code and I get the same > > I was able get to a shell prompt and scp the anaconda.log file so I > think the bnx2 driver is working > > Can you look at this log file and tell me if you see what is wrong? > > > > Phil > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of > kickstart-list-request at redhat.com > Sent: Tuesday, October 28, 2008 11:30 AM > To: kickstart-list at redhat.com > Subject: Kickstart-list Digest, Vol 56, Issue 14 > > > > Send Kickstart-list mailing list submissions to > > kickstart-list at redhat.com > > > > To subscribe or unsubscribe via the World Wide Web, visit > > https://www.redhat.com/mailman/listinfo/kickstart-list > > or, via email, send a message with subject or body 'help' to > > kickstart-list-request at redhat.com > > > > You can reach the person managing the list at > > kickstart-list-owner at redhat.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Kickstart-list digest..." > > > mensaje de correo electr?nico adjunto > > --------- Mensaje reenviado -------- > > De: Phillip Groven > > Responder a: Discussion list about Kickstart > > > > Para: Discussion list about Kickstart > > Asunto: RE: cmdline ignored > > Fecha: Tue, 28 Oct 2008 11:26:49 -0700 > > > > I tried this but it the kickstart still comes up with a text-GUI > > page to configure the drives > > > > I am not sure why > > > > > > > > -----Original Message----- > > From: Pablo Iranzo G?mez [mailto:Pablo.Iranzo at redhat.com] > > Sent: Tuesday, October 28, 2008 12:19 AM > > To: Discussion list about Kickstart > > Subject: Re: cmdline ignored > > > > > > > > Try with something like: > > > > %pre > > > > set $(list-harddrives) > > > > let numd=$#/2 # harddrive number > > > > d1=$1 # 1st device > > > > S1=$2 # 1st device size and so on > > > > > > > > DISCO=$d1 > > > > > > > > echo "clearpart --drives=$DISCO --all --initlabel" > > >> /tmp/part-include > > > > echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" > > >> /tmp/part-include > > > > echo "part pv.100000 --size=1 --grow --ondisk=$DISCO" > > >> /tmp/part-include > > > > echo "volgroup VG --pesize=32768 pv.100000" >> /tmp/part-include > > > > echo "logvol swap --fstype swap --name=Swap --vgname=VG --size=2047" > > >> /tmp/part-include > > > > echo "logvol / --fstype ext3 --name=root --vgname=VG --size=1024" > > >> /tmp/part-include > > > > echo "logvol /home --fstype ext3 --size=1024 --name=home > > --vgname=VG" >> /tmp/part-include > > > > echo "logvol /tmp --fstype ext3 --size=1024 --name=tmp --vgname=VG" > > >> /tmp/part-include > > > > echo "logvol /usr --fstype ext3 --size=3000 --name=usr --vgname=VG" > > >> /tmp/part-include > > > > echo "logvol /opt --fstype ext3 --size=12000 --name=opt --vgname=VG" > > >> /tmp/part-include > > > > echo "part /opt/iso --fstype vfat --size=8000 --ondisk=$DISCO" > > >> /tmp/part-include > > > > > > > > > > > > Regards > > > > Pablo > > > > > > > > > > > > > > > > > > > > El lun, 27-10-2008 a las 17:42 -0700, Phillip Groven escribi?: > > > > > I am trying to kickstart redhat 5.2 64 bit > > > > > > > > > > We have used this %pre script for years and had have no issues. > > > > > > > > > > I am trying to kickstart an HP DL365 G5 but does not like this > > script > > > > > > > > > > The kickstart machine is running Redhat 4.5 > > > > > > > > > > This %pre script worked fine on a G4 with red hat 5.1. > > > > > > > > > > The kickstart always comes up with a GUI to partition the drives > > > > > > > > > > %pre > > > > > NEWDEV=`sed 's/.*rootdev=\([^ $]*\).*/\1/' < /proc/cmdline` > > > > > echo "##" > > > > > echo "## newdev = $NEWDEV" > > > > > > > > > > if test "$NEWDEV" = "cciss" ; then > > > > > DEVICE1="--ondisk cciss/c0d0" > > > > > elif test "$NEWDEV" = "ida" ; then > > > > > DEVICE1="--ondisk ida/c0d0" > > > > > elif test "$NEWDEV" = "hd" ; then > > > > > DEVICE1="--ondisk hda" > > > > > elif test "$NEWDEV" = "sd" ; then > > > > > DEVICE1="--ondisk sda" > > > > > else > > > > > DEVICE1="" > > > > > fi > > > > > echo "## kickstart configured with $DEVICE1" > > > > > > > > > > cat > /tmp/parts.ks < > > > > clearpart --all --initlabel > > > > > part /boot --fstype "ext3" --size=128 --asprimary $DEVICE1 > > > > > part swap --size=2048 $DEVICE1 > > > > > part / --fstype "ext3" --size=512 --grow --asprimary $DEVICE1 > > > > > > > > > > EOPARTS > > > > > > > > > > > > > > > > > > > > I have tried this fix but it did not resolve the issue > > > > > > > > > > > > http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=1121516&prodTypeId=15351&prodSeriesId=1121516&objectID=c01430330 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Kickstart-list mailing list > > > > > Kickstart-list at redhat.com > > > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > -- > > > > > > > > Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) > > > > RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain > > > > Phone: +34 645 01 01 49 (CET/CEST) > > > > GnuPG KeyID: 0xFAD3CF0D > > > > > > > > -- > > > > Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 > > > > Directores: Michael Cunningham, Charlie Peters y David Owens > > > > Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, > > Espa?a > > > > Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta > > 3?D, 28016 Madrid, Spain > > > > > > > > > > > > > mensaje de correo electr?nico adjunto > > --------- Mensaje reenviado -------- > > De: Pablo Iranzo G?mez > > Responder a: Discussion list about Kickstart > > > > Para: Discussion list about Kickstart > > Asunto: RE: cmdline ignored > > Fecha: Tue, 28 Oct 2008 11:30:12 -0700 > > > > > > > > On Tue, 28 Oct 2008, Phillip Groven wrote: > > > > > I tried this but it the kickstart still comes up with a text-GUI > > page to configure the drives > > > > > > I am not sure why > > > > What information did you get at your /tmp/part-include (or your file > > name), as well as anaconda.log ? > > > > Regards > > Pablo > > > > > > > > > > > > > > -----Original Message----- > > > From: Pablo Iranzo Gmez [mailto:Pablo.Iranzo at redhat.com] > > > Sent: Tuesday, October 28, 2008 12:19 AM > > > To: Discussion list about Kickstart > > > Subject: Re: cmdline ignored > > > > > > > > > > > > Try with something like: > > > > > > %pre > > > > > > set $(list-harddrives) > > > > > > let numd=$#/2 # harddrive number > > > > > > d1=$1 # 1st device > > > > > > S1=$2 # 1st device size and so on > > > > > > > > > > > > DISCO=$d1 > > > > > > > > > > > > echo "clearpart --drives=$DISCO --all --initlabel" > > >> /tmp/part-include > > > > > > echo "part /boot --fstype ext3 --size=100 --ondisk=$DISCO" > > >> /tmp/part-include > > > > > > echo "part pv.100000 --size=1 --grow --ondisk=$DISCO" > > >> /tmp/part-include > > > > > > echo "volgroup VG --pesize=32768 pv.100000" >> /tmp/part-include > > > > > > echo "logvol swap --fstype swap --name=Swap --vgname=VG > > --size=2047" >> /tmp/part-include > > > > > > echo "logvol / --fstype ext3 --name=root --vgname=VG --size=1024" > > >> /tmp/part-include > > > > > > echo "logvol /home --fstype ext3 --size=1024 --name=home > > --vgname=VG" >> /tmp/part-include > > > > > > echo "logvol /tmp --fstype ext3 --size=1024 --name=tmp > > --vgname=VG" >> /tmp/part-include > > > > > > echo "logvol /usr --fstype ext3 --size=3000 --name=usr > > --vgname=VG" >> /tmp/part-include > > > > > > echo "logvol /opt --fstype ext3 --size=12000 --name=opt > > --vgname=VG" >> /tmp/part-include > > > > > > echo "part /opt/iso --fstype vfat --size=8000 --ondisk=$DISCO" > > >> /tmp/part-include > > > > > > > > > > > > > > > > > > Regards > > > > > > Pablo > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > El lun, 27-10-2008 a las 17:42 -0700, Phillip Groven escribi: > > > > > >> I am trying to kickstart redhat 5.2 64 bit > > > > > >> > > > > > >> We have used this %pre script for years and had have no issues. > > > > > >> > > > > > >> I am trying to kickstart an HP DL365 G5 but does not like this > > script > > > > > >> > > > > > >> The kickstart machine is running Redhat 4.5 > > > > > >> > > > > > >> This %pre script worked fine on a G4 with red hat 5.1. > > > > > >> > > > > > >> The kickstart always comes up with a GUI to partition the drives > > > > > >> > > > > > >> %pre > > > > > >> NEWDEV=`sed 's/.*rootdev=\([^ $]*\).*/\1/' < /proc/cmdline` > > > > > >> echo "##" > > > > > >> echo "## newdev = $NEWDEV" > > > > > >> > > > > > >> if test "$NEWDEV" = "cciss" ; then > > > > > >> DEVICE1="--ondisk cciss/c0d0" > > > > > >> elif test "$NEWDEV" = "ida" ; then > > > > > >> DEVICE1="--ondisk ida/c0d0" > > > > > >> elif test "$NEWDEV" = "hd" ; then > > > > > >> DEVICE1="--ondisk hda" > > > > > >> elif test "$NEWDEV" = "sd" ; then > > > > > >> DEVICE1="--ondisk sda" > > > > > >> else > > > > > >> DEVICE1="" > > > > > >> fi > > > > > >> echo "## kickstart configured with $DEVICE1" > > > > > >> > > > > > >> cat > /tmp/parts.ks < > > > > >> clearpart --all --initlabel > > > > > >> part /boot --fstype "ext3" --size=128 --asprimary $DEVICE1 > > > > > >> part swap --size=2048 $DEVICE1 > > > > > >> part / --fstype "ext3" --size=512 --grow --asprimary $DEVICE1 > > > > > >> > > > > > >> EOPARTS > > > > > >> > > > > > >> > > > > > >> > > > > > >> I have tried this fix but it did not resolve the issue > > > > > >> > > > > > >> > > http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=1121516&prodTypeId=15351&prodSeriesId=1121516&objectID=c01430330 > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> _______________________________________________ > > > > > >> Kickstart-list mailing list > > > > > >> Kickstart-list at redhat.com > > > > > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > > > > > > > > > -- > > Pablo Iranzo G?mez > > (http://Alufis35.uv.es/~iranzo/) > > (PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp) > > -- > > Postulado de Boling sobre la Ley de Murphy: > > > > Si se encuentra bien, no se preocupe. Se le pasar? > > > > -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Esta parte del mensaje est? firmada digitalmente URL: From jason.gnu at gmail.com Fri Oct 31 08:56:53 2008 From: jason.gnu at gmail.com (jason zhang) Date: Fri, 31 Oct 2008 16:56:53 +0800 Subject: add a prompt screen to let user confirm disk partition operation In-Reply-To: References: Message-ID: I'm using RHEL5 to test this, anaconda version should be 11.1.2.87. that's so strange, I do think anaconda should wait pre-script finish then perform next action. Maybe os.wait() not work properly this case? so anaconda think the pre-script has already done while the subprocess of pre-script is still running. Best Regards, Kevin On Thu, Oct 30, 2008 at 9:49 PM, Peter ?strand wrote: > > That's strange; Anaconda should halt until the %pre script is finished. > You are sure you haven't added a '&' by mistake, or something like that? > Or, it might depend on the Anaconda version; we are using Fedora 8. > > Regards, > Peter ?strand > > On Thu, 30 Oct 2008, jason zhang wrote: > > > Peter, > > I've tested the code you offered, seems it can not stop anaconda doing > > partition erase while the your code promote the user to confirm, that > means > > if user don't select 'reboot' action at the VT8 screen before anaconda > keep > > processing 'package dependency check' then perform partition and disk > > format at VT6, the user still will face data loss risk. Any trick to > suspend > > anaconda to wait user indeed do a confirmation? > > > > BR, > > Kevin > > > > On Mon, Oct 27, 2008 at 5:07 PM, Peter ?strand > wrote: > > > > > > > > > > does anyone know how can I add a custom screen to prompt user to > confirm > > > the > > > > disk operations(they will lose their disk data) when perform a > kickstart > > > > auto-installation. It's just need add some magic in %pre scripts, Eg. > use > > > > > > This is what we are doing in TLCOS (ThinLinc Client OS): > > > > > > In ks.cfg: > > > > > > %pre > > > /mnt/runtime/confirm-erase > > > %end > > > > > > confirm-erase looks like: > > > > > > #!/usr/bin/python > > > # -*-mode: python; coding: UTF-8 -*- > > > # > > > # Copyright 2002-2008 Cendio AB. > > > # For more information, see http://www.cendio.com > > > > > > # FIXME: Determine current VT to switch back to > > > > > > VT = 8 > > > import os > > > import sys > > > import snack > > > import time > > > import fcntl > > > import termios > > > > > > pid = os.fork() > > > if pid != 0: > > > os.wait() > > > os._exit(0) > > > os.system("chvt %d" % VT) > > > fd = os.open("/dev/tty%d" % VT, os.O_RDWR) > > > os.dup2(fd, 0) > > > os.dup2(fd, 1) > > > os.dup2(fd, 2) > > > sys.stdin = os.fdopen(0, "r") > > > sys.stdout = os.fdopen(1, "w") > > > sys.stderr = os.fdopen(2, "w") > > > os.setsid() > > > fcntl.ioctl(fd, termios.TIOCSCTTY, 1) > > > screen = snack.SnackScreen() > > > if "reboot" == snack.ButtonChoiceWindow(screen, "WARNING", > > > "WARNING! All data on your hard disk will be DELETED!", > > > buttons=["reboot", "continue"]): > > > os.system("reboot") > > > while 1: time.sleep(10) > > > screen.finish() > > > os.system("chvt %d" % 1) > > > > > > > > > Regards, > > > --- > > > Peter ?strand ThinLinc Chief Developer > > > Cendio AB http://www.cendio.com > > > Wallenbergs gata 4 > > > 583 30 Link?ping Phone: +46-13-21 46 00 > > > _______________________________________________ > > > Kickstart-list mailing list > > > Kickstart-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > > > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.com > Wallenbergs gata 4 > 583 30 Link?ping Phone: +46-13-21 46 00 > > _______________________________________________ > 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: