From co55-sy1t at dea.spamcon.org Fri Oct 1 05:40:00 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Thu, 30 Sep 2010 22:40:00 -0700 Subject: Kickstart-list Digest, Vol 79, Issue 11 References: <4CA4B777.6020403@cadence.com> <1285863630-sup-8284@ezyang> <4CA4BB89.5010006@cadence.com> Message-ID: Steve Robson wrote: >Edward Z. Yang wrote: >> Excerpts from Steve Robson's message of Thu Sep 30 12:14:47 -0400 2010: >>> Not sure where you got "%end" from but I've never heard of it or used >>> it. It's not mentioned in the RHEL5 kickstart documentation starting at >>> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Installation_Guide/s1-kickstart2-file.html >> >> Hello Steve, >> >> %end is recommended practice by Fedora's wiki page on Kickstart: >> >> http://fedoraproject.org/wiki/Anaconda/Kickstart > >Hi Edward, > > Current Fedora is years ahead of RHEL5. For instance, I see "fc6" in >some of the package names on the RHEL5.3 I'm currently using. The >"%end" directive must be new. Well, newer than RHEL5.3. Thanks to all for the answers - I ran into this years ago with CentOS 4.4 and didn't get an answer at the time. I'm just surprised that almost 5 years later, it's still not in RHEL! It doesn't help that Anaconda doesn't plainly show its version ID to the user during kickstart, and that its various web documentation doesn't show or distinguish what version is being documented, which might have clued me in that there were such wide-apart versions in current use. From co55-sy1t at dea.spamcon.org Fri Oct 1 05:43:35 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Thu, 30 Sep 2010 22:43:35 -0700 Subject: The %end tag causes errors References: <9s78a6pubeuipo8tf4a676g1g1260u6ttk@4ax.com> Message-ID: whitivery wrote: >In a CentOS 5.5 kickstart file, adding %end to mark the end of the >%packages, %pre, or %post sections causes an error. In the first two >cases the kickstart fails and stops. For the %post it gives an error >message but it has already run all of my post steps so it doesn't have a >functional impact. > >Without the %end lines, the kickstart file works fine. > >Details: > >- %end on %packages: traceback starts with: > File "/usr/bin/anaconda", line 733, in ? > and near end says KickstartParseError > and identifies a kickstart line (which doesn't correspond > to a %end) > >- %end on %pre: traceback starts with: > File "/usr/bin/anaconda", line 900, in ? > >- %end on %post: my steps work but at end: > {temporary ks filename}: line 490: fg: no job control > > >I don't see anaconda identify its version, but the RPM included >with CentOS 5.5 is anaconda-11.1.2.209-1.el5. I'm replying to myself: For some reason answers to this showed up in the thread titled "Re: Kickstart-list Digest, Vol 79, Issue 11". Per those and a private email: basically, %end is in Fedora (and has been for years), but still is not in RHEL/CentOS. From co55-sy1t at dea.spamcon.org Fri Oct 1 05:50:30 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Thu, 30 Sep 2010 22:50:30 -0700 Subject: Simple way to update kickstart RPM files? Message-ID: I have a kickstart server with the files copied from the CentOS 5.5 DVD's "CentOS" directory to a "CentOS" directory on the server, accessed by ftp during kickstart. On a target built by this system, I did a yum update, and over 100 packages were updated. I would like to merge the updates back to the kickstart server. But I don't see a simple way to just throw the *.rpm files (as grabbed from yum's cache) into some "updates" directory and the kickstart will do the right thing and resolve dependencies and install the latest. I would rather the updates just get installed in the first place, instead of having to take a second pass to do some kind of yum update method. Is there an elegant way? From jim at rossberry.com Fri Oct 1 11:36:25 2010 From: jim at rossberry.com (Jim Wildman) Date: Fri, 1 Oct 2010 07:36:25 -0400 (EDT) Subject: Simple way to update kickstart RPM files? In-Reply-To: References: Message-ID: On Thu, 30 Sep 2010, whitivery wrote: > I would like to merge the updates back to the kickstart server. Use mrepo or lftp (or favorite mirror tool) to mirror the centos updates tree onto your build server. Add the update repo to the server you build as part of kickstart. Run yum -y update in %post... ---------------------------------------------------------------------- Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine From Todd_Campbell at premierinc.com Fri Oct 1 12:33:53 2010 From: Todd_Campbell at premierinc.com (Campbell, Todd) Date: Fri, 1 Oct 2010 08:33:53 -0400 Subject: Simple way to update kickstart RPM files? In-Reply-To: References: Message-ID: Actually there is a 'repo' Kickstart keyword that can pull in the updates automatically, no need for running 'yum -y update'. repo --name= --baseurl=http://10.10.10.10/5.5/updates/x86_64/RPMS/ This essentially merges the install media RPM's with the updates. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Jim Wildman Sent: Friday, October 01, 2010 7:36 AM To: Discussion list about Kickstart Subject: Re: Simple way to update kickstart RPM files? On Thu, 30 Sep 2010, whitivery wrote: > I would like to merge the updates back to the kickstart server. Use mrepo or lftp (or favorite mirror tool) to mirror the centos updates tree onto your build server. Add the update repo to the server you build as part of kickstart. Run yum -y update in %post... ---------------------------------------------------------------------- Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ----------------------------------------- ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. From email at jasonkohles.com Fri Oct 1 12:46:46 2010 From: email at jasonkohles.com (Jason Kohles) Date: Fri, 1 Oct 2010 08:46:46 -0400 Subject: Simple way to update kickstart RPM files? In-Reply-To: References: Message-ID: I just use reposync (from the yum-utils package) to mirror the repositories, and then use them for the install. On Oct 1, 2010, at 1:50 AM, whitivery wrote: > I have a kickstart server with the files copied from the CentOS > 5.5 DVD's "CentOS" directory to a "CentOS" directory on the > server, accessed by ftp during kickstart. > > On a target built by this system, I did a yum update, and over > 100 packages were updated. > > I would like to merge the updates back to the kickstart server. > > But I don't see a simple way to just throw the *.rpm files (as > grabbed from yum's cache) into some "updates" directory and the > kickstart will do the right thing and resolve dependencies and > install the latest. > > I would rather the updates just get installed in the first place, > instead of having to take a second pass to do some kind of yum > update method. > > Is there an elegant way? > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From jake at v2gnu.com Fri Oct 1 12:57:15 2010 From: jake at v2gnu.com (Jake Vickers) Date: Fri, 01 Oct 2010 08:57:15 -0400 Subject: Simple way to update kickstart RPM files? In-Reply-To: References: Message-ID: <4CA5DAAB.4020400@v2gnu.com> On 10/01/2010 01:50 AM, whitivery wrote: > I have a kickstart server with the files copied from the CentOS > 5.5 DVD's "CentOS" directory to a "CentOS" directory on the > server, accessed by ftp during kickstart. > > On a target built by this system, I did a yum update, and over > 100 packages were updated. > > I would like to merge the updates back to the kickstart server. > > But I don't see a simple way to just throw the *.rpm files (as > grabbed from yum's cache) into some "updates" directory and the > kickstart will do the right thing and resolve dependencies and > install the latest. > > I would rather the updates just get installed in the first place, > instead of having to take a second pass to do some kind of yum > update method. > > Is there an elegant way? I usually do an install into a VM from my ISO, enable the yum cache, and then perform an update. Once that is complete, I gzip the updates and get them back onto my build machine. This process is a little tedious, but you copy the updates into the package folder for your ISO build and then delete the old versions that are in there. Then just run: rm -rf /ISO-Build-Dir/.olddata discinfo=`head -1 /ISO-Build-Dir/.discinfo` createrepo -u ?media://$discinfo? -g repodata/comps.xml /ISO-Build-Dir From clumens at redhat.com Fri Oct 1 14:05:45 2010 From: clumens at redhat.com (Chris Lumens) Date: Fri, 1 Oct 2010 10:05:45 -0400 Subject: Kickstart-list Digest, Vol 79, Issue 11 In-Reply-To: References: <4CA4B777.6020403@cadence.com> <1285863630-sup-8284@ezyang> <4CA4BB89.5010006@cadence.com> Message-ID: <20101001140545.GD23005@exeter.usersys.redhat.com> > I'm just surprised that almost 5 years later, it's still not in RHEL! Not five years: commit 5fb4af761cdc87b4025681e5306015a5f6adb560 Author: Chris Lumens Date: Fri Aug 24 15:41:44 2007 +0000 Add support for the %end directive, and issue DeprecationWarnings if it's not used. And it will be in RHEL6. Keep in mind that we have to keep compatibility in RHEL for a very long time, so there was no point in introducing it for RHEL5. In RHEL6 it's recommended like it's been in Fedora forever, and in RHEL7 it will be required like it is in F14. > It doesn't help that Anaconda doesn't plainly show its version ID > to the user during kickstart, and that its various web > documentation doesn't show or distinguish what version is being > documented, which might have clued me in that there were such > wide-apart versions in current use. anaconda currently prints its version number in the startup messages: if (FL_RESCUE(flags)) { fmt = _("Running anaconda %s, the %s rescue mode - please wait.\n"); } else { fmt = _("Running anaconda %s, the %s system installer - please wait.\n"); } printf(fmt, VERSION, getProductName()); In the log files: logMessage(INFO, "anaconda version %s on %s starting", VERSION, getProductArch()); And in tracebacks: lst.insert(0, "%s %s exception report\n" % (self.conf.programName, self.conf.programVersion)) In addition, given any kickstart file, ksvalidator (from the pykickstart package) can tell you whether it's syntactically correct for any version of RHEL or Fedora, back as far as RHEL3. - Chris From co55-sy1t at dea.spamcon.org Sat Oct 2 07:16:38 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Sat, 02 Oct 2010 00:16:38 -0700 Subject: Simple way to update kickstart RPM files? References: Message-ID: Jim Wildman wrote: >On Thu, 30 Sep 2010, whitivery wrote: > >> I would like to merge the updates back to the kickstart server. > >Use mrepo or lftp (or favorite mirror tool) to mirror the centos >updates tree onto your build server. Add the update repo to the server >you build as part of kickstart. Run yum -y update in %post... Thanks - but I'd like to try a 1-step solution first (no yum update needed, just install the latest versions in the first place). Reading about mrepo, it seems to be for online use. I should have mentioned that this kickstart server is on a standalone network. To update it I'd get the needed files some other way, then copy them to the server. From co55-sy1t at dea.spamcon.org Sat Oct 2 07:19:17 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Sat, 02 Oct 2010 00:19:17 -0700 Subject: Simple way to update kickstart RPM files? References: Message-ID: "Campbell, Todd" wrote: >Actually there is a 'repo' Kickstart keyword that can pull in the updates automatically, no need for running 'yum -y update'. > >repo --name= --baseurl=http://10.10.10.10/5.5/updates/x86_64/RPMS/ > >This essentially merges the install media RPM's with the updates. That sounds very good. All I need are the RPMs? No special directory structure or metadata files? Just plop them in a directory and point to it per your example (except I'd use ftp)? From co55-sy1t at dea.spamcon.org Sat Oct 2 07:20:20 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Sat, 02 Oct 2010 00:20:20 -0700 Subject: Simple way to update kickstart RPM files? References: Message-ID: Jason Kohles wrote: >I just use reposync (from the yum-utils package) to mirror the repositories, and then use them for the install. Thanks, I played with reposync. I first ran it without arguments, it was going to download something like 2500 packages! I then specified just the updates repo (I assume that's all I'd need). Still 580 packages. Read docs, add -n, brought it down to 392 packages. But it's still downloading many packages I don't have installed. I didn't see in its man page any way to download only for those packages already installed, like yum itself does - is there a way to do that? From co55-sy1t at dea.spamcon.org Sat Oct 2 07:21:32 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Sat, 02 Oct 2010 00:21:32 -0700 Subject: Simple way to update kickstart RPM files? References: <4CA5DAAB.4020400@v2gnu.com> Message-ID: Jake Vickers wrote: > On 10/01/2010 01:50 AM, whitivery wrote: >> I have a kickstart server with the files copied from the CentOS >> 5.5 DVD's "CentOS" directory to a "CentOS" directory on the >> server, accessed by ftp during kickstart. >> >> On a target built by this system, I did a yum update, and over >> 100 packages were updated. >> >> I would like to merge the updates back to the kickstart server. >> >> But I don't see a simple way to just throw the *.rpm files (as >> grabbed from yum's cache) into some "updates" directory and the >> kickstart will do the right thing and resolve dependencies and >> install the latest. >> >> I would rather the updates just get installed in the first place, >> instead of having to take a second pass to do some kind of yum >> update method. >> >> Is there an elegant way? > >I usually do an install into a VM from my ISO, enable the yum cache, and >then perform an update. Once that is complete, I gzip the updates and >get them back onto my build machine. This process is a little tedious, >but you copy the updates into the package folder for your ISO build and >then delete the old versions that are in there. Then just run: >rm -rf /ISO-Build-Dir/.olddata >discinfo=`head -1 /ISO-Build-Dir/.discinfo` >createrepo -u ?media://$discinfo? -g repodata/comps.xml /ISO-Build-Dir Thanks, but I want to avoid having to manually delete the old versions, as you say it's tedious, and too error-prone - I've seen tools mentioned to help with that, but would like to find a way to avoid it in the first place. The kickstart repo specification, or reposync method, mentioned by others in this thread might be the way to go. From co55-sy1t at dea.spamcon.org Sat Oct 2 07:32:58 2010 From: co55-sy1t at dea.spamcon.org (whitivery) Date: Sat, 02 Oct 2010 00:32:58 -0700 Subject: Kickstart-list Digest, Vol 79, Issue 11 References: <4CA4B777.6020403@cadence.com> <1285863630-sup-8284@ezyang> <4CA4BB89.5010006@cadence.com> <20101001140545.GD23005@exeter.usersys.redhat.com> Message-ID: Chris Lumens wrote: >> I'm just surprised that almost 5 years later, it's still not in RHEL! > >Not five years: Sorry, you are right, it was only Spring 2008 when I first ran into %end - seemed longer ago. >Keep in mind that we have to keep compatibility in RHEL for a very long time I see - didn't realize there were incompatibility concerns, since the places that mentioned it said it was still optional. >> It doesn't help that Anaconda doesn't plainly show its version ID >> >anaconda currently prints its version number in the startup messages: > ... I can see no startup message with the version number, unless it's one that flashes by in the early screens. The only user-level place it says anaconda is at the bottom of a blue screen just before saying the video card it found, and I don't think it says the version there. >In the log files: > ... There is no version number in the kickstart /tmp/anaconda.log, nor in the files placed in the target's root: anaconda-ks.cfg, install.log, and install.log.syslog. >And in tracebacks: > ... That's good but hopefully I'm not generating errors to cause a traceback. >In addition, given any kickstart file, ksvalidator (from the pykickstart >package) can tell you whether it's syntactically correct for any version >of RHEL or Fedora, back as far as RHEL3. That's good to know, I'll use that when I'm changing the kickstart file as a quick check. From Todd_Campbell at premierinc.com Sat Oct 2 11:49:49 2010 From: Todd_Campbell at premierinc.com (Campbell, Todd) Date: Sat, 2 Oct 2010 07:49:49 -0400 Subject: Simple way to update kickstart RPM files? In-Reply-To: References: Message-ID: No, you would need to create a repository based on those RPM's. Check out createrepo. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of whitivery Sent: Saturday, October 02, 2010 3:19 AM To: Kickstart-list at redhat.com Subject: Re: Simple way to update kickstart RPM files? "Campbell, Todd" wrote: >Actually there is a 'repo' Kickstart keyword that can pull in the updates automatically, no need for running 'yum -y update'. > >repo --name= --baseurl=http://10.10.10.10/5.5/updates/x86_64/RPMS/ > >This essentially merges the install media RPM's with the updates. That sounds very good. All I need are the RPMs? No special directory structure or metadata files? Just plop them in a directory and point to it per your example (except I'd use ftp)? _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ----------------------------------------- ***Note:The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by replying to the message and deleting it from your computer. Thank you. Premier Inc. From streamscalelance at gmail.com Tue Oct 5 20:44:53 2010 From: streamscalelance at gmail.com (Lance Gropper) Date: Tue, 5 Oct 2010 13:44:53 -0700 Subject: Can anaconda rerun itself? Message-ID: Hello Ya'all: Is it possible to put something in the %pre such that Anaconda re-runs itself without rebooting the system or running grub? Lance -------------- next part -------------- An HTML attachment was scrubbed... URL: From joe_wulf at yahoo.com Tue Oct 5 21:29:31 2010 From: joe_wulf at yahoo.com (Joe Wulf) Date: Tue, 5 Oct 2010 14:29:31 -0700 (PDT) Subject: Can anaconda rerun itself? In-Reply-To: References: Message-ID: <969458.73433.qm@web113301.mail.gq1.yahoo.com> Hello Lance---what is the use case?? What will you leverage this for? R, -Joe Wulf > >From: Lance Gropper >To: kickstart-list at redhat.com >Sent: Tue, October 5, 2010 4:44:53 PM >Subject: Can anaconda rerun itself? > >Hello Ya'all: > > >Is it possible to put something in the %pre such that Anaconda re-runs itself >without rebooting the system or running grub? > > >Lance > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From clumens at redhat.com Wed Oct 6 13:07:51 2010 From: clumens at redhat.com (Chris Lumens) Date: Wed, 6 Oct 2010 09:07:51 -0400 Subject: Can anaconda rerun itself? In-Reply-To: References: Message-ID: <20101006130750.GF13501@exeter.usersys.redhat.com> > Is it possible to put something in the %pre such that Anaconda re-runs > itself without rebooting the system or running grub? anaconda does not do a good job cleaning up after itself since it knows it runs with /tmp on a ramdisk and nothing will persist anyway. Therefore while it's likely you can do this, there's going to be a bunch of stuff in /tmp and mounted on the system that you will have to clean up yourself. I think this is a bad idea, though. - Chris From streamscalelance at gmail.com Wed Oct 6 16:28:33 2010 From: streamscalelance at gmail.com (Lance Gropper) Date: Wed, 6 Oct 2010 09:28:33 -0700 Subject: Kickstart-list Digest, Vol 80, Issue 4 In-Reply-To: References: Message-ID: Hello Joe: This is a followup to a previous posting - I need to alter constants in the kickstart file, which can't be altered in the %pre or %post sections. In particular, I'm creating an automated install, however the source installation device varies from machine to machine (on some machines, it's sda, on some it is sdb, and on some it is the last available sd device). The thinking here is that I can put statements in the %pre section which will modify the kickstart file only if the system is different from how the kickstart is currently set, then I want to rerun Anaconda at that point. When the Anaconda restarts (or starts), if it sees that the file matches the system, it continues with the kickstart process without modifying the file and without restarting Anaconda. I have no problem with the logic or modifying the file - I just need a way to restart anaconda without rebooting the machine or rerunning GRUB. Maybe even run a second instance of Anaconda from within Anaconda (but then clean exiting will become an issue). Lance On Wed, Oct 6, 2010 at 9:00 AM, wrote: > Send Kickstart-list mailing list submissions to > kickstart-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/kickstart-list > or, via email, send a message with subject or body 'help' to > kickstart-list-request at redhat.com > > You can reach the person managing the list at > kickstart-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Kickstart-list digest..." > > Today's Topics: > > 1. Can anaconda rerun itself? (Lance Gropper) > 2. Re: Can anaconda rerun itself? (Joe Wulf) > 3. Re: Can anaconda rerun itself? (Chris Lumens) > > > ---------- Forwarded message ---------- > From: Lance Gropper > To: kickstart-list at redhat.com > Date: Tue, 5 Oct 2010 13:44:53 -0700 > Subject: Can anaconda rerun itself? > Hello Ya'all: > > Is it possible to put something in the %pre such that Anaconda re-runs > itself without rebooting the system or running grub? > > Lance > > > > ---------- Forwarded message ---------- > From: Joe Wulf > To: Discussion list about Kickstart > Date: Tue, 5 Oct 2010 14:29:31 -0700 (PDT) > Subject: Re: Can anaconda rerun itself? > Hello Lance---what is the use case? What will you leverage this for? > > R, > -Joe Wulf > > > *From:* Lance Gropper > *To:* kickstart-list at redhat.com > *Sent:* Tue, October 5, 2010 4:44:53 PM > *Subject:* Can anaconda rerun itself? > > Hello Ya'all: > > Is it possible to put something in the %pre such that Anaconda re-runs > itself without rebooting the system or running grub? > > Lance > > > > ---------- Forwarded message ---------- > From: Chris Lumens > To: kickstart-list at redhat.com > Date: Wed, 6 Oct 2010 09:07:51 -0400 > Subject: Re: Can anaconda rerun itself? > > Is it possible to put something in the %pre such that Anaconda re-runs > > itself without rebooting the system or running grub? > > anaconda does not do a good job cleaning up after itself since it knows > it runs with /tmp on a ramdisk and nothing will persist anyway. > Therefore while it's likely you can do this, there's going to be a bunch > of stuff in /tmp and mounted on the system that you will have to clean > up yourself. > > I think this is a bad idea, though. > > - Chris > > > > _______________________________________________ > 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 matt at indigo.nu Thu Oct 7 03:38:14 2010 From: matt at indigo.nu (Matthew Sellers) Date: Wed, 6 Oct 2010 22:38:14 -0500 Subject: Kickstart-list Digest, Vol 80, Issue 4 In-Reply-To: References: Message-ID: Hi Lance, I think the easiest route to your solution is to use %ksappend or %include. You can create a script that runs in %pre to generate the customized portions of the kickstart, then %include that customization via the include statement. A step up from this concept is using a tool like cobbler... check out its website if you have never heard of it before. Basic Concept -- %pre # script to detect hardware and spit out custom kickstart lines: bash /root/ks_setup_drives.sh > /tmp/ks_drive_config.ks .... then inside kickstart: # include generated script: %include /tmp/ks_drive_config.ks I hope I am right that this behavior is consistent across older releases of Anaconda? -- Matt On Wed, Oct 6, 2010 at 11:28 AM, Lance Gropper wrote: > Hello Joe: > This is a followup to a previous posting - I need to alter constants in the > kickstart file, which can't be altered in the %pre or %post sections. In > particular, I'm creating an automated install, however the source > installation device varies from machine to machine (on some machines, it's > sda, on some it is sdb, and on some it is the last available sd device). The > thinking here is that I can put statements in the %pre section which will > modify the kickstart file only if the system is different from how the > kickstart is currently set, then I want to rerun Anaconda at that point. > When the Anaconda restarts (or starts), if it sees that the file matches the > system, it continues with the kickstart process without modifying the file > and without restarting Anaconda. I have no problem with the logic or > modifying the file - I just need a way to restart anaconda without rebooting > the machine or rerunning GRUB. Maybe even run a second instance of Anaconda > from within Anaconda (but then clean exiting will become an issue). > Lance > On Wed, Oct 6, 2010 at 9:00 AM, wrote: >> >> Send Kickstart-list mailing list submissions to >> ? ? ? ?kickstart-list at redhat.com >> >> To subscribe or unsubscribe via the World Wide Web, visit >> ? ? ? ?https://www.redhat.com/mailman/listinfo/kickstart-list >> or, via email, send a message with subject or body 'help' to >> ? ? ? ?kickstart-list-request at redhat.com >> >> You can reach the person managing the list at >> ? ? ? ?kickstart-list-owner at redhat.com >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Kickstart-list digest..." >> >> Today's Topics: >> >> ? 1. Can anaconda rerun itself? (Lance Gropper) >> ? 2. Re: Can anaconda rerun itself? (Joe Wulf) >> ? 3. Re: Can anaconda rerun itself? (Chris Lumens) >> >> >> ---------- Forwarded message ---------- >> From:?Lance Gropper >> To:?kickstart-list at redhat.com >> Date:?Tue, 5 Oct 2010 13:44:53 -0700 >> Subject:?Can anaconda rerun itself? >> Hello Ya'all: >> Is it possible to put something in the %pre such that Anaconda re-runs >> itself without rebooting the system or running grub? >> Lance >> >> >> ---------- Forwarded message ---------- >> From:?Joe Wulf >> To:?Discussion list about Kickstart >> Date:?Tue, 5 Oct 2010 14:29:31 -0700 (PDT) >> Subject:?Re: Can anaconda rerun itself? >> Hello Lance---what is the use case?? What will you leverage this for? >> >> R, >> -Joe Wulf >> >> From: Lance Gropper >> To: kickstart-list at redhat.com >> Sent: Tue, October 5, 2010 4:44:53 PM >> Subject: Can anaconda rerun itself? >> >> Hello Ya'all: >> Is it possible to put something in the %pre such that Anaconda re-runs >> itself without rebooting the system or running grub? >> Lance >> >> >> ---------- Forwarded message ---------- >> From:?Chris Lumens >> To:?kickstart-list at redhat.com >> Date:?Wed, 6 Oct 2010 09:07:51 -0400 >> Subject:?Re: Can anaconda rerun itself? >> > Is it possible to put something in the %pre such that Anaconda re-runs >> > itself without rebooting the system or running grub? >> >> anaconda does not do a good job cleaning up after itself since it knows >> it runs with /tmp on a ramdisk and nothing will persist anyway. >> Therefore while it's likely you can do this, there's going to be a bunch >> of stuff in /tmp and mounted on the system that you will have to clean >> up yourself. >> >> I think this is a bad idea, though. >> >> - Chris >> >> >> >> _______________________________________________ >> 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 juels at photodiagnostic.com Thu Oct 7 15:00:25 2010 From: juels at photodiagnostic.com (Philip Juels) Date: Thu, 7 Oct 2010 11:00:25 -0400 Subject: RHEL6 kickstart installation from USB key Message-ID: Hi all, I've been kickstart installing RHEL4 and 5 from a 32GB USB key for a couple of years now. The method I use to create the USB installation environment is roughly: 1) Re-partition USB key: one small, 100MB, vfat partition containing the boot loader, kernel, ramdisk image, and kickstart config file; remainder of storage is a ext2 partition containing the package repository and installation customizations. 2) Use syslinux and lilo for bootloader. I tried this method to build a similar RHEL6 USB key installer, but with no success. Basically, after the kernel loads, I get nothing, just a hung system (something going wrong at the ramdisk loading?). Anyway, as anyone else successfully created a USB-based RHEL6 kickstart installer? THX, --PJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From streamscalelance at gmail.com Thu Oct 7 18:59:21 2010 From: streamscalelance at gmail.com (Lance Gropper) Date: Thu, 7 Oct 2010 11:59:21 -0700 Subject: Kickstart-list Digest, Vol 80, Issue 5 In-Reply-To: References: Message-ID: Hello Matt: The include doesn't work for the installation source - only the destination. I have already modified other portions to use include, but if you try to modify it to use a different install from directory, it's ignored. Lance On Thu, Oct 7, 2010 at 9:00 AM, wrote: > Send Kickstart-list mailing list submissions to > kickstart-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/kickstart-list > or, via email, send a message with subject or body 'help' to > kickstart-list-request at redhat.com > > You can reach the person managing the list at > kickstart-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Kickstart-list digest..." > > Today's Topics: > > 1. Re: Kickstart-list Digest, Vol 80, Issue 4 (Lance Gropper) > 2. Re: Kickstart-list Digest, Vol 80, Issue 4 (Matthew Sellers) > 3. RHEL6 kickstart installation from USB key (Philip Juels) > > > ---------- Forwarded message ---------- > From: Lance Gropper > To: kickstart-list at redhat.com > Date: Wed, 6 Oct 2010 09:28:33 -0700 > Subject: Re: Kickstart-list Digest, Vol 80, Issue 4 > Hello Joe: > > This is a followup to a previous posting - I need to alter constants in the > kickstart file, which can't be altered in the %pre or %post sections. In > particular, I'm creating an automated install, however the source > installation device varies from machine to machine (on some machines, it's > sda, on some it is sdb, and on some it is the last available sd device). The > thinking here is that I can put statements in the %pre section which will > modify the kickstart file only if the system is different from how the > kickstart is currently set, then I want to rerun Anaconda at that point. > When the Anaconda restarts (or starts), if it sees that the file matches the > system, it continues with the kickstart process without modifying the file > and without restarting Anaconda. I have no problem with the logic or > modifying the file - I just need a way to restart anaconda without rebooting > the machine or rerunning GRUB. Maybe even run a second instance of Anaconda > from within Anaconda (but then clean exiting will become an issue). > > Lance > > On Wed, Oct 6, 2010 at 9:00 AM, wrote: > >> Send Kickstart-list mailing list submissions to >> kickstart-list at redhat.com >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.redhat.com/mailman/listinfo/kickstart-list >> or, via email, send a message with subject or body 'help' to >> kickstart-list-request at redhat.com >> >> You can reach the person managing the list at >> kickstart-list-owner at redhat.com >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Kickstart-list digest..." >> >> Today's Topics: >> >> 1. Can anaconda rerun itself? (Lance Gropper) >> 2. Re: Can anaconda rerun itself? (Joe Wulf) >> 3. Re: Can anaconda rerun itself? (Chris Lumens) >> >> >> ---------- Forwarded message ---------- >> From: Lance Gropper >> To: kickstart-list at redhat.com >> Date: Tue, 5 Oct 2010 13:44:53 -0700 >> Subject: Can anaconda rerun itself? >> Hello Ya'all: >> >> Is it possible to put something in the %pre such that Anaconda re-runs >> itself without rebooting the system or running grub? >> >> Lance >> >> >> >> ---------- Forwarded message ---------- >> From: Joe Wulf >> To: Discussion list about Kickstart >> Date: Tue, 5 Oct 2010 14:29:31 -0700 (PDT) >> Subject: Re: Can anaconda rerun itself? >> Hello Lance---what is the use case? What will you leverage this for? >> >> R, >> -Joe Wulf >> >> >> *From:* Lance Gropper >> *To:* kickstart-list at redhat.com >> *Sent:* Tue, October 5, 2010 4:44:53 PM >> *Subject:* Can anaconda rerun itself? >> >> Hello Ya'all: >> >> Is it possible to put something in the %pre such that Anaconda re-runs >> itself without rebooting the system or running grub? >> >> Lance >> >> >> >> ---------- Forwarded message ---------- >> From: Chris Lumens >> To: kickstart-list at redhat.com >> Date: Wed, 6 Oct 2010 09:07:51 -0400 >> Subject: Re: Can anaconda rerun itself? >> > Is it possible to put something in the %pre such that Anaconda re-runs >> > itself without rebooting the system or running grub? >> >> anaconda does not do a good job cleaning up after itself since it knows >> it runs with /tmp on a ramdisk and nothing will persist anyway. >> Therefore while it's likely you can do this, there's going to be a bunch >> of stuff in /tmp and mounted on the system that you will have to clean >> up yourself. >> >> I think this is a bad idea, though. >> >> - Chris >> >> >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list >> > > > > ---------- Forwarded message ---------- > From: Matthew Sellers > To: Discussion list about Kickstart > Date: Wed, 6 Oct 2010 22:38:14 -0500 > Subject: Re: Kickstart-list Digest, Vol 80, Issue 4 > Hi Lance, > > I think the easiest route to your solution is to use %ksappend or > %include. You can create a script that runs in %pre to generate the > customized portions of the kickstart, then %include that customization > via the include statement. A step up from this concept is using a > tool like cobbler... check out its website if you have never heard of > it before. > > Basic Concept > -- > > %pre > > # script to detect hardware and spit out custom kickstart lines: > bash /root/ks_setup_drives.sh > /tmp/ks_drive_config.ks > > .... then inside kickstart: > > # include generated script: > %include /tmp/ks_drive_config.ks > > I hope I am right that this behavior is consistent across older > releases of Anaconda? > > -- > Matt > > > > > > > > > > > > On Wed, Oct 6, 2010 at 11:28 AM, Lance Gropper > wrote: > > Hello Joe: > > This is a followup to a previous posting - I need to alter constants in > the > > kickstart file, which can't be altered in the %pre or %post sections. In > > particular, I'm creating an automated install, however the source > > installation device varies from machine to machine (on some machines, > it's > > sda, on some it is sdb, and on some it is the last available sd device). > The > > thinking here is that I can put statements in the %pre section which will > > modify the kickstart file only if the system is different from how the > > kickstart is currently set, then I want to rerun Anaconda at that point. > > When the Anaconda restarts (or starts), if it sees that the file matches > the > > system, it continues with the kickstart process without modifying the > file > > and without restarting Anaconda. I have no problem with the logic or > > modifying the file - I just need a way to restart anaconda without > rebooting > > the machine or rerunning GRUB. Maybe even run a second instance of > Anaconda > > from within Anaconda (but then clean exiting will become an issue). > > Lance > > On Wed, Oct 6, 2010 at 9:00 AM, > wrote: > >> > >> Send Kickstart-list mailing list submissions to > >> kickstart-list at redhat.com > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> https://www.redhat.com/mailman/listinfo/kickstart-list > >> or, via email, send a message with subject or body 'help' to > >> kickstart-list-request at redhat.com > >> > >> You can reach the person managing the list at > >> kickstart-list-owner at redhat.com > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of Kickstart-list digest..." > >> > >> Today's Topics: > >> > >> 1. Can anaconda rerun itself? (Lance Gropper) > >> 2. Re: Can anaconda rerun itself? (Joe Wulf) > >> 3. Re: Can anaconda rerun itself? (Chris Lumens) > >> > >> > >> ---------- Forwarded message ---------- > >> From: Lance Gropper > >> To: kickstart-list at redhat.com > >> Date: Tue, 5 Oct 2010 13:44:53 -0700 > >> Subject: Can anaconda rerun itself? > >> Hello Ya'all: > >> Is it possible to put something in the %pre such that Anaconda re-runs > >> itself without rebooting the system or running grub? > >> Lance > >> > >> > >> ---------- Forwarded message ---------- > >> From: Joe Wulf > >> To: Discussion list about Kickstart > >> Date: Tue, 5 Oct 2010 14:29:31 -0700 (PDT) > >> Subject: Re: Can anaconda rerun itself? > >> Hello Lance---what is the use case? What will you leverage this for? > >> > >> R, > >> -Joe Wulf > >> > >> From: Lance Gropper > >> To: kickstart-list at redhat.com > >> Sent: Tue, October 5, 2010 4:44:53 PM > >> Subject: Can anaconda rerun itself? > >> > >> Hello Ya'all: > >> Is it possible to put something in the %pre such that Anaconda re-runs > >> itself without rebooting the system or running grub? > >> Lance > >> > >> > >> ---------- Forwarded message ---------- > >> From: Chris Lumens > >> To: kickstart-list at redhat.com > >> Date: Wed, 6 Oct 2010 09:07:51 -0400 > >> Subject: Re: Can anaconda rerun itself? > >> > Is it possible to put something in the %pre such that Anaconda re-runs > >> > itself without rebooting the system or running grub? > >> > >> anaconda does not do a good job cleaning up after itself since it knows > >> it runs with /tmp on a ramdisk and nothing will persist anyway. > >> Therefore while it's likely you can do this, there's going to be a bunch > >> of stuff in /tmp and mounted on the system that you will have to clean > >> up yourself. > >> > >> I think this is a bad idea, though. > >> > >> - Chris > >> > >> > >> > >> _______________________________________________ > >> 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 > > > > > > > ---------- Forwarded message ---------- > From: Philip Juels > To: Kickstart-list > Date: Thu, 7 Oct 2010 11:00:25 -0400 > Subject: RHEL6 kickstart installation from USB key > Hi all, > > I've been kickstart installing RHEL4 and 5 from a 32GB USB key for a couple > of years now. The method I use to create the USB installation environment > is roughly: > > 1) Re-partition USB key: one small, 100MB, vfat partition containing the > boot loader, kernel, ramdisk image, and kickstart config file; remainder of > storage is a ext2 partition containing the package repository and > installation customizations. > 2) Use syslinux and lilo for bootloader. > > I tried this method to build a similar RHEL6 USB key installer, but with no > success. Basically, after the kernel loads, I get nothing, just a hung > system (something going wrong at the ramdisk loading?). > > Anyway, as anyone else successfully created a USB-based RHEL6 kickstart > installer? > > THX, > > --PJ > > > > _______________________________________________ > 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 flaks at bnl.gov Wed Oct 13 13:56:38 2010 From: flaks at bnl.gov (Leonid Flaks) Date: Wed, 13 Oct 2010 09:56:38 -0400 Subject: Strange behavior of grubby in anaconda (fedora 13) Message-ID: <4CB5BA96.7060707@bnl.gov> Hi! I am trying to run the following command in anaconda during installation of Fedora 13: /sbin/grubby --update-kernel=`/sbin/grubby --default-kernel` --args="console=tty0" And it does not work - no changes to grub.conf are made. If I run it on the system after installation is complete, it works just fine. Some more information - this command is generated by cobbler snippet post_install_kernel_options. I have it as a part of more complicated set - the original command uses --agrs="console=tty0 console=console=ttyS0,9600n8". The second part (with ttyS0) works fine, but the first one is dropped. I tried to swap them - the order does not matter. I have the same setting working on Scientific Linux without any problems. It is not a cobbler issue - the snippet is rendered properly and also I tried to run it manually during post installation logging into the system with ssh. Any comments/ideas why would that happens? Thanks! Leon