From mhubbard at secureworks.com Fri Sep 5 14:38:51 2008 From: mhubbard at secureworks.com (Mike Hubbard) Date: Fri, 5 Sep 2008 10:38:51 -0400 Subject: Holding configuration information Message-ID: Hello - I am very new at this kick-start stuff. I need to build a kickstart CD that completely repartitions the hard drive and yet is able to hold on to configuration information to lay it back down after the installation. I have been reading and trying different things, but I can't seem to figure this out. My thought was to write things, perhaps, to a ramdisk during %pre and then access it in %post, but I'm not getting anywhere with that. Could someone please direct me to the proper documentation for this, or help me correct my entire line of thinking about what I want to do? I think I'm deep down in some rat-hole or am just missing something obvious. Thanks Michael Hubbard -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chip.Shabazian at bankofamerica.com Fri Sep 5 17:20:10 2008 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Fri, 05 Sep 2008 10:20:10 -0700 Subject: Holding configuration information In-Reply-To: References: Message-ID: You can write to a ramdisk in %pre and access it in %post, but you have to remember to unmount it in %pre or it won't be available. It may be a two step process, but if the box is up, you can log on, get you config information backed up and copied to another server, then simply wget that config information in the %post. I would probably do this at least the first few times, just to make sure I had a good backup of everything I needed and no more. ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Mike Hubbard Sent: Friday, September 05, 2008 7:39 AM To: kickstart-list at redhat.com Subject: Holding configuration information Hello - I am very new at this kick-start stuff. I need to build a kickstart CD that completely repartitions the hard drive and yet is able to hold on to configuration information to lay it back down after the installation. I have been reading and trying different things, but I can't seem to figure this out. My thought was to write things, perhaps, to a ramdisk during %pre and then access it in %post, but I'm not getting anywhere with that. Could someone please direct me to the proper documentation for this, or help me correct my entire line of thinking about what I want to do? I think I'm deep down in some rat-hole or am just missing something obvious. Thanks Michael Hubbard -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdehaan at redhat.com Fri Sep 5 19:06:30 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Fri, 05 Sep 2008 15:06:30 -0400 Subject: Holding configuration information In-Reply-To: References: Message-ID: <48C18336.4050900@redhat.com> Mike Hubbard wrote: > > Hello ? > > I am very new at this kick-start stuff. > > I need to build a kickstart CD that completely repartitions the hard > drive and yet is able to hold on to configuration information to lay > it back down after the installation. > > I have been reading and trying different things, but I can?t seem to > figure this out. My thought was to write things, perhaps, to a ramdisk > during %pre and then access it in %post, but I?m not getting anywhere > with that. > > Could someone please direct me to the proper documentation for this, > or help me correct my entire line of thinking about what I want to do? > I think I?m deep down in some rat-hole or am just missing something > obvious. > > Thanks > > Michael Hubbard > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list What config information are you trying to save? I think I'd much rather solve this as a backup/restore kind of use case, whether that's something as simple as cp or rsync or something more complex. --Michael From terry.mcintyre at gmail.com Fri Sep 5 19:57:28 2008 From: terry.mcintyre at gmail.com (Terry McIntyre) Date: Fri, 5 Sep 2008 12:57:28 -0700 Subject: Holding configuration information In-Reply-To: <48C18336.4050900@redhat.com> References: <48C18336.4050900@redhat.com> Message-ID: <67f096ea0809051257i1712efe9kfce37e53caf96c9d@mail.gmail.com> > Mike Hubbard wrote: >> >> Hello ? >> >> I am very new at this kick-start stuff. >> >> I need to build a kickstart CD that completely repartitions the hard drive >> and yet is able to hold on to configuration information to lay it back down >> after the installation. >> >> I have been reading and trying different things, but I can't seem to >> figure this out. My thought was to write things, perhaps, to a ramdisk >> during %pre and then access it in %post, but I'm not getting anywhere with >> that. >> >> Could someone please direct me to the proper documentation for this, or >> help me correct my entire line of thinking about what I want to do? I think >> I'm deep down in some rat-hole or am just missing something obvious. >> > > What config information are you trying to save? > > I think I'd much rather solve this as a backup/restore kind of use case, > whether that's something as simple as cp or rsync or something more complex. I concur. If this stuff is saved into RAM, it could vanish due to a power outage or programming error. Do you want to retain this configuration information somewhere off-box, the better to recreate the box whenever the disk fails? -- Terry McIntyre UNIX for hire Software Development, Systems Administration, Security terry.mcintyre at gmail.com From cduffy at messageone.com Tue Sep 9 08:24:18 2008 From: cduffy at messageone.com (Charles Duffy) Date: Tue, 09 Sep 2008 03:24:18 -0500 Subject: Device naming for hd:: when installing off a USB HD Message-ID: Howdy, all. I'm trying to install CentOS 5 off an external USB device. The conflict here is that the system I'm installing on has other USB storage devices built-in, and the boot order between them is inconsistent. This means that even if I scan the current list of device names and labels and then kexec into the installer after observing how my initial kernel names them, I have only a 50/50 chance of the device names used for ks=hd::/ks.cfg and method=hd::/ being valid. What's the Right Way to resolve this issue? Would it work to copy ks.cfg onto the local hard drive (which *isn't* changing names between boots), have a %pre that generates an appropriate harddrive stanza, and %include that? From Pablo.Iranzo at redhat.com Tue Sep 9 08:36:19 2008 From: Pablo.Iranzo at redhat.com (Pablo Iranzo =?ISO-8859-1?Q?G=F3mez?=) Date: Tue, 09 Sep 2008 08:36:19 +0000 Subject: Device naming for hd:: when installing off a USB HD In-Reply-To: References: Message-ID: <1220949379.14176.45.camel@iranzo.users.redhat.com> Hi Charles El mar, 09-09-2008 a las 03:24 -0500, Charles Duffy escribi?: > Howdy, all. > > I'm trying to install CentOS 5 off an external USB device. The conflict > here is that the system I'm installing on has other USB storage devices > built-in, and the boot order between them is inconsistent. > This means that even if I scan the current list of device names and > labels and then kexec into the installer after observing how my initial > kernel names them, I have only a 50/50 chance of the device names used > for ks=hd::/ks.cfg and method=hd::/ being valid. > > > What's the Right Way to resolve this issue? LiveUSB's use a UUID=????-???? that identifies the root filesystem to boot > > Would it work to copy ks.cfg onto the local hard drive (which *isn't* > changing names between boots), have a %pre that generates an appropriate > harddrive stanza, and %include that? What I did to resolve this issue is to create a LiveUSB using livecd-tools from EPEL, and then inside the disk created a small script that searched for the hard drive to partition, give it boot files 'syslinux' and then reboot, so the system starts from that hard drive and perform an installation with the correct devices placed there. The problem with mixing both scsi, usb drives is that you'll never know what are your drive names going to be on the next system... so UUID could work but... will need tweaks as afaik anaconda checks for device name. Probably you could hack anaconda to run a custom script than looks for the correct path, and passes it to 'real' anaconda... Regards Pablo -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) RHCE/RHCSP/RHCSS Global Profesional Services Consultant Spain Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D -- Inscrita en el Reg. Mercantil de Madrid ? C.I.F. B-82 65 79 41 Directores: Michael Cunningham, Charlie Peters y David Owens Direcci?n Registrada: Red Hat S.L., C/ Velazquez 63, Madrid 28001, Espa?a Direcci?n contacto: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, Planta 3?D, 28016 Madrid, Spain -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Esta parte del mensaje est? firmada digitalmente URL: From niallel at gmail.com Mon Sep 15 22:00:39 2008 From: niallel at gmail.com (niall el-assaad) Date: Mon, 15 Sep 2008 23:00:39 +0100 Subject: Removing old linux in the %pre section Message-ID: Hi, I've got a fc6 build that I want to move to centos, i just want to keep a single directory. Is there some way in the %pre section I could delete all the directories off the disk (apart from 1) and then have kickstart continue and install centos? I've tried but the %pre section doesn't seem to work. I'm using /mnt/sysimage to access the hard disk, but doesn't seem to work. Any ideas? thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chip.Shabazian at bankofamerica.com Mon Sep 15 22:16:11 2008 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 15 Sep 2008 15:16:11 -0700 Subject: Removing old linux in the %pre section In-Reply-To: References: Message-ID: If you are just doing one machine, just backup that directory. If you need to do lots of machines, put a sleep statement in your %pre and figure out what you want to do, then add those commands to the %pre. ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of niall el-assaad Sent: Monday, September 15, 2008 3:01 PM To: Kickstart-list at redhat.com Subject: Removing old linux in the %pre section Hi, I've got a fc6 build that I want to move to centos, i just want to keep a single directory. Is there some way in the %pre section I could delete all the directories off the disk (apart from 1) and then have kickstart continue and install centos? I've tried but the %pre section doesn't seem to work. I'm using /mnt/sysimage to access the hard disk, but doesn't seem to work. Any ideas? thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From niallel at gmail.com Mon Sep 15 22:44:01 2008 From: niallel at gmail.com (niall el-assaad) Date: Mon, 15 Sep 2008 23:44:01 +0100 Subject: Removing old linux in the %pre section In-Reply-To: References: Message-ID: Thanks chip, i worked out what I did wrong. In %pre I needed to mount the disk, /mnt/sysimage isn't there. Good hint on the sleep command though. thanks, On Mon, Sep 15, 2008 at 11:16 PM, Shabazian, Chip < Chip.Shabazian at bankofamerica.com> wrote: > If you are just doing one machine, just backup that directory. If you > need to do lots of machines, put a sleep statement in your %pre and figure > out what you want to do, then add those commands to the %pre. > ------------------------------ > > *From:* kickstart-list-bounces at redhat.com [mailto: > kickstart-list-bounces at redhat.com] *On Behalf Of *niall el-assaad > *Sent:* Monday, September 15, 2008 3:01 PM > *To:* Kickstart-list at redhat.com > *Subject:* Removing old linux in the %pre section > > > > Hi, > > I've got a fc6 build that I want to move to centos, i just want to keep a > single directory. > > Is there some way in the %pre section I could delete all the directories > off the disk (apart from 1) and then have kickstart continue and install > centos? > > I've tried but the %pre section doesn't seem to work. I'm using > /mnt/sysimage to access the hard disk, but doesn't seem to work. > > Any ideas? > > thanks, > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fc9 at prosentia.co.uk Mon Sep 22 00:16:41 2008 From: fc9 at prosentia.co.uk (Richard) Date: Mon, 22 Sep 2008 01:16:41 +0100 Subject: initiating kickstart install from fc9 media Message-ID: <48D6E3E9.1020109@prosentia.co.uk> Hi, I am probably missing something very obvious. But I cannot see how I initiate the kickstart install from the fc9 media (neither the Fedora-9-i386-disc1.iso nor the Fedora-9-i386-netinst.iso). I have performed the following successfully .... 1. downloaded and extracted the full fc9 DVD.iso to a local "kickstart server" 2. downloaded and created CD's from the images .... * Fedora-9-i386-disc1.iso * Fedora-9-i386-netinst.iso 3. successfully performed a network install from the extracted fc9 media (via http) * booted from Fedora-9-i386-netinst.iso * via menu's, pointed installation process at the fc9 media on my "kickstart server" * entered data for configuration and package selection manually * ended up with a fully functional server! 4. copied the kickstart file created during the manual install * placed it in the media directory (i.e. ./fc9/i386/os/) as ks.cfg * using a browser from another machine confirmed ks.cfg is readable via http Now I want to initiate my kickstart installation to "repeat" the install I have performed interactively on other machines. Bit I cannot work out how using the fc9 media I can access the boot: command line. The OLDER Fedora install media had a selection menu at boot time that enabled you to select the command line and simply enter "boot: linux ks=http://192.168.3.204/fcx/ks.cfg". The fc9 kickstart documentation still advises to enter a boot command at the boot prompt. "linux ks=..." etc. But the fc9 media that I have just runs straight past the point where you can enter a command at the boot prompt. I can see this stage of the install process "flashing by" on the display but it does not pause for me to make a selection. I assume this is because there are now separate .iso images / CD's for the network install and the "CD install". Any suggestions gratefully received. Cheers, Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian at herakles.homelinux.org Mon Sep 22 04:55:50 2008 From: debian at herakles.homelinux.org (John Summerfield) Date: Mon, 22 Sep 2008 12:55:50 +0800 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D6E3E9.1020109@prosentia.co.uk> References: <48D6E3E9.1020109@prosentia.co.uk> Message-ID: <48D72556.4010409@herakles.homelinux.org> Richard wrote: > Hi, > Note, it's "Fedora Core" no more. > I am probably missing something very obvious. But I cannot see how I > initiate the kickstart install from the fc9 media (neither the > Fedora-9-i386-disc1.iso nor the Fedora-9-i386-netinst.iso). > > I have performed the following successfully .... > 1. downloaded and extracted the full fc9 DVD.iso to a local > "kickstart server" > 2. downloaded and created CD's from the images .... > * Fedora-9-i386-disc1.iso > * Fedora-9-i386-netinst.iso > 3. successfully performed a network install from the extracted fc9 > media (via http) > * booted from Fedora-9-i386-netinst.iso > * via menu's, pointed installation process at the fc9 media > on my "kickstart server" > * entered data for configuration and package selection manually > * ended up with a fully functional server! > 4. copied the kickstart file created during the manual install > * placed it in the media directory (i.e. ./fc9/i386/os/) as > ks.cfg > * using a browser from another machine confirmed ks.cfg is > readable via http > > Now I want to initiate my kickstart installation to "repeat" the install > I have performed interactively on other machines. Bit I cannot work out > how using the fc9 media I can access the boot: command line. "media" refers to the actual boot disk, not to the install tree. > > The OLDER Fedora install media had a selection menu at boot time that > enabled you to select the command line and simply enter "boot: linux > ks=http://192.168.3.204/fcx/ks.cfg". I'm sure something of that kind will work now. > > The fc9 kickstart documentation still advises to enter a boot command at > the boot prompt. "linux ks=..." etc. > > But the fc9 media that I have just runs straight past the point where > you can enter a command at the boot prompt. I can see this stage of the > install process "flashing by" on the display but it does not pause for > me to make a selection. I assume this is because there are now separate > .iso images / CD's for the network install and the "CD install". ? I recently used the f9 netinst iso image as a a rescue disk. I had no problem selecting the correct entrey and appending my preferred boot option (I like to add vga=794 whenever my hardware supports it). > > Any suggestions gratefully received. I would unpack the iso and edit/add a menu entry having hs=http://example.com/f9/install.ks or similar, then recreate the ISO using mkisofs (google for the right incantation, it's not obvious) and burn a new CD. The advantage to using http to get the ks file is simplicity in changing the file's content, no need to burn more CDs. You could also set up and use PXE, no CDs required. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From kanarip at kanarip.com Mon Sep 22 18:53:39 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Mon, 22 Sep 2008 20:53:39 +0200 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D6E3E9.1020109@prosentia.co.uk> References: <48D6E3E9.1020109@prosentia.co.uk> Message-ID: <48D7E9B3.5040905@kanarip.com> Richard wrote: > The fc9 kickstart documentation still advises to enter a boot command at > the boot prompt. "linux ks=..." etc. > What you do is press Escape at the graphical boot menu to get the boot: prompt back. -Jeroen From fc9 at prosentia.co.uk Tue Sep 23 09:36:25 2008 From: fc9 at prosentia.co.uk (Richard) Date: Tue, 23 Sep 2008 10:36:25 +0100 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D72556.4010409@herakles.homelinux.org> References: <48D6E3E9.1020109@prosentia.co.uk> <48D72556.4010409@herakles.homelinux.org> Message-ID: <48D8B899.9050903@prosentia.co.uk> Hi John, thanks for the reply. john> "media" refers to the actual boot disk, not to the install tree. Yes. That's what I was referring to - the boot disk created from one of Fedora-9-i386-disc1.iso, Fedora-9-i386-netinst.iso or Fedora-9-i386-DVD.iso. My problem was that whichever one I booted from I could not find the stage where I could add the necessary "linux ks=http://... etc." commands in the format that I used on older versions of fedora which is the same as the format shown in the current anaconda / kickstart documentation. Since posting my question on this mailing list I have resolved my problem. With Fedora 9 media you can initiate a kickstart installation by editing one of the standard grub menu options (hitting TAB when the menu is displayed) and ADDING "linux ks=http://ksserver.example.com/ks.cfg ksdevice=eth0" to the existing text on the command line i.e. "vmlinuz initrd=initrd.img". On earlier versions of Fedora, I simply entered the "linux ks=... " etc. on a blank "boot:" prompt. The Fedora 9 installer appears to "leap frog" the stage in the boot process where you previously had the option to open the boot: prompt directly (though you do see this stage flash past on the display). Alternatively, you can hit the ESCAPE key when the menu is displayed which drops you to the boot: prompt. From here the kickstart initiation is exactly as per old/existing docs. So the process is .... 1. insert CD or DVD 2. power on computer 3. wait for "Welcome to Fedora 9" menu Then either .. 4. hit the TAB key 5. command line is displayed already showing "vmlinuz initrd=initrd.img" 6. edit line to read "vmlinuz initrd=initrd.img linux ks=http://ksserver.example.com/ks.cfg ksdevice=eth0" and hit the enter key .. or .. 4. hit the ESCAPE key 5. boot prompt is displayed 6. enter "linux ks=http://ksserver.example.com/ks.cfg ksdevice=eth0" and hit the enter key It would be nice if there was a prompt under the menu to "hit ESCAPE for boot prompt" (as there is for the TAB action). Thanks for your advice. Cheers, Richard -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian at herakles.homelinux.org Tue Sep 23 11:34:13 2008 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 23 Sep 2008 19:34:13 +0800 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D8B899.9050903@prosentia.co.uk> References: <48D6E3E9.1020109@prosentia.co.uk> <48D72556.4010409@herakles.homelinux.org> <48D8B899.9050903@prosentia.co.uk> Message-ID: <48D8D435.6020609@herakles.homelinux.org> Richard wrote: > Hi John, > > thanks for the reply. > > john> "media" refers to the actual boot disk, not to the install tree. > > Yes. That's what I was referring to - the boot disk created from one of > Fedora-9-i386-disc1.iso, Fedora-9-i386-netinst.iso or > Fedora-9-i386-DVD.iso. > My problem was that whichever one I booted from I could not find the > stage where I could add the necessary "linux ks=http://... etc." > commands in the format that I used on older versions of fedora which is > the same as the format shown in the current anaconda / kickstart > documentation. > > Since posting my question on this mailing list I have resolved my problem. > With Fedora 9 media you can initiate a kickstart installation by editing > one of the standard grub menu options (hitting TAB when the menu is > displayed) and ADDING "linux ks=http://ksserver.example.com/ks.cfg > ksdevice=eth0" to the existing text on the command line i.e. "vmlinuz > initrd=initrd.img". On earlier versions of Fedora, I simply entered the > "linux ks=... " etc. on a blank "boot:" prompt. The Fedora 9 installer > appears to "leap frog" the stage in the boot process where you > previously had the option to open the boot: prompt directly (though you > do see this stage flash past on the display). > > Alternatively, you can hit the ESCAPE key when the menu is displayed > which drops you to the boot: prompt. From here the kickstart initiation > is exactly as per old/existing docs. > > So the process is .... > 1. insert CD or DVD > 2. power on computer > 3. wait for "Welcome to Fedora 9" menu > > Then either .. > 4. hit the TAB key > 5. command line is displayed already showing "vmlinuz > initrd=initrd.img" > 6. edit line to read "vmlinuz initrd=initrd.img linux > ks=http://ksserver.example.com/ks.cfg ksdevice=eth0" and hit the enter key > > .. or .. > 4. hit the ESCAPE key > 5. boot prompt is displayed > 6. enter "linux ks=http://ksserver.example.com/ks.cfg ksdevice=eth0" > and hit the enter key I-m _sure_ that's what I did years ago, say RHL 7.x or so. > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From kanarip at kanarip.com Tue Sep 23 16:08:48 2008 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Tue, 23 Sep 2008 18:08:48 +0200 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D8B899.9050903@prosentia.co.uk> References: <48D6E3E9.1020109@prosentia.co.uk> <48D72556.4010409@herakles.homelinux.org> <48D8B899.9050903@prosentia.co.uk> Message-ID: <48D91490.6080601@kanarip.com> Richard wrote: > Then either .. > 4. hit the TAB key > 5. command line is displayed already showing "vmlinuz > initrd=initrd.img" > 6. edit line to read "vmlinuz initrd=initrd.img linux > ks=http://ksserver.example.com/ks.cfg ksdevice=eth0" and hit the enter key > 6. is supposed to be "just append": ks=http://ksserver.example.com/ks.cfg ksdevice=eth0 The "linux" goes to the label in the syslinux menu configuration file of the menu entry you want to boot (see isolinux/isolinux.cfg). No problem in specifying whatever at the boot line though, I thought I'd just mention this. -Jeroen From fc9 at prosentia.co.uk Wed Sep 24 10:34:52 2008 From: fc9 at prosentia.co.uk (Richard) Date: Wed, 24 Sep 2008 11:34:52 +0100 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D8D435.6020609@herakles.homelinux.org> References: <48D6E3E9.1020109@prosentia.co.uk> <48D72556.4010409@herakles.homelinux.org> <48D8B899.9050903@prosentia.co.uk> <48D8D435.6020609@herakles.homelinux.org> Message-ID: <48DA17CC.504@prosentia.co.uk> Hi John, john> I-m _sure_ that's what I did years ago, say RHL 7.x or so. I don't think so. I never used RHL 7.x but RHL 5.2, 6, 9 and Fedora up to 4 (the most recent one I used before Fedora 9) all (by default) pause at a "boot:" prompt during the boot sequence from the standard media. At that boot: prompt you can directly enter: linux ks=http://ksserver.example.com/ks.cfg ksdevice=eth0 The Fedora 9 install process goes straight passed the 'old' boot: prompt and doesn't pause until it gets to the "Welcome to Fedora 9" menu? There is an option to edit one of the menu options (by hitting TAB) but when you do so you are NOT dropped to the boot prompt and have to enter a subtly different command line. However, you CAN get back to the boot prompt on Fedora 9 from this menu. To do so, you simply hit ESCAPE (as stated in Jeroen's answer https://www.redhat.com/archives/kickstart-list/2008-September/msg00011.html). It would be nice if this was on the screen next to the prompt to "hit TAB to edit". Thanks again for your advice. Cheers, Richard From debian at herakles.homelinux.org Wed Sep 24 15:45:23 2008 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 24 Sep 2008 23:45:23 +0800 Subject: initiating kickstart install from fc9 media In-Reply-To: <48DA17CC.504@prosentia.co.uk> References: <48D6E3E9.1020109@prosentia.co.uk> <48D72556.4010409@herakles.homelinux.org> <48D8B899.9050903@prosentia.co.uk> <48D8D435.6020609@herakles.homelinux.org> <48DA17CC.504@prosentia.co.uk> Message-ID: <48DA6093.5080401@herakles.homelinux.org> Richard wrote: > Hi John, > > john> I-m _sure_ that's what I did years ago, say RHL 7.x or so. > > I don't think so. I never used RHL 7.x but RHL 5.2, 6, 9 and Fedora up You're right, I have a set of RHL 7.3 CDs right here. > to 4 (the most recent one I used before Fedora 9) all (by default) pause > at a "boot:" prompt during the boot sequence from the standard media. At > that boot: prompt you can directly enter: > linux ks=http://ksserver.example.com/ks.cfg ksdevice=eth0 > > The Fedora 9 install process goes straight passed the 'old' boot: prompt > and doesn't pause until it gets to the "Welcome to Fedora 9" menu? > There is an option to edit one of the menu options (by hitting TAB) but > when you do so you are NOT dropped to the boot prompt and have to enter > a subtly different command line. That much was clear enough it didn't confuse me. > > However, you CAN get back to the boot prompt on Fedora 9 from this menu. > To do so, you simply hit ESCAPE (as stated in Jeroen's answer I wasn't confused about that either:-) Didn't know it was possible. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From mdehaan at redhat.com Fri Sep 26 16:50:03 2008 From: mdehaan at redhat.com (Michael DeHaan) Date: Fri, 26 Sep 2008 12:50:03 -0400 Subject: initiating kickstart install from fc9 media In-Reply-To: <48D6E3E9.1020109@prosentia.co.uk> References: <48D6E3E9.1020109@prosentia.co.uk> Message-ID: <48DD12BB.20307@redhat.com> Richard wrote: > Hi, > > I am probably missing something very obvious. But I cannot see how I > initiate the kickstart install from the fc9 media (neither the > Fedora-9-i386-disc1.iso nor the Fedora-9-i386-netinst.iso). > > I have performed the following successfully .... > 1. downloaded and extracted the full fc9 DVD.iso to a local > "kickstart server" > 2. downloaded and created CD's from the images .... > * Fedora-9-i386-disc1.iso > * Fedora-9-i386-netinst.iso > 3. successfully performed a network install from the extracted fc9 > media (via http) > * booted from Fedora-9-i386-netinst.iso > * via menu's, pointed installation process at the fc9 > media on my "kickstart server" > * entered data for configuration and package selection > manually > * ended up with a fully functional server! > 4. copied the kickstart file created during the manual install > * placed it in the media directory (i.e. ./fc9/i386/os/) > as ks.cfg > * using a browser from another machine confirmed ks.cfg is > readable via http > > Now I want to initiate my kickstart installation to "repeat" the > install I have performed interactively on other machines. Bit I > cannot work out how using the fc9 media I can access the boot: command > line. > > The OLDER Fedora install media had a selection menu at boot time that > enabled you to select the command line and simply enter "boot: linux > ks=http://192.168.3.204/fcx/ks.cfg". > > The fc9 kickstart documentation still advises to enter a boot command > at the boot prompt. "linux ks=..." etc. > > But the fc9 media that I have just runs straight past the point where > you can enter a command at the boot prompt. I can see this stage of > the install process "flashing by" on the display but it does not pause > for me to make a selection. I assume this is because there are now > separate .iso images / CD's for the network install and the "CD install". > > Any suggestions gratefully received. > > > Cheers, > > > Richard > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list If you are primarily interested in doing netinstall like activity, cobbler can set this up for you pretty simply. yum install cobbler vi /etc/cobbler/settings cobbler check cobbler import --name=F9 --mirror=/mnt/cdrom cobbler profile edit --name=F9-i386 --kickstart=/etc/cobbler/mykickstart.template # let's verify that looks like what we want cobbler profile getks --name=F9 # repeat as desired or add more distributions, or further customize your profiles cobbler buildiso This will create a net install ISO that points back to your cobbler server, which is perhaps more useful if you do have a datacenter environment as then you're also doing the mirroring and doing have large ISOs to truck around ... the ISO contains no packages, just kernel+initrds and references to kickstart files hostetd on the cobbler server. --Michael From mpotla at cisco.com Tue Sep 30 18:30:47 2008 From: mpotla at cisco.com (Murali Potla (mpotla)) Date: Tue, 30 Sep 2008 11:30:47 -0700 Subject: Ethernet bonding configuration Message-ID: <5547014632ED654F971D7E1E0C2E0C3E06947EB3@xmb-sjc-215.amer.cisco.com> Is it possible to configure the network devices as bonded devices via kickstart process. Bond0 with a specific IP address and eth0 and eth1 as the slaves ? Thanks, Murali From Chip.Shabazian at bankofamerica.com Tue Sep 30 18:44:24 2008 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Tue, 30 Sep 2008 11:44:24 -0700 Subject: Ethernet bonding configuration In-Reply-To: <5547014632ED654F971D7E1E0C2E0C3E06947EB3@xmb-sjc-215.amer.cisco.com> References: <5547014632ED654F971D7E1E0C2E0C3E06947EB3@xmb-sjc-215.amer.cisco.com> Message-ID: We do this in our %post. Basically, we Kickstart and build from eth0, then source the ifcfg-eth0 file and use that to setup the bond0, then overwrite the eth0 and eth1 config files. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Murali Potla (mpotla) Sent: Tuesday, September 30, 2008 11:31 AM To: Discussion list about Kickstart Subject: Ethernet bonding configuration Is it possible to configure the network devices as bonded devices via kickstart process. Bond0 with a specific IP address and eth0 and eth1 as the slaves ? Thanks, Murali _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list