From roger.leonard at ericsson.com Wed Nov 7 16:17:51 2007 From: roger.leonard at ericsson.com (Roger Leonard) Date: Wed, 7 Nov 2007 10:17:51 -0600 Subject: EL5 kickstart configuration issue Message-ID: <941D5DCD8C42014FAF70FB7424686DCF017FF264@eusrcmw721.eamcs.ericsson.se> I have been using nfs kickstart for years with no issues by mounting iso 1 and copying the "Redhat" dir to my installation area specified in my ks.cfg and then mounting CD's 2-5 and copying the Redhat/RPMS dir to the installation RPMS dir. This worked up until ES5 where it looks like the installation paths changed from Redhat to Server and the rpms are directly under the Server dir rather than being in a Redhat/RPMS dir. So I copied the entire contents of my cd #1 to the installation area and then mounted and copied just the Server dir to my installation area and anaconda appears to work ok but as soon as it trys to install the rpms it can't find xorg-x11-drv-i810-1.6.5-9.2.el5.x86_64.rpm or says its corrupt. That file is there and is the same md5sum as the iso so it looks like there is some sort of path issue or something. Permissions are fine. Can anyone point me at the "proper" way to set up a cdrom based NFS kickstart installation tree with EL5? Do I copy all the CD's over on top of each other in the installation area? What am I missing here? thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanarip at kanarip.com Wed Nov 7 16:40:46 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 07 Nov 2007 17:40:46 +0100 Subject: EL5 kickstart configuration issue In-Reply-To: <941D5DCD8C42014FAF70FB7424686DCF017FF264@eusrcmw721.eamcs.ericsson.se> References: <941D5DCD8C42014FAF70FB7424686DCF017FF264@eusrcmw721.eamcs.ericsson.se> Message-ID: <4731EA8E.40809@kanarip.com> Roger Leonard wrote: > I have been using nfs kickstart for years with no issues by mounting iso > 1 and copying the ?Redhat? dir to my installation area specified in my > ks.cfg and then mounting CD?s 2-5 and copying the Redhat/RPMS dir to the > installation RPMS dir. This worked up until ES5 where it looks like the > installation paths changed from Redhat to Server and the rpms are > directly under the Server dir rather than being in a Redhat/RPMS dir. > So I copied the entire contents of my cd #1 to the installation area and > then mounted and copied just the Server dir to my installation area and > anaconda appears to work ok but as soon as it trys to install the rpms > it can?t find xorg-x11-drv-i810-1.6.5-9.2.el5.x86_64.rpm or says its > corrupt. That file is there and is the same md5sum as the iso so it > looks like there is some sort of path issue or something. Permissions > are fine. Can anyone point me at the ?proper? way to set up a cdrom > based NFS kickstart installation tree with EL5? Do I copy all the CD?s > over on top of each other in the installation area? What am I missing here? > > Actually you can just copy the ISO files into the NFS shared directory, it doesn't necessarily need to be an exploded tree. Kind regards, Jeroen van Meeuwen -kanarip From roger.leonard at ericsson.com Wed Nov 7 19:33:17 2007 From: roger.leonard at ericsson.com (Roger Leonard) Date: Wed, 7 Nov 2007 13:33:17 -0600 Subject: EL5 kickstart configuration issue In-Reply-To: <4731EA8E.40809@kanarip.com> References: <941D5DCD8C42014FAF70FB7424686DCF017FF264@eusrcmw721.eamcs.ericsson.se> <4731EA8E.40809@kanarip.com> Message-ID: <941D5DCD8C42014FAF70FB7424686DCF017FF268@eusrcmw721.eamcs.ericsson.se> Wow that was way too easy but it appears to be working so far. All this time I have been expanding and fooling around with the iso's. you can tell that Redhat is not my first language. Thanks so much for the help. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Jeroen van Meeuwen Sent: Wednesday, November 07, 2007 11:41 AM To: Discussion list about Kickstart Subject: Re: EL5 kickstart configuration issue Roger Leonard wrote: > I have been using nfs kickstart for years with no issues by mounting iso > 1 and copying the "Redhat" dir to my installation area specified in my > ks.cfg and then mounting CD's 2-5 and copying the Redhat/RPMS dir to the > installation RPMS dir. This worked up until ES5 where it looks like the > installation paths changed from Redhat to Server and the rpms are > directly under the Server dir rather than being in a Redhat/RPMS dir. > So I copied the entire contents of my cd #1 to the installation area and > then mounted and copied just the Server dir to my installation area and > anaconda appears to work ok but as soon as it trys to install the rpms > it can't find xorg-x11-drv-i810-1.6.5-9.2.el5.x86_64.rpm or says its > corrupt. That file is there and is the same md5sum as the iso so it > looks like there is some sort of path issue or something. Permissions > are fine. Can anyone point me at the "proper" way to set up a cdrom > based NFS kickstart installation tree with EL5? Do I copy all the CD's > over on top of each other in the installation area? What am I missing here? > > Actually you can just copy the ISO files into the NFS shared directory, it doesn't necessarily need to be an exploded tree. Kind regards, Jeroen van Meeuwen -kanarip _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Joe_Wulf at yahoo.com Thu Nov 8 16:45:51 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Thu, 8 Nov 2007 11:45:51 -0500 Subject: More on NFS problem Message-ID: The anaconda portions of the boot (with DHCP and tftp) go very well. I can see in VC3 and VC4 that the booted system gets all the right network attributes and have carefully verified them (hostname, IP, GW, dns, NM, broadcast, network, next_server, and domain). In VC3, eventually, I get the error message "reverse name lookup failed", then it says "failed to mount nfs source". It displays a url and file location, both of which are, in fact, correct. Efforts at toying with various anaconda options for the pxeconfig isolinux file provide no improvement. On the kickstart server, I configure it for use of a MAC address for another system that I've successfully kickstarted before (within dhcp and the tftp/pxeconfig link), boot that other system and the installation goes perfectly to completion. The nfs mount occurs instantly here, where it times out and fails on the other server. I switch the MAC address back on the kickstart server to the problem box (no other changes to this world) and the NFS fails at the same point again. When manually attempting to continue the build interactively, the information is given for the NFS server (192.168.10.2) and the directory (/kickstart/ks-files/ks.cfg) but always results in the error message "That directory could not be mounted from the server". Yet a manually built VM, on the same physical server where the kickstarted VM is can immediately mount the exact same path without fail. The physical network is a 4-port Linksys hub (yes hub), 1 PC with Fedora 7 installed and configured for the kickstart server, one Dell XPS laptop with VMware Workstation v6 installed (32 bit VM's kickstarted into here always install successfully) and a MacPro with Windoze XP 64 bit installed and it also has VMware Workstation v6 installed (32/64bit VM's kickstarted into here ALWAYS exhibit the problems outlined above). Regardless of isolating this hub from the internet or making it standalone, the results are the same. To do other troubleshooting, I've 'shared' the C: drive of the MacPro, mapped it into a drive letter on the Dell, pointed VMware on the Dell to the mounted filesystem on the Mac for the 'problem' VM and it boots, installs to completion 3 times in a row. I try it natively on the Mac again, with failure as before. I've temporarily replaces Windoze XP on the Mac with Windoze 2003, and the VM died at the same place. Also, I can successfully manually build, via ISO image any RHEL AS4, RHEL5, Fedora 7 OS I want, either 32 and/or 64 bit on the MacPro. Subsequently to the build, NFS mounts work correctly. Unfortunately, entries to the RedHat kickstart mailing list didn't provide any useful help. One suggestion was to switch over to squid and apache on the kickstart server and 'try' that. Not good suggestions for me in resolving an NFS problem within anaconda. My customer has a pretty widely installed base deployed via NFS based kickstart servers. Nor am I familiar with squid/apache and their complexities. Reviews of /var/log/messages on the kickstart server show only normal DHCP handshaking. No DNS, DHCP or NFS errors. Any suggestions on what I can do to temporarily elevate the volume of messages those services provide into syslog, or some other log file for review for problems that I'm not aware of yet??? Any suggestions on what I can do to further troubleshoot this NFS mount problem? R, -Joe -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.davison at computer.org Thu Nov 8 17:29:20 2007 From: s.davison at computer.org (s.davison at computer.org) Date: Thu, 08 Nov 2007 17:29:20 +0000 Subject: More on NFS problem Message-ID: >-----Original Message----- >From: Joe_Wulf [mailto:Joe_Wulf at yahoo.com] >Sent: Thursday, November 8, 2007 12:45 PM >To: kickstart-list at redhat.com >Subject: More on NFS problem > >The anaconda portions of the boot (with DHCP and tftp) go very well. I can see in >VC3 and VC4 that the booted system gets all the right network attributes and have >carefully verified them (hostname, IP, GW, dns, NM, broadcast, network, >next_server, and domain). In VC3, eventually, I get the error message "reverse >name lookup failed", then it says "failed to mount nfs source". It displays a url >and file location, both of which are, in fact, correct. Efforts at toying with >various anaconda options for the pxeconfig isolinux file provide no improvement.......................... ................................. The problem sounds something like the one described in... http://www.redhat.com/archives/kickstart-list/2005-November/msg00034.html Stowe Davison From Joe_Wulf at yahoo.com Fri Nov 9 04:02:25 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Thu, 8 Nov 2007 23:02:25 -0500 Subject: More on NFS problem In-Reply-To: References: Message-ID: Stowe, Thank you for identifying that post. I find it radical to have to go to all the trouble of rebuilding an initrd image for one OS, much less for all the ones I have to work with, just to get it to boot past an NFS problem. I'm still struggling with this. It just floors me that I can totally kickstart a VM to completion on one system, simply register the MAC address in the kickstart server to foster a build on the other physical system (that is the ONLY change) and it NEVER builds. Is anyone besides me using a MAC to virtually build systems? Will updating my kickstart server to Fedora 8 do me any good? Will reverting back to something like Fedora Core 4 or Fedora Core 5, be any better? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of s.davison at computer.org Sent: Thursday, November 08, 2007 12:29 To: Discussion list about Kickstart Subject: Re: More on NFS problem The problem sounds something like the one described in... http://www.redhat.com/archives/kickstart-list/2005-November/msg00034.html Stowe Davison From debian at herakles.homelinux.org Fri Nov 9 04:16:35 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 09 Nov 2007 13:16:35 +0900 Subject: More on NFS problem In-Reply-To: References: Message-ID: <4733DF23.90109@herakles.homelinux.org> Joe_Wulf wrote: > Stowe, > > Thank you for identifying that post. I find it radical to have to go to all the > trouble of rebuilding an initrd image for one OS, much less for all the ones I > have to work with, just to get it to boot past an NFS problem. Stowe was trying to help you; I find the tone of your response and the fact you've addressed him personally offensive. > > I'm still struggling with this. It just floors me that I can totally kickstart a > VM to completion on one system, simply register the MAC address in the kickstart > server to foster a build on the other physical system (that is the ONLY change) > and it NEVER builds. Stowe says "it sounds something like...." It's an old post, that problem should not occur now. Why don't you just settle down and apply the advice there to the extent you can, and see whether it helps? Do that, and you're closer to fixing the problem. > > Is anyone besides me using a MAC to virtually build systems? > > Will updating my kickstart server to Fedora 8 do me any good? Try it and see. > > Will reverting back to something like Fedora Core 4 or Fedora Core 5, be any > better? Bear in mind that the post Stowe referred to is much older than those, and that they're no longer supported. > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of s.davison at computer.org > Sent: Thursday, November 08, 2007 12:29 > To: Discussion list about Kickstart > Subject: Re: More on NFS problem > > > > The problem sounds something like the one described in... > http://www.redhat.com/archives/kickstart-list/2005-November/msg00034.html > > Stowe Davison > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- 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 Please do not reply off-list From Joe_Wulf at yahoo.com Fri Nov 9 05:28:55 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Fri, 9 Nov 2007 00:28:55 -0500 Subject: More on NFS problem In-Reply-To: <4733DF23.90109@herakles.homelinux.org> References: <4733DF23.90109@herakles.homelinux.org> Message-ID: John, I apologize, John, since my bluntness has offended you. This is a technical forum where I've raised questions, issues and sought to help others, too. I am technically experienced, professional and seeking to associate and collaborate with the same kind of folks. I'm driven and motivated to be clear as well as succeed. I've been comfortable for many years now in presenting ideas, accepting/reviewing the ideas of others and offering constructive criticism, as well as accepting theirs in return---a matter of professionalism, as I've come to learn. I've banged my head for the last 22 or 23 days straight (since I got this MacPro, thru work) on the problems I've identified, with an intent to achieve success, typically staying up until 2 or 3 am, then still going to work. I've read every page on the Fedora anaconda/kickstart wiki, tried multitudes of combinations (as scientifically and methodically as I possibly can). I've posted questions on Apple/MacPro, VMware, ITToolBox forums, and then some others, too. What I have desired is to get feedback from those that have dealt with this specific problem and who didn't resolve it with solutions that ranged in other directions. I've been specifically seeking a method to resolve the NFS mount problem on this system. Or, at least advice directed at troubleshooting it. Maybe, I'm expecting too much. I've logically presented a detailed narrative, several times, of exactly what I've done, what the organization is like, what pieces/parts I've got, what I'm doing with them, what success I've achieved, and where this is breaking down at. Pretty much in the way I know from experience good technicians want to see the problem description, as it allows them to laser in, based on their experience, on just what the right solution is. Maybe, I've not been reaching the right person. What I know I cannot do is go back to work and offer my customer a solution radical from their way of doing business. I'm encountering some pretty unique difficulties and soliciting for support from the multitudes who have done this far more that I have. I have spent a lot of time searching/reading, actively seeking a description of this problem somewhere, and where a solution has been described (or at least enough of something I can troubleshoot with and/or implement). Searches for even basic phrases, such as those I've previously reported have not turned up something sufficiently similar to my problem, much less with a solution. My experience tells me that massaging/rolling unique initrd file images exponentially aggravates my relatively good solution set. Rerolling one initrd.img for one OS still has to then be subsequently tested against a large selection of hardware and end-use implementations, configurations, etc... When I am familiar with all that I'm already doing---I just need to get past this darn NFS problem. My time was supposed to be focused, not on troubleshooting/solving an intransient NFS problem, but on rolling up specific scripts and app-builds in the kickstart %post section and beyond. I'm WAY behind on that. Thank you for the feedback. I'll accept it, with an eye towards improving in the future, away from being offensive. Being a gentleman is and always has been my demeanor. It is strange and difficult to understand what another intends sometimes without asking them, or knowing them. Especially/doubly difficult when the only medium is text words/messages. Anyone else have thoughts on this? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield Sent: Thursday, November 08, 2007 23:17 To: Discussion list about Kickstart Subject: Re: More on NFS problem Joe_Wulf wrote: > Stowe, > > Thank you for identifying that post. I find it radical to have to go to all the > trouble of rebuilding an initrd image for one OS, much less for all the ones I > have to work with, just to get it to boot past an NFS problem. Stowe was trying to help you; I find the tone of your response and the fact you've addressed him personally offensive. > > I'm still struggling with this. It just floors me that I can totally kickstart a > VM to completion on one system, simply register the MAC address in the kickstart > server to foster a build on the other physical system (that is the ONLY change) > and it NEVER builds. Stowe says "it sounds something like...." It's an old post, that problem should not occur now. Why don't you just settle down and apply the advice there to the extent you can, and see whether it helps? Do that, and you're closer to fixing the problem. > > Is anyone besides me using a MAC to virtually build systems? > > Will updating my kickstart server to Fedora 8 do me any good? Try it and see. > > Will reverting back to something like Fedora Core 4 or Fedora Core 5, be any > better? Bear in mind that the post Stowe referred to is much older than those, and that they're no longer supported. > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of s.davison at computer.org > Sent: Thursday, November 08, 2007 12:29 > To: Discussion list about Kickstart > Subject: Re: More on NFS problem > > > > The problem sounds something like the one described in... > http://www.redhat.com/archives/kickstart-list/2005-November/msg00034.html > > Stowe Davison > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- 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 Please do not reply off-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From debian at herakles.homelinux.org Fri Nov 9 06:15:11 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 09 Nov 2007 15:15:11 +0900 Subject: More on NFS problem In-Reply-To: References: <4733DF23.90109@herakles.homelinux.org> Message-ID: <4733FAEF.7040904@herakles.homelinux.org> Joe_Wulf wrote: > John, > > I apologize, John, since my bluntness has offended you. > I accept all that you say, and I now understand your frustration. Now, if you read through my reply and respond to each point in turn, you can address the other points I raised. Quite possibly I won't find your solution, but perhaps with some more, to the point, responses someone will get you there. It might be that you need to do something to help sort out the problem that won't be acceptable as a final solution, but if it's plausible, it's worth trying. Hacking on an initrd is no big deal, these days it can be a CPIO archive, compressed (with gzip) or not. btw Perhaps you should ask on which ever list applies to your distro? Lots of folk there use kickstart too. > > Anyone else have thoughts on this? > > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield > Sent: Thursday, November 08, 2007 23:17 > To: Discussion list about Kickstart > Subject: Re: More on NFS problem > > Joe_Wulf wrote: >> Stowe, >> >> Thank you for identifying that post. I find it radical to have to go to all > the >> trouble of rebuilding an initrd image for one OS, much less for all the ones I >> have to work with, just to get it to boot past an NFS problem. > > Stowe was trying to help you; I find the tone of your response and the > fact you've addressed him personally offensive. > >> I'm still struggling with this. It just floors me that I can totally kickstart > a >> VM to completion on one system, simply register the MAC address in the > kickstart >> server to foster a build on the other physical system (that is the ONLY change) >> and it NEVER builds. > > Stowe says "it sounds something like...." It's an old post, that problem > should not occur now. > > Why don't you just settle down and apply the advice there to the extent > you can, and see whether it helps? > > Do that, and you're closer to fixing the problem. > >> Is anyone besides me using a MAC to virtually build systems? >> >> Will updating my kickstart server to Fedora 8 do me any good? > > Try it and see. >> Will reverting back to something like Fedora Core 4 or Fedora Core 5, be any >> better? > > Bear in mind that the post Stowe referred to is much older than those, > and that they're no longer supported. > >> R, >> -Joe Wulf, CISSP, USN(RET) >> Senior IA Engineer >> ProSync Technology Group, LLC >> www.prosync.com >> >> -----Original Message----- >> From: kickstart-list-bounces at redhat.com >> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of s.davison at computer.org >> Sent: Thursday, November 08, 2007 12:29 >> To: Discussion list about Kickstart >> Subject: Re: More on NFS problem >> >> >> >> The problem sounds something like the one described in... >> http://www.redhat.com/archives/kickstart-list/2005-November/msg00034.html >> >> Stowe Davison >> >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > > -- 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 Please do not reply off-list From Joe_Wulf at yahoo.com Fri Nov 9 06:34:01 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Fri, 9 Nov 2007 01:34:01 -0500 Subject: More on NFS problem In-Reply-To: <4733FAEF.7040904@herakles.homelinux.org> References: <4733DF23.90109@herakles.homelinux.org> <4733FAEF.7040904@herakles.homelinux.org> Message-ID: John, Thank you. I probably could dig into initrd.img hacking, but the subsequent rounds of testing to handle scenarios of employment don't seem to make it worth doing when compared with my targets/goals/objectives. My customer tends to look for hardware and operating systems that work right out of the box, with the end-implementation being the holy-rolled magic bean. You'd mentioned about an old post, and from that, its "... something that should not occur now". I agree. I would have thought these versions of the OS, being years later, would have had such problems nuked. And again, rolling up many initrd images simply didn't seem like a practical application of time. Would still like to know if anyone is using a MacPro, with Windoze and VMware installed to kickstart build systems. I'd asked about migrating my kickstart server to Fedora 8 for a couple of reasons. I've heard that it might actually be more stable and reliable (like for avoiding the kinds of problems I have) by using an older OS for the kickstart'er. So along those lines I'd expected to hear from folks who've experience and/or an opinion on that, based on their experiences in the past. Further, I wanted to save the time installing Fedora 8 if someone's experience told them it would be a waste of time. Sure, I can try it, and see what I get. And with the exhaustion of other viable things to test/try, might be worth it. I think I got everything. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield Sent: Friday, November 09, 2007 01:15 To: Discussion list about Kickstart Subject: Re: More on NFS problem Joe_Wulf wrote: > John, > > I apologize, John, since my bluntness has offended you. > I accept all that you say, and I now understand your frustration. Now, if you read through my reply and respond to each point in turn, you can address the other points I raised. Quite possibly I won't find your solution, but perhaps with some more, to the point, responses someone will get you there. It might be that you need to do something to help sort out the problem that won't be acceptable as a final solution, but if it's plausible, it's worth trying. Hacking on an initrd is no big deal, these days it can be a CPIO archive, compressed (with gzip) or not. btw Perhaps you should ask on which ever list applies to your distro? Lots of folk there use kickstart too. From debian at herakles.homelinux.org Fri Nov 9 08:36:39 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 09 Nov 2007 17:36:39 +0900 Subject: More on NFS problem In-Reply-To: References: <4733DF23.90109@herakles.homelinux.org> <4733FAEF.7040904@herakles.homelinux.org> Message-ID: <47341C17.8070406@herakles.homelinux.org> Joe_Wulf wrote: > John, > > Thank you. > > I probably could dig into initrd.img hacking, but the subsequent rounds of > testing to handle scenarios of employment don't seem to make it worth doing when > compared with my targets/goals/objectives. My customer tends to look for > hardware and operating systems that work right out of the box, with the > end-implementation being the holy-rolled magic bean. If you can't make an effort to help solve your own problem, then you can hardly expect anyone else to do so. > Would still like to know if anyone is using a MacPro, with Windoze and VMware > installed to kickstart build systems. > Probably, if any regular reader of this list has, they'd have spoken up by now. Good luck, -- 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 Please do not reply off-list From Gordon.Keegan at fmr.com Fri Nov 9 14:40:25 2007 From: Gordon.Keegan at fmr.com (Keegan, Gordon) Date: Fri, 9 Nov 2007 09:40:25 -0500 Subject: More on NFS problem References: <4733DF23.90109@herakles.homelinux.org><4733FAEF.7040904@herakles.homelinux.org> Message-ID: <942A778F73A72141889C1F53A8EAA1C53A6496@MSGMMKCLM2WIN.DMN1.FMR.COM> Joe, (apologies if this has already been suggested or discounted...) For what it's worth, we initially migrated away from an NFS-based install back in the RedHat 7.2/AS 2.1 days when the NFS drivers took up too much space on the boot floppy and we needed to add other NIC drivers. We have had success ever since using the http install method. It would be a fairly simple change in the ks.cfg file to change the "nfs --server a.b.c.d --dir /x/y/z" line to a "url --url http://server/install_dir " line, with slightly more involved work in the postinstall if you need to convert NFS-accessed data to "wget"-accessed data. Gordon Keegan -----Original Message----- From: Joe_Wulf [mailto:Joe_Wulf at yahoo.com] Sent: Friday, November 09, 2007 1:34 AM To: 'Discussion list about Kickstart' Subject: RE: More on NFS problem John, Thank you. I probably could dig into initrd.img hacking, but the subsequent rounds of testing to handle scenarios of employment don't seem to make it worth doing when compared with my targets/goals/objectives. My customer tends to look for hardware and operating systems that work right out of the box, with the end-implementation being the holy-rolled magic bean. You'd mentioned about an old post, and from that, its "... something that should not occur now". I agree. I would have thought these versions of the OS, being years later, would have had such problems nuked. And again, rolling up many initrd images simply didn't seem like a practical application of time. Would still like to know if anyone is using a MacPro, with Windoze and VMware installed to kickstart build systems. I'd asked about migrating my kickstart server to Fedora 8 for a couple of reasons. I've heard that it might actually be more stable and reliable (like for avoiding the kinds of problems I have) by using an older OS for the kickstart'er. So along those lines I'd expected to hear from folks who've experience and/or an opinion on that, based on their experiences in the past. Further, I wanted to save the time installing Fedora 8 if someone's experience told them it would be a waste of time. Sure, I can try it, and see what I get. And with the exhaustion of other viable things to test/try, might be worth it. I think I got everything. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield Sent: Friday, November 09, 2007 01:15 To: Discussion list about Kickstart Subject: Re: More on NFS problem Joe_Wulf wrote: > John, > > I apologize, John, since my bluntness has offended you. > I accept all that you say, and I now understand your frustration. Now, if you read through my reply and respond to each point in turn, you can address the other points I raised. Quite possibly I won't find your solution, but perhaps with some more, to the point, responses someone will get you there. It might be that you need to do something to help sort out the problem that won't be acceptable as a final solution, but if it's plausible, it's worth trying. Hacking on an initrd is no big deal, these days it can be a CPIO archive, compressed (with gzip) or not. btw Perhaps you should ask on which ever list applies to your distro? Lots of folk there use kickstart too. From acapotorto at lastminute.com Fri Nov 9 17:01:09 2007 From: acapotorto at lastminute.com (Anibal Capotorto) Date: Fri, 9 Nov 2007 17:01:09 +0000 Subject: nic problems on hp servers Message-ID: Hi all, I have to build some x86_64 boxes (HP Proliant DL585 G2) and the kickstart doesn't recognize the onboard nics Ive seen 2 "solutions so far" that i've tried one is changing in the bios a feature that says something along the lines of Linux x86_64 HPET (set to enable) and also using pci=nommconf (and pci=conf1) as kernel parameters all with no joy if I install the OS from the ISOS it wil work no problem anyway that you can help me wll be appreciated Saludos Anibal "Bicho[DBZ]" capotorto From Pablo.Iranzo at redhat.com Fri Nov 9 17:09:54 2007 From: Pablo.Iranzo at redhat.com (=?UTF-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Fri, 9 Nov 2007 18:09:54 +0100 (CET) Subject: nic problems on hp servers In-Reply-To: References: Message-ID: Anibal, and after instalation from CD media, do you have network support? Maybe it's something related with the updates.img not being loaded or not containing what you need to get your server's NIC online. Do that check, and let us know. Pay attention to the updates.img at anaconda's logs... Regards Pablo On Fri, 9 Nov 2007, Anibal Capotorto wrote: > Hi all, I have to build some x86_64 boxes (HP Proliant DL585 G2) and > the kickstart doesn't recognize the onboard nics > > Ive seen 2 "solutions so far" that i've tried > > one is changing in the bios a feature that says something along the > lines of > > Linux x86_64 HPET (set to enable) > > and also using pci=nommconf (and pci=conf1) as kernel parameters all > with no joy > > if I install the OS from the ISOS it wil work no problem > > anyway that you can help me wll be appreciated > > > Saludos > Anibal "Bicho[DBZ]" capotorto > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From acapotorto at lastminute.com Fri Nov 9 17:18:10 2007 From: acapotorto at lastminute.com (Anibal Capotorto) Date: Fri, 9 Nov 2007 17:18:10 +0000 Subject: nic problems on hp servers In-Reply-To: References: Message-ID: <7B1F59AD-C14D-4F2B-A1D5-EF15DF2CD8D6@lastminute.com> I do have nics when the os is installed and on the CD installation I get asked about how to configure the 4 nics that box has thing is.... to kickstart the box I only have the vmlinuz and the initrd.img no updates... and the updates can't be downloaded because .. it's just not nics to do that if there's a way to put the updates.img on the 1st stages and you have a link to do that , please post it here, I will research in the meantime Saludos Anibal "Bicho[DBZ]" capotorto On 9 Nov 2007, at 17:09, Pablo Iranzo G?mez wrote: > Anibal, and after instalation from CD media, do you have > network > support? > > Maybe it's something related with the updates.img not being > loaded > or not containing what you need to get your server's NIC online. > > Do that check, and let us know. Pay attention to the > updates.img > at anaconda's logs... > > Regards > Pablo > > > > On Fri, 9 Nov 2007, Anibal Capotorto wrote: > > > Hi all, I have to build some x86_64 boxes (HP Proliant DL585 G2) and > > the kickstart doesn't recognize the onboard nics > > > > Ive seen 2 "solutions so far" that i've tried > > > > one is changing in the bios a feature that says something along the > > lines of > > > > Linux x86_64 HPET (set to enable) > > > > and also using pci=nommconf (and pci=conf1) as kernel parameters all > > with no joy > > > > if I install the OS from the ISOS it wil work no problem > > > > anyway that you can help me wll be appreciated > > > > > > Saludos > > Anibal "Bicho[DBZ]" capotorto > > > > > > > > _______________________________________________ > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdavis at hess.com Fri Nov 9 17:55:36 2007 From: jdavis at hess.com (Davis, Jeff (Houston)) Date: Fri, 9 Nov 2007 11:55:36 -0600 Subject: (no subject) Message-ID: <0973EB3CBD819F4DB7FD7DD2B482BFB201CD3C6A@HACSSEX006.ihess.com> Jeff Davis Hess Corporation Exploration and Production Global IT Infrastructure Technical Computing Houston, Texas jdavis at hess.com 832 212-2936 (mobile) Sent by BlackBerry Wireless Email From mytechacc at gmail.com Fri Nov 9 18:47:47 2007 From: mytechacc at gmail.com (MyTechAccount) Date: Fri, 9 Nov 2007 13:47:47 -0500 Subject: kssendmac flipping eth port ID? Message-ID: why is it that the kssendmac argument sends a flipped ethX address ? key=HTTP_X_RHN_PROVISIONING_MAC_0 value=eth1 00:17:A4:8E:E2:41 key=HTTP_X_RHN_PROVISIONING_MAC_1 value=eth0 00:17:A4:8E:E2:42 is this a bug or feature? thanks -zaq From Chip.Shabazian at bankofamerica.com Fri Nov 9 18:56:02 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 09 Nov 2007 10:56:02 -0800 Subject: kssendmac flipping eth port ID? In-Reply-To: References: Message-ID: Are you using RHEL 4 update 1 through 4? If so, there is a known bus remuneration issue that is corrected in update 5+. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of MyTechAccount Sent: Friday, November 09, 2007 10:48 AM To: kickstart-list at redhat.com Subject: kssendmac flipping eth port ID? why is it that the kssendmac argument sends a flipped ethX address ? key=HTTP_X_RHN_PROVISIONING_MAC_0 value=eth1 00:17:A4:8E:E2:41 key=HTTP_X_RHN_PROVISIONING_MAC_1 value=eth0 00:17:A4:8E:E2:42 is this a bug or feature? thanks -zaq _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Pablo.Iranzo at redhat.com Sat Nov 10 10:26:27 2007 From: Pablo.Iranzo at redhat.com (=?UTF-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Sat, 10 Nov 2007 11:26:27 +0100 (CET) Subject: nic problems on hp servers In-Reply-To: <7B1F59AD-C14D-4F2B-A1D5-EF15DF2CD8D6@lastminute.com> References: <7B1F59AD-C14D-4F2B-A1D5-EF15DF2CD8D6@lastminute.com> Message-ID: Ok, then you'll need to pack those drivers on a custom initrd and insmod them before continue with the installation... There seems to be some questions regarding this in previous posts, do a site:redhat.com search at google for "packing drivers into anaconda" and equivalent senteces, and you'll get some pointers Regards Pablo -- 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?? On Fri, 9 Nov 2007, Anibal Capotorto wrote: > I do have nics when the os is installed and on the CD installation I > get asked about how to configure the 4 nics that box has > > thing is.... to kickstart the box I only have the vmlinuz and the > initrd.img no updates... and the updates can't be downloaded > because .. it's just not nics to do that > > if there's a way to put the updates.img on the 1st stages and you have > a link to do that , please post it here, I will research in the meantime > > Saludos > Anibal "Bicho[DBZ]" capotorto > > > > > On 9 Nov 2007, at 17:09, Pablo Iranzo G?mez wrote: > > > Anibal, and after instalation from CD media, do you have > > network > > support? > > > > Maybe it's something related with the updates.img not being > > loaded > > or not containing what you need to get your server's NIC online. > > > > Do that check, and let us know. Pay attention to the > > updates.img > > at anaconda's logs... > > > > Regards > > Pablo > > > > > > > > On Fri, 9 Nov 2007, Anibal Capotorto wrote: > > > > > Hi all, I have to build some x86_64 boxes (HP Proliant DL585 G2) and > > > the kickstart doesn't recognize the onboard nics > > > > > > Ive seen 2 "solutions so far" that i've tried > > > > > > one is changing in the bios a feature that says something along the > > > lines of > > > > > > Linux x86_64 HPET (set to enable) > > > > > > and also using pci=nommconf (and pci=conf1) as kernel parameters all > > > with no joy > > > > > > if I install the OS from the ISOS it wil work no problem > > > > > > anyway that you can help me wll be appreciated > > > > > > > > > Saludos > > > Anibal "Bicho[DBZ]" capotorto > > > > > > > > > > > > _______________________________________________ > > > Kickstart-list mailing list > > > Kickstart-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > From acapotorto at lastminute.com Mon Nov 12 11:05:37 2007 From: acapotorto at lastminute.com (Anibal Capotorto) Date: Mon, 12 Nov 2007 11:05:37 +0000 Subject: nic problems on hp servers In-Reply-To: References: <7B1F59AD-C14D-4F2B-A1D5-EF15DF2CD8D6@lastminute.com> Message-ID: <80E210E8-A210-4BE5-B729-5157A2B64E59@lastminute.com> I (out if luck|) found that in this particular case I was adding acpi=off as a kernel parameter, remiving it resulted in the box installing normally. thanks for the help and hope the solution can help more ppl. Saludos Anibal "Bicho[DBZ]" capotorto On 10 Nov 2007, at 10:26, Pablo Iranzo G?mez wrote: > Ok, then you'll need to pack those drivers on a custom > initrd and > insmod them before continue with the installation... > > There seems to be some questions regarding this in previous > posts, > do a site:redhat.com search at google for "packing drivers into > anaconda" > and equivalent senteces, and you'll get some pointers > > Regards > Pablo > > > > -- > 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? > > On Fri, 9 Nov 2007, Anibal Capotorto wrote: > > > I do have nics when the os is installed and on the CD installation I > > get asked about how to configure the 4 nics that box has > > > > thing is.... to kickstart the box I only have the vmlinuz and the > > initrd.img no updates... and the updates can't be downloaded > > because .. it's just not nics to do that > > > > if there's a way to put the updates.img on the 1st stages and you > have > > a link to do that , please post it here, I will research in the > meantime > > > > Saludos > > Anibal "Bicho[DBZ]" capotorto > > > > > > > > > > On 9 Nov 2007, at 17:09, Pablo Iranzo Gmez wrote: > > > > > Anibal, and after instalation from CD media, do you have > > > network > > > support? > > > > > > Maybe it's something related with the updates.img not > being > > > loaded > > > or not containing what you need to get your server's NIC online. > > > > > > Do that check, and let us know. Pay attention to the > > > updates.img > > > at anaconda's logs... > > > > > > Regards > > > Pablo > > > > > > > > > > > > On Fri, 9 Nov 2007, Anibal Capotorto wrote: > > > > > > > Hi all, I have to build some x86_64 boxes (HP Proliant DL585 > G2) and > > > > the kickstart doesn't recognize the onboard nics > > > > > > > > Ive seen 2 "solutions so far" that i've tried > > > > > > > > one is changing in the bios a feature that says something > along the > > > > lines of > > > > > > > > Linux x86_64 HPET (set to enable) > > > > > > > > and also using pci=nommconf (and pci=conf1) as kernel > parameters all > > > > with no joy > > > > > > > > if I install the OS from the ISOS it wil work no problem > > > > > > > > anyway that you can help me wll be appreciated > > > > > > > > > > > > Saludos > > > > Anibal "Bicho[DBZ]" capotorto > > > > > > > > > > > > > > > > _______________________________________________ > > > > Kickstart-list mailing list > > > > Kickstart-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > > > > > _______________________________________________ > > > Kickstart-list mailing list > > > Kickstart-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alessiof at gmail.com Thu Nov 15 10:08:48 2007 From: alessiof at gmail.com (Alessio Focardi) Date: Thu, 15 Nov 2007 11:08:48 +0100 Subject: cdrom option of Fedora 8 results in anaconda crash Message-ID: <8bc972b70711150208na848393vb7ddfba8237221b6@mail.gmail.com> Hi all, I have a ks file that is working with F7 but if used with F8 results in an anaconda crash. I pinpointed the issue to the "cdrom" option, removing it the installation asks for the source and everything else (except for the post install "eject") is working as usual. Anyone else got this problem ? Tnx for any help! Alessio Focardi Interconnessioni Italy From clumens at redhat.com Thu Nov 15 15:40:21 2007 From: clumens at redhat.com (Chris Lumens) Date: Thu, 15 Nov 2007 10:40:21 -0500 Subject: cdrom option of Fedora 8 results in anaconda crash In-Reply-To: <8bc972b70711150208na848393vb7ddfba8237221b6@mail.gmail.com> References: <8bc972b70711150208na848393vb7ddfba8237221b6@mail.gmail.com> Message-ID: <20071115154018.GE3490@exeter.boston.redhat.com> > I have a ks file that is working with F7 but if used with F8 results > in an anaconda crash. > > I pinpointed the issue to the "cdrom" option, removing it the > installation asks for the source and everything else (except for the > post install "eject") is working as usual. > > Anyone else got this problem ? Yes, this is a known bug in pykickstart that is fixed in 1.19-1 in f8-updates. - Chris From kanarip at kanarip.com Thu Nov 15 15:54:30 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Thu, 15 Nov 2007 16:54:30 +0100 Subject: cdrom option of Fedora 8 results in anaconda crash In-Reply-To: <20071115154018.GE3490@exeter.boston.redhat.com> References: <8bc972b70711150208na848393vb7ddfba8237221b6@mail.gmail.com> <20071115154018.GE3490@exeter.boston.redhat.com> Message-ID: <473C6BB6.4030806@kanarip.com> Chris Lumens wrote: >> I have a ks file that is working with F7 but if used with F8 results >> in an anaconda crash. >> >> I pinpointed the issue to the "cdrom" option, removing it the >> installation asks for the source and everything else (except for the >> post install "eject") is working as usual. >> >> Anyone else got this problem ? > > Yes, this is a known bug in pykickstart that is fixed in 1.19-1 in > f8-updates. > /me notes that this fix is going to end up on a Fedora Unity Re-Spin. Kind regards, Jeroen van Meeuwen From alessiof at gmail.com Thu Nov 15 16:07:58 2007 From: alessiof at gmail.com (Alessio Focardi) Date: Thu, 15 Nov 2007 17:07:58 +0100 Subject: cdrom option of Fedora 8 results in anaconda crash In-Reply-To: <473C6BB6.4030806@kanarip.com> References: <8bc972b70711150208na848393vb7ddfba8237221b6@mail.gmail.com> <20071115154018.GE3490@exeter.boston.redhat.com> <473C6BB6.4030806@kanarip.com> Message-ID: <8bc972b70711150807r709d8c19j748dd7990cc126b3@mail.gmail.com> > >> I have a ks file that is working with F7 but if used with F8 results > >> in an anaconda crash. > > Yes, this is a known bug in pykickstart that is fixed in 1.19-1 in > > f8-updates. > /me notes that this fix is going to end up on a Fedora Unity Re-Spin. Tnx for the support! What's the fastest way to repack the update in the installation iso? Unfortunately I can't wait for respins ... Alessio Focardi Interconnessioni Italy From kanarip at kanarip.com Thu Nov 15 20:20:56 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Thu, 15 Nov 2007 21:20:56 +0100 Subject: cdrom option of Fedora 8 results in anaconda crash In-Reply-To: <8bc972b70711150807r709d8c19j748dd7990cc126b3@mail.gmail.com> References: <8bc972b70711150208na848393vb7ddfba8237221b6@mail.gmail.com> <20071115154018.GE3490@exeter.boston.redhat.com> <473C6BB6.4030806@kanarip.com> <8bc972b70711150807r709d8c19j748dd7990cc126b3@mail.gmail.com> Message-ID: <473CAA28.6020803@kanarip.com> Alessio Focardi wrote: >>>> I have a ks file that is working with F7 but if used with F8 results >>>> in an anaconda crash. > >>> Yes, this is a known bug in pykickstart that is fixed in 1.19-1 in >>> f8-updates. > >> /me notes that this fix is going to end up on a Fedora Unity Re-Spin. > > Tnx for the support! > > What's the fastest way to repack the update in the installation iso? > Unfortunately I can't wait for respins ... > Use Revisor, optionally combined with the configuration used by Fedora Unity, available from git://git.kanarip.com/unityspin Mind that we have not yet tweaked our F8 config for a respin, as we are currently tracking what bugs exactly have been solved in F8. Kind regards, Jeroen van Meeuwen -kanarip From Vivek.Kalia at Euroclear.com Fri Nov 16 22:02:53 2007 From: Vivek.Kalia at Euroclear.com (Vivek.Kalia at Euroclear.com) Date: Fri, 16 Nov 2007 22:02:53 +0000 Subject: Vivek Kalia is out of the office. Message-ID: I will be out of the office starting 16/11/2007 and will not return until 19/11/2007. Please contact Mario Nevrides, Adam Burton or James Connolly in my abscence. This e-mail message, including any attachments transmitted with it, is CONFIDENTIAL and may contain legally privileged information. This message is intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient you should not read, copy, distribute, disclose or otherwise use this information. If you have received this message in error, please notify us immediately and delete it from your system. The integrity and security of this message cannot be guaranteed and it may be subject to data corruption and unauthorised amendment, for which we accept no liability. Euroclear reserves the right to retain email messages on its systems and to the extent and under circumstances permitted by applicable law, to monitor and intercept email messages to and from its systems. Euroclear is the marketing name for the Euroclear System, Euroclear plc, Euroclear SA/NV and their affiliates. Please visit our website: http://www.euroclear.com From grgoffe at yahoo.com Sat Nov 17 12:10:57 2007 From: grgoffe at yahoo.com (George R Goffe) Date: Sat, 17 Nov 2007 04:10:57 -0800 (PST) Subject: A possible problem with kickstart. Message-ID: <276674.63040.qm@web90406.mail.mud.yahoo.com> Howdy, I have been trying to kickstart my systems and am having troubles with a usb-key. The key is recognized as /dev/sda. My install drive is /dev/cciss/c0d0. When it comes to placing the MBR for Grub, anaconda seems to want/insist on placing it on /dev/sda. This leads to a problem when booting since I boot from /dev/cciss/c0d0p0 since that partition has NO MBR on it. I've tried ignoredisk --drives=sda and bootloader --driveorder=cciss/c0d0 without affecting the behavior described above. Am I missing something here or is this a bug? Regards and THANKS for your help, George... ===== _/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/ _/_/_/_/ _/_/_/_/ ----- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/ _/_/_/_/ _/ _/ _/_/_/ _/ _/_/ _/_/_/_/ ----- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/ ----- "It's not what you know that hurts you, It's what you know that ain't so." Will Rogers ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From squid at oranged.to Sat Nov 17 12:15:27 2007 From: squid at oranged.to (Jimmy Stewpot) Date: Sat, 17 Nov 2007 12:15:27 +0000 Subject: Redhat Kickstart directory structure Message-ID: <473EDB5F.1050602@oranged.to> Hi, I am wondering how I would go about having both the AS and ES RPM's in the same directory structure for EL3/4. Is it possible or do I need to have them in separate folders. Any advice would be great. Regards, Jimmy From jos at xos.nl Sat Nov 17 12:23:37 2007 From: jos at xos.nl (Jos Vos) Date: Sat, 17 Nov 2007 13:23:37 +0100 Subject: Redhat Kickstart directory structure In-Reply-To: <473EDB5F.1050602@oranged.to> References: <473EDB5F.1050602@oranged.to> Message-ID: <20071117122337.GA31126@jasmine.xos.nl> On Sat, Nov 17, 2007 at 12:15:27PM +0000, Jimmy Stewpot wrote: > I am wondering how I would go about having both the AS and ES RPM's in > the same directory structure for EL3/4. Is it possible or do I need to > have them in separate folders. Any advice would be great. The AS and ES RPMs are the same, except for the redhat-release, comps and anaconda-product packages in RHEL4. For RHEL3 I'm not 100% sure about this list, I have to check. Having two trees and hardlinking all RPMs that are the same (just make a script for doing that) gives you only a minimal overhead. -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From gwaugh at frontstreetnetworks.com Sat Nov 17 13:19:00 2007 From: gwaugh at frontstreetnetworks.com (Gerald Waugh) Date: Sat, 17 Nov 2007 07:19:00 -0600 Subject: Problem with installing system using ICH8 Message-ID: <032901c8291c$6fdf2fe0$0101a8c0@systemax> We are trying to run a CentOS 4.5 install on Tyan GT14 Sata Hard Drives are not found. We can install on Tyan GS14 and then move the drives to the GT14 and the system boots OK. Chipset on the GT14 is; Intel Q965 (Broadwater) MCH SMSC SCH5027 Super I/O SMSC EMCD103HWM - Gerald Waugh http://frontstreetnetworks.com Front Street Networks 4604 Fern Ave Shreveport, LA 71105-3118 V: 318-862-3575/3577 F: 318-862-3576 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From gwaugh at frontstreetnetworks.com Sat Nov 17 14:04:16 2007 From: gwaugh at frontstreetnetworks.com (Gerald Waugh) Date: Sat, 17 Nov 2007 08:04:16 -0600 Subject: Problem with installing system using ICH8 In-Reply-To: <032901c8291c$6fdf2fe0$0101a8c0@systemax> Message-ID: <033501c82922$c15fd850$0101a8c0@systemax> > We are trying to run a CentOS 4.5 install on Tyan GT14 > Sata Hard Drives are not found. > > We can install on Tyan GS14 and then move the drives to the > GT14 and the system boots OK. > > Chipset on the GT14 is; > Intel Q965 (Broadwater) MCH > SMSC SCH5027 Super I/O > SMSC EMCD103HWM > I did get CentOS 4.0 to attempt an install. by entering at the boot prompt linux generic-ide=1 But, got "kernel panic" after the install - Gerald -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From ator1158 at xs4all.nl Sat Nov 17 18:17:52 2007 From: ator1158 at xs4all.nl (John van Zantvoort) Date: Sat, 17 Nov 2007 19:17:52 +0100 (CET) Subject: Redhat Kickstart directory structure Message-ID: <24366.77.251.86.117.1195323472.squirrel@webmail.xs4all.nl> use the 'hardlink' tool, minimized storage overhead and is dead easy to use. > On Sat, Nov 17, 2007 at 12:15:27PM +0000, Jimmy Stewpot wrote: > >> I am wondering how I would go about having both the AS and ES RPM's in >> the same directory structure for EL3/4. Is it possible or do I need to >> have them in separate folders. Any advice would be great. > > The AS and ES RPMs are the same, except for the redhat-release, > comps and anaconda-product packages in RHEL4. For RHEL3 I'm not > 100% sure about this list, I have to check. > > Having two trees and hardlinking all RPMs that are the same (just make > a script for doing that) gives you only a minimal overhead. > > -- > -- Jos Vos > -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 > -- Amsterdam, The Netherlands | Fax: +31 20 6948204 > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > Met vriendelijke groeten/with kind regards John van Zantvoort --- Paranoia is simply an optimistic outlook on life. GCM d- s+:+ a- C+ UL+++ P+++ L++ E--- W++ N+ o K- w-- O- M- V- PS+ PE- Y+ PGP+ t+ 5 X- R- tv b+ DI++ D+ G e h- r++ y+ From vikumar at redhat.com Tue Nov 20 14:52:12 2007 From: vikumar at redhat.com (Vimal Kumar) Date: Tue, 20 Nov 2007 20:22:12 +0530 Subject: Kickstarting IBM servers Message-ID: <4742F49C.5070409@redhat.com> Hello, I have a scenario in which its not able to do a kickstart on IBM servers, the process halts at the keymap. Tried various alternatives in the kickstart config; gb, uk, us; and also changed the keyboard and language settings. The problem occurs on both x86 or x86_64 bit RHEL5. The IBM Servers are mainly x345s and x346s. Tried Compaq KVMs, HP KVMs, standard Dell PS2 keyboards and other non-brand keyboards... with a mixture of US and UK keymaps. It's not possible to use the keyboard at all during the kickstart process... it's just garbled characters and renders it useless. The ks.cfg is as follows : ----------------------- install nfs --server=X.X.X.X --dir=/kickstart/install-tree/rhel-5 text lang en_US #langsupport --default=en_GB.UTF-8 en_GB.UTF-8 keyboard us keymap us graphical network --device eth0 --bootproto static --ip X.X.X.X --netmask 255.255.254.0 --nameserver X.X.X.X --hostname XY.com firewall --disabled selinux --disabled authconfig --enableshadow --enablemd5 firstboot --disabled timezone Europe/London bootloader --location=mbr --append="rhgb quiet" clearpart --all part /boot --fstype "ext3" --size=100 --ondisk=sda --asprimary part / --fstype "ext3" --size=6144 --ondisk=sda --asprimary part swap --size=2048 --ondisk=sda --asprimary part /var --fstype "ext3" --size=8192 --grow --ondisk=sda part /var/spool/exim/input --fstype "ext3" --size=65536 --grow --ondisk=sdb ------------------------ Any ideas why this is happening. Regards, Vimal Kumar From ebrown at lanl.gov Tue Nov 20 15:39:00 2007 From: ebrown at lanl.gov (Ed Brown) Date: Tue, 20 Nov 2007 08:39:00 -0700 Subject: Kickstarting IBM servers In-Reply-To: <4742F49C.5070409@redhat.com> References: <4742F49C.5070409@redhat.com> Message-ID: <4742FF94.7050908@lanl.gov> I don't see 'keymap' listed as a kickstart option in the docs at: Have you already tried 'keyboard uk', without 'keymap'? Also, 'text' and 'graphical' are mutually exclusive, use one or the other (or leave it out, since graphical is default). -Ed Vimal Kumar wrote: > Hello, > > I have a scenario in which its not able to do a kickstart on IBM > servers, the process halts at the keymap. Tried various alternatives in > the kickstart config; gb, uk, us; and also changed the keyboard and > language settings. The problem occurs on both x86 or x86_64 bit RHEL5. > The IBM Servers are mainly x345s and x346s. Tried Compaq KVMs, HP KVMs, > standard Dell PS2 keyboards and other non-brand keyboards... with a > mixture of US and UK keymaps. It's not possible to use the keyboard at > all during the kickstart process... it's just garbled characters and > renders it useless. > > The ks.cfg is as follows : > > ----------------------- > install > nfs --server=X.X.X.X --dir=/kickstart/install-tree/rhel-5 > text > lang en_US > #langsupport --default=en_GB.UTF-8 en_GB.UTF-8 > keyboard us > keymap us > graphical > network --device eth0 --bootproto static --ip X.X.X.X --netmask > 255.255.254.0 --nameserver X.X.X.X --hostname XY.com > firewall --disabled > selinux --disabled > authconfig --enableshadow --enablemd5 > firstboot --disabled > timezone Europe/London > bootloader --location=mbr --append="rhgb quiet" > clearpart --all > part /boot --fstype "ext3" --size=100 --ondisk=sda --asprimary > part / --fstype "ext3" --size=6144 --ondisk=sda --asprimary > part swap --size=2048 --ondisk=sda --asprimary > part /var --fstype "ext3" --size=8192 --grow --ondisk=sda > part /var/spool/exim/input --fstype "ext3" --size=65536 --grow --ondisk=sdb > ------------------------ > > Any ideas why this is happening. > > Regards, > > Vimal Kumar > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From ks-list at puzzled.xs4all.nl Tue Nov 20 17:10:33 2007 From: ks-list at puzzled.xs4all.nl (Patrick) Date: Tue, 20 Nov 2007 18:10:33 +0100 Subject: Kickstarting IBM servers In-Reply-To: <4742F49C.5070409@redhat.com> References: <4742F49C.5070409@redhat.com> Message-ID: <1195578633.3312.15.camel@luna.puzzled.xs4all.nl> On Tue, 2007-11-20 at 20:22 +0530, Vimal Kumar wrote: > Hello, > > I have a scenario in which its not able to do a kickstart on IBM > servers, the process halts at the keymap. Tried various alternatives in > the kickstart config; gb, uk, us; and also changed the keyboard and > language settings. The problem occurs on both x86 or x86_64 bit RHEL5. > The IBM Servers are mainly x345s and x346s. Tried Compaq KVMs, HP KVMs, > standard Dell PS2 keyboards and other non-brand keyboards... with a > mixture of US and UK keymaps. It's not possible to use the keyboard at > all during the kickstart process... it's just garbled characters and > renders it useless. I use: keyboard us lang en_US The file /usr/lib/python2.2/site-packages/rhpl/keyboard_models.py contains the list of possible keyboards and is part of the rhpl package The file /usr/share/system-config-language/locale-list provides a list of the valid language codes in the first column of each line and is part of the system-config-language package. Regards, Patrick From debian at herakles.homelinux.org Tue Nov 20 21:20:55 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 21 Nov 2007 06:20:55 +0900 Subject: Kickstarting IBM servers In-Reply-To: <4742F49C.5070409@redhat.com> References: <4742F49C.5070409@redhat.com> Message-ID: <47434FB7.2050004@herakles.homelinux.org> Vimal Kumar wrote: > Hello, > > I have a scenario in which its not able to do a kickstart on IBM > servers, the process halts at the keymap. Tried various alternatives in > the kickstart config; gb, uk, us; and also changed the keyboard and > language settings. The problem occurs on both x86 or x86_64 bit RHEL5. > The IBM Servers are mainly x345s and x346s. Tried Compaq KVMs, HP KVMs, > standard Dell PS2 keyboards and other non-brand keyboards... with a > mixture of US and UK keymaps. It's not possible to use the keyboard at > all during the kickstart process... it's just garbled characters and > renders it useless. > > The ks.cfg is as follows : > > ----------------------- > install > nfs --server=X.X.X.X --dir=/kickstart/install-tree/rhel-5 > text > lang en_US > #langsupport --default=en_GB.UTF-8 en_GB.UTF-8 > keyboard us > keymap us I did a manual install of Tikanga-clone. There is no keymap statement in the ks anaconda produced. Try an interactive install, it will ask about your mistakes. Here's the relevant part of my ks file: # Kickstart file automatically generated by anaconda. install url --url http://rhel.demo.lan/ScientificLinux/5.0/i386/os lang en_US.UTF-8 keyboard us xconfig --startxonboot network --device eth0 --bootproto dhcp rootpw youwish firewall --enabled --port=22:tcp authconfig --enableshadow --enablemd5 selinux --enforcing timezone Australia/Perth bootloader --location=mbr --driveorder=hda,sda --append="rhgb quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work -- 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 Please do not reply off-list From annappa_uttara at yahoo.com Wed Nov 21 11:29:38 2007 From: annappa_uttara at yahoo.com (annappa gk) Date: Wed, 21 Nov 2007 16:59:38 +0530 (IST) Subject: mounting nfs directory in kickstart post installation scripts Message-ID: <573220.42109.qm@web94504.mail.in2.yahoo.com> Hi all, I have copied some rpms to nfs dir. how do i mount this in post installtion script to install these RPMS. thanks in advance, Annappa Now you can chat without downloading messenger. Go to http://in.messenger.yahoo.com/webmessengerpromo.php From dadembro at rockwellcollins.com Wed Nov 21 14:23:29 2007 From: dadembro at rockwellcollins.com (dadembro at rockwellcollins.com) Date: Wed, 21 Nov 2007 09:23:29 -0500 Subject: Does Kickstart Support Secure HTTP (port 443) Message-ID: I have been asked to disable port 80 for security reasons. I use it to supply a kickstart file to other systems on the network for Red Hat Enterprise Linux 4 (update 4). Trying to get the kickstart with ks=https://ip_address/kickstart_filename.cfg fails. Should I expect this to work or not? Thanks, ---d.dembrow -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Fahrner at coat.com Wed Nov 21 14:31:25 2007 From: Matt.Fahrner at coat.com (Matt Fahrner) Date: Wed, 21 Nov 2007 09:31:25 -0500 Subject: Does Kickstart Support Secure HTTP (port 443) In-Reply-To: References: Message-ID: <4744413D.9000906@coat.com> I looked into it for similar reasons and from what I can see it doesn't. What we ended up doing is just making the firewall ACL more specific to allow only port 80 to the kickstart host. Maybe I'm wrong, I would be happy to hear it did support this, but I don't think it does. - Matt dadembro at rockwellcollins.com wrote: > > I have been asked to disable port 80 for security reasons. I use it to > supply a kickstart file to other systems on the network for Red Hat > Enterprise Linux 4 (update 4). Trying to get the kickstart with > ks=https://ip_address/kickstart_filename.cfg fails. > > Should I expect this to work or not? > > Thanks, > ---d.dembrow > -- --------------------------------------------------------------------- Matt Fahrner 2 South Park St. Chief Systems Architect Willis House Burlington Coat Factory Warehouse Lebanon, N.H. 03766 Tel: (603) 448-4100 x5150 USA Fax: (603) 443-6190 Matt.Fahrner at COAT.COM --------------------------------------------------------------------- From clumens at redhat.com Wed Nov 21 17:30:33 2007 From: clumens at redhat.com (Chris Lumens) Date: Wed, 21 Nov 2007 12:30:33 -0500 Subject: Does Kickstart Support Secure HTTP (port 443) In-Reply-To: References: Message-ID: <20071121173033.GE6864@localhost.localdomain> > I have been asked to disable port 80 for security reasons. I use it to > supply a kickstart file to other systems on the network for Red Hat > Enterprise Linux 4 (update 4). Trying to get the kickstart with > ks=https://ip_address/kickstart_filename.cfg fails. > > Should I expect this to work or not? No, and it's not limited to kickstart. The URL fetching code in the loader does not support HTTPS at all, so you would discover that this does not work in interactive installs either. - Chris From klaus.steden at thomson.net Wed Nov 21 19:46:03 2007 From: klaus.steden at thomson.net (Klaus Steden) Date: Wed, 21 Nov 2007 11:46:03 -0800 Subject: Does Kickstart Support Secure HTTP (port 443) In-Reply-To: <20071121173033.GE6864@localhost.localdomain> Message-ID: The ROCKS installer (based heavily on Kickstart, but with significant modifications) does support HTTPS installation. Might be worth looking into, since it's open-source. hth, Klaus On 11/21/07 9:30 AM, "Chris Lumens" did etch on stone tablets: >> I have been asked to disable port 80 for security reasons. I use it to >> supply a kickstart file to other systems on the network for Red Hat >> Enterprise Linux 4 (update 4). Trying to get the kickstart with >> ks=https://ip_address/kickstart_filename.cfg fails. >> >> Should I expect this to work or not? > > No, and it's not limited to kickstart. The URL fetching code in the > loader does not support HTTPS at all, so you would discover that this > does not work in interactive installs either. > > - Chris > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Joe_Wulf at yahoo.com Wed Nov 21 13:42:35 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Wed, 21 Nov 2007 08:42:35 -0500 Subject: mounting nfs directory in kickstart post installation scripts In-Reply-To: <573220.42109.qm@web94504.mail.in2.yahoo.com> References: <573220.42109.qm@web94504.mail.in2.yahoo.com> Message-ID: Annappa, What I've found successful is to execute the mount and other command no differently than I would in a regular fully built system. Note that this does happen AFTER all the other RH installation activities. %post mount :/source/directory /mnt cp /mnt/ /root cd /root rpm -ivh *.rpm R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of annappa gk Sent: Wednesday, November 21, 2007 06:30 To: kickstart-list at redhat.com Subject: mounting nfs directory in kickstart post installation scripts Hi all, I have copied some rpms to nfs dir. how do i mount this in post installtion script to install these RPMS. thanks in advance, Annappa From debian at herakles.homelinux.org Wed Nov 21 21:27:52 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 22 Nov 2007 06:27:52 +0900 Subject: mounting nfs directory in kickstart post installation scripts In-Reply-To: References: <573220.42109.qm@web94504.mail.in2.yahoo.com> Message-ID: <4744A2D8.1030200@herakles.homelinux.org> Joe_Wulf wrote: > Annappa, > > What I've found successful is to execute the mount and other command no > differently than I would in a regular fully built system. Note that this > does happen AFTER all the other RH installation activities. > > > %post > mount :/source/directory /mnt I don't know whether it's still the case, but '-o nolock' used to be good. -- 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 Please do not reply off-list From srobson at cadence.com Thu Nov 22 10:40:59 2007 From: srobson at cadence.com (Steve Robson) Date: Thu, 22 Nov 2007 10:40:59 +0000 Subject: Does Kickstart Support Secure HTTP (port 443) In-Reply-To: <20071121170013.DFE2274CA4@hormel.redhat.com> References: <20071121170013.DFE2274CA4@hormel.redhat.com> Message-ID: <47455CBB.50301@cadence.com> > Subject: Does Kickstart Support Secure HTTP (port 443) > From: dadembro at rockwellcollins.com > Date: Wed, 21 Nov 2007 09:23:29 -0500 > > I have been asked to disable port 80 for security reasons. I use it to > supply a kickstart file to other systems on the network for Red Hat > Enterprise Linux 4 (update 4). Trying to get the kickstart with > ks=https://ip_address/kickstart_filename.cfg fails. How about trying http but on some alternate port? ie. ks=http://ip_address:port/kickstart_filename.cfg -- Regards, Steve IT Support - UNIX/Linux Cadence Design Systems Bagshot Road Bracknell BERKSHIRE RG12 0PH UK From rainer at ultra-secure.de Thu Nov 22 15:54:38 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Thu, 22 Nov 2007 16:54:38 +0100 (CET) Subject: RHEL5.1 and lvm Message-ID: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> Hi, I'm trying to do an install of RHEL5.1 (i386), with the help of cobbler. All in a VMware at the moment. The partitioning section looks like this: part /boot --fstype ext3 --size=150 --ondisk=sda --asprimary part swap --fstype swap --size=4096 --ondisk=sda --asprimary part pv.01 --size=2048 --ondisk=sda volgroup rootvol pv.01 --pesize=32768 logvol / --vgname=rootvol --size=1024 --name=root --grow --fstype=ext3 part pv.02 --size=4096 --ondisk=sda volgroup usrvol pv.02 --pesize=32768 logvol /usr --vgname=usrvol --size=1024 --name=usr --grow --fstype=ext3 part pv.03 --size=2048 --grow --ondisk=sda volgroup varvol pv.03 --pesize=32768 logvol /var --vgname=varvol --size=1024 --name=var --grow --fstype=ext3 part pv.04 --size=4096 --ondisk=sda volgroup varlogvol pv.04 --pesize=32768 logvol /var/log --vgname=varlogvol --size=1024 --name=varlog --grow --fstype=ext3 But the installer halts with the "Big Problem, I can only reboot - OK?" screen. The problem seems to be that the volumegroups are not active (I can activate them via vgscan and vgchange -ay on the 2nd terminal, I see on the 3rd that anaconda can't find them in /dev)). I tried a "pre"-scripts, but I think anaconda enters into some kind of chroot and the device-files are not there anymore, when it wants to format the devices... Has anyone had this problem? I couldn't find anything in the archives. Rainer From jwildebo at redhat.com Thu Nov 22 15:46:39 2007 From: jwildebo at redhat.com (Jan Wildeboer) Date: Thu, 22 Nov 2007 16:46:39 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> Message-ID: <1195746399.3761.18.camel@jwcorp.muc.redhat.com> On Thu, 2007-11-22 at 16:54 +0100, Rainer Duffner wrote: > I'm trying to do an install of RHEL5.1 (i386), with the help of cobbler. > All in a VMware at the moment. AFAIK there are problems with older versions of VMWare and RHEL5. What VMWare version are you using? Jan -- Jan H Wildeboer | Solution Architect, RHCE | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Otto-Hahn-Str.20 | Fax: +49 (0)89 205071-111 D-85609 Dornach/Munich | eMail: jan.wildeboer at redhat.com _____________________________________________________________________ GPG-Key-ID: 5DEBAFB0 GPG-Fingerprint: 6104 0F74 8513 F17E DFD5 E820 6F61 A078 5DEB AFB0 _____________________________________________________________________ Reg. Adresse: Red Hat GmbH, Hauptstaetter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich _____________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rainer at ultra-secure.de Thu Nov 22 16:03:06 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Thu, 22 Nov 2007 17:03:06 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <1195746399.3761.18.camel@jwcorp.muc.redhat.com> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> Message-ID: <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> Am Do, 22.11.2007, 16:46, schrieb Jan Wildeboer: > On Thu, 2007-11-22 at 16:54 +0100, Rainer Duffner wrote: > >> I'm trying to do an install of RHEL5.1 (i386), with the help of cobbler. >> All in a VMware at the moment. > > AFAIK there are problems with older versions of VMWare and RHEL5. > > What VMWare version are you using? Oh, I forgot to mention. I use Workstation 6.0.2 build 59824 I wanted to use server first, but server1.0.4 is only for RHEL4 and server2 is beta still ;-) It's running quite nicely on a Ubuntu 7.10. cheers, Rainer From jwildebo at redhat.com Thu Nov 22 15:54:29 2007 From: jwildebo at redhat.com (Jan Wildeboer) Date: Thu, 22 Nov 2007 16:54:29 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> Message-ID: <1195746869.3761.21.camel@jwcorp.muc.redhat.com> On Thu, 2007-11-22 at 17:03 +0100, Rainer Duffner wrote: > Oh, I forgot to mention. > I use Workstation 6.0.2 build 59824 Any error messages on the VMWare level? If you try without LVs, does it work? You can use the remote-syslog feature of anaconda to collect possible error messages during install. Cobbler uses this by default, so it might be worth checking these logs too. Jan -- Jan H Wildeboer | Solution Architect, RHCE | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Otto-Hahn-Str.20 | Fax: +49 (0)89 205071-111 D-85609 Dornach/Munich | eMail: jan.wildeboer at redhat.com _____________________________________________________________________ GPG-Key-ID: 5DEBAFB0 GPG-Fingerprint: 6104 0F74 8513 F17E DFD5 E820 6F61 A078 5DEB AFB0 _____________________________________________________________________ Reg. Adresse: Red Hat GmbH, Hauptstaetter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich _____________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rainer at ultra-secure.de Thu Nov 22 16:16:44 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Thu, 22 Nov 2007 17:16:44 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <1195746869.3761.21.camel@jwcorp.muc.redhat.com> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> Message-ID: <2962.212.71.112.230.1195748204.squirrel@www.ultra-secure.de> Am Do, 22.11.2007, 16:54, schrieb Jan Wildeboer: > On Thu, 2007-11-22 at 17:03 +0100, Rainer Duffner wrote: > >> Oh, I forgot to mention. >> I use Workstation 6.0.2 build 59824 > > Any error messages on the VMWare level? > > If you try without LVs, does it work? I think it would work (because /boot is formated OK. "sda" is there, after all. > You can use the remote-syslog feature of anaconda to collect possible > error messages during install. Cobbler uses this by default, so it might > be worth checking these logs too. here: 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO moving (1) to step enablefilesystems 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO lv is rootvol/root, size of 2016 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO lv is usrvol/usr, size of 4064 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO lv is varlogvol/varlog, size of 4064 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO lv is varvol/var, size of 22368 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO formatting / as ext3 1195741327.0 Thu Nov 22 15:22:07 2007 172.16.50.50 <14>INFO Format command: ['/usr/sbin/mke2fs', '/dev/rootvol/root', '-i', '4096', '-j'] On sceen 5, it says: ---> Could not stat "/dev/rootvol/root" --- no such file or directory The device apparently does not exist; did you specify it correctly. <--- Is it a problem that I use several volume-groups? cheers, Rainer From rainer at ultra-secure.de Thu Nov 22 16:30:03 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Thu, 22 Nov 2007 17:30:03 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <1195746869.3761.21.camel@jwcorp.muc.redhat.com> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> Message-ID: <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> Am Do, 22.11.2007, 16:54, schrieb Jan Wildeboer: > On Thu, 2007-11-22 at 17:03 +0100, Rainer Duffner wrote: > >> Oh, I forgot to mention. >> I use Workstation 6.0.2 build 59824 > > Any error messages on the VMWare level? Not really. Nov 22 15:20:41.598: vcpu-0| CPU reset: soft Nov 22 15:20:41.749: vcpu-0| SVGA: Unregistering IOSpace at 0x1060 Nov 22 15:20:41.750: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) Nov 22 15:20:41.871: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) Nov 22 15:20:41.882: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) Nov 22 15:20:41.921: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) Nov 22 15:20:41.935: vcpu-0| SVGA: Unregistering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) Nov 22 15:20:41.938: vcpu-0| SVGA: Registering IOSpace at 0x1060 Nov 22 15:20:41.938: vcpu-0| SVGA: Registering MemSpace at 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) Nov 22 15:20:42.072: mks| Ignoring update request in VGA_Expose (mode change pending). Nov 22 15:20:42.072: mks| Ignoring update request in VGA_Expose (mode change pending). Nov 22 15:20:42.200: vcpu-0| DISKUTIL: scsi0:0 : geometry=4699/255/63 Nov 22 15:20:42.282: vcpu-0| BIOS-UUID is 56 4d c3 8c 59 de 63 5a-07 8a cc e3 9a 64 e1 f2 Nov 22 15:20:42.453: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 0 Nov 22 15:20:42.454: vcpu-0| DISKUTIL: Offline toolsVersion = 0 Nov 22 15:20:50.129: mks| Ignoring update request in VGA_Expose (mode change pending). Nov 22 15:20:50.132: mks| Ignoring update request in VGA_Expose (mode change pending). Nov 22 15:20:51.720: mks| Ignoring update request in VGA_Expose (mode change pending). Nov 22 15:20:51.720: mks| Ignoring update request in VGA_Expose (mode change pending). Nov 22 15:20:59.928: vcpu-0| SVGA: Unregistering IOSpace at 0x1060 Nov 22 15:20:59.928: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0 Nov 22 15:20:59.928: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0 Nov 22 15:20:59.928: vcpu-0| SVGA: Registering IOSpace at 0x1060 Nov 22 15:21:08.795: vcpu-0| SCSI0: RESET BUS Nov 22 15:21:08.808: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0 Nov 22 15:21:08.808: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8 Nov 22 15:21:08.809: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0 Nov 22 15:21:08.810: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for unsupported page 0x8 Nov 22 15:22:12.674: vcpu-0| VLANCE: Ethernet1 skipped 2304 time(s) Nov 22 15:22:12.674: vcpu-0| VLANCE: 981 549 534 56 48 23 34 34 20 12 8 4 0 0 0 1 Nov 22 15:22:12.674: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nov 22 15:22:12.749: vcpu-0| VLANCE: Ethernet1 skipped 2560 time(s) Nov 22 15:22:12.749: vcpu-0| VLANCE: 1075 614 587 68 59 29 41 38 22 13 9 4 0 0 0 1 Nov 22 15:22:12.749: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nov 22 15:22:12.825: vcpu-0| VLANCE: Ethernet1 skipped 2816 time(s) Nov 22 15:22:12.825: vcpu-0| VLANCE: 1164 668 655 82 71 36 47 41 22 15 9 4 1 0 0 1 Nov 22 15:22:12.825: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nov 22 15:22:12.895: vcpu-0| VLANCE: Ethernet1 skipped 3072 time(s) Nov 22 15:22:12.896: vcpu-0| VLANCE: 1253 741 731 93 73 39 48 42 22 15 9 4 1 0 0 1 Nov 22 15:22:12.896: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nov 22 15:22:12.968: vcpu-0| VLANCE: Ethernet1 skipped 3328 time(s) Nov 22 15:22:12.968: vcpu-0| VLANCE: 1346 806 800 104 78 43 53 42 25 16 9 4 1 0 0 1 Nov 22 15:22:12.968: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nov 22 15:22:29.347: vcpu-0| FLOPPY-MAIN : CMD Checking status for non-existent Drive 0 Nov 22 15:22:29.393: vcpu-0| SCSI DEVICE (scsi0:0): INQUIRY request with EVPD set Nov 22 15:22:29.393: vcpu-0| SCSI DEVICE (scsi0:0): INQUIRY request with EVPD set Nov 22 15:22:35.030: vcpu-0| FLOPPY-MAIN : CMD Checking status for non-existent Drive 0 I can send the whole ks.cfg file, if it is of any use. We have been doing kickstart installs with RHEL4 for some time (with LVMs), but my co-worker tells me that the syntax he used with RHEL4 has stopped working with RHEL5. [root at vmrhel5 syslog]# cat /var/www/cobbler/kickstarts_sys/rhel5-test-client/ks.cfg #platform=x86, AMD64, or Intel EM64T # System authorization information auth --useshadow --enablemd5 # System bootloader configuration bootloader --location=mbr # Partition clearing information clearpart --all --initlabel --drives=sda # Use text mode install text key --skip # Firewall configuration firewall --enabled # Run the Setup Agent on first boot firstboot --disable # System keyboard keyboard us # System language lang en_US # Use network installation url --url=http://172.16.50.100/cblr/links/RHEL5-i386 # If any cobbler repo definitions were referenced in the kickstart profile, include them here. # Network information network --bootproto=static --device=eth0 --onboot=on --ip=172.16.50.56 --netmask=255.255.255.0 --gateway=172.16.50.2 --nameserver=172.16.50.2 # Reboot after installation reboot #Root password rootpw --iscrypted $1$yadayadayadayadayadayada. # SELinux configuration selinux --disabled # Do not configure the X Window System skipx # System timezone timezone --utc Europe/Zurich # Install OS instead of upgrade install # Clear the Master Boot Record zerombr # Magically figure out how to partition this thing #SNIPPET::partition_select_normal # or not part /boot --fstype ext3 --size=150 --ondisk=sda --asprimary part swap --fstype swap --size=4096 --ondisk=sda --asprimary part pv.01 --size=2048 --ondisk=sda --asprimary volgroup rootvol pv.01 --pesize=32768 logvol / --vgname=rootvol --size=1024 --name=root --grow --fstype=ext3 part pv.02 --size=4096 --ondisk=sda volgroup usrvol pv.02 --pesize=32768 logvol /usr --vgname=usrvol --size=1024 --name=usr --grow --fstype=ext3 part pv.03 --size=2048 --grow --ondisk=sda volgroup varvol pv.03 --pesize=32768 logvol /var --vgname=varvol --size=1024 --name=var --grow --fstype=ext3 part pv.04 --size=4096 --ondisk=sda volgroup varlogvol pv.04 --pesize=32768 logvol /var/log --vgname=varlogvol --size=1024 --name=varlog --grow --fstype=ext3 %packages #-s390utils #-bluez-bluefw #-bluez-hcidump #-bluez-libs #-bluez-utils #-bluez-gnome #-bridge-utils #-dhclient #-dhcpv6_client #-irda-utils #-pcmciautils #-rp-pppoe #-sendmail #-mutt #-fetchmail #-mdadm #-wireless-tools #-rhpl #-NetworkManager #lvm2 #grub #e2fsprogs #compat-libstdc++-296 #compat-libstdc++-33 #elinks #ntp #postfix #vim-common #vim-enhanced %post wget http://172.16.50.100/cblr/watcher.py?system_done=rhel5-test-client -b wget http://172.16.50.100/cobbler/kickstarts_sys/rhel5-test-client/ks.cfg -O /root/cobbler.ks %pre #!/bin/sh echo "Running LVM scan..." /usr/sbin/lvm.static vgscan /usr/sbin/lvm.static vgchange -ay /usr/bin/sleep 5 echo "...done!" From jwildebo at redhat.com Thu Nov 22 16:25:29 2007 From: jwildebo at redhat.com (Jan Wildeboer) Date: Thu, 22 Nov 2007 17:25:29 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> Message-ID: <1195748729.3761.23.camel@jwcorp.muc.redhat.com> On Thu, 2007-11-22 at 17:30 +0100, Rainer Duffner wrote: > but my co-worker tells me that the syntax he used with RHEL4 has > stopped working with RHEL5. This is directly from one one of my (working) RHEL5 kickstarts: partition /boot --fstype=ext3 --size=200 partition pv.01 --size=1000 --grow partition swap --size=1000 --maxsize=2000 volgroup myvg pv.01 logvol / --vgname=myvg --name=rootvol --size=1000 --grow -- Jan H Wildeboer | Solution Architect, RHCE | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Otto-Hahn-Str.20 | Fax: +49 (0)89 205071-111 D-85609 Dornach/Munich | eMail: jan.wildeboer at redhat.com _____________________________________________________________________ GPG-Key-ID: 5DEBAFB0 GPG-Fingerprint: 6104 0F74 8513 F17E DFD5 E820 6F61 A078 5DEB AFB0 _____________________________________________________________________ Reg. Adresse: Red Hat GmbH, Hauptstaetter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich _____________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Pablo.Iranzo at redhat.com Thu Nov 22 16:32:13 2007 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?ISO-8859-1?Q?G=F3mez?=) Date: Thu, 22 Nov 2007 17:32:13 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> Message-ID: <1195749133.4182.51.camel@iranzo.users.redhat.com> Why do you create so much physical volumes instead of creating just one and several LV on it? ?Why so much VG too? Regards Pablo El jue, 22-11-2007 a las 17:30 +0100, Rainer Duffner escribi?: > Am Do, 22.11.2007, 16:54, schrieb Jan Wildeboer: > > On Thu, 2007-11-22 at 17:03 +0100, Rainer Duffner wrote: > > > >> Oh, I forgot to mention. > >> I use Workstation 6.0.2 build 59824 > > > > Any error messages on the VMWare level? > > Not really. > > Nov 22 15:20:41.598: vcpu-0| CPU reset: soft > Nov 22 15:20:41.749: vcpu-0| SVGA: Unregistering IOSpace at 0x1060 > Nov 22 15:20:41.750: vcpu-0| SVGA: Unregistering MemSpace at > 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) > Nov 22 15:20:41.871: vcpu-0| SVGA: Registering MemSpace at > 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) > Nov 22 15:20:41.882: vcpu-0| SVGA: Unregistering MemSpace at > 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) > Nov 22 15:20:41.921: vcpu-0| SVGA: Registering MemSpace at > 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) > Nov 22 15:20:41.935: vcpu-0| SVGA: Unregistering MemSpace at > 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) > Nov 22 15:20:41.938: vcpu-0| SVGA: Registering IOSpace at 0x1060 > Nov 22 15:20:41.938: vcpu-0| SVGA: Registering MemSpace at > 0xf0000000(0xf0000000) and 0xe8000000(0xe8000000) > Nov 22 15:20:42.072: mks| Ignoring update request in VGA_Expose (mode > change pending). > Nov 22 15:20:42.072: mks| Ignoring update request in VGA_Expose (mode > change pending). > Nov 22 15:20:42.200: vcpu-0| DISKUTIL: scsi0:0 : geometry=4699/255/63 > Nov 22 15:20:42.282: vcpu-0| BIOS-UUID is 56 4d c3 8c 59 de 63 5a-07 8a cc > e3 9a 64 e1 f2 > Nov 22 15:20:42.453: vcpu-0| DISKUTIL: scsi0:0 : toolsVersion = 0 > Nov 22 15:20:42.454: vcpu-0| DISKUTIL: Offline toolsVersion = 0 > Nov 22 15:20:50.129: mks| Ignoring update request in VGA_Expose (mode > change pending). > Nov 22 15:20:50.132: mks| Ignoring update request in VGA_Expose (mode > change pending). > Nov 22 15:20:51.720: mks| Ignoring update request in VGA_Expose (mode > change pending). > Nov 22 15:20:51.720: mks| Ignoring update request in VGA_Expose (mode > change pending). > Nov 22 15:20:59.928: vcpu-0| SVGA: Unregistering IOSpace at 0x1060 > Nov 22 15:20:59.928: vcpu-0| SVGA: Registering IOSpace at 0xfffffff0 > Nov 22 15:20:59.928: vcpu-0| SVGA: Unregistering IOSpace at 0xfffffff0 > Nov 22 15:20:59.928: vcpu-0| SVGA: Registering IOSpace at 0x1060 > Nov 22 15:21:08.795: vcpu-0| SCSI0: RESET BUS > Nov 22 15:21:08.808: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for > unsupported page 0 > Nov 22 15:21:08.808: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for > unsupported page 0x8 > Nov 22 15:21:08.809: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for > unsupported page 0 > Nov 22 15:21:08.810: vcpu-0| SCSI DEVICE (scsi0:0): MODE SENSE(6) for > unsupported page 0x8 > Nov 22 15:22:12.674: vcpu-0| VLANCE: Ethernet1 skipped 2304 time(s) > Nov 22 15:22:12.674: vcpu-0| VLANCE: 981 549 534 56 48 23 34 34 20 12 8 4 > 0 0 0 1 > Nov 22 15:22:12.674: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > Nov 22 15:22:12.749: vcpu-0| VLANCE: Ethernet1 skipped 2560 time(s) > Nov 22 15:22:12.749: vcpu-0| VLANCE: 1075 614 587 68 59 29 41 38 22 13 9 4 > 0 0 0 1 > Nov 22 15:22:12.749: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > Nov 22 15:22:12.825: vcpu-0| VLANCE: Ethernet1 skipped 2816 time(s) > Nov 22 15:22:12.825: vcpu-0| VLANCE: 1164 668 655 82 71 36 47 41 22 15 9 4 > 1 0 0 1 > Nov 22 15:22:12.825: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > Nov 22 15:22:12.895: vcpu-0| VLANCE: Ethernet1 skipped 3072 time(s) > Nov 22 15:22:12.896: vcpu-0| VLANCE: 1253 741 731 93 73 39 48 42 22 15 9 4 > 1 0 0 1 > Nov 22 15:22:12.896: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > Nov 22 15:22:12.968: vcpu-0| VLANCE: Ethernet1 skipped 3328 time(s) > Nov 22 15:22:12.968: vcpu-0| VLANCE: 1346 806 800 104 78 43 53 42 25 16 9 > 4 1 0 0 1 > Nov 22 15:22:12.968: vcpu-0| VLANCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > Nov 22 15:22:29.347: vcpu-0| FLOPPY-MAIN : CMD Checking status for > non-existent Drive 0 > Nov 22 15:22:29.393: vcpu-0| SCSI DEVICE (scsi0:0): INQUIRY request with > EVPD set > Nov 22 15:22:29.393: vcpu-0| SCSI DEVICE (scsi0:0): INQUIRY request with > EVPD set > Nov 22 15:22:35.030: vcpu-0| FLOPPY-MAIN : CMD Checking status for > non-existent Drive 0 > > > I can send the whole ks.cfg file, if it is of any use. > We have been doing kickstart installs with RHEL4 for some time (with > LVMs), but my co-worker tells me that the syntax he used with RHEL4 has > stopped working with RHEL5. > > [root at vmrhel5 syslog]# cat > /var/www/cobbler/kickstarts_sys/rhel5-test-client/ks.cfg > > #platform=x86, AMD64, or Intel EM64T > # System authorization information > auth --useshadow --enablemd5 > # System bootloader configuration > bootloader --location=mbr > # Partition clearing information > clearpart --all --initlabel --drives=sda > # Use text mode install > text > key --skip > # Firewall configuration > firewall --enabled > # Run the Setup Agent on first boot > firstboot --disable > # System keyboard > keyboard us > # System language > lang en_US > # Use network installation > url --url=http://172.16.50.100/cblr/links/RHEL5-i386 > # If any cobbler repo definitions were referenced in the kickstart > profile, include them here. > # Network information > network --bootproto=static --device=eth0 --onboot=on --ip=172.16.50.56 > --netmask=255.255.255.0 --gateway=172.16.50.2 --nameserver=172.16.50.2 > # Reboot after installation > reboot > > #Root password > rootpw --iscrypted $1$yadayadayadayadayadayada. > # SELinux configuration > selinux --disabled > # Do not configure the X Window System > skipx > # System timezone > timezone --utc Europe/Zurich > > # Install OS instead of upgrade > install > # Clear the Master Boot Record > zerombr > > # Magically figure out how to partition this thing > #SNIPPET::partition_select_normal > # or not > part /boot --fstype ext3 --size=150 --ondisk=sda --asprimary > part swap --fstype swap --size=4096 --ondisk=sda --asprimary > > part pv.01 --size=2048 --ondisk=sda --asprimary > volgroup rootvol pv.01 --pesize=32768 > logvol / --vgname=rootvol --size=1024 --name=root --grow --fstype=ext3 > > part pv.02 --size=4096 --ondisk=sda > volgroup usrvol pv.02 --pesize=32768 > logvol /usr --vgname=usrvol --size=1024 --name=usr --grow --fstype=ext3 > > part pv.03 --size=2048 --grow --ondisk=sda > volgroup varvol pv.03 --pesize=32768 > logvol /var --vgname=varvol --size=1024 --name=var --grow --fstype=ext3 > > part pv.04 --size=4096 --ondisk=sda > volgroup varlogvol pv.04 --pesize=32768 > logvol /var/log --vgname=varlogvol --size=1024 --name=varlog --grow > --fstype=ext3 > > > %packages > #-s390utils > #-bluez-bluefw > #-bluez-hcidump > > #-bluez-libs > #-bluez-utils > > #-bluez-gnome > #-bridge-utils > #-dhclient > #-dhcpv6_client > > #-irda-utils > #-pcmciautils > #-rp-pppoe > #-sendmail > #-mutt > #-fetchmail > #-mdadm > > #-wireless-tools > #-rhpl > #-NetworkManager > > #lvm2 > #grub > #e2fsprogs > #compat-libstdc++-296 > #compat-libstdc++-33 > #elinks > #ntp > #postfix > #vim-common > #vim-enhanced > > > %post > > wget http://172.16.50.100/cblr/watcher.py?system_done=rhel5-test-client -b > wget http://172.16.50.100/cobbler/kickstarts_sys/rhel5-test-client/ks.cfg > -O /root/cobbler.ks > > %pre > #!/bin/sh > echo "Running LVM scan..." > /usr/sbin/lvm.static vgscan > /usr/sbin/lvm.static vgchange -ay > /usr/bin/sleep 5 > echo "...done!" > > > > _______________________________________________ > 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/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 rainer at ultra-secure.de Fri Nov 23 10:06:53 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Fri, 23 Nov 2007 11:06:53 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <1195748729.3761.23.camel@jwcorp.muc.redhat.com> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> <1195748729.3761.23.camel@jwcorp.muc.redhat.com> Message-ID: <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> Am Do, 22.11.2007, 17:25, schrieb Jan Wildeboer: > On Thu, 2007-11-22 at 17:30 +0100, Rainer Duffner wrote: >> but my co-worker tells me that the syntax he used with RHEL4 has >> stopped working with RHEL5. > > This is directly from one one of my (working) RHEL5 kickstarts: > > partition /boot --fstype=ext3 --size=200 > partition pv.01 --size=1000 --grow > partition swap --size=1000 --maxsize=2000 > > volgroup myvg pv.01 > > logvol / --vgname=myvg --name=rootvol --size=1000 --grow I don't know what I'm doing wrong. partition /boot --fstype=ext3 --size=200 partition swap --fstype=swap --size=4096 partition pv.01 --size=2048 --grow volgroup vgMain pv.01 --pesize=32768 logvol / --vgname=vgMain --size=7000 --name=root logvol /var --vgname=vgMain --size=2048 --name=var logvol /var/log --vgname=vgMain --size=4096 --name=varlog logvol /data --vgname=vgMain --size=4096 --name=data --grow Disk is a virtual 36 GB disk, newly created. Rest of the ks-file is unchanged, but I deleted the %pre-section. Same error again. /dev/mapper is empty, apart from the "control" file. If I vgscan && vgchange -ay, the devices show up. Can you take my ks-file and try it at your site? I'm using vmware, because it boots faster ;-) cheers, Rainer From jwildebo at redhat.com Fri Nov 23 10:16:13 2007 From: jwildebo at redhat.com (Jan Wildeboer) Date: Fri, 23 Nov 2007 11:16:13 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> <1195748729.3761.23.camel@jwcorp.muc.redhat.com> <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> Message-ID: <1195812973.5392.3.camel@jwcorp.muc.redhat.com> On Fri, 2007-11-23 at 11:06 +0100, Rainer Duffner wrote: > Can you take my ks-file and try it at your site? > I'm using vmware, because it boots faster ;-) I am using Xen, because it is Free Software ;-) Will try over the weekend. I *guess* this is related to the storage driver and VMWare combination, but who knows ... Jan -- Jan H Wildeboer | Solution Architect, RHCE | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Otto-Hahn-Str.20 | Fax: +49 (0)89 205071-111 D-85609 Dornach/Munich | eMail: jan.wildeboer at redhat.com _____________________________________________________________________ GPG-Key-ID: 5DEBAFB0 GPG-Fingerprint: 6104 0F74 8513 F17E DFD5 E820 6F61 A078 5DEB AFB0 _____________________________________________________________________ Reg. Adresse: Red Hat GmbH, Hauptstaetter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich _____________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rainer at ultra-secure.de Fri Nov 23 10:51:36 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Fri, 23 Nov 2007 11:51:36 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <1195812973.5392.3.camel@jwcorp.muc.redhat.com> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> <1195748729.3761.23.camel@jwcorp.muc.redhat.com> <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> <1195812973.5392.3.camel@jwcorp.muc.redhat.com> Message-ID: <5764.212.71.112.230.1195815096.squirrel@www.ultra-secure.de> Am Fr, 23.11.2007, 11:16, schrieb Jan Wildeboer: > On Fri, 2007-11-23 at 11:06 +0100, Rainer Duffner wrote: > >> Can you take my ks-file and try it at your site? >> I'm using vmware, because it boots faster ;-) > > I am using Xen, because it is Free Software ;-) ;-) If Xen would run FreeBSD out of the box, I'd be sold. VMware Server is free, too (just not Free, but the commercial versions of Xen aren't either...) > Will try over the weekend. I *guess* this is related to the storage > driver and VMWare combination, but who knows ... My co-worker tells me that he was unable to get this to work on real hardware, too. There must be something in the ks-file that is bad. I'll try to re-do it with the graphical editor. cheers, Rainer From rainer at ultra-secure.de Fri Nov 23 11:06:46 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Fri, 23 Nov 2007 12:06:46 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <5764.212.71.112.230.1195815096.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> <1195748729.3761.23.camel@jwcorp.muc.redhat.com> <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> <1195812973.5392.3.camel@jwcorp.muc.redhat.com> <5764.212.71.112.230.1195815096.squirrel@www.ultra-secure.de> Message-ID: <6350.212.71.112.230.1195816006.squirrel@www.ultra-secure.de> Am Fr, 23.11.2007, 11:51, schrieb Rainer Duffner: > I'll try to re-do it with the graphical editor. ...and to great hilarity, system-config-kickstart doesn't do LVMs... Argh. cu, Rainer From jwildebo at redhat.com Fri Nov 23 11:02:00 2007 From: jwildebo at redhat.com (Jan Wildeboer) Date: Fri, 23 Nov 2007 12:02:00 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <6350.212.71.112.230.1195816006.squirrel@www.ultra-secure.de> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> <1195748729.3761.23.camel@jwcorp.muc.redhat.com> <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> <1195812973.5392.3.camel@jwcorp.muc.redhat.com> <5764.212.71.112.230.1195815096.squirrel@www.ultra-secure.de> <6350.212.71.112.230.1195816006.squirrel@www.ultra-secure.de> Message-ID: <1195815720.15902.2.camel@jwcorp.muc.redhat.com> On Fri, 2007-11-23 at 12:06 +0100, Rainer Duffner wrote: > ...and to great hilarity, system-config-kickstart doesn't do LVMs... Why don't you simply do a manual install and use the autogenerated kickstart in /root (anacondaks.cfg) as a template? Jan -- Jan H Wildeboer | Solution Architect, RHCE | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Otto-Hahn-Str.20 | Fax: +49 (0)89 205071-111 D-85609 Dornach/Munich | eMail: jan.wildeboer at redhat.com _____________________________________________________________________ GPG-Key-ID: 5DEBAFB0 GPG-Fingerprint: 6104 0F74 8513 F17E DFD5 E820 6F61 A078 5DEB AFB0 _____________________________________________________________________ Reg. Adresse: Red Hat GmbH, Hauptstaetter Strasse 58, 70178 Stuttgart Handelsregister: Amtsgericht Stuttgart HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Werner Knoblich _____________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From rainer at ultra-secure.de Fri Nov 23 16:11:39 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Fri, 23 Nov 2007 17:11:39 +0100 (CET) Subject: RHEL5.1 and lvm In-Reply-To: <1195815720.15902.2.camel@jwcorp.muc.redhat.com> References: <2836.212.71.112.230.1195746878.squirrel@www.ultra-secure.de> <1195746399.3761.18.camel@jwcorp.muc.redhat.com> <2933.212.71.112.230.1195747386.squirrel@www.ultra-secure.de> <1195746869.3761.21.camel@jwcorp.muc.redhat.com> <3056.212.71.112.230.1195749003.squirrel@www.ultra-secure.de> <1195748729.3761.23.camel@jwcorp.muc.redhat.com> <5245.212.71.112.230.1195812413.squirrel@www.ultra-secure.de> <1195812973.5392.3.camel@jwcorp.muc.redhat.com> <5764.212.71.112.230.1195815096.squirrel@www.ultra-secure.de> <6350.212.71.112.230.1195816006.squirrel@www.ultra-secure.de> <1195815720.15902.2.camel@jwcorp.muc.redhat.com> Message-ID: <7747.212.71.112.230.1195834299.squirrel@www.ultra-secure.de> Am Fr, 23.11.2007, 12:02, schrieb Jan Wildeboer: > On Fri, 2007-11-23 at 12:06 +0100, Rainer Duffner wrote: > >> ...and to great hilarity, system-config-kickstart doesn't do LVMs... > > Why don't you simply do a manual install and use the autogenerated > kickstart in /root (anacondaks.cfg) as a template? > Yeah, I did that. Guess which of these: partition /boot --fstype=ext3 --size=200 partition swap --fstype=swap --size=4096 clearpart --all --initlabel --drives=sda partition pv.03 --size=2048 --grow volgroup vgMain pv.03 --pesize=32768 logvol / --vgname=vgMain --size=7000 --name=root logvol /var --vgname=vgMain --size=2048 --name=var logvol /var/log --vgname=vgMain --size=4096 --name=varlog logvol /data --vgname=vgMain --size=4096 --name=data --grow *** clearpart --all --drives=sda part /boot --fstype ext3 --size=100 --ondisk=sda part pv.2 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=512 --grow --maxsize=1024 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow *** clearpart --all --initlabel --drives=sda partition /boot --fstype ext3 --size=200 --ondisk=sda partition swap --fstype swap --size=4096 --ondisk=sda partition pv.03 --size=2048 --grow volgroup vgMain --pesize=32768 pv.03 logvol / --fstype ext3 --name=root --vgname=vgMain --size=7000 logvol /var --fstype ext3 --name=var --vgname=vgMain --size=2048 logvol /var/log --fstype ext3 --name=varlog --vgname=vgMain --size=4096 logvol /data --fstype ext3 --name=data --vgname=vgMain --size=4096 --grow ...actually works? ;-) I just don't know why. Cheers, Rainer From astrand at cendio.se Tue Nov 27 08:09:43 2007 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Tue, 27 Nov 2007 09:09:43 +0100 (CET) Subject: Confirming predefined partition layout using kickstart In-Reply-To: <1196089642.3328.25.camel@localhost.localdomain> References: <1196089642.3328.25.camel@localhost.localdomain> Message-ID: On Mon, 26 Nov 2007, Jeremy Katz wrote: > > Using F8 and Kickstart, we want to predefine everything about partitions, > > but also let the user confirm that the disk is going to be wiped. I > > thought this could be done with just > You could go with the route of popping up a dialog in %pre for > confirmation if that's all you really want. Thanks for your help. I've tried a %pre solution now and it seems to work great. Here's what I did: %pre --interpreter /usr/bin/python TTY = 3 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" % TTY) fd = os.open("/dev/tty%d" % TTY, 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) %end Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.se Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From Chip.Shabazian at bankofamerica.com Tue Nov 27 10:29:08 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Tue, 27 Nov 2007 02:29:08 -0800 Subject: Confirming predefined partition layout using kickstart In-Reply-To: Message-ID: That's a lot of python for a confirmation box. Have you looked at using dialog? -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Peter ?strand Sent: Tuesday, November 27, 2007 12:10 AM To: Discussion of Fedora build system; kickstart-list at redhat.com Subject: Re: Confirming predefined partition layout using kickstart On Mon, 26 Nov 2007, Jeremy Katz wrote: > > Using F8 and Kickstart, we want to predefine everything about > > partitions, but also let the user confirm that the disk is going to > > be wiped. I thought this could be done with just > You could go with the route of popping up a dialog in %pre for > confirmation if that's all you really want. Thanks for your help. I've tried a %pre solution now and it seems to work great. Here's what I did: %pre --interpreter /usr/bin/python TTY = 3 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" % TTY) fd = os.open("/dev/tty%d" % TTY, 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) %end Best regards, --- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.se Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From astrand at cendio.se Tue Nov 27 14:47:33 2007 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Tue, 27 Nov 2007 15:47:33 +0100 (CET) Subject: Confirming predefined partition layout using kickstart In-Reply-To: References: Message-ID: > That's a lot of python for a confirmation box. Have you looked at using dialog? Last time I checked, dialog was not available in the installation environment. Also, most of the code is for changing virtual console. This would be necessary even with the dialog binary. But if anyone has a smaller solution, please let me know. Best regards, Peter ?strand > -----Original Message----- > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Peter ?strand > Sent: Tuesday, November 27, 2007 12:10 AM > To: Discussion of Fedora build system; kickstart-list at redhat.com > Subject: Re: Confirming predefined partition layout using kickstart > > On Mon, 26 Nov 2007, Jeremy Katz wrote: > > > > Using F8 and Kickstart, we want to predefine everything about > > > partitions, but also let the user confirm that the disk is going to > > > be wiped. I thought this could be done with just > > > You could go with the route of popping up a dialog in %pre for > > confirmation if that's all you really want. > > Thanks for your help. I've tried a %pre solution now and it seems to work great. Here's what I did: > > %pre --interpreter /usr/bin/python > TTY = 3 > 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" % TTY) > fd = os.open("/dev/tty%d" % TTY, 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) > %end > > > Best regards, > --- > Peter ?strand ThinLinc Chief Developer > Cendio AB http://www.cendio.se > 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.se Wallenbergs gata 4 583 30 Link?ping Phone: +46-13-21 46 00 From victor_sira at yahoo.com Wed Nov 28 07:17:53 2007 From: victor_sira at yahoo.com (Victor Sira) Date: Tue, 27 Nov 2007 23:17:53 -0800 (PST) Subject: RHEL5.1 and lvm Message-ID: <861344.45233.qm@web51302.mail.re2.yahoo.com> ----- Original Message ---- > From: Rainer Duffner > To: Discussion list about Kickstart > Sent: Friday, November 23, 2007 8:11:39 AM > Subject: Re: RHEL5.1 and lvm > > Am Fr, 23.11.2007, 12:02, schrieb Jan Wildeboer: > > On Fri, 2007-11-23 at 12:06 +0100, Rainer Duffner wrote: > > > >> ...and to great hilarity, system-config-kickstart doesn't do LVMs... > > > > Why don't you simply do a manual install and use the autogenerated > > kickstart in /root (anacondaks.cfg) as a template? > > > > Yeah, I did that. > > Guess which of these: > > > partition /boot --fstype=ext3 --size=200 > partition swap --fstype=swap --size=4096 > clearpart --all --initlabel --drives=sda > partition pv.03 --size=2048 --grow > volgroup vgMain pv.03 --pesize=32768 > logvol / --vgname=vgMain --size=7000 --name=root > logvol /var --vgname=vgMain --size=2048 --name=var > logvol /var/log --vgname=vgMain --size=4096 --name=varlog > logvol /data --vgname=vgMain --size=4096 --name=data --grow > > *** > > clearpart --all --drives=sda > part /boot --fstype ext3 --size=100 --ondisk=sda > part pv.2 --size=0 --grow --ondisk=sda > volgroup VolGroup00 --pesize=32768 pv.2 > logvol swap --fstype swap --name=LogVol01 > --vgname=VolGroup00 > --size=512 > --grow --maxsize=1024 > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 > --size=1024 > --grow > > *** > > clearpart --all --initlabel --drives=sda > > partition /boot --fstype ext3 --size=200 --ondisk=sda > partition swap --fstype swap --size=4096 --ondisk=sda > > partition pv.03 --size=2048 --grow > volgroup vgMain --pesize=32768 pv.03 > logvol / --fstype ext3 --name=root --vgname=vgMain --size=7000 > logvol /var --fstype ext3 --name=var --vgname=vgMain --size=2048 > logvol /var/log --fstype ext3 --name=varlog --vgname=vgMain --size=4096 > logvol /data --fstype ext3 --name=data --vgname=vgMain > --size=4096 > --grow > > > ...actually works? > > ;-) > I just don't know why. > I had a somewhat similar situation today as well. My partition layout would work for RHEL 4u5 but when I tried on 5.1 it failed. What seems to have fixed my problem was moving the swap partition out of the vg group I was using and setup a regular linux partition for it. I wonder if that's what did it for you as well, although of course that would explain why. --Victor ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From rainer at ultra-secure.de Wed Nov 28 13:08:21 2007 From: rainer at ultra-secure.de (Rainer Duffner) Date: Wed, 28 Nov 2007 14:08:21 +0100 Subject: RHEL5.1 and lvm In-Reply-To: <861344.45233.qm@web51302.mail.re2.yahoo.com> References: <861344.45233.qm@web51302.mail.re2.yahoo.com> Message-ID: <474D6845.8060009@ultra-secure.de> Victor Sira wrote: >> >> I had a somewhat similar situation today as well. My partition layout would work for RHEL 4u5 but when I tried on 5.1 it failed. What seems to have fixed my problem was moving the swap partition out of the vg group I was using and setup a regular linux partition for it. I wonder if that's what did it for you as well, although of course that would explain why. >> >> --Victor >> >> Well, in my case, the autogenerated anaconda kickstart-file had the swap as a logvol - and from the above (not quoted) examples, it was the only one that worked. cheers, Rainer From mdehaan at redhat.com Wed Nov 28 16:44:06 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 28 Nov 2007 11:44:06 -0500 Subject: Does Kickstart Support Secure HTTP (port 443) In-Reply-To: <47455CBB.50301@cadence.com> References: <20071121170013.DFE2274CA4@hormel.redhat.com> <47455CBB.50301@cadence.com> Message-ID: <474D9AD6.3060007@redhat.com> Steve Robson wrote: >> Subject: Does Kickstart Support Secure HTTP (port 443) >> From: dadembro at rockwellcollins.com >> Date: Wed, 21 Nov 2007 09:23:29 -0500 >> >> I have been asked to disable port 80 for security reasons. I use it >> to supply a kickstart file to other systems on the network for Red >> Hat Enterprise Linux 4 (update 4). Trying to get the kickstart with >> ks=https://ip_address/kickstart_filename.cfg fails. > > How about trying http but on some alternate port? ie. > ks=http://ip_address:port/kickstart_filename.cfg > Moving the port really doesn't make it "secure"... what are you trying to restrict access to in the kickstart tree? Perhaps there's some package/change that you could push out using a config management system (or even something as simple as rsync) later? Or (for limited applications), you could serve (part of) your kickstart up by a CGI script based on the MAC address with 'kssendmac' on the kernel command line. That's not really secure either as environment variables can be forged, but it would allow for some limited access control. It really depends on what the problem you are trying to solve is though, any of those having ways to be solved other than kickstart over https:// with authentication. (And without authentication, there's not all that much point to installs over https:// anyway). --Michael From Gary.Schlachter at tavve.com Thu Nov 29 21:51:59 2007 From: Gary.Schlachter at tavve.com (Gary Schlachter) Date: Thu, 29 Nov 2007 21:51:59 +0000 (UTC) Subject: Problems with DHCP in F7 kickstart References: <1187109830.5578.325.camel@scooter.eps.surrey.ac.uk> Message-ID: Bevis R W King surrey.ac.uk> writes: > > I'm currently trying to get Fedora 7 (F7) to kickstart a PC. I've tried > various kickstart files, but the one I've settled on is an > anaconda-ks.cfg created by a manual workstation install via HTTP on that > very machine. > Prune text. > > The DHCP server in question worked fine for dynamic assignment in FC6, > and has all the options configured for that - dns-servers, etc, etc. > > Any thoughts on what might be causing this? > > Regards, Bevis. > Did you ever solve this? I am having a very similar problem. According to ethereal, the DHCPOFFER look valid but the FC7 server seems to be ignoring them. Thanks, Gary From B.King at surrey.ac.uk Fri Nov 30 10:38:00 2007 From: B.King at surrey.ac.uk (Bevis R W King) Date: Fri, 30 Nov 2007 10:38:00 +0000 Subject: Problems with DHCP in F7 kickstart In-Reply-To: References: <1187109830.5578.325.camel@scooter.eps.surrey.ac.uk> Message-ID: <1196419080.24867.307.camel@scooter.eps.surrey.ac.uk> Gary On Thu, 2007-11-29 at 21:51 +0000, Gary Schlachter wrote: > Did you ever solve this? I am having a very similar problem. According to > ethereal, the DHCPOFFER look valid but the FC7 server seems to be ignoring them. I'm sorry to say I don't remember. Basically we decided to wait for F8 and not develop an F(C)7 desktop installation package after all... I shall be starting again to look at this within the next few days. Regards, Bevis.