From i.jochim at querysoft.de Mon Dec 3 15:45:43 2007 From: i.jochim at querysoft.de (Ingo Jochim) Date: Mon, 03 Dec 2007 16:45:43 +0100 Subject: langsupport in Fedora 7 ? Message-ID: <475424A7.8040704@querysoft.de> Hi guys, where is the "langsupport" option in the kickstart config in Fedora 7 ? I get "unknown command" running a kickstart file with that option which works fine on FC4. I read that there is a new option called @french-support for example. But this does not add something to /etc/sysconfig/i18n which I'm using. What has changed? I appreciate your help. Ingo From srobson at cadence.com Tue Dec 4 09:42:59 2007 From: srobson at cadence.com (Steve Robson) Date: Tue, 04 Dec 2007 09:42:59 +0000 Subject: langsupport in Fedora 7 In-Reply-To: <20071203170023.8CDC0735FA@hormel.redhat.com> References: <20071203170023.8CDC0735FA@hormel.redhat.com> Message-ID: <47552123.7050305@cadence.com> Ingo Jochim wrote: > Subject: langsupport in Fedora 7 ? > From: Ingo Jochim > Date: Mon, 03 Dec 2007 16:45:43 +0100 > > Hi guys, > > where is the "langsupport" option in the kickstart config in Fedora 7 ? > I get "unknown command" running a kickstart file with that option which > works fine on FC4. > > I read that there is a new option called @french-support for example. > But this does not add something to /etc/sysconfig/i18n which I'm using. > What has changed? > I appreciate your help. Hi Ingo, Language packages such as "@french-support" need to be entered into the "%packages" section of your kickstart config file. Interested readers are directed to the 'Kickstart Options' section of the RHEL5 manual (which will be largely applicable to Fedora 7: http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html I note that the entry for 'langsupport' contradicts itself by first saying that it's required and then saying that it's deprecated! langsupport (required) The langsupport keyword is deprecated and its use will cause an error message to be printed to the screen and installation to halt. Instead of using the langsupport keyword, you should now list the support package groups for all languages you want supported in the %packages section of your kickstart file. For instance, adding support for French means you should add the following to %packages: @french-support -- Regards, Steve IT Support - UNIX/Linux Cadence Design Systems Bagshot Road http://www.cadence.com Bracknell BERKSHIRE RG12 0PH UK From Joe_Wulf at yahoo.com Wed Dec 5 06:31:54 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Wed, 5 Dec 2007 01:31:54 -0500 Subject: Couple of questions Message-ID: Hello everyone, When kickstarting, in text mode, eventually there is a pair of boxes which are displayed; they are labeled "Dynamic IP" and "Hostname". This occurs after the kernel images have been downloaded and booted. I've two questions at this point: - Is "Dynamic IP"'s message about "Sending request for IP information for eth0" soliciting DHCP or DNS for its answer? - Is "Hostname"''s message about "Determining host name and domain ..." soliciting its information from DHCP or DNS? Around this same time in the process, on VC4, I can see three entries that I'd like to better understand. - "bootp_gw_ip" has a value listed of 0.0.0.0 - "hwaddr:" is blank, with no value listed - "servername: is blank, with no value listed Any further insight for these would be nicely helpful, thank you. One thing that is interesting, and frustrating, is while looking directly at VC4 during the boot process, the network information is displayed without any respect to line breaks. However, when I switch to that page once its information is listed, it appears nice, normal and neat. Easy to read. Anything I can do to get it to display nicely even when actively viewing it? Another question is about the various outputs on the other VC's. Is there any method to control their output going to a text log file for subsequent review? Should would be a nice troubleshooting aid. Once a system has reached %post, I've been successful in echo'ing text progress messages to /dev/console. This shows me progress in all of the post processing I do in a upfront visual method. Only problem is that the messages would display and the cursor will drop a line, but not begin at the left margin. I've tried various options with escaping tab and newline and carriage return types of characters to have the text display at the beginning of the next line. Any suggestions on how to go about doing this in %post? An example is like this: text message1 text message 2 test message 3 Thank you. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com (410) 772-7969 office (410) 772-7967 fax (443) 801-5597 personal cell -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.hollifield1 at wachovia.com Wed Dec 5 06:34:08 2007 From: brian.hollifield1 at wachovia.com (brian.hollifield1 at wachovia.com) Date: Wed, 5 Dec 2007 00:34:08 -0600 Subject: Brian Hollifield is out of the office. Message-ID: I will be out of the office starting 12/04/2007 and will not return until 12/10/2007. I will be out of the office in training with no access to e-mail or voicemail. I will check e-mail in the evening. Thank You, Brian Hollifield CIBT - Platform Engineering 704-715-5674 From i.jochim at querysoft.de Wed Dec 5 13:57:13 2007 From: i.jochim at querysoft.de (Ingo Jochim) Date: Wed, 05 Dec 2007 14:57:13 +0100 Subject: langsupport in Fedora 7 In-Reply-To: <47552123.7050305@cadence.com> References: <20071203170023.8CDC0735FA@hormel.redhat.com> <47552123.7050305@cadence.com> Message-ID: <4756AE39.2010200@querysoft.de> I understand that new option in the kickstart script. But it doesn't add anything to the /etc/sysconfig/i18n file. I was using the SUPPORTED option by another script which I can't use any more. Adding a language by using @french-support doesn't create something at SUPPORTED. LANG="de_DE.UTF-8" SYSFONT="latarcyrheb-sun16" SUPPORTED="de_DE.UTF-8:de_DE:de:en_US:en:fr_FR.UTF-8:fr_FR:fr:es_ES.UTF-8:es_ES:es" Is there a new file now? I read something about M17N and SCIM? Has that been changed? Ingo Steve Robson schrieb: > Ingo Jochim wrote: >> Subject: langsupport in Fedora 7 ? >> From: Ingo Jochim >> Date: Mon, 03 Dec 2007 16:45:43 +0100 >> >> Hi guys, >> >> where is the "langsupport" option in the kickstart config in Fedora 7 ? >> I get "unknown command" running a kickstart file with that option >> which works fine on FC4. >> >> I read that there is a new option called @french-support for example. >> But this does not add something to /etc/sysconfig/i18n which I'm using. >> What has changed? >> I appreciate your help. > > Hi Ingo, > > Language packages such as "@french-support" need to be entered into > the "%packages" section of your kickstart config file. Interested > readers are directed to the 'Kickstart Options' section of the RHEL5 > manual (which will be largely applicable to Fedora 7: > http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html > > > I note that the entry for 'langsupport' contradicts itself by first > saying that it's required and then saying that it's deprecated! > > > > langsupport (required) > > The langsupport keyword is deprecated and its use will cause an > error message to be printed to the screen and installation to halt. > Instead of using the langsupport keyword, you should now list the > support package groups for all languages you want supported in the > %packages section of your kickstart file. For instance, adding support > for French means you should add the following to %packages: > > @french-support > > > From mdehaan at redhat.com Wed Dec 5 15:55:45 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Wed, 05 Dec 2007 10:55:45 -0500 Subject: Couple of questions In-Reply-To: References: Message-ID: <4756CA01.50102@redhat.com> Joe_Wulf wrote: > > Hello everyone, > > When kickstarting, in text mode, eventually there is a pair of boxes > which are displayed; they are labeled "Dynamic IP" and "Hostname". > This occurs after the kernel images have been downloaded and booted. > I've two questions at this point: > > - Is "Dynamic IP"'s message about "Sending request for IP information > for eth0" soliciting DHCP or DNS for its answer? > DHCP. > - Is "Hostname"''s message about "Determining host name and domain > ..." soliciting its information from DHCP or DNS? > DNS. ..snip... > Another question is about the various outputs on the other VC's. Is > there any method to control their output going to a text log file for > subsequent review? Should would be a nice troubleshooting aid. > Remote syslog support is available in FC6 and later, and RHEL5 and later. syslog=ip:port on the kernel options line. cobblerd (part of Cobbler) has a daemon to capture this information and log it, which the data from each kickstarting IP going to a seperate file. > Once a system has reached %post, I've been successful in echo'ing text > progress messages to /dev/console. This shows me progress in all of > the post processing I do in a upfront visual method. Only problem is > that the messages would display and the cursor will drop a line, but > not begin at the left margin. I've tried various options with > escaping tab and newline and carriage return types of characters to > have the text display at the beginning of the next line. Any > suggestions on how to go about doing this in %post? > > An example is like this: > > text message1 > > text message 2 > > test message 3 > If this is for debugging, just sticking a long "sleep 99999" in your post section allows you do to anything you want with the shell, and is IMHO less ugly than relying on printing stuff to the console. > Thank you. > > > R, > -*Joe Wulf*, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > *_ www.prosync.com_* > (410) 772-7969 / office/ > (410) 772-7967 / fax/ > (443) 801-5597 / personal cell/** > > ** > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From rigg0022 at umn.edu Wed Dec 5 16:05:06 2007 From: rigg0022 at umn.edu (Riggs, Ben) Date: Wed, 05 Dec 2007 10:05:06 -0600 Subject: Couple of questions In-Reply-To: <4756CA01.50102@redhat.com> References: <4756CA01.50102@redhat.com> Message-ID: <4756CC32.6070304@umn.edu> Just commenting out the reboot line in the kickstart works as well. Michael DeHaan wrote: > If this is for debugging, just sticking a long "sleep 99999" in your > post section allows you do to anything you want with the shell, and is > IMHO less ugly than relying on printing stuff to the console. From Joe_Wulf at yahoo.com Wed Dec 5 16:23:21 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Wed, 5 Dec 2007 11:23:21 -0500 Subject: Couple of questions In-Reply-To: <4756CC32.6070304@umn.edu> References: <4756CA01.50102@redhat.com> <4756CC32.6070304@umn.edu> Message-ID: Thank you both for the helpful feedback. My post section does a number of things before ever letting the system boot. My desire was to see some progress messages on the console while that process was working. Such as "reached point x", "reached point y". The display of them to "/dev/console" wasn't very pretty and attempts to clean it up hasn't proven successful. Was hoping someone has also done this and found a way to have lines of text display neatly. Thank you R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com (410) 772-7969 office (410) 772-7967 fax (443) 801-5597 personal cell -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Riggs, Ben Sent: Wednesday, December 05, 2007 11:05 To: Discussion list about Kickstart Subject: Re: Couple of questions Just commenting out the reboot line in the kickstart works as well. Michael DeHaan wrote: > If this is for debugging, just sticking a long "sleep 99999" in your > post section allows you do to anything you want with the shell, and is > IMHO less ugly than relying on printing stuff to the console. _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From srobson at cadence.com Wed Dec 5 16:55:33 2007 From: srobson at cadence.com (Steve Robson) Date: Wed, 05 Dec 2007 16:55:33 +0000 Subject: progress messages In-Reply-To: <20071205162327.30EE873363@hormel.redhat.com> References: <20071205162327.30EE873363@hormel.redhat.com> Message-ID: <4756D805.9040602@cadence.com> > Subject: RE: Couple of questions > From: "Joe_Wulf" > > Thank you both for the helpful feedback. > > My post section does a number of things before ever letting the system boot. > My desire was to see some progress messages on the console while that process was > working. Such as "reached point x", "reached point y". The display of them to > "/dev/console" wasn't very pretty and attempts to clean it up hasn't proven > successful. Was hoping someone has also done this and found a way to have lines > of text display neatly. Not exactly the same, but similar; in my %pre section I make an NFS mount and then run a script from the mount. Verbiage in that script is simply echoed out: echo "blah blah" and this appears on VC3, with proper cr/lf. Hope this helps, -- Regards, Steve IT Support - UNIX/Linux Cadence Design Systems Bagshot Road Bracknell BERKSHIRE RG12 0PH UK From Joe_Wulf at yahoo.com Wed Dec 5 17:36:06 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Wed, 5 Dec 2007 12:36:06 -0500 Subject: progress messages In-Reply-To: <4756D805.9040602@cadence.com> References: <20071205162327.30EE873363@hormel.redhat.com> <4756D805.9040602@cadence.com> Message-ID: Thank you. I'll give that a try. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com (410) 772-7969 office (410) 772-7967 fax (443) 801-5597 personal cell -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Steve Robson Sent: Wednesday, December 05, 2007 11:56 To: kickstart-list at redhat.com Subject: Re: progress messages > Subject: RE: Couple of questions > From: "Joe_Wulf" > > Thank you both for the helpful feedback. > > My post section does a number of things before ever letting the system boot. > My desire was to see some progress messages on the console while that process was > working. Such as "reached point x", "reached point y". The display of them to > "/dev/console" wasn't very pretty and attempts to clean it up hasn't proven > successful. Was hoping someone has also done this and found a way to have lines > of text display neatly. Not exactly the same, but similar; in my %pre section I make an NFS mount and then run a script from the mount. Verbiage in that script is simply echoed out: echo "blah blah" and this appears on VC3, with proper cr/lf. Hope this helps, -- Regards, Steve IT Support - UNIX/Linux Cadence Design Systems Bagshot Road Bracknell BERKSHIRE RG12 0PH UK _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From sjbrowne at bluebottle.com Wed Dec 5 22:01:56 2007 From: sjbrowne at bluebottle.com (Stuart J. Browne) Date: Thu, 6 Dec 2007 09:01:56 +1100 Subject: progress messages In-Reply-To: References: <20071205162327.30EE873363@hormel.redhat.com><4756D805.9040602@cadence.com> Message-ID: <007101c8378a$764902d0$1f00a8c0@trusteddelivery.local> > > > Thank you both for the helpful feedback. > > > > > > My post section does a number of things before ever letting > > > the system boot. My desire was to see some progress messages > > > on the console while that process was working. Such as > > > "reached point x", "reached point y". The display of them to > > > "/dev/console" wasn't very pretty and attempts to clean it > > > up hasn't provensuccessful. Was hoping someone has also done > > > this and found a way to have lines > > > of text display neatly. > > > > Not exactly the same, but similar; in my %pre section I make an NFS > > mount and then run a script from the mount. Verbiage in that > > script is > > simply echoed out: > > echo "blah blah" > > and this appears on VC3, with proper cr/lf. Hope this helps, > > Thank you. I'll give that a try. You could always 'chvt', or just echo to a specific tty.. i.e. echo "blah blah" > /dev/ttyX or chvt X echo "blah blah" Stuart From astrand at cendio.se Thu Dec 6 20:02:47 2007 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Thu, 6 Dec 2007 21:02:47 +0100 (CET) Subject: Confirming predefined partition layout using kickstart In-Reply-To: References: Message-ID: On Mon, 26 Nov 2007, Peter ?strand wrote: >... > "Could not allocate requested partitions". If we are using: > > zerombr > clearpart --all --initlabel > partition / --fstype ext3 --size=1600 --asprimary > partition swap --recommended > > ...things works great, but then there's no confirmation. I've discovered one major problem: When booting from a USB stick with diskboot.img, a kickstart file like this erases the USB stick! How can this be prevented? It seems like it's fairly reliable that the first disk is normally sda, but if booting from USB stick, sda is the stick. I guess we need to use "ignoredisk" on the USB stick or something like that, but I cannot find any obvious solution. 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 d.lesca at solinos.it Fri Dec 7 11:28:22 2007 From: d.lesca at solinos.it (Dario Lesca) Date: Fri, 07 Dec 2007 12:28:22 +0100 Subject: [Fwd: f8: install via PXE/NFS problem (mount)] Message-ID: <1197026902.13142.82.camel@lesca.home.solinos.it> ------- Messaggio inoltrato ------- Da: Dario Lesca Rispondi-a: For users of Fedora A: Fedora Project List CC: Fedora Devel Oggetto: f8: install via PXE/NFS problem (mount) Data: Fri, 07 Dec 2007 12:24:03 +0100 Hi, I have a PXE/NFS systems for install Fedora from fc1 to f7. All work fine. Today I have add also f8 in this system but I having problems with mount via NFS. kickstart.cfg file is load via nfs (ks=nfs:pxesetup:/u/kickstart/ks-8.cfg) and the source files are in pxesetup:/u/f8 The process start correctly, mount an load ks-8.cfg, mount source dir but when anaconda trying remount kickstart file got an error and the setup process stop. I have switch to CTRL+ALT+F2 and I have trying mount some other dir: mount -t nfs pxesetup:/u/f7 /tmp/f7 but the mount command fail with timeout ... Some problema I have get when I have trying add to my PXE system setup last f7respin ... Probably is a kernel-2.6.23 problem or new-NFS problem ?.... Someone can help me? Many thanks. -- Dario Lesca -- Dario Lesca From Joe_Wulf at yahoo.com Fri Dec 7 14:56:37 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Fri, 7 Dec 2007 09:56:37 -0500 Subject: [Fwd: f8: install via PXE/NFS problem (mount)] In-Reply-To: <1197026902.13142.82.camel@lesca.home.solinos.it> References: <1197026902.13142.82.camel@lesca.home.solinos.it> Message-ID: Dario, Your description seems remarkably similar to a problem I've described through this list before and continue to have. Questions for you: - What is the OS of the system hosting your PXE/kickstart processes? Is it updated and current with patches? - How good (what kind) of computer is doing the hosting, how much memory, what kind of nic card, what network equipment are you dealing with? - What is the hardware you are booting via PXE/kickstart (CPU, 32/64 bit, mem)? - Are you booting this system to be kickstarted as a virtual machine or as the physical box itself? - Can you get a second physically different system to successfully boot via kickstart for Fedora 8? - What else can you describe of the physical network that might have any bearing on this problem? - What specifically is the condition you are seeing that ends the kickstart? What error message(s) do you see on the console? What is the gist of the output in VC3 and VC4? >From my own experience I suggest you re-validate your DHCP, DNS, tftp and PXEboot configuration. Maybe have a second person independently verify it for you. I have done just that myself. In my current/on-going problem set, my kickstart server is Fedora 7 and updated nearly daily with patches (I might miss a day here and there). I'm building a number of virtual machines on both a Dell XPS 32 bit laptop and also have a Mac Pro (64 bit with dual quad-cores, 4GB ram) running Win XP 64 bit. Both have VMware workstation 6.02 installed. I'm encountering zero problems with any OS build via kickstart to the Dell laptop. I'm encountering zero problems manually building any OS within VMs on the Mac Pro. Finally, I'm getting zero success once reaching the NFS mount on the RedHat VMs being built on the Mac. I'm nearly stymied with no clue what to do for help myself. Hopefully these questions will be beneficial to getting your problem resolved. 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 Dario Lesca Sent: Friday, December 07, 2007 06:28 To: Kickstart List Subject: [Fwd: f8: install via PXE/NFS problem (mount)] ------- Messaggio inoltrato ------- Da: Dario Lesca Rispondi-a: For users of Fedora A: Fedora Project List CC: Fedora Devel Oggetto: f8: install via PXE/NFS problem (mount) Data: Fri, 07 Dec 2007 12:24:03 +0100 Hi, I have a PXE/NFS systems for install Fedora from fc1 to f7. All work fine. Today I have add also f8 in this system but I having problems with mount via NFS. kickstart.cfg file is load via nfs (ks=nfs:pxesetup:/u/kickstart/ks-8.cfg) and the source files are in pxesetup:/u/f8 The process start correctly, mount an load ks-8.cfg, mount source dir but when anaconda trying remount kickstart file got an error and the setup process stop. I have switch to CTRL+ALT+F2 and I have trying mount some other dir: mount -t nfs pxesetup:/u/f7 /tmp/f7 but the mount command fail with timeout ... Some problema I have get when I have trying add to my PXE system setup last f7respin ... Probably is a kernel-2.6.23 problem or new-NFS problem ?.... Someone can help me? Many thanks. -- Dario Lesca -- Dario Lesca _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From d.lesca at solinos.it Fri Dec 7 16:18:18 2007 From: d.lesca at solinos.it (Dario Lesca) Date: Fri, 07 Dec 2007 17:18:18 +0100 Subject: [Fwd: f8: install via PXE/NFS problem (mount)] In-Reply-To: References: <1197026902.13142.82.camel@lesca.home.solinos.it> Message-ID: <1197044298.13142.163.camel@lesca.home.solinos.it> Il giorno ven, 07/12/2007 alle 09.56 -0500, Joe_Wulf ha scritto: > - What is the OS of the system hosting your PXE/kickstart processes? Is it > updated and current with patches? Fedora 7 + all standard updates > - How good (what kind) of computer is doing the hosting, how much memory, what > kind of nic card, what network equipment are you dealing with? HP-DL380-G5 4Gb RAM - 2 Intel Xeon CPU Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit > - What is the hardware you are booting via PXE/kickstart (CPU, 32/64 bit, mem)? HP Compaq - 512Mb RAM - 1 Intel(R) Pentium(R) Dual 80GHz > - Are you booting this system to be kickstarted as a virtual machine or as the > physical box itself? Is a physical PC but the problem happened also with VMware > - Can you get a second physically different system to successfully boot via > kickstart for Fedora 8? No, all my test fail. > - What else can you describe of the physical network that might have any bearing > on this problem? All work file, from fc1 to f7 ... > - What specifically is the condition you are seeing that ends the kickstart? > What error message(s) do you see on the console? What is the gist of the > output in VC3 and VC4? something like "mount failed" on VC3/4 and on VC6 a box which show an error in anaconda (ks not found) > >From my own experience I suggest you re-validate your DHCP, DNS, tftp and PXEboot > configuration. With current configuration, if I choice f7 at PXE boot, all work fine. The procedure is the same for all version (i use a shell script in %pre section). > Hopefully these questions will be beneficial to getting your problem resolved. thanks for help. -- Dario Lesca From email at jasonkohles.com Fri Dec 7 20:29:00 2007 From: email at jasonkohles.com (Jason Kohles) Date: Fri, 7 Dec 2007 15:29:00 -0500 Subject: Confirming predefined partition layout using kickstart In-Reply-To: References: Message-ID: <663F9BFD-A39D-4A64-9C42-8EA7BB908B77@jasonkohles.com> On Dec 6, 2007, at 3:02 PM, Peter ?strand wrote: > On Mon, 26 Nov 2007, Peter ?strand wrote: > >> ... >> "Could not allocate requested partitions". If we are using: >> >> zerombr >> clearpart --all --initlabel >> partition / --fstype ext3 --size=1600 --asprimary >> partition swap --recommended >> >> ...things works great, but then there's no confirmation. > > I've discovered one major problem: When booting from a USB stick with > diskboot.img, a kickstart file like this erases the USB stick! How can > this be prevented? It seems like it's fairly reliable that the first > disk > is normally sda, but if booting from USB stick, sda is the stick. I > guess > we need to use "ignoredisk" on the USB stick or something like that, > but I > cannot find any obvious solution. > If you know it will always be sda, you can do: ignoredisk --drives=sda If you don't know for sure that it will always be sda, you can build an ignoredisk line from %pre. This is the code I use to ignore the usb stick regardless of where it shows up... # This part goes in the main body of ks.cfg, I use it for several # different configuration things built by my %pre scripts %include /tmp/generated-configuration %pre # This %pre just makes sure the file exists, so the include # never fails touch /tmp/generated-configuration %pre --interpreter=python # This is a generic %pre script that creates a file named # /tmp/disks with the device name and the size of the disk in MB # You can use this for all kinds of stuff import os import sys import parted sys.path.append('/usr/lib/anaconda') import isys drives = isys.hardDriveDict().keys() drives.sort() f = open( "/tmp/disks", "w" ) for drive in drives: device = "/tmp/" + drive if not os.access(device, os.O_RDONLY): try: isys.makeDevInode(drive, device) except: continue dev = parted.PedDevice.get(device) mb = (float(dev.heads * dev.cylinders * dev.sectors) / (1024 * 1024) * dev.sector_size) dev.close() f.write( "%s %s\n" % ( drive, mb ) ) %pre # This one looks for disks smaller than a given size, and if any are found, ignores them TINY=`awk 'BEGIN { ORS="," } $2 < 2000 { print $1 }' /tmp/disks | sed 's/,$//'` if [ -n "$TINY" ]; then echo "ignoredisk --drives=$TINY" >> /tmp/generated-configuration fi -- Jason Kohles, RHCA RHCDS RHCE email at jasonkohles.com - http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire From astrand at cendio.se Mon Dec 10 08:30:04 2007 From: astrand at cendio.se (=?UTF-8?Q?Peter_=C3=85strand?=) Date: Mon, 10 Dec 2007 09:30:04 +0100 (CET) Subject: Confirming predefined partition layout using kickstart In-Reply-To: <663F9BFD-A39D-4A64-9C42-8EA7BB908B77@jasonkohles.com> References: <663F9BFD-A39D-4A64-9C42-8EA7BB908B77@jasonkohles.com> Message-ID: On Fri, 7 Dec 2007, Jason Kohles wrote: > >I've discovered one major problem: When booting from a USB stick with > >diskboot.img, a kickstart file like this erases the USB stick! How can > ignoredisk line from %pre. This is the code I use to ignore the usb stick > regardless of where it shows up... > %pre > # This one looks for disks smaller than a given size, and if any are found, > ignores them > TINY=`awk 'BEGIN { ORS="," } $2 < 2000 { print $1 }' /tmp/disks | sed > 's/,$//'` > if [ -n "$TINY" ]; then > echo "ignoredisk --drives=$TINY" >> /tmp/generated-configuration > fi Thanks. In our case, however, I don't think this will work. Our target disk requirement is only 1.5 GB and 2 GB USB sticks are not uncommon. We ended up with another method that disables all SCSI devices that contains the ISOLINUX splash file. 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 rvandolson at esri.com Wed Dec 12 17:40:04 2007 From: rvandolson at esri.com (Ray Van Dolson) Date: Wed, 12 Dec 2007 09:40:04 -0800 Subject: Kickstart installation via network -- not able to override network settings? Message-ID: <20071212174004.GA24416@esri.com> May repost this on the anaconda list as I'm not sure which list is more appropriate. In any case, I am doing network-based kickstart installs with RHEL 5.1 and running into an issue where anaconda is not prompting me for network card information. We specify the location of the kickstart file as located on an NFS share on bootup. The installation URL is via HTTP. Back in the RHEL4 days we used this same method -- we essentially use the kickstart file as "defalts" and do an interactive install so the installer may override things on an as-needed basis. Often times I machine requires a static IP address so the installer would simply provide this information when prompted to by anaconda. However, in RHEL5 we are _never_ prompted for network information at all. From reading the kickstart documentation it seems that if you are doing a network installation and do not provide any network configuration information in the kickstart file then it is assumed that you will be acquring your IP address via DHCP and the installed system is also configured in this same way. It would seem that my alternatives would be to either specify the full static IP information via the network keyword in the kickstart file or rely on a CD-based installation so that I am presented with the network settings dialog during installation. Neither is a great option as this means I will have to maintain special copies of the kickstart file for machines requiring static IP's or require the user to configure networking post installation to override the default DHCP setup. I realize I could also pass IP information via the bootup options, but I am trying to make this as trivial as possible for installers, and all that extra typing is prone to typo's. I have tried modifying my kickstart file to include only "network --bootproto=static" to no avail. Apparently it needs all of the options for this to work. And I still don't get a screen in the installer to manually configure networking. I've enabled debugging during the installation and don't see anything pointing to why the networking screen isn't brought up. Am I doing something wrong? Is this just "how it works" now with kickstart / anaconda? Thanks in advance. Ray From Chip.Shabazian at bankofamerica.com Wed Dec 12 18:21:15 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 12 Dec 2007 10:21:15 -0800 Subject: Kickstart installation via network -- not able to override network settings? In-Reply-To: <20071212174004.GA24416@esri.com> Message-ID: Have you tried using the "interactive" option in your kickstart file? -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ray Van Dolson Sent: Wednesday, December 12, 2007 9:40 AM To: kickstart-list at redhat.com Subject: Kickstart installation via network -- not able to override network settings? May repost this on the anaconda list as I'm not sure which list is more appropriate. In any case, I am doing network-based kickstart installs with RHEL 5.1 and running into an issue where anaconda is not prompting me for network card information. We specify the location of the kickstart file as located on an NFS share on bootup. The installation URL is via HTTP. Back in the RHEL4 days we used this same method -- we essentially use the kickstart file as "defalts" and do an interactive install so the installer may override things on an as-needed basis. Often times I machine requires a static IP address so the installer would simply provide this information when prompted to by anaconda. However, in RHEL5 we are _never_ prompted for network information at all. From reading the kickstart documentation it seems that if you are doing a network installation and do not provide any network configuration information in the kickstart file then it is assumed that you will be acquring your IP address via DHCP and the installed system is also configured in this same way. It would seem that my alternatives would be to either specify the full static IP information via the network keyword in the kickstart file or rely on a CD-based installation so that I am presented with the network settings dialog during installation. Neither is a great option as this means I will have to maintain special copies of the kickstart file for machines requiring static IP's or require the user to configure networking post installation to override the default DHCP setup. I realize I could also pass IP information via the bootup options, but I am trying to make this as trivial as possible for installers, and all that extra typing is prone to typo's. I have tried modifying my kickstart file to include only "network --bootproto=static" to no avail. Apparently it needs all of the options for this to work. And I still don't get a screen in the installer to manually configure networking. I've enabled debugging during the installation and don't see anything pointing to why the networking screen isn't brought up. Am I doing something wrong? Is this just "how it works" now with kickstart / anaconda? Thanks in advance. Ray _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From rvandolson at esri.com Wed Dec 12 18:40:23 2007 From: rvandolson at esri.com (Ray Van Dolson) Date: Wed, 12 Dec 2007 10:40:23 -0800 Subject: Kickstart installation via network -- not able to override network settings? In-Reply-To: References: <20071212174004.GA24416@esri.com> Message-ID: <20071212184023.GA3480@esri.com> On Wed, Dec 12, 2007 at 10:21:15AM -0800, Shabazian, Chip wrote: > Have you tried using the "interactive" option in your kickstart file? Yep, I can post KS file if necessary too. We've always used interactive BTW. Tough to give the installers access to override things via the installer otherwise ;) Ray From Chip.Shabazian at bankofamerica.com Wed Dec 12 18:47:11 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 12 Dec 2007 10:47:11 -0800 Subject: Kickstart installation via network -- not able to override network settings? In-Reply-To: <20071212184023.GA3480@esri.com> Message-ID: I assumed (obviously incorrectly) that you were just leaving network blank and only having that set interactively instead of using the interactive command to allow installers to change every value. Could you use non-routable IP's in the kickstart file along with interactive? Wouldn't that give you what you want? Alternatively, you could pop up a dialog box in the %pre environment and use that to set the network settings, writing to a file and then including it. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ray Van Dolson Sent: Wednesday, December 12, 2007 10:40 AM To: kickstart-list at redhat.com Subject: Re: Kickstart installation via network -- not able to override network settings? On Wed, Dec 12, 2007 at 10:21:15AM -0800, Shabazian, Chip wrote: > Have you tried using the "interactive" option in your kickstart file? Yep, I can post KS file if necessary too. We've always used interactive BTW. Tough to give the installers access to override things via the installer otherwise ;) Ray _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From rvandolson at esri.com Wed Dec 12 19:00:34 2007 From: rvandolson at esri.com (Ray Van Dolson) Date: Wed, 12 Dec 2007 11:00:34 -0800 Subject: Kickstart installation via network -- not able to override network settings? In-Reply-To: References: <20071212184023.GA3480@esri.com> Message-ID: <20071212190034.GA3701@esri.com> > Could you use non-routable IP's in the kickstart file along with > interactive? Wouldn't that give you what you want? Hmm, I'm not sure I totally follow here. You are suggesting throwing in a RFC1918 IP in kickstart (using bootproto=static) or a bogus IP (like 256.256.2.2)? Would the latter result in the network dialog being made available to me? > Alternatively, you could pop up a dialog box in the %pre environment and > use that to set the network settings, writing to a file and then > including it. This is probably the route we'll end up going if there's no way to get anaconda to present the network config page during installation the way we want... Thanks! From Chip.Shabazian at bankofamerica.com Wed Dec 12 19:14:36 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 12 Dec 2007 11:14:36 -0800 Subject: Kickstart installation via network -- not able to override network settings? In-Reply-To: <20071212190034.GA3701@esri.com> Message-ID: I was suggesting using something like: network --bootproto=static --ip=10.0.0.2 --netmask=255.255.255.0 --gateway=10.0.0.1 interactive I'm not sure if that will work or not, I haven't tried it, but give it a shot. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ray Van Dolson Sent: Wednesday, December 12, 2007 11:01 AM To: kickstart-list at redhat.com Subject: Re: Kickstart installation via network -- not able to override network settings? > Could you use non-routable IP's in the kickstart file along with > interactive? Wouldn't that give you what you want? Hmm, I'm not sure I totally follow here. You are suggesting throwing in a RFC1918 IP in kickstart (using bootproto=static) or a bogus IP (like 256.256.2.2)? Would the latter result in the network dialog being made available to me? > Alternatively, you could pop up a dialog box in the %pre environment > and use that to set the network settings, writing to a file and then > including it. This is probably the route we'll end up going if there's no way to get anaconda to present the network config page during installation the way we want... Thanks! _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Pablo.Iranzo at redhat.com Wed Dec 12 20:05:23 2007 From: Pablo.Iranzo at redhat.com (=?UTF-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Wed, 12 Dec 2007 21:05:23 +0100 (CET) Subject: Kickstart installation via network -- not able to override network settings? In-Reply-To: References: Message-ID: I was this evening at IRC channel suggesting to use smth like: chvt 3 echo "Enter IP" read IP echo "Enter NetMask" read NM ... verify data ... create /etc/sysconfig/network-scripts/ifcfg-eth0 using that information 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 Wed, 12 Dec 2007, Shabazian, Chip wrote: > > I was suggesting using something like: > network --bootproto=static --ip=10.0.0.2 --netmask=255.255.255.0 > --gateway=10.0.0.1 > interactive > > I'm not sure if that will work or not, I haven't tried it, but give it a > shot. > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ray Van Dolson > Sent: Wednesday, December 12, 2007 11:01 AM > To: kickstart-list at redhat.com > Subject: Re: Kickstart installation via network -- not able to override > network settings? > > > Could you use non-routable IP's in the kickstart file along with > > interactive? Wouldn't that give you what you want? > > Hmm, I'm not sure I totally follow here. You are suggesting throwing in > a RFC1918 IP in kickstart (using bootproto=static) or a bogus IP (like > 256.256.2.2)? Would the latter result in the network dialog being made > available to me? > > > Alternatively, you could pop up a dialog box in the %pre environment > > and use that to set the network settings, writing to a file and then > > including it. > > This is probably the route we'll end up going if there's no way to get > anaconda to present the network config page during installation the way > we want... > > Thanks! > > _______________________________________________ > 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 matteo.faleschini at fisica.unimi.it Fri Dec 14 12:02:56 2007 From: matteo.faleschini at fisica.unimi.it (Matteo Faleschini) Date: Fri, 14 Dec 2007 13:02:56 +0100 Subject: fedora 8 static ip not accepted Message-ID: <476270F0.6070306@fisica.unimi.it> I'm having problems to use this option inside the kickstart file network --bootproto=static --device=eth0 --gateway=192.168.1.254 --ip=192.168.1.1 --netmask=255.255.255.0 --onboot=on with a nfs or http installation. nfs --server ksbox.local.domain --dir /fedora/8.0/os In our departement we use a templating system that we wrote since redhat 9 to fedora 6 (and scientific linux 4, a redhat derived) without problems. When I prepared the kickstart for the new fedora 8, I noticed that anaconda (11.3.0.50) does not use the static ip information provided by the kickstart and chooses a dhcp configuration. To verify that it is not an error of our kickstart creator, I prepared a kickstart file on a fedora 8 machine with the system-config-kickstart script. But I found the same problem. I also switched the network and nfs lines but i found no difference. At first I thought about a new anaconda behaviour (nfs install uses only dynamic configuration) but having a look at the source code of the anaconda loader I have the impression that the network bootstrap follows the same principles. I searched through the mailing list for keywords bootproto and 11.3.0.50 with no success. I also googled about but i did not find any hint. I don't know if it's a known anaconda issue or a syntax error of my kickstart. Matteo Faleschini From accarlson at gmail.com Fri Dec 14 14:54:54 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Fri, 14 Dec 2007 12:54:54 -0200 Subject: fedora 8 ks and cdrom Message-ID: Hi! I'm would like to install Fedora 8 with kickstart using a cdrom media. But as reported in the link below, there is a bug. http://www.nabble.com/Fedora-8-Update-3A-pykickstart-1.19-1.fc8-to13716979.html I saw in the list archives a message about that problem (https://www.redhat.com/archives/kickstart-list/2007-November/msg00020.html), but I do not understand how to fix that. Can I substitute the pyickstart package and rebuild the DVD iso to burn it? What other files I need to modify? Any other solution? Thanks in advance! Regards, -- Augusto From kanarip at kanarip.com Fri Dec 14 14:59:25 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Fri, 14 Dec 2007 15:59:25 +0100 Subject: fedora 8 ks and cdrom In-Reply-To: References: Message-ID: <47629A4D.9090903@kanarip.com> Augusto Castelan Carlson wrote: > Hi! > > I'm would like to install Fedora 8 with kickstart using a cdrom media. > But as reported in the link below, there is a bug. > > http://www.nabble.com/Fedora-8-Update-3A-pykickstart-1.19-1.fc8-to13716979.html > > I saw in the list archives a message about that problem > (https://www.redhat.com/archives/kickstart-list/2007-November/msg00020.html), > but I do not understand how to fix that. > > Can I substitute the pyickstart package and rebuild the DVD iso to > burn it? What other files I need to modify? > > Any other solution? > The Fedora 8 Re-Spin has this fix, amongst others, so you might want to wait until it's fully tested, or help testing it (send me a mail). All you need to do is re-spin with the updates/ repository enabled; either using pungi or Revisor. Kind regards, Jeroen van Meeuwen -kanarip From binbrain at gmail.com Fri Dec 14 16:02:19 2007 From: binbrain at gmail.com (jim Pharis) Date: Fri, 14 Dec 2007 11:02:19 -0500 Subject: kickstart w/o netconfig in RHEL5 Message-ID: <77f231800712140802v2ac80100n8115791cbed4e848@mail.gmail.com> Kickstarters, We kickstart systems in a quarantined network. Once an installation has completed, we move the system to its actual network, and then run post-installation scripts to configure the actual network and then cfengine the machine. We use a package called netconfig in our post-installation scripts to move the system to its permanent network just before we do the key exchange w/ our cfengine server. netconfig appears to be long gone and removed from RHEL5. The alternative tool appears to be system-configure-network-tui, but it has a GUI and requires user interaction. We need a command line tool to configure the network interface. Any suggestions for solving this. The only alternative way I can think of would be to write post-installation scripts by hand to edit the ifcfg-eth files. Can anybody think of better process/tool? TIA -- - Jim Pharis From richzendy at gmail.com Fri Dec 14 16:41:27 2007 From: richzendy at gmail.com (Edwind Richzendy Contreras Soto) Date: Sat, 15 Dec 2007 12:11:27 +1930 Subject: fedora 8 static ip not accepted In-Reply-To: <476270F0.6070306@fisica.unimi.it> References: <476270F0.6070306@fisica.unimi.it> Message-ID: <90ba020d0712140841s7acfda5fr5fdf66d990b32679@mail.gmail.com> 2007/12/15, Matteo Faleschini : > > > I'm having problems to use this option inside the kickstart file > > network --bootproto=static --device=eth0 --gateway=192.168.1.254 > --ip=192.168.1.1 --netmask=255.255.255.0 --onboot=on > > with a nfs or http installation. > > nfs --server ksbox.local.domain --dir /fedora/8.0/os > > In our departement we use a templating system that we wrote since > redhat 9 to fedora 6 (and scientific linux 4, a redhat derived) without > problems. > > When I prepared the kickstart for the new fedora 8, I noticed that > anaconda (11.3.0.50) does not use the static ip information provided by > the kickstart and chooses a dhcp configuration. > > To verify that it is not an error of our kickstart creator, I prepared a > kickstart file on a fedora 8 machine with the system-config-kickstart > script. But I found the same problem. > I also switched the network and nfs lines but i found no difference. > > At first I thought about a new anaconda behaviour (nfs install uses only > dynamic configuration) but having a look at the source code of the > anaconda loader I have the impression that the network bootstrap follows > the same principles. > > I searched through the mailing list for keywords bootproto and 11.3.0.50 > with no success. I also googled about but i did not find any hint. I > don't know if it's a known anaconda issue or a syntax error of my > kickstart. > > Matteo Faleschini i have a same problem, it's a bug in anaconda for fedora 8? _______________________________________________ > 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 richzendy at gmail.com Fri Dec 14 18:37:04 2007 From: richzendy at gmail.com (Edwind Richzendy Contreras Soto) Date: Sat, 15 Dec 2007 14:07:04 +1930 Subject: fedora 8 static ip not accepted In-Reply-To: <90ba020d0712140841s7acfda5fr5fdf66d990b32679@mail.gmail.com> References: <476270F0.6070306@fisica.unimi.it> <90ba020d0712140841s7acfda5fr5fdf66d990b32679@mail.gmail.com> Message-ID: <90ba020d0712141037j6d558c8aj5b8238f2adc5449c@mail.gmail.com> My kickstart file is: install network --device eth0 --bootproto static --noipv6 --ip 192.168.X.XXX--netmask 255.255.255.0 --gateway 192.168.X.XXX --nameserver 192.168.X.XXX --hostname pc1.XXXX.XXX.XX url --url http://192.168.X.XX/linux/f8/releases/Everything/i386/os keyboard la-latin1 lang es_ES.UTF-8 xconfig --startxonboot auth --useshadow --enablemd5 --enableldap --enableldapauth --ldapserver= 192.168.X.XXX -ldapbasedn=ou=People,dc=XXXX,dc=XXX,dc=XX rootpw --iscrypted $1$NxRxxxxvxNxvxSd$fboxXxwZxxcLSGxAx68xuxyxsxyxEx6xBu5/ firewall --enabled --port=22:tcp authconfig --enableshadow --enablemd5 selinux --enforcing timezone --utc America/Caracas bootloader --location=mbr --driveorder=sda --append="vga=791 rhgb quiet" --md5pass=$1$/v6xxNxxgx05A$BxFxxYxbxsxOxaxbx7xkxEBxUixuxBxlxdxxx1h0 # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --drives=sda part /boot --fstype ext3 --size=200 --ondisk=sda part pv.6 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.6 logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=576 logvol /home --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=60000 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=496 --grow --maxsize=992 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=14496 repo --name=XXXXX-Livna --baseurl=http://192.168.X.XX/linux/f8/livna/i386/ repo --name=XXXX-Update --baseurl=http://192.168.X.XX/linux/f8/updates #reboot after install reboot --eject %post echo "session required pam_mkhomedir.so skel=/etc/skel/ umask=0022" >> /etc/pam.d/gdm %packages packages ... ... ... i put a kickstart from http server and it's is my boot line: boot: linux ks=http://192.168.X.XX ip=192.168.x.xx netmask=255.255.255.0gateway= 192.168.x.xx ip and gateway ips in boot line same equal to a ip and gateway ips to network line in kickstart file. but my instalation is frozen in a infinite loop searching a DHCP server after read and put kickstart file. What is wrong? 2007/12/15, Edwind Richzendy Contreras Soto : > > > > 2007/12/15, Matteo Faleschini : > > > > > > I'm having problems to use this option inside the kickstart file > > > > network --bootproto=static --device=eth0 --gateway=192.168.1.254 > > --ip=192.168.1.1 --netmask=255.255.255.0 --onboot=on > > > > with a nfs or http installation. > > > > nfs --server ksbox.local.domain --dir /fedora/8.0/os > > > > In our departement we use a templating system that we wrote since > > redhat 9 to fedora 6 (and scientific linux 4, a redhat derived) without > > problems. > > > > When I prepared the kickstart for the new fedora 8, I noticed that > > anaconda (11.3.0.50) does not use the static ip information provided by > > the kickstart and chooses a dhcp configuration. > > > > To verify that it is not an error of our kickstart creator, I prepared a > > kickstart file on a fedora 8 machine with the system-config-kickstart > > script. But I found the same problem. > > I also switched the network and nfs lines but i found no difference. > > > > At first I thought about a new anaconda behaviour (nfs install uses only > > dynamic configuration) but having a look at the source code of the > > anaconda loader I have the impression that the network bootstrap follows > > the same principles. > > > > I searched through the mailing list for keywords bootproto and 11.3.0.50 > > with no success. I also googled about but i did not find any hint. I > > don't know if it's a known anaconda issue or a syntax error of my > > kickstart. > > > > Matteo Faleschini > > > > i have a same problem, it's a bug in anaconda for fedora 8? > > _______________________________________________ > > 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 email at jasonkohles.com Mon Dec 17 14:10:59 2007 From: email at jasonkohles.com (Jason Kohles) Date: Mon, 17 Dec 2007 09:10:59 -0500 Subject: kickstart w/o netconfig in RHEL5 In-Reply-To: <77f231800712140802v2ac80100n8115791cbed4e848@mail.gmail.com> References: <77f231800712140802v2ac80100n8115791cbed4e848@mail.gmail.com> Message-ID: <8979FE10-CC7F-40C9-A1E8-552285B46EF0@jasonkohles.com> On Dec 14, 2007, at 11:02 AM, jim Pharis wrote: > Kickstarters, > > We kickstart systems in a quarantined network. Once an > installation has completed, we move the system to its actual network, > and then run post-installation scripts to configure the actual network > and then cfengine the machine. We use a package called netconfig in > our post-installation scripts to move the system to its permanent > network just before we do the key exchange w/ our cfengine server. > > netconfig appears to be long gone and removed from RHEL5. The > alternative tool appears to be system-configure-network-tui, but it > has a > GUI and requires user interaction. We need a command line tool to > configure the network interface. Any suggestions for solving this. > The only > alternative way I can think of would be to write post-installation > scripts by hand to edit > the ifcfg-eth files. Can anybody think of better process/tool? > In addition to system-config-network-tui, there is also a command-line tool called system-config-network-cmd. The easiest way to handle this is to use it to export the configuration, modify the file as required, then re-import it. That way you don't even have to worry about where the files are stored, just let the tools handle the files... # -e for export system-config-network-cmd -e > /tmp/network-config # modify /tmp/network-config as required # -i = import, -c = clear existing configuration before import, -f import this file... system-config-network-cmd -i -c -f /tmp/network-config -- Jason Kohles, RHCA RHCDS RHCE email at jasonkohles.com - http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire From binbrain at gmail.com Tue Dec 18 18:25:01 2007 From: binbrain at gmail.com (jim Pharis) Date: Tue, 18 Dec 2007 13:25:01 -0500 Subject: kickstart w/o netconfig in RHEL5 In-Reply-To: <8979FE10-CC7F-40C9-A1E8-552285B46EF0@jasonkohles.com> References: <77f231800712140802v2ac80100n8115791cbed4e848@mail.gmail.com> <8979FE10-CC7F-40C9-A1E8-552285B46EF0@jasonkohles.com> Message-ID: <77f231800712181025q137e9854k983a7d93f0888e8c@mail.gmail.com> That will do the trick. Thanks Jason. On Dec 17, 2007 9:10 AM, Jason Kohles wrote: > > On Dec 14, 2007, at 11:02 AM, jim Pharis wrote: > > > Kickstarters, > > > > We kickstart systems in a quarantined network. Once an > > installation has completed, we move the system to its actual network, > > and then run post-installation scripts to configure the actual network > > and then cfengine the machine. We use a package called netconfig in > > our post-installation scripts to move the system to its permanent > > network just before we do the key exchange w/ our cfengine server. > > > > netconfig appears to be long gone and removed from RHEL5. The > > alternative tool appears to be system-configure-network-tui, but it > > has a > > GUI and requires user interaction. We need a command line tool to > > configure the network interface. Any suggestions for solving this. > > The only > > alternative way I can think of would be to write post-installation > > scripts by hand to edit > > the ifcfg-eth files. Can anybody think of better process/tool? > > > > In addition to system-config-network-tui, there is also a command-line > tool called system-config-network-cmd. The easiest way to handle this > is to use it to export the configuration, modify the file as required, > then re-import it. That way you don't even have to worry about where > the files are stored, just let the tools handle the files... > > # -e for export > system-config-network-cmd -e > /tmp/network-config > > # modify /tmp/network-config as required > > # -i = import, -c = clear existing configuration before import, -f > import this file... > system-config-network-cmd -i -c -f /tmp/network-config > > -- > Jason Kohles, RHCA RHCDS RHCE > email at jasonkohles.com - http://www.jasonkohles.com/ > "A witty saying proves nothing." -- Voltaire > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- - Jim Pharis From linuxgod at gmail.com Tue Dec 18 15:06:33 2007 From: linuxgod at gmail.com (Geoff Silver) Date: Tue, 18 Dec 2007 15:06:33 +0000 (UTC) Subject: Kickstart issue References: Message-ID: We ran into the same issue at my company, and I didn't want anaconda to install on the SAN and wipe out a database. The trick is to use a python script in the %pre section of your kickstart to write out a partitioning file, then import that using %import. Your kickstart should looks like so: install text network --bootproto dhcp ... zerombr yes bootloader --location mbr clearpart --all --initlabel %include /tmp/part-include %packages ... %pre /usr/bin/python < References: <476270F0.6070306@fisica.unimi.it> <90ba020d0712140841s7acfda5fr5fdf66d990b32679@mail.gmail.com> <90ba020d0712141037j6d558c8aj5b8238f2adc5449c@mail.gmail.com> Message-ID: <476A7875.5080006@fisica.unimi.it> I posted a possible solution to redhat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=392021 Install the anaconda source rpm and prepare the sources with rpmbuild -bp (in /usr/src/redhat/SPEC/) They are in /usr/src/redhat/BUILD/anaconda.xxx Enter the directory loader2 and edit file loader.c as explained on bugzilla. Change directory to the anaconda root dir ( ../ ) and do make. Now you have to copy loader2/loader inside the initrd.img of the isolinux directory. It's a gzipped cpio archive To open it copy it to a tmp dir then mkdir initrd.dir cd initrd.dir zcat ../initrd.img | cpio -idv Copy inside bin/ the previously compiled loader then recreate the initrd.img. Inside initrd.dir do find . -print | cpio -o -c --quiet | gzip -c9 > ../initrd.img.new And finally copy the inird.img.new as initrd.img inside the isolinux/ directory, the one you use for creating kickstart cd's. Matteo Faleschini Edwind Richzendy Contreras Soto wrote: > My kickstart file is: > > > install > network --device eth0 --bootproto static --noipv6 --ip 192.168.X.XXX--netmask > 255.255.255.0 --gateway 192.168.X.XXX --nameserver 192.168.X.XXX --hostname > pc1.XXXX.XXX.XX > url --url http://192.168.X.XX/linux/f8/releases/Everything/i386/os > keyboard la-latin1 > lang es_ES.UTF-8 > xconfig --startxonboot > auth --useshadow --enablemd5 --enableldap --enableldapauth --ldapserver= > 192.168.X.XXX -ldapbasedn=ou=People,dc=XXXX,dc=XXX,dc=XX > rootpw --iscrypted $1$NxRxxxxvxNxvxSd$fboxXxwZxxcLSGxAx68xuxyxsxyxEx6xBu5/ > firewall --enabled --port=22:tcp > authconfig --enableshadow --enablemd5 > selinux --enforcing > timezone --utc America/Caracas > bootloader --location=mbr --driveorder=sda --append="vga=791 rhgb quiet" > --md5pass=$1$/v6xxNxxgx05A$BxFxxYxbxsxOxaxbx7xkxEBxUixuxBxlxdxxx1h0 > # The following is the partition information you requested > # Note that any partitions you deleted are not expressed > # here so unless you clear all partitions first, this is > # not guaranteed to work > clearpart --all --drives=sda > part /boot --fstype ext3 --size=200 --ondisk=sda > part pv.6 --size=0 --grow --ondisk=sda > volgroup VolGroup00 --pesize=32768 pv.6 > logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=576 > logvol /home --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=60000 > logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=496 > --grow --maxsize=992 > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=14496 > repo --name=XXXXX-Livna --baseurl=http://192.168.X.XX/linux/f8/livna/i386/ > repo --name=XXXX-Update --baseurl=http://192.168.X.XX/linux/f8/updates > #reboot after install > reboot --eject > > %post > echo "session required pam_mkhomedir.so skel=/etc/skel/ umask=0022" >>> /etc/pam.d/gdm > > %packages > packages > ... > ... > ... > > > i put a kickstart from http server and it's is my boot line: > > boot: linux ks=http://192.168.X.XX ip=192.168.x.xx netmask=255.255.255.0gateway= > 192.168.x.xx > > ip and gateway ips in boot line same equal to a ip and gateway ips to > network line in kickstart file. > > but my instalation is frozen in a infinite loop searching a DHCP server > after read and put kickstart file. > > What is wrong? > > > 2007/12/15, Edwind Richzendy Contreras Soto : >> >> >> 2007/12/15, Matteo Faleschini : >>> >>> I'm having problems to use this option inside the kickstart file >>> >>> network --bootproto=static --device=eth0 --gateway=192.168.1.254 >>> --ip=192.168.1.1 --netmask=255.255.255.0 --onboot=on >>> >>> with a nfs or http installation. >>> >>> nfs --server ksbox.local.domain --dir /fedora/8.0/os >>> >>> In our departement we use a templating system that we wrote since >>> redhat 9 to fedora 6 (and scientific linux 4, a redhat derived) without >>> problems. >>> >>> When I prepared the kickstart for the new fedora 8, I noticed that >>> anaconda (11.3.0.50) does not use the static ip information provided by >>> the kickstart and chooses a dhcp configuration. >>> >>> To verify that it is not an error of our kickstart creator, I prepared a >>> kickstart file on a fedora 8 machine with the system-config-kickstart >>> script. But I found the same problem. >>> I also switched the network and nfs lines but i found no difference. >>> >>> At first I thought about a new anaconda behaviour (nfs install uses only >>> dynamic configuration) but having a look at the source code of the >>> anaconda loader I have the impression that the network bootstrap follows >>> the same principles. >>> >>> I searched through the mailing list for keywords bootproto and 11.3.0.50 >>> with no success. I also googled about but i did not find any hint. I >>> don't know if it's a known anaconda issue or a syntax error of my >>> kickstart. >>> >>> Matteo Faleschini >> >> >> i have a same problem, it's a bug in anaconda for fedora 8? >> >> _______________________________________________ >>> 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 Floydsmith at aol.com Sun Dec 23 11:17:41 2007 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Sun, 23 Dec 2007 06:17:41 EST Subject: how do I split Fedora-8-i386-Everything-DVD1.iso Message-ID: I managed to pullin Re-Spin: Fedora-8-i386-Everything-DVD1.iso last night only to find that although it fits onto a single DVD, it expects to be split up into 3 images on 3 DVDs. Can anyone tell me on my pristeen f8 machine what tools I will need to download and how to do the "split". Floyd, ************************************** See AOL's top rated recipes (http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanarip at kanarip.com Sun Dec 23 12:23:18 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Sun, 23 Dec 2007 13:23:18 +0100 Subject: how do I split Fedora-8-i386-Everything-DVD1.iso In-Reply-To: References: Message-ID: <476E5336.2060506@kanarip.com> Floydsmith at aol.com wrote: > I managed to pullin Re-Spin: > Fedora-8-i386-Everything-DVD1.iso > last night only to find that although it > fits onto a single DVD, it expects to be > split up into 3 images on 3 DVDs. Can > anyone tell me on my pristeen f8 machine > what tools I will need to download and > how to do the "split". > > Floyd, > Hi Floyd, This spin is not a Re-Spin, but a custom spin built off the installation tree, containing all packages available. It doesn't expect to the split into 3 DVDs, but there's 3 DVDs to the entire spin, and you'll need all of them if you are going to do a complete installation or if you select packages that are on the second or third DVD. You should download the other DVDs along with the one you just downloaded, or choose another spin from http://fedoraproject.org/get-fedora (it has single DVDs there), wait for the Fedora Unity Re-Spin of Fedora 8 to be released (that'll have single DVDs too). Kind regards, Jeroen van Meeuwen -kanarip From nauman.yousuf at gmail.com Mon Dec 24 07:02:44 2007 From: nauman.yousuf at gmail.com (Nauman yousuf) Date: Sun, 23 Dec 2007 23:02:44 -0800 (PST) Subject: Invitation to connect on LinkedIn Message-ID: <1349622276.1198479764638.JavaMail.app@com04.prod> Discussion, I'd like to add you to my professional network on LinkedIn. -Nauman Follow this link to join Nauman yousuf on LinkedIn: https://www.linkedin.com/e/isd/184165551/Oav4BXSn/ ------------------------------------------ "Increasingly, if you're not LinkedIn, you're left out." --CNN Money ------ (c) 2007, LinkedIn Corporation -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at netcore.co.in Mon Dec 24 07:15:45 2007 From: ram at netcore.co.in (ram) Date: Mon, 24 Dec 2007 12:45:45 +0530 Subject: Invitation to connect on LinkedIn In-Reply-To: <1349622276.1198479764638.JavaMail.app@com04.prod> References: <1349622276.1198479764638.JavaMail.app@com04.prod> Message-ID: <1198480545.3330.0.camel@localhost.localdomain> Stop, this is spamming On Sun, 2007-12-23 at 23:02 -0800, Nauman yousuf wrote: > Discussion, > > I'd like to add you to my professional network on LinkedIn. > > -Nauman > > Follow this link to join Nauman yousuf on LinkedIn: > https://www.linkedin.com/e/isd/184165551/Oav4BXSn/ > > > ______________________________________________________________________ > > "Increasingly, if you're not LinkedIn, you're left out." --CNN Money > > > ? 2007, LinkedIn Corporation > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Floydsmith at aol.com Wed Dec 26 10:37:59 2007 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Wed, 26 Dec 2007 05:37:59 EST Subject: pykickstart1-19-1-f8 (and -18-) does not support CDROM install with onpart= Message-ID: Using a revisor image from the aftertoon of 12-24-07 I have learned that (unlike in Fedora 5, 6 and 7) that a very simple kickstart cfg involving onpart does not work. First, the following two (which clear the MBR) DO WORK: # System bootloader configuration bootloader --location=mbr # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart text # System bootloader configuration bootloader --location=mbr # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel part /boot --fstype ext3 --size=100 --ondisk=sda part pv.1 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=16384 pv.1 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=512 --grow --maxsize=512 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=15000 text However, none of the many of the cfg(s) which DO NOT CLEAR the MBR DO NOT WORK. What I normally do is use fdisk to create a pre existing linux parttition and at least one swap and then use: # System bootloader configuration bootloader --location=mbr # Partition clearing information clearpart --none # I have already created a patition of the desired size with type linux # and a swap partition has already been setup. part / --fstype=ext3 --onpart=sda1 text I have tried many variations of this such as providing a size or leaving some unallocated space on the drive and then using (ondisk=sda) instead. All attempts result in exactly the same error msg of: File "/usr/lib/anaconda/kickstart.py, line 295, in parse log.setHandlersLevel... KeyError: '' If something is different in F8 regrading the syntax has changed please let me know. The reason I can't use the examples that clear the MBR is I have other partitions on the disk that I want to preserve. Any help will be greatly appreciated. Floyd, ************************************** See AOL's top rated recipes (http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Floydsmith at aol.com Thu Dec 27 14:41:54 2007 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Thu, 27 Dec 2007 09:41:54 EST Subject: more info on pykickstart parse error - simple reproduce Message-ID: Here is a ks.cfg that produces the 295 parse error but does NOT refernce onpart or ondisk. (It is intended to run on a machine with a sda drive that I wish to preserve) and a sdb drive (that is completely unallocated space) and is the drive I wish to install on. As I said above, it fails (as is) but WILL WORK BY ADDING JUST ONE CHAR. That is, comment out with a # char line 25 (logging info) line to have it be parsed correctly and the OS be installed. Now, I have seen this behavior with the orginal F8 pykistart prog (ver. -18-) but not with -19- (until now). I may be wrong, but seems that to reproduce the prob, lines like this fail ONLY in certain cases. If that is the case, this may be corruption in the paring buffer (overflow, for example). I know from my many experiements that commenting out this line is NOT ENOUGH when either "onpart OR odisk" is used. Here is the bad parse ks.cfg # Kickstart file for composing the "Fedora" spin of Fedora 8 #platform=x86, AMD64, or Intel EM64T # System authorization information auth --useshadow --enablemd5 # System bootloader configuration bootloader --location=mbr ignoredisk --drives=sda clearpart --drives=sdb part /boot --fstype ext3 --size=100 --ondisk=sdb part pv.1 --size=0 --grow --ondisk=sdb volgroup VolGroup00 --pesize=16384 pv.1 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=512 --grow --maxsize=512 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=15000 text # Firewall configuration firewall --enabled # Run the Setup Agent on first boot firstboot --enabled #interactive # System keyboard keyboard us # System language lang en_US # Installation logging level logging info # Use CDROM installation media cdrom #harddrive --partition=sda1 --dir=/ # Network information network --device eth0 --bootproto dhcp --hostname floydsmi --onboot=on network --device eth1 --bootproto dhcp --hostname floydsmi --onboot=on # Reboot after installation reboot #Root password #rootpw --iscrypted $1$aaaaaa$GXMJ3udCd0ey9r4NUNOsk/ rootpw --iscrypted $1$812aSfDP$n3uhf7d//gw1Lh.cei.ue1 # SELinux configuration selinux --disabled # System timezone timezone America/New_York # Install OS instead of upgrade install # X Window System configuration information #xconfig --defaultdesktop=GNOME --startxonboot xconfig --driver "sis" --defaultdesktop=GNOME --resolution 1024x768 --depth 24 # Package manifest for the compose. Uses repo group metadata to translate groups. # (@base is added by default unless you add --nobase to %packages) %packages # core @core @base-x kernel* # Hardware stuff @hardware-support @dial-up # Desktop Packages @gnome-desktop @kde-desktop echo-icon-theme tracker gnash liferea esc # apps @authoring-and-publishing @eclipse @editors emacs @games @graphical-internet @graphics @java @office @sound-and-video @text-internet @system-tools wireshark-gnome # Devel packages @development-libs @development-tools @gnome-software-development @java-development @kde-software-development @web-development @x-software-development # Server packages @dns-server @ftp-server @mail-server @mysql @network-server @news-server @printing @server-cfg @smb-server @sql-server @web-server --optional # Virt group @virtualization --optional # filesystem stuff reiserfs-utils xfsprogs jfsutils # Languages @filipino-support @tagalog-support # Compose Needs anaconda-runtime iscsi-initiator-utils memtest86+ vnc-server createrepo # This one is already in core 6 Fedora/RPMS dir - no need to copy it to there in mkisofsDVD4.sh # This is needed when comps.xml is chged to update the repository database. glib # This lib is needed by nerolinux. # 3rd party extra (from rpm.pbone.net) # (glib-1.2.10-18.2.2.i386.rpm) needs to be copied to Fedora/RPMS dir from NEWRPMS dir in mkisofsDVD4.sh (when it is in NEWRPMS dir). This is done by run of mkisofsDVD4.sh. It must be added manually to /dosc/d/5/comps.xml before that. gtk+ # This lib is needed by nerolinux. # newrpm (from yum install gtk+) # (gtk+-1.2.10-55.fc6.i386.rpm) needs to be copied to Fedora/RPMS dir from NEWRPMS dir in mkisofsDVD4.sh (when it is in NEWRPMS dir). This is done by run of mkisofsDVD4.sh. It must be added manually to /dosc/d/5/comps.xml before that. nerolinux # newrpm (from nero.com) # (nerolinux-2.1.0.3-x86.rpm) needs to be copied to Fedora/RPMS dir from NEWRPMS dir in mkisofsDVD4.sh. This is done by run of mkisofsDVD4.sh (when it is in NEWRPMS dir). It must be added manually to /dosc/d/5/comps.xml before that. pykickstart # This one is already in Fedora/RPMS dir - no need to copy it to there in mkisofsDVD4.sh # This is needed by GUI kickstart configurator. system-config-kickstart # This one is already in Fedora/RPMS dir - no need to copy it to there in mkisofsDVD4.sh # This is needed by GUI kickstart configurator. unifdef # This one is already in Fedora/RPMS dir - no need to copy it to there in mkisofsDVD4.sh # This is needed to build a redhat kernel src rpm. #yy #yy%post --nochroot #yy #yy# /dosc/cpfiles - cp file(s) for new fedora core install. #yy #yy[ ! -d /mnt/sysimage/dosc ] && mkdir /mnt/sysimage/dosc #yymount -t vfat /dev/sda1 /mnt/sysimage/dosc #yy #yyif [ ! -f /mnt/sysimage/dosc/d/5/zdrivezks.i ]; then #yy ksversion=0 #yyelse #yy ksversion=`cat /mnt/sysimage/dosc/d/5/zdrivezks.i` #yyfi #yyecho "$ksversion" >/mnt/sysimage/dosc/d/5/ksver.i #yyecho "$ksversion" >/mnt/sysimage/ksver.i #yyecho "" >>/mnt/sysimage/dosc/ovdos/oveinfor/ovinfo.i #yyecho "install on zdrivez via kickstart with version ($ksversion) was done on: `date`" >>/mnt/sysimage/dosc/ovdos/oveinfor/ovinfo.i #yyecho "install via kickstart with version ($ksversion) was done on: `date`" >/mnt/sysimage/install.i #yylet "ksversion=ksversion+1" #yyecho -n "$ksversion" >/mnt/sysimage/dosc/d/5/zdrivezks.i #yy #yy/mnt/sysimage/bin/bash -c "/mnt/sysimage/dosc/d/5/ks_post_install_script.sh zdrivez zlabelz" #yy #yyecho "IN KS.CFG - signal /dosc/rclocal to invoke /dosc/ncpfiles the very first time we boot" >/mnt/sysimage/var/doncpfiles.s #yyecho ok9 >/mnt/sysimage/test9K0 #yy #yy%end %end ************************************** See AOL's top rated recipes (http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004) -------------- next part -------------- An HTML attachment was scrubbed... URL: From richzendy at gmail.com Thu Dec 27 15:00:16 2007 From: richzendy at gmail.com (Edwind Richzendy Contreras Soto) Date: Fri, 28 Dec 2007 10:30:16 +1930 Subject: fedora 8 static ip not accepted In-Reply-To: <476A7875.5080006@fisica.unimi.it> References: <476270F0.6070306@fisica.unimi.it> <90ba020d0712140841s7acfda5fr5fdf66d990b32679@mail.gmail.com> <90ba020d0712141037j6d558c8aj5b8238f2adc5449c@mail.gmail.com> <476A7875.5080006@fisica.unimi.it> Message-ID: <90ba020d0712270700x2ed26028sfef601198f0757f5@mail.gmail.com> 2007/12/21, Matteo Faleschini : > I posted a possible solution to redhat bugzilla > https://bugzilla.redhat.com/show_bug.cgi?id=392021 > > Install the anaconda source rpm and prepare the sources > with rpmbuild -bp (in /usr/src/redhat/SPEC/) > They are in /usr/src/redhat/BUILD/anaconda.xxx > > Enter the directory loader2 and edit file loader.c as explained on bugzilla. > Change directory to the anaconda root dir ( ../ ) and do make. > > Now you have to copy loader2/loader inside the initrd.img of the > isolinux directory. It's a gzipped cpio archive > > To open it copy it to a tmp dir then > mkdir initrd.dir > cd initrd.dir > zcat ../initrd.img | cpio -idv > > Copy inside bin/ the previously compiled loader then recreate the > initrd.img. > Inside initrd.dir do > find . -print | cpio -o -c --quiet | gzip -c9 > ../initrd.img.new > > And finally copy the inird.img.new as initrd.img inside the isolinux/ > directory, the one you use for creating kickstart cd's. > Thanks, i will probe this solution, my solution was install a DHCP server and create a network vlan for install :-( ( sorry for my bad english ) > Matteo Faleschini > > Edwind Richzendy Contreras Soto wrote: > > My kickstart file is: > > > > > > install > > network --device eth0 --bootproto static --noipv6 --ip 192.168.X.XXX--netmask > > 255.255.255.0 --gateway 192.168.X.XXX --nameserver 192.168.X.XXX --hostname > > pc1.XXXX.XXX.XX > > url --url http://192.168.X.XX/linux/f8/releases/Everything/i386/os > > keyboard la-latin1 > > lang es_ES.UTF-8 > > xconfig --startxonboot > > auth --useshadow --enablemd5 --enableldap --enableldapauth --ldapserver= > > 192.168.X.XXX -ldapbasedn=ou=People,dc=XXXX,dc=XXX,dc=XX > > rootpw --iscrypted $1$NxRxxxxvxNxvxSd$fboxXxwZxxcLSGxAx68xuxyxsxyxEx6xBu5/ > > firewall --enabled --port=22:tcp > > authconfig --enableshadow --enablemd5 > > selinux --enforcing > > timezone --utc America/Caracas > > bootloader --location=mbr --driveorder=sda --append="vga=791 rhgb quiet" > > --md5pass=$1$/v6xxNxxgx05A$BxFxxYxbxsxOxaxbx7xkxEBxUixuxBxlxdxxx1h0 > > # The following is the partition information you requested > > # Note that any partitions you deleted are not expressed > > # here so unless you clear all partitions first, this is > > # not guaranteed to work > > clearpart --all --drives=sda > > part /boot --fstype ext3 --size=200 --ondisk=sda > > part pv.6 --size=0 --grow --ondisk=sda > > volgroup VolGroup00 --pesize=32768 pv.6 > > logvol /tmp --fstype ext3 --name=LogVol03 --vgname=VolGroup00 --size=576 > > logvol /home --fstype ext3 --name=LogVol02 --vgname=VolGroup00 --size=60000 > > logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=496 > > --grow --maxsize=992 > > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=14496 > > repo --name=XXXXX-Livna --baseurl=http://192.168.X.XX/linux/f8/livna/i386/ > > repo --name=XXXX-Update --baseurl=http://192.168.X.XX/linux/f8/updates > > #reboot after install > > reboot --eject > > > > %post > > echo "session required pam_mkhomedir.so skel=/etc/skel/ umask=0022" > >>> /etc/pam.d/gdm > > > > %packages > > packages > > ... > > ... > > ... > > > > > > i put a kickstart from http server and it's is my boot line: > > > > boot: linux ks=http://192.168.X.XX ip=192.168.x.xx netmask=255.255.255.0gateway= > > 192.168.x.xx > > > > ip and gateway ips in boot line same equal to a ip and gateway ips to > > network line in kickstart file. > > > > but my instalation is frozen in a infinite loop searching a DHCP server > > after read and put kickstart file. > > > > What is wrong? > > > > > > 2007/12/15, Edwind Richzendy Contreras Soto : > >> > >> > >> 2007/12/15, Matteo Faleschini : > >>> > >>> I'm having problems to use this option inside the kickstart file > >>> > >>> network --bootproto=static --device=eth0 --gateway=192.168.1.254 > >>> --ip=192.168.1.1 --netmask=255.255.255.0 --onboot=on > >>> > >>> with a nfs or http installation. > >>> > >>> nfs --server ksbox.local.domain --dir /fedora/8.0/os > >>> > >>> In our departement we use a templating system that we wrote since > >>> redhat 9 to fedora 6 (and scientific linux 4, a redhat derived) without > >>> problems. > >>> > >>> When I prepared the kickstart for the new fedora 8, I noticed that > >>> anaconda (11.3.0.50) does not use the static ip information provided by > >>> the kickstart and chooses a dhcp configuration. > >>> > >>> To verify that it is not an error of our kickstart creator, I prepared a > >>> kickstart file on a fedora 8 machine with the system-config-kickstart > >>> script. But I found the same problem. > >>> I also switched the network and nfs lines but i found no difference. > >>> > >>> At first I thought about a new anaconda behaviour (nfs install uses only > >>> dynamic configuration) but having a look at the source code of the > >>> anaconda loader I have the impression that the network bootstrap follows > >>> the same principles. > >>> > >>> I searched through the mailing list for keywords bootproto and 11.3.0.50 > >>> with no success. I also googled about but i did not find any hint. I > >>> don't know if it's a known anaconda issue or a syntax error of my > >>> kickstart. > >>> > >>> Matteo Faleschini > >> > >> > >> i have a same problem, it's a bug in anaconda for fedora 8? > >> > >> _______________________________________________ > >>> Kickstart-list mailing list > >>> Kickstart-list at redhat.com > >>> https://www.redhat.com/mailman/listinfo/kickstart-list > >>> > >> > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From Floydsmith at aol.com Fri Dec 28 08:35:34 2007 From: Floydsmith at aol.com (Floydsmith at aol.com) Date: Fri, 28 Dec 2007 03:35:34 EST Subject: my mistake; it is just the logging info line that causes the 295 parse error Message-ID: After looking at all of my cfg(s) that passed and the ones that failed I discovered that it is JUST the "logging info" line that seems to be causing the parse error as verified by repeatring the some experiments with just that change. That is, both ondisk and onpart (the one I need) work once this line is commented out. And, the two orginal ones using autopart and a two drive LVM setup (I believe) will fail if this line is not commented out (although I have test that yet). And, I have not tested changing the clearpart line to use "-none" as in all my previous cfg(s) but I don't think that will have any effect. It takes me over two hours to do a complete test because I am using a very old slow 20gig drive for experimenting. Floyd, ************************************** See AOL's top rated recipes (http://food.aol.com/top-rated-recipes?NCID=aoltop00030000000004) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tim.Mooney at ndsu.edu Fri Dec 28 18:13:33 2007 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Fri, 28 Dec 2007 12:13:33 -0600 (CST) Subject: possible FAQ: setting filesystem parameters with part/logvol? Message-ID: Hi All- I'm new to the list, though not kickstart. We've been using it since the RH 2.1 ES days for server deployment, and I'm very pleased to see some of the latest improvments available in ks (like remote logging). Now the questions: - is there a kickstart FAQ? Googling for kickstart FAQ didn't turn up anything related to the kickstart that's the topic of this list. - is there a way to pass filesystem creation parameters to part/logvol? I need to set the stride size on all the filesystems on several boxes I will be kickstarting (RHEL 4u6, unfortunately I can't use 5u1 because the software the boxes will be running doesn't support 5.x yet). I essentially want to pass -E stride=16 to part/logvol. Any suggestions on the best way to accomplish this? Thanks, Tim -- Tim Mooney Tim.Mooney at ndsu.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From Chip.Shabazian at bankofamerica.com Fri Dec 28 18:58:00 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 28 Dec 2007 10:58:00 -0800 Subject: possible FAQ: setting filesystem parameters with part/logvol? In-Reply-To: References: Message-ID: I've found the best info on kickstart is actually on the Fedora site. Here is a link to the presentation I did earlier this year at Linuxworld in case there is anything in there that might be of help: www.shabazian.com/lw2007.pdf As for your filesystem setup, you may need to do it in the %pre. Not sure about stride as I've never used it. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Tim Mooney Sent: Friday, December 28, 2007 10:14 AM To: kickstart-list at redhat.com Subject: possible FAQ: setting filesystem parameters with part/logvol? Hi All- I'm new to the list, though not kickstart. We've been using it since the RH 2.1 ES days for server deployment, and I'm very pleased to see some of the latest improvments available in ks (like remote logging). Now the questions: - is there a kickstart FAQ? Googling for kickstart FAQ didn't turn up anything related to the kickstart that's the topic of this list. - is there a way to pass filesystem creation parameters to part/logvol? I need to set the stride size on all the filesystems on several boxes I will be kickstarting (RHEL 4u6, unfortunately I can't use 5u1 because the software the boxes will be running doesn't support 5.x yet). I essentially want to pass -E stride=16 to part/logvol. Any suggestions on the best way to accomplish this? Thanks, Tim -- Tim Mooney Tim.Mooney at ndsu.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From klandreth at theplanet.com Mon Dec 31 14:58:14 2007 From: klandreth at theplanet.com (Landreth, Kevin) Date: Mon, 31 Dec 2007 08:58:14 -0600 Subject: possible FAQ: setting file system parameters with part/logvol? In-Reply-To: References: Message-ID: <69F7A3B9C49D9D409AF0F06F8AC507670357D35A@HOUEXCH01.PLANET.LOCAL> Going along with what Chip said, you will *have* to use pre because there doesn't seem to be a way to specify the mkfs options via the part command. The way I see it, is you have two options. 1) If the partition you need to use "custom" formatting options on does not contain any OS data, then just have part create the partition for you and re-format it in %post. (Personally, I'd have part make a VG, but not LV, and create it during %post to speed up deployment time) 2) If you do require OS data, then you will need to calculate the size of the partition you need, then format them accordingly, then just have part use --noformat --onpart Fedora link: http://fedoraproject.org/wiki/Anaconda/Kickstart Good luck :) -- Thanks, Kevin Landreth, RHCE Technology Architect -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Friday, December 28, 2007 12:58 PM To: Discussion list about Kickstart Subject: RE: possible FAQ: setting filesystem parameters with part/logvol? I've found the best info on kickstart is actually on the Fedora site. Here is a link to the presentation I did earlier this year at Linuxworld in case there is anything in there that might be of help: www.shabazian.com/lw2007.pdf As for your filesystem setup, you may need to do it in the %pre. Not sure about stride as I've never used it. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Tim Mooney Sent: Friday, December 28, 2007 10:14 AM To: kickstart-list at redhat.com Subject: possible FAQ: setting filesystem parameters with part/logvol? Hi All- I'm new to the list, though not kickstart. We've been using it since the RH 2.1 ES days for server deployment, and I'm very pleased to see some of the latest improvments available in ks (like remote logging). Now the questions: - is there a kickstart FAQ? Googling for kickstart FAQ didn't turn up anything related to the kickstart that's the topic of this list. - is there a way to pass filesystem creation parameters to part/logvol? I need to set the stride size on all the filesystems on several boxes I will be kickstarting (RHEL 4u6, unfortunately I can't use 5u1 because the software the boxes will be running doesn't support 5.x yet). I essentially want to pass -E stride=16 to part/logvol. Any suggestions on the best way to accomplish this? Thanks, Tim -- Tim Mooney Tim.Mooney at ndsu.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ 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 Tim.Mooney at ndsu.edu Mon Dec 31 22:40:57 2007 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Mon, 31 Dec 2007 16:40:57 -0600 (CST) Subject: possible FAQ: setting file system parameters with part/logvol? In-Reply-To: <69F7A3B9C49D9D409AF0F06F8AC507670357D35A@HOUEXCH01.PLANET.LOCAL> References: <69F7A3B9C49D9D409AF0F06F8AC507670357D35A@HOUEXCH01.PLANET.LOCAL> Message-ID: In regard to: RE: possible FAQ: setting file system parameters with...: > Going along with what Chip said, you will *have* to use pre because > there doesn't seem to be a way to specify the mkfs options via the part > command. Thanks to both you and Chip for confirming what I suspected. I was just hoping there was some undocumented way to pass things through part/logvol, since that would have made my life much easier. We make heavy use of %post in all of our kickstart files, but although I knew %pre existed, I had never needed to use it before. I have now. > The way I see it, is you have two options. > > 1) If the partition you need to use "custom" formatting options on does > not contain any OS data, then just have part create the partition for > you and re-format it in %post. (Personally, I'd have part make a VG, > but not LV, and create it during %post to speed up deployment time) > 2) If you do require OS data, then you will need to calculate the size > of the partition you need, then format them accordingly, then just have > part use --noformat --onpart The second option is essentially what I ended up doing. Here's what my partitioning section of my ks config files look like: zerombr yes # # TVM: don't do anything to the disk label. # clearpart --none #/boot part /boot --noformat --onpart=hda1 # swap part swap --noformat --onpart=hda2 # / part / --noformat --onpart=hda3 # remainder for LVM part pv.01 --noformat --onpart=hda4 volgroup localvg1 pv.01 --noformat logvol /usr/local --noformat --name=local --vgname=localvg1 logvol /tmp --noformat --name=tmp --vgname=localvg1 logvol /var --noformat --name=var --vgname=localvg1 logvol /home --noformat --name=home --vgname=localvg1 logvol /u01 --noformat --name=oracle --vgname=localvg1 Here's the %pre I ended up using (don't laugh, I was pressed for time): %pre echo '***' echo '*** Perform manual partitioning step now.' echo '***' sleep 99999 echo 'boot-alignment-check' > /dev/hda1 echo 'swap-alignment-check' > /dev/hda2 echo 'root-alignment-check' > /dev/hda3 echo 'vg-alignment-check' > /dev/hda4 echo '***' echo '*** Perform alignment checks for boot/swap/root/vg now.' echo '***' sleep 99999 lvm.static pvcreate /dev/hda4 lvm.static vgcreate --alloc contiguous -s 8M localvg1 /dev/hda4 lvm.static lvcreate --alloc contiguous --name var --size 36864 localvg1 lvm.static lvcreate --alloc contiguous --name tmp --size 2048 localvg1 lvm.static lvcreate --alloc contiguous --name local --size 1024 localvg1 lvm.static lvcreate --alloc contiguous --name home --size 2048 localvg1 # figure out how many free physical extents there are remaining, and use # them up. pe=`lvm.static vgdisplay localvg1 | \ sed -ne 's+^.*Free *PE.*/ Size *\([0-9]*\) /.*$+\1+p'` #lvm.static lvcreate --alloc contiguous --name oracle --extents $pe localvg1 lvm.static lvcreate --alloc contiguous --name oracle --size 24576 localvg1 echo 'var-alignment-check' > /dev/localvg1/var echo 'tmp-alignment-check' > /dev/localvg1/tmp echo 'local-alignment-check' > /dev/localvg1/local echo 'home-alignment-check' > /dev/localvg1/home echo 'oracle-alignment-check' > /dev/localvg1/oracle echo '***' echo '*** Perform alignment checks for var/tmp/local/home/oracle now.' echo '***' sleep 99999 mkfs.ext3 -j -L /boot -E stride=16 /dev/hda1 mkswap -L swap /dev/hda2 mkfs.ext3 -j -L / -E stride=16 /dev/hda3 mkfs.ext3 -j -L /var -E stride=16 /dev/localvg1/var mkfs.ext3 -j -L /tmp -E stride=16 /dev/localvg1/tmp mkfs.ext3 -j -L /local -E stride=16 /dev/localvg1/local mkfs.ext3 -j -L /home -E stride=16 /dev/localvg1/home mkfs.ext3 -j -L /u01 -E stride=16 /dev/localvg1/oracle echo '***' echo '*** Filesystems created, perform any remaining tests you wish now.' echo '***' sleep 3600 Some explanation of the %pre is probably in order. First, each of the four boxes I was kickstarting were actually RHEL4.6 Xen (fully) virtual machines on a RHEL5.1 base host. The RHEL5.1 host has about 300 GB of SAN storage, and I created four LVs within that, and put each of the virtual hosts directly on one of the LVs (kickstarting with Xen, the LV appears as /dev/hda). Within the %pre: - I pause the %pre with sleep and manually switch to virtual console #2 (bash prompt) and perform the partitioning manually. I didn't have time to figure out how to script sfdisk to automate the partitioning. That's something I plan to play with in the coming days. When I'm done with partitioning and have things the way I want, I find the pid of the sleep command and kill it. - the echo commands write a bit of text to the beginning of each partition, and then a sleep pauses %pre again. I then use a utility on the RHEL5.1 base host to verify that each of the bits of text that were written to the start of the VMs partitions is aligned on a 64K boundary. Since all of the partitions ultimately get their storage from a RAID5 volume with a 64K stripe cache, you pay a signficant performance hit if your partitions or LVs are not aligned on a 64K boundary. - once I've verified that the partitions are aligned on 64K boundaries, I again switch to virtual console 2 in the kickstart and kill the sleep. - the LVM commands run to create the PV, volume group, and my LVs, and then write a bit of text to the start of each of the LVs, and again %pre pauses - switch back to the RHEL5.1 base host, and spot check that at least one of the LVs is aligned on a 64K boundary by checking for the bit of text that was written to the start of the LV. If one LV is correctly aligned, all of them will be. - kill the sleep, at which point mkfs runs to create the empty filesystems on the partitions and LVs, with the stride=16, as well as setting up swap. The stride is used to make the filesystem play nicely with a RAID5 stripe cache of 64K. - the final sleep really isn't needed, kill it and %pre ends and the kickstart actually begins. Thanks again for your help. With the suggestions you provided, I was able to get these four VMs kickstarted over the past weekend, and I've verified that their filesystems are all correctly aligned for the maximum performance all the way through the storage stack (which in this case is unbelievably deep). Tim -- Tim Mooney Tim.Mooney at ndsu.edu Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164