From ebpeele2 at pams.ncsu.edu Thu Apr 1 02:30:10 2004 From: ebpeele2 at pams.ncsu.edu (Elliot Peele) Date: Wed, 31 Mar 2004 21:30:10 -0500 Subject: ks config managers In-Reply-To: <1080740488.31796.6.camel@biblos.oit.duke.edu> References: <1080740488.31796.6.camel@biblos.oit.duke.edu> Message-ID: <1080786609.29574.1.camel@localhost.localdomain> This is what we have developed for this purpose. http://linux.ncsu.edu/projects/web-kickstart Elliot On Wed, 2004-03-31 at 08:41, Chris Geddings wrote: > What projects are out there for building kickstart files and maintaining > them over time? > > The problem I'm looking to address involves the maintenance of a large > number of kickstart configurations over time. What is in my head right > now is a system that has a series of configurations, each configuration > can have parts that are sort of stubs or templates that may be shared > between multiple configurations. Updating one of the stubs causes an > update in all relevant configurations. > > Many thanks, > Chris > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From Siva.Jayaraman at Glenayre.com Thu Apr 1 14:32:14 2004 From: Siva.Jayaraman at Glenayre.com (Jayaraman, Siva) Date: Thu, 1 Apr 2004 09:32:14 -0500 Subject: RHEL AS-2.1 U3 extremely slow - nfs issue? Message-ID: that was it! I moved to a e.38 boot image and it worked perfectly as it should. Thanks! Siva Jayaraman siva.jayaraman at glenayre.com 770.283.2559 > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Joshua Jensen > Sent: Monday, March 29, 2004 1:14 PM > To: Discussion list about Kickstart > Subject: Re: RHEL AS-2.1 U3 extremely slow - nfs issue? > > > Could it be this? > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112766 > > Joshua > > > > On Mon, Mar 29, 2004 at 11:43:17AM -0500, Jayaraman, Siva wrote: > > > > hello all, > > > > We are in the process of moving to more recent > distributions of RH viz RHEL > > AS-2.1 Update3 & RH AS-3.0. > > > > We have kickstart infrastructure in place deploying RH7.2 > and RH AS-2.1 > > distributions. > > The kickstarts are done over NFS. > > > > The new distributions were added to the NFS server (which > is the same as the > > DHCP server). > > But the new kickstarts (AS-2.1-U3 & AS-3.0) take an > extremely long time now. > > > > The older kickstarts install around 800M of pkgs in about 3 > minutes, whereas > > now the newer kickstarts take around 50 minutes to install > 650M of packages. > > > > I checked the network connection and it is always 100Mbps > Full Duplex for > > both cases. > > The only difference I notice is that I get this message on > one of the > > virtual consoles - > > "nfs: mount version older than kernel" > > > > The older kickstarts mount the nfs directory as nfs v2 > whereas the newer > > kickstarts mount the directory as v3. > > Could this be the source of my problem? > > > > The NFS server is a RH7.2 box capable of doing both v2 & v3. > > > > If anyone has suggestions on how to debug/correct this > problem, I would > > highly appreciate it. > > > > thanks! > > Siva Jayaraman > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > -- > Joshua Jensen > Work: 919 392 1488 Mobile: 919 454 9679 Fax: 919 392 7377 > Pager: 866 264 2691 Epage: jjensen at epage.cisco.com > IBM Linux Architect - RHCE, RHCT, etc > "If God didn't want us to eat animals, why did he make them > out of meat?" > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From chris at geddings.org Thu Apr 1 14:49:51 2004 From: chris at geddings.org (Chris Geddings) Date: Thu, 01 Apr 2004 09:49:51 -0500 Subject: ks config managers In-Reply-To: References: Message-ID: <1080830990.8514.6.camel@biblos.oit.duke.edu> Could you send more detail on the design specs and pit falls? So far, I've seen everything folks posted before, and there are elements in each project of what I want, but I'm trying to think my way through a fairly general solution that will work for a lot of groups. I'm thinking something that is completely web manageable. Ideally, I'd also like to work in some sort of validation system that could pick up obvious errors in the key value sections (though that is an interesting problem there.) --Chris On Wed, 2004-03-31 at 14:09, James_Martin at ao.uscourts.gov wrote: > I wrote such a system using PHP and MySQL.. I actually store parts of the > kickstart file as templates in the database, and regexp certain things > like network information, packages, etc. It works quite well. I wish I > could Open Source it, but the powers that be get lost in the red tape. > > James > > > James S. Martin, RHCE > Contractor > Administrative Office of the United States Courts > Washington, DC > (202) 502-2394 > > > > > Ken Teh > Sent by: kickstart-list-bounces at redhat.com > 03/31/2004 10:10 AM > Please respond to Discussion list about Kickstart > > > To: Discussion list about Kickstart > cc: > Subject: Re: ks config managers > > > My simple minded approach: Use CVS or RCS to track your files. Sharing, > stubs, templates can be done with a Makefile, shell script and a metafile > containing the differences. And put these under RCS as well. > > Cheers! Ken > > > On Wed, 31 Mar 2004, Chris Geddings wrote: > > > What projects are out there for building kickstart files and maintaining > > them over time? > > > > The problem I'm looking to address involves the maintenance of a large > > number of kickstart configurations over time. What is in my head right > > now is a system that has a series of configurations, each configuration > > can have parts that are sort of stubs or templates that may be shared > > between multiple configurations. Updating one of the stubs causes an > > update in all relevant configurations. > > > > Many thanks, > > 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 > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From jjensen at cisco.com Thu Apr 1 16:07:42 2004 From: jjensen at cisco.com (Joshua Jensen) Date: Thu, 1 Apr 2004 11:07:42 -0500 Subject: RHEL AS-2.1 U3 extremely slow - nfs issue? In-Reply-To: References: Message-ID: <20040401160742.GD28616@cisco.com> Yup... as that bug that I opened said, NFS over UDP (which is what anaconda uses for installs) was _badly_ broken. Where did you find the e.38 boot images? On Thu, Apr 01, 2004 at 09:32:14AM -0500, Jayaraman, Siva wrote: > > that was it! > I moved to a e.38 boot image and it worked perfectly as it should. > > Thanks! > Siva Jayaraman > siva.jayaraman at glenayre.com > 770.283.2559 > > > > -----Original Message----- > > From: kickstart-list-bounces at redhat.com > > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Joshua Jensen > > Sent: Monday, March 29, 2004 1:14 PM > > To: Discussion list about Kickstart > > Subject: Re: RHEL AS-2.1 U3 extremely slow - nfs issue? > > > > > > Could it be this? > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112766 > > > > Joshua > > > > > > > > On Mon, Mar 29, 2004 at 11:43:17AM -0500, Jayaraman, Siva wrote: > > > > > > hello all, > > > > > > We are in the process of moving to more recent > > distributions of RH viz RHEL > > > AS-2.1 Update3 & RH AS-3.0. > > > > > > We have kickstart infrastructure in place deploying RH7.2 > > and RH AS-2.1 > > > distributions. > > > The kickstarts are done over NFS. > > > > > > The new distributions were added to the NFS server (which > > is the same as the > > > DHCP server). > > > But the new kickstarts (AS-2.1-U3 & AS-3.0) take an > > extremely long time now. > > > > > > The older kickstarts install around 800M of pkgs in about 3 > > minutes, whereas > > > now the newer kickstarts take around 50 minutes to install > > 650M of packages. > > > > > > I checked the network connection and it is always 100Mbps > > Full Duplex for > > > both cases. > > > The only difference I notice is that I get this message on > > one of the > > > virtual consoles - > > > "nfs: mount version older than kernel" > > > > > > The older kickstarts mount the nfs directory as nfs v2 > > whereas the newer > > > kickstarts mount the directory as v3. > > > Could this be the source of my problem? > > > > > > The NFS server is a RH7.2 box capable of doing both v2 & v3. > > > > > > If anyone has suggestions on how to debug/correct this > > problem, I would > > > highly appreciate it. > > > > > > thanks! > > > Siva Jayaraman > > > > > > > > > _______________________________________________ > > > Kickstart-list mailing list > > > Kickstart-list at redhat.com > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > -- > > Joshua Jensen > > Work: 919 392 1488 Mobile: 919 454 9679 Fax: 919 392 7377 > > Pager: 866 264 2691 Epage: jjensen at epage.cisco.com > > IBM Linux Architect - RHCE, RHCT, etc > > "If God didn't want us to eat animals, why did he make them > > out of meat?" > > > > > > _______________________________________________ > > 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 -- Joshua Jensen Work: 919 392 1488 Mobile: 919 454 9679 Fax: 919 392 7377 Pager: 866 264 2691 Epage: jjensen at epage.cisco.com IBM Linux Architect - RHCE, RHCT, etc "If God didn't want us to eat animals, why did he make them out of meat?" From adam_gautier at yahoo.com Thu Apr 1 17:09:07 2004 From: adam_gautier at yahoo.com (Adam T. Gautier) Date: Thu, 01 Apr 2004 12:09:07 -0500 Subject: Kickstart Configuration Managers Message-ID: <406C4CB3.8050609@yahoo.com> I am in the process of creating a system that could incorporate the feature of a kickstart configuration manager. I am building an online service for designing and building custom Linux distributions based on the big four Linux distos (RedHat(Fedora), Mandrake, Suse, and Debian). I am building this for two reasons. 1.) I have a series of utilities and scripts already built for my own use in this area. 2.) I would like to bootstrap some consulting services around this concept. The main purpose of this service is to allow the community to design distos around particular solutions without fracturing the Linux community with more bistro's. An example of solutions could be a pre configured dedicated email server, a Linux gaming distribution, etc... To me, there is no reason that a PROPERLY customized distribution of an existing distro is any different from installing packages and modifying their configuration files. I am striving that it would not even invalidate the support contract. I want to expand this concept by pushing more configuration capabilities into Anaconda (by default also supporting Kickstart) and the initial config script. I am also hoping to provide a set of services to support the community. I would like to allow the sharing of these custom distro iso, ks files, anaconda modules, etc... for anyone to pick and choose between what they want to include in their own distro. Currently, I am working on a package tracker for the service (think rpmfind.net or Brad Smith's Tracker http://academy.phpwebhosting.com/cgi-bin/tracker/tracker.py ). This will provide an online service that resolves package dependencies and allow for the definition of solution sets (think groups of the comp.xml file). These solution sets would be shared with the community. These solutions would then be added to the top of defined distribution bases (the big four Linux distros). All of these selections on the webapp are structured into a distro spec file. This is my own invention and would define base distro, packages (location, versions), configurations (ks, anaconda), This can be downloaded and fed into some client software (the utilities and scripts I already have). Then, client software will download the packages (distro packages and third-party packages), check them (MD5 and GPG), and setup the distribution directory. This client software will also allow for the customization of look and feel (logo's, desktop, icons, display names) and additional private packages not exposed to the community. Then the user would just use mkisofs to create iso files or deploy using http and/or ftp. The main features of this service would be: 1.) Custom distros based on existing Linux distros 2.) Custom distros based on existing custom distros 3.) A library of custom disto's 4.) A library of ks file components 5.) A library of anaconda modules 6.) A library of package solution sets 7.) A library of packages (distro's and third-party packages) 8.) Client software to simplify branding of the custom distro. 9.) Community (forum's and mailing lists) 10.) Ongoing package support for the custom distros. (Customized up2date/yum) 11.) Many more... I have an ongoing wishlist I am thinking of charging $30/year for access to the service. This is simply to help pay for the massive costs of hosting. The market is not that big and I am not trying to get rich, I just want to split the cost (like I said I am hoping to make my money in consulting). Does $30/year seem reasonable for this service? I also want to charge $2-5/month for end user ongoing package support. I was thinking of allowing the distro creators a revenue sharing model whenever an end user registers to receive updated packages. Not sure if any of these money concepts are going to fly, I am building the service anyway and worst case scenario I give allot of code to the community. Again, I just want to come up with a way to offset my costs to put up this service. Please, let me know what everyone thinks. I am about 1 month into the development and should have an alpha version deployed mid April for review. Also, please help me with ideas around how best to dissect the ks config file into reusable chunks for publication. Thanks, Adam From chris at geddings.org Thu Apr 1 19:15:22 2004 From: chris at geddings.org (Chris Geddings) Date: Thu, 01 Apr 2004 14:15:22 -0500 Subject: Kickstart Configuration Managers In-Reply-To: <406C4CB3.8050609@yahoo.com> References: <406C4CB3.8050609@yahoo.com> Message-ID: <1080846922.8514.93.camel@biblos.oit.duke.edu> Can you frame out what the word 'distro' means in your vision? I'm thinking one major problem you are going to see will center around packaging and distribution centric assumptions in packages. I admit to being largely RedHat focused for the past few years, so I'm not sure how much of what I understand in distributions has been widely adopted versus rh centric. I'm thinking about things like chkconfig for service management. Differing versions of rpm not always playing well together. Different distributions assumptions about what it is a package is providing and where files should go. So on and so forth. How are you foreseeing addressing those sorts of issues? --Chris On Thu, 2004-04-01 at 12:09, Adam T. Gautier wrote: > I am in the process of creating a system that could incorporate the > feature of a kickstart configuration manager. I am building an online > service for designing and building custom Linux distributions based on > the big four Linux distos (RedHat(Fedora), Mandrake, Suse, and Debian). > I am building this for two reasons. > > 1.) I have a series of utilities and scripts already built for my own > use in this area. > 2.) I would like to bootstrap some consulting services around this concept. > > The main purpose of this service is to allow the community to design > distos around particular solutions without fracturing the Linux > community with more bistro's. An example of solutions could be a pre > configured dedicated email server, a Linux gaming distribution, etc... > To me, there is no reason that a PROPERLY customized distribution of an > existing distro is any different from installing packages and modifying > their configuration files. I am striving that it would not even > invalidate the support contract. I want to expand this concept by > pushing more configuration capabilities into Anaconda (by default also > supporting Kickstart) and the initial config script. I am also hoping > to provide a set of services to support the community. I would like to > allow the sharing of these custom distro iso, ks files, anaconda > modules, etc... for anyone to pick and choose between what they want to > include in their own distro. > > Currently, I am working on a package tracker for the service (think > rpmfind.net or Brad Smith's Tracker > http://academy.phpwebhosting.com/cgi-bin/tracker/tracker.py ). This > will provide an online service that resolves package dependencies and > allow for the definition of solution sets (think groups of the comp.xml > file). These solution sets would be shared with the community. These > solutions would then be added to the top of defined distribution bases > (the big four Linux distros). All of these selections on the webapp are > structured into a distro spec file. This is my own invention and would > define base distro, packages (location, versions), configurations (ks, > anaconda), This can be downloaded and fed into some client software (the > utilities and scripts I already have). Then, client software will > download the packages (distro packages and third-party packages), check > them (MD5 and GPG), and setup the distribution directory. This client > software will also allow for the customization of look and feel (logo's, > desktop, icons, display names) and additional private packages not > exposed to the community. Then the user would just use mkisofs to > create iso files or deploy using http and/or ftp. > > The main features of this service would be: > > 1.) Custom distros based on existing Linux distros > 2.) Custom distros based on existing custom distros > 3.) A library of custom disto's > 4.) A library of ks file components > 5.) A library of anaconda modules > 6.) A library of package solution sets > 7.) A library of packages (distro's and third-party packages) > 8.) Client software to simplify branding of the custom distro. > 9.) Community (forum's and mailing lists) > 10.) Ongoing package support for the custom distros. (Customized > up2date/yum) > 11.) Many more... I have an ongoing wishlist > > I am thinking of charging $30/year for access to the service. This is > simply to help pay for the massive costs of hosting. The market is not > that big and I am not trying to get rich, I just want to split the cost > (like I said I am hoping to make my money in consulting). Does $30/year > seem reasonable for this service? I also want to charge $2-5/month for > end user ongoing package support. I was thinking of allowing the distro > creators a revenue sharing model whenever an end user registers to > receive updated packages. Not sure if any of these money concepts are > going to fly, I am building the service anyway and worst case scenario I > give allot of code to the community. Again, I just want to come up with > a way to offset my costs to put up this service. > > Please, let me know what everyone thinks. I am about 1 month into the > development and should have an alpha version deployed mid April for > review. Also, please help me with ideas around how best to dissect the > ks config file into reusable chunks for publication. > > Thanks, > > Adam > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From adam_gautier at yahoo.com Fri Apr 2 15:00:42 2004 From: adam_gautier at yahoo.com (Adam T. Gautier) Date: Fri, 02 Apr 2004 10:00:42 -0500 Subject: Kickstart Configuration Managers In-Reply-To: <1080846922.8514.93.camel@biblos.oit.duke.edu> References: <406C4CB3.8050609@yahoo.com> <1080846922.8514.93.camel@biblos.oit.duke.edu> Message-ID: <406D801A.5000408@yahoo.com> Chris Geddings wrote: >Can you frame out what the word 'distro' means in your vision? > > Distro is a linux distribution. Redhat, Fedora, Mandrake, Suse, and Debian are all distros. The 'vision' if it should even be called that is an easy way to customize those established distros and re-distribute a new distro. These new custom distros would be more solution specific than the established distros. Examples, Defining a custom desktop for a company, dedicated servers (email, webserver, application firewall(Zorp), CMS (/.), etc..), beowolf clusters, gamming distro, and the list goes on... >I'm thinking one major problem you are going to see will center around >packaging and distribution centric assumptions in packages. I admit to >being largely RedHat focused for the past few years, so I'm not sure how >much of what I understand in distributions has been widely adopted >versus rh centric. > > Well, I have built distros from RedHat(Fedora)/Mandrake and run test around Suse. They all use RPM and Anaconda. Of course a package for RedHat probably will not work in a different base distro (Suse or Mandrake) but the solution I propose still provides some value. For example, A user in company A defines a customized desktop distribution around Mandrake; another user whose company B uses RedHat could use the previous distro specification as a starting point(what packages, ks config, linux config, etc) to create a similar distro for hist company. Eventually, I think I can automate this process. I would also hope that each custom distro would be able to fall under existing supprt contracts with RedHat and Mandrake. The big anomoly is Debian. I will work on that one last but I am designing the solution with package distribution features so any distro that uses packages (rpm or apt) should be pluggable into the solution. >I'm thinking about things like chkconfig for service management. >Differing versions of rpm not always playing well together. Different >distributions assumptions about what it is a package is providing and >where files should go. > > Yes, that is exactly right. To solve this the first choice in creating a distro will be what base distro to use. That will limit which packages you should access. But with all the packages in one place there is no reason why you could not try another distro's package. This probably will not work but what the hell... If this idea catches on maybe enough people could push the big distro's to standardize, who knows... From jeremy at broadware.com Fri Apr 2 16:14:37 2004 From: jeremy at broadware.com (Jeremy Silver) Date: Fri, 2 Apr 2004 08:14:37 -0800 Subject: dhcp okay, but no http In-Reply-To: Message-ID: <001701c418cd$9b4b9280$a13c0a0a@slaptop> Seph, Do the precisions have multiple NICs? I have repeatedly had problems with booting off one NIC and Linux defines the other as eth0, tries to get the config file (in my case with NFS) and fails since only the other NIC was connected. In which case, try booting off the other NIC. Also, I think there is a kernel parameter in RH9 (and therefore may be in Fedora) where you can specify which NIC to use, such as 'ksdevice=link' to use the connected NIC or 'ksdevice=eth1' to force kickstart to use the secondary NIC. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of seph Sent: Wednesday, March 31, 2004 01:58 PM To: kickstart-list at redhat.com Subject: Re: dhcp okay, but no http > They boot, they get dhcp, but they always fail to get the config file. > If I run things through a hub, I see the dhcp traffic, but the machine > never even sends an http request. > > Playing around a bit more, I seem to only have trouble with the > precisions when plugged into netgear hubs or switches. Even with > network cards that work in the dimensions on the same switches. I realize this is confusing. Let me try again... The precision machines, with their onboard NICs fail when talking to netgear equipment. However, the failure is not what I'd expect for network incompatability. They get dhcp, they ping. They claim http fails, but they send no packets, and drop into manual mode. From manual mode, http works fine. seph _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From f.leeflang at hva.nl Fri Apr 2 16:41:57 2004 From: f.leeflang at hva.nl (Fred Leeflang) Date: Fri, 02 Apr 2004 18:41:57 +0200 Subject: Kickstart Configuration Managers In-Reply-To: <406D801A.5000408@yahoo.com> References: <406C4CB3.8050609@yahoo.com> <1080846922.8514.93.camel@biblos.oit.duke.edu> <406D801A.5000408@yahoo.com> Message-ID: <406D97D5.1090002@hva.nl> Adam T. Gautier wrote: > If this idea catches on > maybe enough people could push the big distro's to standardize, who > knows... Don't you think that their reasons for not standardizing completely is what gives each distro it's uniqueness, it's branding? I mean, if Redhat would supply *exactly* the same functionality as Debian, what reason would there be for anybody to purchase an RHN entitlement for example? From adam_gautier at yahoo.com Fri Apr 2 17:08:56 2004 From: adam_gautier at yahoo.com (Adam T. Gautier) Date: Fri, 02 Apr 2004 12:08:56 -0500 Subject: Kickstart Configuration Managers In-Reply-To: <406D97D5.1090002@hva.nl> References: <406C4CB3.8050609@yahoo.com> <1080846922.8514.93.camel@biblos.oit.duke.edu> <406D801A.5000408@yahoo.com> <406D97D5.1090002@hva.nl> Message-ID: <406D9E28.5040909@yahoo.com> > Don't you think that their reasons for not standardizing completely > is what gives each distro it's uniqueness, it's branding? I mean, > if Redhat would supply *exactly* the same functionality as > Debian, what reason would there be for anybody to purchase > an RHN entitlement for example? > I think that difference is the spice of life, take for example Suse's superb Yast Configuration System, which IMHO is far superior to the RedHat Config utilities. The differences between distros is needed if not just for the basic contribution the differences make to the promotion of innovation. But, why do the major distros have minor differences in the installation on Apache? I do not think that the major distro's will converge into one, but I think that we can all agree that we don't want Linux do degenerate into the incompatable Unix*s of the past. Anyway, this is off topic for this list. Does anyone have any suggestiuons about what they would like to see in standard web-based ks config database? > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From Siva.Jayaraman at Glenayre.com Fri Apr 2 18:28:39 2004 From: Siva.Jayaraman at Glenayre.com (Jayaraman, Siva) Date: Fri, 2 Apr 2004 13:28:39 -0500 Subject: RHEL AS-2.1 U3 extremely slow - nfs issue? Message-ID: https://rhn.redhat.com/network/errata/details/index.pxt?eid=2017 if that doesnt work, the advisory is:- "RHSA-2004:069" the initrd image the the boot kernel comes with has barely any modules in it. also it is structured a little differently than normal. i pretty much rebuilt the initrd image by hand... Siva Jayaraman > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Joshua Jensen > Sent: Thursday, April 01, 2004 11:08 AM > To: Discussion list about Kickstart > Subject: Re: RHEL AS-2.1 U3 extremely slow - nfs issue? > > > Yup... as that bug that I opened said, NFS over UDP (which is what > anaconda uses for installs) was _badly_ broken. > > Where did you find the e.38 boot images? > > > On Thu, Apr 01, 2004 at 09:32:14AM -0500, Jayaraman, Siva wrote: > > > > that was it! > > I moved to a e.38 boot image and it worked perfectly as it should. > > > > Thanks! > > Siva Jayaraman > > siva.jayaraman at glenayre.com > > 770.283.2559 > > > > > > > -----Original Message----- > > > From: kickstart-list-bounces at redhat.com > > > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of > Joshua Jensen > > > Sent: Monday, March 29, 2004 1:14 PM > > > To: Discussion list about Kickstart > > > Subject: Re: RHEL AS-2.1 U3 extremely slow - nfs issue? > > > > > > > > > Could it be this? > > > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112766 > > > > > > Joshua > > > > > > > > > > > > On Mon, Mar 29, 2004 at 11:43:17AM -0500, Jayaraman, Siva wrote: > > > > > > > > hello all, > > > > > > > > We are in the process of moving to more recent > > > distributions of RH viz RHEL > > > > AS-2.1 Update3 & RH AS-3.0. > > > > > > > > We have kickstart infrastructure in place deploying RH7.2 > > > and RH AS-2.1 > > > > distributions. > > > > The kickstarts are done over NFS. > > > > > > > > The new distributions were added to the NFS server (which > > > is the same as the > > > > DHCP server). > > > > But the new kickstarts (AS-2.1-U3 & AS-3.0) take an > > > extremely long time now. > > > > > > > > The older kickstarts install around 800M of pkgs in about 3 > > > minutes, whereas > > > > now the newer kickstarts take around 50 minutes to install > > > 650M of packages. > > > > > > > > I checked the network connection and it is always 100Mbps > > > Full Duplex for > > > > both cases. > > > > The only difference I notice is that I get this message on > > > one of the > > > > virtual consoles - > > > > "nfs: mount version older than kernel" > > > > > > > > The older kickstarts mount the nfs directory as nfs v2 > > > whereas the newer > > > > kickstarts mount the directory as v3. > > > > Could this be the source of my problem? > > > > > > > > The NFS server is a RH7.2 box capable of doing both v2 & v3. > > > > > > > > If anyone has suggestions on how to debug/correct this > > > problem, I would > > > > highly appreciate it. > > > > > > > > thanks! > > > > Siva Jayaraman > > > > > > > > > > > > _______________________________________________ > > > > Kickstart-list mailing list > > > > Kickstart-list at redhat.com > > > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > > > -- > > > Joshua Jensen > > > Work: 919 392 1488 Mobile: 919 454 9679 Fax: 919 392 7377 > > > Pager: 866 264 2691 Epage: jjensen at epage.cisco.com > > > IBM Linux Architect - RHCE, RHCT, etc > > > "If God didn't want us to eat animals, why did he make them > > > out of meat?" > > > > > > > > > _______________________________________________ > > > 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 > > -- > Joshua Jensen > Work: 919 392 1488 Mobile: 919 454 9679 Fax: 919 392 7377 > Pager: 866 264 2691 Epage: jjensen at epage.cisco.com > IBM Linux Architect - RHCE, RHCT, etc > "If God didn't want us to eat animals, why did he make them > out of meat?" > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From seph at directionless.org Fri Apr 2 20:29:27 2004 From: seph at directionless.org (seph) Date: Fri, 02 Apr 2004 15:29:27 -0500 Subject: dhcp okay, but no http In-Reply-To: <001701c418cd$9b4b9280$a13c0a0a@slaptop> (Jeremy Silver's message of "Fri, 2 Apr 2004 08:14:37 -0800") References: <001701c418cd$9b4b9280$a13c0a0a@slaptop> Message-ID: > Do the precisions have multiple NICs? the precisions have only their onboard NICs. the dimensions have 2 nics though, so my cds already specify ksdevice=eth0. > What is the NIC hardware in the Precision? Does its module take extended > debug flags which can be passed on the kernel command line? If so, you > may be able to see something in the output of dmesg, after getting far > enough to use the shell on Alt+F2. lspci identifies it as: 03:0e.0 Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller (Copper) (rev 01) dmesg says: Intel(R) PRO/1000 Network Driver - version 5.2.20-k1 passing the kernel debug flags, and seeing if that shows anything is an excellent idea. I'll try that this weekend. seph From mark at mitre.org Tue Apr 6 15:21:39 2004 From: mark at mitre.org (Mark Heslep) Date: Tue, 06 Apr 2004 11:21:39 -0400 Subject: Limitations on %include Message-ID: <4072CB03.6030502@mitre.org> Im looking for some documentation on which kickstart commands / options can not be used with %include. For instance, it appears that the install method (-url http://... in my case) is required on the first kisckstart scan or at least well before the %pre scripts are executed that generate my files picked up by %include. I'm attempting to pick my network installation tree via a command line parameter used with a single common kickstart file, picking it up from /proc/cmdline in %pre and then customizing the install url via %include. Apparently the tree is already set at that point. I assume on consideration that must be so since the installer must pick up the stage2 images from the tree to continue? Im starting to wade through kickstart.py but I'd appreciated any comments on a) what commands effectively can't be used in %include and b) other clean ways to accomplish the tree customization. Regards, Mark From dallase at nmgi.com Fri Apr 9 20:31:18 2004 From: dallase at nmgi.com (Dallas L. Engelken) Date: Fri, 9 Apr 2004 15:31:18 -0500 Subject: Missing ext3 on a 7.3 rebuild with 2.4.20-28.7 Message-ID: I just rebuilt my redhat 7.3 CD's containing all the updates available, which includes the 2.4.20-28.7 kernels. After I did that my kickstarts began failing with a "you don't have enough disk space error". Digging into it deeper and running the install manually, I see that I no longer have the ext3 option on disk druid, and looking at /proc/filesystems from an ALT+F2 prompt, I see ext3 is no longer in there. If I rebuild the CDs with 2.4.20-24 it works fine. Any ideas where ext3 would have went or how I get it back. Is ext3 support missing in 2.4.20-28.7BOOT ?? Thanks, Dallas From forrestx.taylor at intel.com Fri Apr 9 20:49:14 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Fri, 09 Apr 2004 13:49:14 -0700 Subject: Missing ext3 on a 7.3 rebuild with 2.4.20-28.7 In-Reply-To: References: Message-ID: <1081543754.13875.6.camel@bad.jf.intel.com> On Fri, 2004-04-09 at 13:31, Dallas L. Engelken wrote: > I just rebuilt my redhat 7.3 CD's containing all the updates available, > which includes the 2.4.20-28.7 kernels. After I did that my kickstarts > began failing with a "you don't have enough disk space error". Digging > into it deeper and running the install manually, I see that I no longer > have the ext3 option on disk druid, and looking at /proc/filesystems > from an ALT+F2 prompt, I see ext3 is no longer in there. > > If I rebuild the CDs with 2.4.20-24 it works fine. Any ideas where ext3 > would have went or how I get it back. Is ext3 support missing in > 2.4.20-28.7BOOT ?? The -28 kernel was too large to fit in the images. Either stay with the -24 kernel and install -28 in %post, or remove some modules in the initrd images (like PCMCIA or SCSI) and make the initrd images larger. Forrest From mark at mitre.org Tue Apr 13 03:41:10 2004 From: mark at mitre.org (Mark Heslep) Date: Mon, 12 Apr 2004 23:41:10 -0400 Subject: Fedora Core 2 test2 and kickstart In-Reply-To: <406B17CC.1010400@web.turner.com> References: <406B17CC.1010400@web.turner.com> Message-ID: <407B6156.60901@mitre.org> Brian Akins wrote: > I have the following in my pxe config (watch for wrap): > > LABEL external > KERNEL vmlinuz > APPEND ksdevice=eth0 > ks=http://10.165.5.11/kickstart/RHAS2.1/config/ks.cfg.external > initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 console=tty0 > console=ttyS0,9600n81 > > LABEL fedora > KERNEL vmlinuz-fc2 > APPEND ksdevice=eth0 > ks=http://10.165.5.11/kickstart/fc2test2/config/ks.cfg.external > initrd=initrd.img-fc2 lang= devfs=nomount ramdisk_size=7168 > console=tty0 console=ttyS0,9600n81 iommu=merge > > > The "external" label works fine for RHAS 2.1. Looking at my access > logs, it doesn't seem that the fedora ever tries to fetch the config > file, it just dumps me to a normal install which I can perform over > http. Any pointers? > From syslinux.doc which mostly applies to PXE " Notes: Labels are mangled as if they were filenames, and must be unique after mangling. For example, two labels "v2.1.30" and "v2.1.31" will not be distinguishable under SYSLINUX, since both mangle to the same DOS filename." (1) Not sure if the -fc2 is picked up in your second image name. (2) Try a 'wget' from the machine in a post install shell. I think Anaconda gives you wget in the 'rescue' mode (?), ie, just append 'rescue' to the PXE boot prompt: fedora rescue. From mark at mitre.org Tue Apr 13 04:16:42 2004 From: mark at mitre.org (Mark Heslep) Date: Tue, 13 Apr 2004 00:16:42 -0400 Subject: web enabling kickstart Message-ID: <407B69AA.9000208@mitre.org> I've noted several nice efforts on this list to produce ks files from dynamically generated web forms such as Brian Long's Kickstart tools (http://kickstart-tools.sf.net/ ) and NC State's web-kickstart (http://linux.ncsu.edu/projects/web-kickstart/) to name just two. However, rolling your own ks web form effectively creates your own personal fork of ..config-kickstart that must then be maintained and so loses the leverage of the mainstream RH/Fedora tool. The recent addition of SElinux <--disable> <--enforce> ... switch and the included hardward lists come to mind as details I'd rather not be updating on web scripts. So Im interested in ways to directly leverage this existing tool as much as possible for creating remote ks config files for multiple hosts/ users. We've looked at the Java X Server weirdx for instance as a way of giving anyone (including Win32 people) w/ a browser the ability to gen a ks file but so far weirdx doesnt work to well with the python based gui coming from ..config-kickstart ( weird has poor/no support for X extensions like Render). So any other ideas? Whats the level of effort to mod the python config tool to throw out html ala SWAT for Samba? -Mark From jjensen at cisco.com Tue Apr 13 21:51:59 2004 From: jjensen at cisco.com (Joshua Jensen) Date: Tue, 13 Apr 2004 17:51:59 -0400 Subject: AMD64 kickstart arch pref problems Message-ID: <20040413215159.GI22474@cisco.com> So I've built my own comps.xml file for my AMD64 distro... and I can kickstart with everything working. However, anaconda isn't preferring the x86_64 packages over the i686 and i386 packages. Has anyone run into this when they had a custom comps.xml file? Everything installs, the arch preferences just aren't working. -- Joshua Jensen Work: 919 392 1488 Mobile: 919 454 9679 Fax: 919 392 7377 Pager: 866 264 2691 Epage: jjensen at epage.cisco.com IBM Linux Architect - RHCE, RHCT, etc "If God didn't want us to eat animals, why did he make them out of meat?" From sergei at gwu.edu Wed Apr 14 02:58:08 2004 From: sergei at gwu.edu (Sergei Mikhailov) Date: Tue, 13 Apr 2004 22:58:08 -0400 Subject: Problem with 'comps' package Message-ID: <21a491fc7f.1fc7f21a49@gwu.edu> Hi, I am trying to do a kickstart install over http. In the %packages section, I use a list of all packages on the system, instead of using package groups (starting with @). The list was generated by running `rpm -qa` and then the version and release numbers were stripped off. One of the packages in the list is "comps" However, the installer complains that it cannot find "comps" once kickstart is running. Any ideas on how to resolve this would be appreciated. In the repository that is available through http, I have Febora/base/comps.rpm. I also compied over comps.rpm into the RPMS directory, so in there I have: comps-1-0.20031103.i386.rpm comps-extras-9.0.3-2.noarch.rpm comps.rpm One more though. Looking at the apache logs, here are the request that the installer makes. /kickstart/Fedora/base/updates.img HTTP/1.0" 404 /kickstart/disc1/Fedora/base/updates.img HTTP/1.0" 404 /kickstart/Fedora/base/product.img HTTP/1.0" 404 /kickstart/disc1/Fedora/base/product.img HTTP/1.0" 404 /kickstart/Fedora/base/netstg2.img HTTP/1.0" 200 /kickstart/Fedora/base/hdlist HTTP/1.0" 200 /kickstart/Fedora/base/comps.xml HTTP/1.0" 200 Looks like it first requested things that were not in the repository, but it continue nevertheless. Also, it never really probed for all the available rpms, so it must have made the decision based on comps.xml and the comps package is not there. Can comps.xml be edited somehow. Thanks Sergei From pantz at lqt.ca Wed Apr 14 14:10:05 2004 From: pantz at lqt.ca (Paul Pianta) Date: Wed, 14 Apr 2004 10:10:05 -0400 Subject: Problem with 'comps' package In-Reply-To: <21a491fc7f.1fc7f21a49@gwu.edu> References: <21a491fc7f.1fc7f21a49@gwu.edu> Message-ID: <407D463D.1080402@lqt.ca> Sergei Mikhailov wrote: >Hi, >I am trying to do a kickstart install over http. In >the %packages section, I use a list of all packages >on the system, instead of using package groups >(starting with @). The list was generated by running >`rpm -qa` and then the version and release numbers >were stripped off. One of the packages in the list >is "comps" However, the installer complains that it >cannot find "comps" once kickstart is running. Any >ideas on how to resolve this would be appreciated. > >In the repository that is available through http, I >have Febora/base/comps.rpm. I also compied over >comps.rpm into the RPMS directory, so in there I have: >comps-1-0.20031103.i386.rpm >comps-extras-9.0.3-2.noarch.rpm >comps.rpm > > >One more though. Looking at the apache logs, here >are the request that the installer makes. >/kickstart/Fedora/base/updates.img HTTP/1.0" 404 >/kickstart/disc1/Fedora/base/updates.img HTTP/1.0" 404 >/kickstart/Fedora/base/product.img HTTP/1.0" 404 >/kickstart/disc1/Fedora/base/product.img HTTP/1.0" 404 >/kickstart/Fedora/base/netstg2.img HTTP/1.0" 200 >/kickstart/Fedora/base/hdlist HTTP/1.0" 200 >/kickstart/Fedora/base/comps.xml HTTP/1.0" 200 > >Looks like it first requested things that were not >in the repository, but it continue nevertheless. >Also, it never really probed for all the available >rpms, so it must have made the decision based on >comps.xml and the comps package is not there. Can >comps.xml be edited somehow. > > > hey sergei check out this site for editing your comps.xml file ... http://fedora.redhat.com/projects/anaconda-installer/comps.html If you edit the comps.xml file to contain only your packages (ie. your rpm -qa output) then you will not need to list *all* of your packages in the kickstart file. You can just list the groups that you have defined in your custom comps.xml. Another advantage is you won't have to worry about the comps rpm. Don't include it in your comps.xml and as long as you leave the comps.rpm where it is on the cd (not in the RPM directory) - it will be installed automagically (ie. I have no idea how comps.rpm works but it always gets installed for me!) hth pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From chris at geddings.org Wed Apr 14 17:43:00 2004 From: chris at geddings.org (Chris Geddings) Date: Wed, 14 Apr 2004 13:43:00 -0400 Subject: Kickstart Configuration Managers In-Reply-To: <406D9E28.5040909@yahoo.com> References: <406C4CB3.8050609@yahoo.com> <1080846922.8514.93.camel@biblos.oit.duke.edu> <406D801A.5000408@yahoo.com> <406D97D5.1090002@hva.nl> <406D9E28.5040909@yahoo.com> Message-ID: <1081964580.23414.35.camel@biblos.oit.duke.edu> On Fri, 2004-04-02 at 12:08, Adam T. Gautier wrote: > > Anyway, this is off topic for this list. Does anyone have any > suggestiuons about what they would like to see in standard web-based ks > config database? > So, I have some ideas, though I'm still trying to work some of them into a verbal representation that makes good sense. What's in my head isn't very understandable at the moment. Essentially, the thing should start as general as possible to be as flexible as possible, and allow for building up the bits that are discovered to need shoring up or building up good ideas as time goes on. It is very important that the tool not get into a lot of macro language garbage. There is enough of that out there...what I want to see is something that makes my managing kickstart files easier, I don't want to see kickstart re-invented, or a super language stuck on top of the existing language. (Very loose use of the term language here.) Keeping the tool from imposing itself on top of kickstart will help prevent a catch up game...ideally, the tool shouldn't even care about versions of kickstart. Obviously, if at some point the tool could start doing validation of individual configurations, that might change, but that isn't even a near term goal of what I would like to see. Really, what I want to do initially is chunk up the kickstart configs into manageable pieces. I have some code I was given that probably does what I want to some degree, though I've not had time to poke at it fully. I know the concept is there though. I have two major feature descriptions: * What I want to do is maintain "stub" files through a web interface. I want those stub files to be version controlled, so that I can see what the changes to individual stubs were and when, and I can roll back to previous versions easily. * Additionally, I want to be able to group these stub files into logical groups. I want similar kinds of version controls over these groups of stub files. I want to be able to access these stub files either directly/"dynamically", or "compile" the groups of stub files out to a directory that can be accessed as static files. That's pretty much it in the beginning. Well, I want the web interface to be reasonably secure, and not horribly ugly or awkward. Notice though, that if implemented properly, the above description could apply to several configuration type challenges. Indeed, the code I've not looked at closely is currently being used to maintain iptables. Anyway, wanted to get this response out, as I've been meaning to send it for a bit of time now. --Chris From Neil at R-T-F-M.Org.Uk Sat Apr 17 22:51:14 2004 From: Neil at R-T-F-M.Org.Uk (Neil Stone) Date: Sat, 17 Apr 2004 23:51:14 +0100 Subject: NFS based KS file.... Message-ID: <4081B4E2.50807@R-T-F-M.Org.Uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I intend to use kickstart as a method to automate the installation of systems. However these systems do not have a floppy drive.. they DO have a CD drive, but I would much prefer to be able to create a kickstart file which could reside on a server (or perhaps a CDROM) and install over the LAN. Does anyone have knowledge on how to do this ?? Also is LVM supported in the KS installs yet ? Thanks Neil Stone ~ Flash on telnet://TR3.Org:3000 and irc://irc.r-t-f-m.org.uk/DCLUG ****************************************************************************** ~ .~. SELECT * FROM windows.users WHERE (clue != NULL AND clue > 0); ~ /V\ ~ // \\ 0 row(s) returned. ~ /( )\ ~ ^`~'^ "Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." - Linus Torvalds -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAgbThz3Av8JKgzxQRAnzPAJ9RuE6lKdKa2AlBLtuk6py8EJMLYgCgrZXW KcSxZ7tceH0fLlPWSnad5/k= =ETu7 -----END PGP SIGNATURE----- From phr at doc.ic.ac.uk Sat Apr 17 23:46:56 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Sun, 18 Apr 2004 00:46:56 +0100 (BST) Subject: NFS based KS file.... In-Reply-To: <4081B4E2.50807@R-T-F-M.Org.Uk> References: <4081B4E2.50807@R-T-F-M.Org.Uk> Message-ID: On Sat, 17 Apr 2004, Neil Stone wrote: >I intend to use kickstart as a method to automate the installation of >systems. However these systems do not have a floppy drive.. they DO have >a CD drive, but I would much prefer to be able to create a kickstart >file which could reside on a server (or perhaps a CDROM) and install >over the LAN. > >Does anyone have knowledge on how to do this ?? > >Also is LVM supported in the KS installs yet ? Neil at R-T-F-M.org.uk, RTFM! Yes, the kickstart file can live on an NFS server, and kickstart can be initated from a bootable CD. LVM is supported in recent versions of anaconda. For the latest kickstart docs, read here: http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/pt-install-info.html Cheers, Phil From tobias at quova.com Sun Apr 18 02:04:04 2004 From: tobias at quova.com (Tobias Speckbacher) Date: Sat, 17 Apr 2004 19:04:04 -0700 Subject: NFS based KS file.... Message-ID: Boot from cd and type linux ks=nfs:nfs-server:/path/to/ks/cfg -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Philip Rowlands Sent: Saturday, April 17, 2004 4:47 PM To: Discussion list about Kickstart Subject: Re: NFS based KS file.... On Sat, 17 Apr 2004, Neil Stone wrote: >I intend to use kickstart as a method to automate the installation of >systems. However these systems do not have a floppy drive.. they DO have >a CD drive, but I would much prefer to be able to create a kickstart >file which could reside on a server (or perhaps a CDROM) and install >over the LAN. > >Does anyone have knowledge on how to do this ?? > >Also is LVM supported in the KS installs yet ? Neil at R-T-F-M.org.uk, RTFM! Yes, the kickstart file can live on an NFS server, and kickstart can be initated from a bootable CD. LVM is supported in recent versions of anaconda. For the latest kickstart docs, read here: http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/pt-install-info.html Cheers, Phil _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From liste at lx-system.de Mon Apr 19 12:58:41 2004 From: liste at lx-system.de (Marco Welter) Date: Mon, 19 Apr 2004 14:58:41 +0200 Subject: Install of rpm packages in %post - script Message-ID: <200404191458.41420.liste@lx-system.de> Hello, i have a rpm package, and i want to install it at the %post script ? The kickstart install from a dvd, and in the root of the dvd is the rpm file. In which directory is the dvd mountet ? Thank you Marco Welter -- Lx-System GbR Tel.: 0700 LXSYSTEM info at lx-system.de Hauptgesch?ftsstelle: Ensinger Strasse 19 - 89073 Ulm 0731 / 602 81 19 Zweigniederlassung: Zur alten Zollbruecke 30 - 87527 Sonthofen Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 E-Mail: mawe at lx-system.de From Neil at R-T-F-M.Org.Uk Mon Apr 19 13:10:02 2004 From: Neil at R-T-F-M.Org.Uk (Neil Stone) Date: Mon, 19 Apr 2004 14:10:02 +0100 Subject: Install of rpm packages in %post - script In-Reply-To: <200404191458.41420.liste@lx-system.de> References: <200404191458.41420.liste@lx-system.de> Message-ID: <4083CFAA.9080901@R-T-F-M.Org.Uk> Marco Welter wrote: > Hello, > > i have a rpm package, and i want to install it at the %post script ? > The kickstart install from a dvd, and in the root of the dvd is the rpm file. > > In which directory is the dvd mountet ? > > Thank you > > Marco Welter /mnt/cdrom i would guess... From pantz at lqt.ca Mon Apr 19 13:23:06 2004 From: pantz at lqt.ca (Paul Pianta) Date: Mon, 19 Apr 2004 09:23:06 -0400 Subject: Install of rpm packages in %post - script In-Reply-To: <200404191458.41420.liste@lx-system.de> References: <200404191458.41420.liste@lx-system.de> Message-ID: <4083D2BA.10009@lqt.ca> Marco Welter wrote: >Hello, > >i have a rpm package, and i want to install it at the %post script ? >The kickstart install from a dvd, and in the root of the dvd is the rpm file. > >In which directory is the dvd mountet ? > > hey marco this is what i do when i want to copy just a single file over from my installation cd to the newly installed filesystem ... %post --nochroot # cdrom is not mounted during post so i mount it with the --nochroot option mkdir -p /mnt/source mount /tmp/cdrom /mnt/source # copy updates.conf from the cd to /tmp on the installed system cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp %post # creation of admin account - the rest of the kickstart can be performed in normal %post mode /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin ... hth pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From liste at lx-system.de Mon Apr 19 14:23:23 2004 From: liste at lx-system.de (Marco Welter) Date: Mon, 19 Apr 2004 16:23:23 +0200 Subject: Install of rpm packages in %post - script In-Reply-To: <4083D2BA.10009@lqt.ca> References: <200404191458.41420.liste@lx-system.de> <4083D2BA.10009@lqt.ca> Message-ID: <200404191623.23418.liste@lx-system.de> Hi, > %post --nochroot > # cdrom is not mounted during post so i mount it with the --nochroot option > mkdir -p /mnt/source > mount /tmp/cdrom /mnt/source > > # copy updates.conf from the cd to /tmp on the installed system > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp thank you, no works ;-) > > %post > # creation of admin account - the rest of the kickstart can be performed > in normal %post mode > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin but not 100 %, when i have a "normal" %post after %post --nochroot whith rpm -ivh /root/xyz.rpm it do not work Bye Marco > ... > > hth > > pantz -- Lx-System GbR Tel.: 0700 LXSYSTEM info at lx-system.de Hauptgesch?ftsstelle: Ensinger Strasse 19 - 89073 Ulm 0731 / 602 81 19 Zweigniederlassung: Zur alten Zollbruecke 30 - 87527 Sonthofen Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 E-Mail: mawe at lx-system.de From liste at lx-system.de Mon Apr 19 14:29:16 2004 From: liste at lx-system.de (Marco Welter) Date: Mon, 19 Apr 2004 16:29:16 +0200 Subject: Install of rpm packages in %post - script In-Reply-To: <200404191623.23418.liste@lx-system.de> References: <200404191458.41420.liste@lx-system.de> <4083D2BA.10009@lqt.ca> <200404191623.23418.liste@lx-system.de> Message-ID: <200404191629.16872.liste@lx-system.de> Hi, Am Montag, 19. April 2004 16:23 schrieb Marco Welter: > Hi, > > > %post --nochroot > > # cdrom is not mounted during post so i mount it with the --nochroot > > option mkdir -p /mnt/source > > mount /tmp/cdrom /mnt/source > > > > # copy updates.conf from the cd to /tmp on the installed system > > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp > > thank you, no works ;-) not "no works" --->> it works !!! Marco -- Lx-System GbR Tel.: 0700 LXSYSTEM info at lx-system.de Hauptgesch?ftsstelle: Ensinger Strasse 19 - 89073 Ulm 0731 / 602 81 19 Zweigniederlassung: Zur alten Zollbruecke 30 - 87527 Sonthofen Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 E-Mail: mawe at lx-system.de From dtegelaar at egenera.com Mon Apr 19 14:34:57 2004 From: dtegelaar at egenera.com (David Tegelaar) Date: Mon, 19 Apr 2004 10:34:57 -0400 Subject: Install of rpm packages in %post - script In-Reply-To: <200404191623.23418.liste@lx-system.de> Message-ID: Once you set --nochroot, you have to handle subsequent lines accordingly. For example with a useradd line you would chroot it to /mnt/sysimage: chroot /mnt/sysimage /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin (you may need to specifiy the full path to the chroot binary like /mnt/sysimage/sbin/chroot). -dave -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Marco Welter Sent: Monday, April 19, 2004 10:23 AM To: Discussion list about Kickstart Subject: Re: Install of rpm packages in %post - script Hi, > %post --nochroot > # cdrom is not mounted during post so i mount it with the --nochroot option > mkdir -p /mnt/source > mount /tmp/cdrom /mnt/source > > # copy updates.conf from the cd to /tmp on the installed system > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp thank you, no works ;-) > > %post > # creation of admin account - the rest of the kickstart can be performed > in normal %post mode > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin but not 100 %, when i have a "normal" %post after %post --nochroot whith rpm -ivh /root/xyz.rpm it do not work Bye Marco > ... > > hth > > pantz -- Lx-System GbR Tel.: 0700 LXSYSTEM info at lx-system.de Hauptgesch?ftsstelle: Ensinger Strasse 19 - 89073 Ulm 0731 / 602 81 19 Zweigniederlassung: Zur alten Zollbruecke 30 - 87527 Sonthofen Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 E-Mail: mawe at lx-system.de _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From MSiddall at imaginativeit.co.uk Mon Apr 19 15:08:16 2004 From: MSiddall at imaginativeit.co.uk (Martin Siddall) Date: Mon, 19 Apr 2004 16:08:16 +0100 Subject: Install of rpm packages in %post - script In-Reply-To: <200404191623.23418.liste@lx-system.de> Message-ID: <000701c42620$24a971f0$7000a8c0@internal.net> I've been struggling with this for days and I still have problems with it. Running Fedora Core 1. When attempting to do mkdir -p /mnt/source the script creates a /mnt/source? Dir (mnt/source + questionmark). I thought well ok and changed the copy command to cp /mnt/source?/custom.tar /mnt/sysimage/root Still no luck. Comes back with error message that is intermingled with the kickstart dialog and I can't work out what's happening and why. [Note the installation has been stripped down to one CD - could I have missed and essential RPM ??] Anyone have an idea Many thanks Martin -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Marco Welter Sent: 19 April 2004 15:23 To: Discussion list about Kickstart Subject: Re: Install of rpm packages in %post - script Hi, > %post --nochroot > # cdrom is not mounted during post so i mount it with the --nochroot option > mkdir -p /mnt/source > mount /tmp/cdrom /mnt/source > > # copy updates.conf from the cd to /tmp on the installed system > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp thank you, no works ;-) > > %post > # creation of admin account - the rest of the kickstart can be performed > in normal %post mode > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin but not 100 %, when i have a "normal" %post after %post --nochroot whith rpm -ivh /root/xyz.rpm it do not work Bye Marco > ... > > hth > > pantz -- Lx-System GbR Tel.: 0700 LXSYSTEM info at lx-system.de Hauptgesch?ftsstelle: Ensinger Strasse 19 - 89073 Ulm 0731 / 602 81 19 Zweigniederlassung: Zur alten Zollbruecke 30 - 87527 Sonthofen Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 E-Mail: mawe at lx-system.de _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From dtegelaar at egenera.com Mon Apr 19 17:22:23 2004 From: dtegelaar at egenera.com (David Tegelaar) Date: Mon, 19 Apr 2004 13:22:23 -0400 Subject: Install of rpm packages in %post - script In-Reply-To: <000701c42620$24a971f0$7000a8c0@internal.net> Message-ID: That's pretty wierd. Try leaving out the "mkdir -p /mnt/source" line (or telling it to mkdir a different directory name). I think the /mnt/source directory already exists anyway. Maybe the ? char is an extra char at the end of the text or is somehow part of a question that gets asked if the directory already exists when you try to mkdir it. -dave -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall Sent: Monday, April 19, 2004 11:08 AM To: 'Discussion list about Kickstart' Subject: RE: Install of rpm packages in %post - script I've been struggling with this for days and I still have problems with it. Running Fedora Core 1. When attempting to do mkdir -p /mnt/source the script creates a /mnt/source? Dir (mnt/source + questionmark). I thought well ok and changed the copy command to cp /mnt/source?/custom.tar /mnt/sysimage/root Still no luck. Comes back with error message that is intermingled with the kickstart dialog and I can't work out what's happening and why. [Note the installation has been stripped down to one CD - could I have missed and essential RPM ??] Anyone have an idea Many thanks Martin -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Marco Welter Sent: 19 April 2004 15:23 To: Discussion list about Kickstart Subject: Re: Install of rpm packages in %post - script Hi, > %post --nochroot > # cdrom is not mounted during post so i mount it with the --nochroot option > mkdir -p /mnt/source > mount /tmp/cdrom /mnt/source > > # copy updates.conf from the cd to /tmp on the installed system > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp thank you, no works ;-) > > %post > # creation of admin account - the rest of the kickstart can be performed > in normal %post mode > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin but not 100 %, when i have a "normal" %post after %post --nochroot whith rpm -ivh /root/xyz.rpm it do not work Bye Marco > ... > > hth > > pantz -- Lx-System GbR Tel.: 0700 LXSYSTEM info at lx-system.de Hauptgesch?ftsstelle: Ensinger Strasse 19 - 89073 Ulm 0731 / 602 81 19 Zweigniederlassung: Zur alten Zollbruecke 30 - 87527 Sonthofen Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 E-Mail: mawe at lx-system.de _______________________________________________ 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 forrestx.taylor at intel.com Mon Apr 19 17:39:19 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Mon, 19 Apr 2004 10:39:19 -0700 Subject: Install of rpm packages in %post - script In-Reply-To: <000701c42620$24a971f0$7000a8c0@internal.net> References: <000701c42620$24a971f0$7000a8c0@internal.net> Message-ID: <1082396359.7721.7.camel@bad.jf.intel.com> On Mon, 2004-04-19 at 08:08, Martin Siddall wrote: > I've been struggling with this for days and I still have problems with > it. Running Fedora Core 1. > > > When attempting to do mkdir -p /mnt/source the script creates a > /mnt/source? Dir (mnt/source + questionmark). I thought well ok and > changed the copy command to cp /mnt/source?/custom.tar > /mnt/sysimage/root This looks like it may have the extra Ctrl+M characters from Windows. Did you edit this file on Windows, or copy it to/from a Windows machine? Try running dos2unix on the kickstart file from within Linux. Forrest From msiddall at imaginativeit.co.uk Mon Apr 19 17:42:06 2004 From: msiddall at imaginativeit.co.uk (Martin Siddall) Date: Mon, 19 Apr 2004 18:42:06 +0100 Subject: Install of rpm packages in %post - script References: Message-ID: <002101c42635$adf31e10$fa01a8c0@internal.net> Cheers , but i've been there allready. I echoed ls /mnt and various other directories in the %post part of the config and quite correctly as Marco has said anaconda umounts the cdrom and for some reason the /mnt/source disappears. I have also tried creating other directories with the same problem so I thorgh screw mkdir and tried to mount the cdrom on an existing directory..... still no joy. The main problem is the anaconda program when it reports an error ... its incomplete and intermingled with its own debugging lines so i can't see what it's moaning about. The only thing I can think of is that the ks.cfg file has some wierd character in it or the shell which anaconda uses is broken. I have include my ks.cfg for your perusal. Any other suggestions would be greatly appreciated. Martin ks.cfg zerombr yes clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --size=1024 --grow --ondisk=hda part swap --size=128 --grow --maxsize=256 --ondisk=hda install cdrom lang en_US.UTF-8 langsupport --default en_GB.UTF-8 en_GB.UTF-8 keyboard uk mouse genericwheelps/2 --device psaux rootpw --iscrypted $1$PRwZ191B$qq1HZQJpK5gfpPhJw/967/ firewall --disabled authconfig --enableshadow --enablemd5 timezone Europe/London bootloader --location=mbr %packages @ network-server @ web-server @ dialup @ sql-server @ system-tools @ british-support @ ftp-server @ development-tools kernel dhcp net-snmp-utils shapecfg tftp-server mysql-server grub mrtg php-mysql mod_auth_mysql freeradius php-odbc %post --nochroot mkdir -p /mnt/source mount /tmp/cdrom /mnt/source cp -f /mnt/source/custom.tar /mnt/sysimage/root ----- Original Message ----- From: "David Tegelaar" To: ; "Discussion list about Kickstart" Sent: Monday, April 19, 2004 6:22 PM Subject: RE: Install of rpm packages in %post - script > That's pretty wierd. Try leaving out the > "mkdir -p /mnt/source" line (or telling > it to mkdir a different directory name). > I think the /mnt/source directory already > exists anyway. Maybe the ? char > is an extra char at the end of the text or > is somehow part of a question that gets > asked if the directory already exists > when you try to mkdir it. > > -dave > > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall > Sent: Monday, April 19, 2004 11:08 AM > To: 'Discussion list about Kickstart' > Subject: RE: Install of rpm packages in %post - script > > > I've been struggling with this for days and I still have problems with > it. Running Fedora Core 1. > > > When attempting to do mkdir -p /mnt/source the script creates a > /mnt/source? Dir (mnt/source + questionmark). I thought well ok and > changed the copy command to cp /mnt/source?/custom.tar > /mnt/sysimage/root > > Still no luck. Comes back with error message that is intermingled with > the kickstart dialog and I can't work out what's happening and why. > > [Note the installation has been stripped down to one CD - could I have > missed and essential RPM ??] > > Anyone have an idea > > > Many thanks > > Martin > > > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Marco Welter > Sent: 19 April 2004 15:23 > To: Discussion list about Kickstart > Subject: Re: Install of rpm packages in %post - script > > Hi, > > > %post --nochroot > > # cdrom is not mounted during post so i mount it with the --nochroot > option > > mkdir -p /mnt/source > > mount /tmp/cdrom /mnt/source > > > > # copy updates.conf from the cd to /tmp on the installed system > > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp > thank you, no works ;-) > > > > %post > > # creation of admin account - the rest of the kickstart can be > performed > > in normal %post mode > > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin > but not 100 %, when i have a "normal" %post after %post --nochroot whith > rpm > -ivh /root/xyz.rpm it do not work > > Bye > > Marco > > ... > > > > hth > > > > pantz > > -- > Lx-System GbR > > Tel.: 0700 LXSYSTEM > info at lx-system.de > > Hauptgesch?ftsstelle: > Ensinger Strasse 19 - 89073 Ulm > 0731 / 602 81 19 > > Zweigniederlassung: > Zur alten Zollbruecke 30 - 87527 Sonthofen > Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 > E-Mail: mawe at lx-system.de > > > _______________________________________________ > 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 dtegelaar at egenera.com Mon Apr 19 18:23:47 2004 From: dtegelaar at egenera.com (David Tegelaar) Date: Mon, 19 Apr 2004 14:23:47 -0400 Subject: Install of rpm packages in %post - script In-Reply-To: <002101c42635$adf31e10$fa01a8c0@internal.net> Message-ID: Yes the suggestion in another email that a Windows char may be in the ks file is a good one. Also I think you may need the "-t" option to mount: mount -t iso9660 /tmp/cdrom /mnt/source You could try writing the output to a log so if you get a failure maybe you can look at the log: mount -t iso9660 /tmp/cdrom /mnt/source >>/tmp/mount.log 2>&1 -dave -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall Sent: Monday, April 19, 2004 1:42 PM To: Discussion list about Kickstart Subject: Re: Install of rpm packages in %post - script Cheers , but i've been there allready. I echoed ls /mnt and various other directories in the %post part of the config and quite correctly as Marco has said anaconda umounts the cdrom and for some reason the /mnt/source disappears. I have also tried creating other directories with the same problem so I thorgh screw mkdir and tried to mount the cdrom on an existing directory..... still no joy. The main problem is the anaconda program when it reports an error ... its incomplete and intermingled with its own debugging lines so i can't see what it's moaning about. The only thing I can think of is that the ks.cfg file has some wierd character in it or the shell which anaconda uses is broken. I have include my ks.cfg for your perusal. Any other suggestions would be greatly appreciated. Martin ks.cfg zerombr yes clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --size=1024 --grow --ondisk=hda part swap --size=128 --grow --maxsize=256 --ondisk=hda install cdrom lang en_US.UTF-8 langsupport --default en_GB.UTF-8 en_GB.UTF-8 keyboard uk mouse genericwheelps/2 --device psaux rootpw --iscrypted $1$PRwZ191B$qq1HZQJpK5gfpPhJw/967/ firewall --disabled authconfig --enableshadow --enablemd5 timezone Europe/London bootloader --location=mbr %packages @ network-server @ web-server @ dialup @ sql-server @ system-tools @ british-support @ ftp-server @ development-tools kernel dhcp net-snmp-utils shapecfg tftp-server mysql-server grub mrtg php-mysql mod_auth_mysql freeradius php-odbc %post --nochroot mkdir -p /mnt/source mount /tmp/cdrom /mnt/source cp -f /mnt/source/custom.tar /mnt/sysimage/root ----- Original Message ----- From: "David Tegelaar" To: ; "Discussion list about Kickstart" Sent: Monday, April 19, 2004 6:22 PM Subject: RE: Install of rpm packages in %post - script > That's pretty wierd. Try leaving out the > "mkdir -p /mnt/source" line (or telling > it to mkdir a different directory name). > I think the /mnt/source directory already > exists anyway. Maybe the ? char > is an extra char at the end of the text or > is somehow part of a question that gets > asked if the directory already exists > when you try to mkdir it. > > -dave > > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall > Sent: Monday, April 19, 2004 11:08 AM > To: 'Discussion list about Kickstart' > Subject: RE: Install of rpm packages in %post - script > > > I've been struggling with this for days and I still have problems with > it. Running Fedora Core 1. > > > When attempting to do mkdir -p /mnt/source the script creates a > /mnt/source? Dir (mnt/source + questionmark). I thought well ok and > changed the copy command to cp /mnt/source?/custom.tar > /mnt/sysimage/root > > Still no luck. Comes back with error message that is intermingled with > the kickstart dialog and I can't work out what's happening and why. > > [Note the installation has been stripped down to one CD - could I have > missed and essential RPM ??] > > Anyone have an idea > > > Many thanks > > Martin > > > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Marco Welter > Sent: 19 April 2004 15:23 > To: Discussion list about Kickstart > Subject: Re: Install of rpm packages in %post - script > > Hi, > > > %post --nochroot > > # cdrom is not mounted during post so i mount it with the --nochroot > option > > mkdir -p /mnt/source > > mount /tmp/cdrom /mnt/source > > > > # copy updates.conf from the cd to /tmp on the installed system > > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp > thank you, no works ;-) > > > > %post > > # creation of admin account - the rest of the kickstart can be > performed > > in normal %post mode > > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin > but not 100 %, when i have a "normal" %post after %post --nochroot whith > rpm > -ivh /root/xyz.rpm it do not work > > Bye > > Marco > > ... > > > > hth > > > > pantz > > -- > Lx-System GbR > > Tel.: 0700 LXSYSTEM > info at lx-system.de > > Hauptgesch?ftsstelle: > Ensinger Strasse 19 - 89073 Ulm > 0731 / 602 81 19 > > Zweigniederlassung: > Zur alten Zollbruecke 30 - 87527 Sonthofen > Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 > E-Mail: mawe at lx-system.de > > > _______________________________________________ > 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 > _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From ebrown at lanl.gov Mon Apr 19 18:40:22 2004 From: ebrown at lanl.gov (Ed Brown) Date: Mon, 19 Apr 2004 12:40:22 -0600 Subject: Install of rpm packages in %post - script In-Reply-To: References: Message-ID: <1082400021.11162.146.camel@edbrown.lanl.gov> Try opening a shell in %post and running the commands manually to see what's happening. %post chvt 3 exec < /dev/tty3 > /dev/tty3 sh -Ed On Mon, 2004-04-19 at 12:23, David Tegelaar wrote: > Yes the suggestion in another email > that a Windows char may be in the ks > file is a good one. Also I think you > may need the "-t" option to mount: > > mount -t iso9660 /tmp/cdrom /mnt/source > > You could try writing the output to a log > so if you get a failure maybe you can look > at the log: > > mount -t iso9660 /tmp/cdrom /mnt/source >>/tmp/mount.log 2>&1 > > -dave > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall > Sent: Monday, April 19, 2004 1:42 PM > To: Discussion list about Kickstart > Subject: Re: Install of rpm packages in %post - script > > > Cheers , but i've been there allready. I echoed ls /mnt and various other > directories in the %post part of the config and quite correctly as Marco has > said anaconda umounts the cdrom and for some reason the /mnt/source > disappears. I have also tried creating other directories with the same > problem so I thorgh screw mkdir and tried to mount the cdrom on an existing > directory..... still no joy. > > The main problem is the anaconda program when it reports an error ... its > incomplete and intermingled with its own debugging lines so i can't see what > it's moaning about. > > The only thing I can think of is that the ks.cfg file has some wierd > character in it or the shell which anaconda uses is broken. > > I have include my ks.cfg for your perusal. Any other suggestions would be > greatly appreciated. > > > Martin > > ks.cfg > > zerombr yes > clearpart --all --drives=hda > part /boot --fstype ext3 --size=100 --ondisk=hda > part / --fstype ext3 --size=1024 --grow --ondisk=hda > part swap --size=128 --grow --maxsize=256 --ondisk=hda > install > cdrom > lang en_US.UTF-8 > langsupport --default en_GB.UTF-8 en_GB.UTF-8 > keyboard uk > mouse genericwheelps/2 --device psaux > rootpw --iscrypted $1$PRwZ191B$qq1HZQJpK5gfpPhJw/967/ > firewall --disabled > authconfig --enableshadow --enablemd5 > timezone Europe/London > bootloader --location=mbr > > %packages > @ network-server > @ web-server > @ dialup > @ sql-server > @ system-tools > @ british-support > @ ftp-server > @ development-tools > kernel > dhcp > net-snmp-utils > shapecfg > tftp-server > mysql-server > grub > mrtg > php-mysql > mod_auth_mysql > freeradius > php-odbc > > %post --nochroot > mkdir -p /mnt/source > mount /tmp/cdrom /mnt/source > cp -f /mnt/source/custom.tar /mnt/sysimage/root > > > ----- Original Message ----- > From: "David Tegelaar" > To: ; "Discussion list about Kickstart" > > Sent: Monday, April 19, 2004 6:22 PM > Subject: RE: Install of rpm packages in %post - script > > > > That's pretty wierd. Try leaving out the > > "mkdir -p /mnt/source" line (or telling > > it to mkdir a different directory name). > > I think the /mnt/source directory already > > exists anyway. Maybe the ? char > > is an extra char at the end of the text or > > is somehow part of a question that gets > > asked if the directory already exists > > when you try to mkdir it. > > > > -dave > > > > > > > > -----Original Message----- > > From: kickstart-list-bounces at redhat.com > > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall > > Sent: Monday, April 19, 2004 11:08 AM > > To: 'Discussion list about Kickstart' > > Subject: RE: Install of rpm packages in %post - script > > > > > > I've been struggling with this for days and I still have problems with > > it. Running Fedora Core 1. > > > > > > When attempting to do mkdir -p /mnt/source the script creates a > > /mnt/source? Dir (mnt/source + questionmark). I thought well ok and > > changed the copy command to cp /mnt/source?/custom.tar > > /mnt/sysimage/root > > > > Still no luck. Comes back with error message that is intermingled with > > the kickstart dialog and I can't work out what's happening and why. > > > > [Note the installation has been stripped down to one CD - could I have > > missed and essential RPM ??] > > > > Anyone have an idea > > > > > > Many thanks > > > > Martin > > > > > > > > > > -----Original Message----- > > From: kickstart-list-bounces at redhat.com > > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Marco Welter > > Sent: 19 April 2004 15:23 > > To: Discussion list about Kickstart > > Subject: Re: Install of rpm packages in %post - script > > > > Hi, > > > > > %post --nochroot > > > # cdrom is not mounted during post so i mount it with the --nochroot > > option > > > mkdir -p /mnt/source > > > mount /tmp/cdrom /mnt/source > > > > > > # copy updates.conf from the cd to /tmp on the installed system > > > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp > > thank you, no works ;-) > > > > > > %post > > > # creation of admin account - the rest of the kickstart can be > > performed > > > in normal %post mode > > > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin > > but not 100 %, when i have a "normal" %post after %post --nochroot whith > > rpm > > -ivh /root/xyz.rpm it do not work > > > > Bye > > > > Marco > > > ... > > > > > > hth > > > > > > pantz > > > > -- > > Lx-System GbR > > > > Tel.: 0700 LXSYSTEM > > info at lx-system.de > > > > Hauptgesch??ftsstelle: > > Ensinger Strasse 19 - 89073 Ulm > > 0731 / 602 81 19 > > > > Zweigniederlassung: > > Zur alten Zollbruecke 30 - 87527 Sonthofen > > Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 > > E-Mail: mawe at lx-system.de > > > > > > _______________________________________________ > > 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 > > > > > _______________________________________________ > 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 MSiddall at imaginativeit.co.uk Tue Apr 20 08:16:26 2004 From: MSiddall at imaginativeit.co.uk (Martin Siddall) Date: Tue, 20 Apr 2004 09:16:26 +0100 Subject: Install of rpm packages in %post - script In-Reply-To: <1082400021.11162.146.camel@edbrown.lanl.gov> Message-ID: <000601c426af$c6f69e80$6800a8c0@internal.net> Thanks everyone for the help. I think I have found the problem but don't know how to sort it out. Dos2unix did help I must have modified the ks.cfg file on a windows system, although I don't remember doing it. Many late nights recently..... The suggestion from Ed is the key .. thanks Ed When opening the shell in the %post section I tried the commands an got an error from mount saying that the file does not exist. Having checked the mnt/source and /tmp/cdrom I found that the device file cdrom had been deleted. As soon as the %packages section completes it's removes the device file and then recreates it once the %post section finishes. Bloody thing. How can I create the device in the /tmp dir. Many thanks to everyone Martin -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ed Brown Sent: 19 April 2004 19:40 To: Discussion list about Kickstart Subject: RE: Install of rpm packages in %post - script Try opening a shell in %post and running the commands manually to see what's happening. %post chvt 3 exec < /dev/tty3 > /dev/tty3 sh -Ed On Mon, 2004-04-19 at 12:23, David Tegelaar wrote: > Yes the suggestion in another email > that a Windows char may be in the ks > file is a good one. Also I think you > may need the "-t" option to mount: > > mount -t iso9660 /tmp/cdrom /mnt/source > > You could try writing the output to a log > so if you get a failure maybe you can look > at the log: > > mount -t iso9660 /tmp/cdrom /mnt/source >>/tmp/mount.log 2>&1 > > -dave > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall > Sent: Monday, April 19, 2004 1:42 PM > To: Discussion list about Kickstart > Subject: Re: Install of rpm packages in %post - script > > > Cheers , but i've been there allready. I echoed ls /mnt and various other > directories in the %post part of the config and quite correctly as Marco has > said anaconda umounts the cdrom and for some reason the /mnt/source > disappears. I have also tried creating other directories with the same > problem so I thorgh screw mkdir and tried to mount the cdrom on an existing > directory..... still no joy. > > The main problem is the anaconda program when it reports an error ... its > incomplete and intermingled with its own debugging lines so i can't see what > it's moaning about. > > The only thing I can think of is that the ks.cfg file has some wierd > character in it or the shell which anaconda uses is broken. > > I have include my ks.cfg for your perusal. Any other suggestions would be > greatly appreciated. > > > Martin > > ks.cfg > > zerombr yes > clearpart --all --drives=hda > part /boot --fstype ext3 --size=100 --ondisk=hda > part / --fstype ext3 --size=1024 --grow --ondisk=hda > part swap --size=128 --grow --maxsize=256 --ondisk=hda > install > cdrom > lang en_US.UTF-8 > langsupport --default en_GB.UTF-8 en_GB.UTF-8 > keyboard uk > mouse genericwheelps/2 --device psaux > rootpw --iscrypted $1$PRwZ191B$qq1HZQJpK5gfpPhJw/967/ > firewall --disabled > authconfig --enableshadow --enablemd5 > timezone Europe/London > bootloader --location=mbr > > %packages > @ network-server > @ web-server > @ dialup > @ sql-server > @ system-tools > @ british-support > @ ftp-server > @ development-tools > kernel > dhcp > net-snmp-utils > shapecfg > tftp-server > mysql-server > grub > mrtg > php-mysql > mod_auth_mysql > freeradius > php-odbc > > %post --nochroot > mkdir -p /mnt/source > mount /tmp/cdrom /mnt/source > cp -f /mnt/source/custom.tar /mnt/sysimage/root > > > ----- Original Message ----- > From: "David Tegelaar" > To: ; "Discussion list about Kickstart" > > Sent: Monday, April 19, 2004 6:22 PM > Subject: RE: Install of rpm packages in %post - script > > > > That's pretty wierd. Try leaving out the > > "mkdir -p /mnt/source" line (or telling > > it to mkdir a different directory name). > > I think the /mnt/source directory already > > exists anyway. Maybe the ? char > > is an extra char at the end of the text or > > is somehow part of a question that gets > > asked if the directory already exists > > when you try to mkdir it. > > > > -dave > > > > > > > > -----Original Message----- > > From: kickstart-list-bounces at redhat.com > > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Martin Siddall > > Sent: Monday, April 19, 2004 11:08 AM > > To: 'Discussion list about Kickstart' > > Subject: RE: Install of rpm packages in %post - script > > > > > > I've been struggling with this for days and I still have problems with > > it. Running Fedora Core 1. > > > > > > When attempting to do mkdir -p /mnt/source the script creates a > > /mnt/source? Dir (mnt/source + questionmark). I thought well ok and > > changed the copy command to cp /mnt/source?/custom.tar > > /mnt/sysimage/root > > > > Still no luck. Comes back with error message that is intermingled with > > the kickstart dialog and I can't work out what's happening and why. > > > > [Note the installation has been stripped down to one CD - could I have > > missed and essential RPM ??] > > > > Anyone have an idea > > > > > > Many thanks > > > > Martin > > > > > > > > > > -----Original Message----- > > From: kickstart-list-bounces at redhat.com > > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Marco Welter > > Sent: 19 April 2004 15:23 > > To: Discussion list about Kickstart > > Subject: Re: Install of rpm packages in %post - script > > > > Hi, > > > > > %post --nochroot > > > # cdrom is not mounted during post so i mount it with the --nochroot > > option > > > mkdir -p /mnt/source > > > mount /tmp/cdrom /mnt/source > > > > > > # copy updates.conf from the cd to /tmp on the installed system > > > cp -f /mnt/source/RedHat/RPMS/updates.conf /mnt/sysimage/tmp > > thank you, no works ;-) > > > > > > %post > > > # creation of admin account - the rest of the kickstart can be > > performed > > > in normal %post mode > > > /usr/sbin/useradd -c 'Administrateur' -s /bin/false admin > > but not 100 %, when i have a "normal" %post after %post --nochroot whith > > rpm > > -ivh /root/xyz.rpm it do not work > > > > Bye > > > > Marco > > > ... > > > > > > hth > > > > > > pantz > > > > -- > > Lx-System GbR > > > > Tel.: 0700 LXSYSTEM > > info at lx-system.de > > > > Hauptgesch??ftsstelle: > > Ensinger Strasse 19 - 89073 Ulm > > 0731 / 602 81 19 > > > > Zweigniederlassung: > > Zur alten Zollbruecke 30 - 87527 Sonthofen > > Tel: 08321 / 67 42 43 - Fax: 08321 / 67 42 44 > > E-Mail: mawe at lx-system.de > > > > > > _______________________________________________ > > 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 > > > > > _______________________________________________ > 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 blin at na.uni-tuebingen.de Tue Apr 20 08:50:09 2004 From: blin at na.uni-tuebingen.de (Kai Blin) Date: Tue, 20 Apr 2004 10:50:09 +0200 Subject: NFS based KS file.... In-Reply-To: References: <4081B4E2.50807@R-T-F-M.Org.Uk> Message-ID: <200404201050.10056.blin@na.uni-tuebingen.de> On Sunday 18 April 2004 01:46, Philip Rowlands wrote: [...] > For the latest kickstart docs, read here: > http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/ >pt-install-info.html Now that would have been interesting last week. Could that be linked from the Fedora web sites instead of the RH9.0 manual? This one really seems up-to-date. Who do I need to prodd for that? Cheers, Kai -- Kai Blin, Sysop Dept. of Numerical Algebra, University of T?bingen, Germany From phr at doc.ic.ac.uk Tue Apr 20 09:26:22 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Tue, 20 Apr 2004 10:26:22 +0100 (BST) Subject: Install of rpm packages in %post - script In-Reply-To: <000601c426af$c6f69e80$6800a8c0@internal.net> References: <000601c426af$c6f69e80$6800a8c0@internal.net> Message-ID: On Tue, 20 Apr 2004, Martin Siddall wrote: >When opening the shell in the %post section I tried the commands an got >an error from mount saying that the file does not exist. Having checked >the mnt/source and /tmp/cdrom I found that the device file cdrom had >been deleted. [snip] >How can I create the device in the /tmp dir. See mknod(1), which I believe is part of the busybox builtin. Cheers, Phil From csahut at lynuxtraining.com Tue Apr 20 09:29:50 2004 From: csahut at lynuxtraining.com (Christophe Sahut) Date: Tue, 20 Apr 2004 11:29:50 +0200 Subject: Multiple ks.cfg o a cdrom Message-ID: <4084ED8E.2030909@lynuxtraining.com> Hi, I am using a RedHat AS 2.1. I would like to use several ks.cfg to boot : syslinux.cfg: ... label auto kernel vmlinuz append ks=hd:hdc:/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 label int kernel vmlinuz append ks=hd:hdc:/ks-int.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 ... When I choose "int" label in the boot.msg menu, ks.cfg is run by default. (ks-int.cfg is the same file as ks.cfg, but with "interactive") Same result when booting with this command line : text ks=hd:hdc:/ks-int.cfg These files are in the initrd's /tmp of the images/boot.img directory. Is it possible to choose which ks.cfg I can load ? Else, how can I do to choose if my installation will be interactive or not ? Other question : Is it possible to put ks.cfg and ks-int.cfg in a directory on the cdrom, for exemple "ADDONS" ? I tried several times with something like : label auto kernel vmlinuz append ks=hd:hdc:/ADDONS/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 but this doesn't work. I tried other paths but the cdrom looks unavailable when being in the initrd boot sequence. I would like to put them on the cdrom "root" to modify them easily. Should i try to mount the cdrom inside the initrd ? (not really sexy). Thanks for help -- cs From MSiddall at imaginativeit.co.uk Tue Apr 20 09:47:17 2004 From: MSiddall at imaginativeit.co.uk (Martin Siddall) Date: Tue, 20 Apr 2004 10:47:17 +0100 Subject: Install of rpm packages in %post - script In-Reply-To: Message-ID: <000701c426bc$77ea7de0$6800a8c0@internal.net> Many thanks to you all. I have got it working and thought I would let you all know the config in the ks.cfg file in case anyone else has the same problems. %post --nochroot ln -sv /dev/hdc /tmp/cdromsource mkdir -p /mnt/source mount -t iso9660 /tmp/cdromsource /mnt/source >>/tmp/mount.log 2>&1 cp -f /mnt/source/custom.tar.gz /mnt/sysimage/root cd /mnt/sysimage/root gunzip custom.tar.gz tar -xf custom.tar rm custom.tar HTH Cheers Martin -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Philip Rowlands Sent: 20 April 2004 10:26 To: Discussion list about Kickstart Subject: RE: Install of rpm packages in %post - script On Tue, 20 Apr 2004, Martin Siddall wrote: >When opening the shell in the %post section I tried the commands an got >an error from mount saying that the file does not exist. Having checked >the mnt/source and /tmp/cdrom I found that the device file cdrom had >been deleted. [snip] >How can I create the device in the /tmp dir. See mknod(1), which I believe is part of the busybox builtin. Cheers, Phil _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From donald_bodle at reyrey.com Tue Apr 20 11:12:50 2004 From: donald_bodle at reyrey.com (Bodle, Donald E) Date: Tue, 20 Apr 2004 07:12:50 -0400 Subject: Multiple ks.cfg o a cdrom Message-ID: <8CFE45BE48312B48940923D31F91BF1F071F6286@oh18ex06.reyrey.com> I think with 2.1 you must embed them in the initrd.img. That's what I do. Here's an example of my syslinux.cfg: root > cat boot/syslinux.cfg implicit 1 prompt 1 display reyboot.msg label i kernel vmlinuz append ks=file:/install.cfg initrd=initrd.img lang= devfs=nomount label r kernel vmlinuz append ks=file:/reload.cfg initrd=initrd.img lang= devfs=nomount install.cfg and reload.cfg are embedded in initrd.img: root > ls initrd bin etc linuxrc modules reload.cfg tmp dev install.cfg lost+found proc sbin var Donald E. Bodle, Jr., RHCT Sr. Systems Integration Engineer Platform Development The Reynolds and Reynolds Co. (937) 485-1954 Dazed and confused, but trying to continue... -----Original Message----- From: Christophe Sahut [mailto:csahut at lynuxtraining.com] Sent: Tuesday, April 20, 2004 5:30 AM To: kickstart-list at redhat.com Subject: Multiple ks.cfg o a cdrom Hi, I am using a RedHat AS 2.1. I would like to use several ks.cfg to boot : syslinux.cfg: ... label auto kernel vmlinuz append ks=hd:hdc:/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 label int kernel vmlinuz append ks=hd:hdc:/ks-int.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 ... When I choose "int" label in the boot.msg menu, ks.cfg is run by default. (ks-int.cfg is the same file as ks.cfg, but with "interactive") Same result when booting with this command line : text ks=hd:hdc:/ks-int.cfg These files are in the initrd's /tmp of the images/boot.img directory. Is it possible to choose which ks.cfg I can load ? Else, how can I do to choose if my installation will be interactive or not ? Other question : Is it possible to put ks.cfg and ks-int.cfg in a directory on the cdrom, for exemple "ADDONS" ? I tried several times with something like : label auto kernel vmlinuz append ks=hd:hdc:/ADDONS/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 but this doesn't work. I tried other paths but the cdrom looks unavailable when being in the initrd boot sequence. I would like to put them on the cdrom "root" to modify them easily. Should i try to mount the cdrom inside the initrd ? (not really sexy). Thanks for help -- cs _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From donald_bodle at reyrey.com Tue Apr 20 11:23:37 2004 From: donald_bodle at reyrey.com (Bodle, Donald E) Date: Tue, 20 Apr 2004 07:23:37 -0400 Subject: Multiple ks.cfg o a cdrom Message-ID: <8CFE45BE48312B48940923D31F91BF1F071F6287@oh18ex06.reyrey.com> Sorry about the word wrap or cut and paste problem. Try this again: root > cat boot/syslinux.cfg implicit 1 prompt 1 display reyboot.msg label i kernel vmlinuz append ks=file:/install.cfg initrd=initrd.img lang= devfs=nomount label r kernel vmlinuz append ks=file:/reload.cfg initrd=initrd.img lang= devfs=nomount install.cfg and reload.cfg are embedded in initrd.img: root > ls initrd bin etc linuxrc modules reload.cfg tmp dev install.cfg lost+found proc sbin var Donald E. Bodle, Jr., RHCT Sr. Systems Integration Engineer Platform Development The Reynolds and Reynolds Co. (937) 485-1954 Dazed and confused, but trying to continue... -----Original Message----- From: Bodle, Donald E Sent: Tuesday, April 20, 2004 7:13 AM To: 'Discussion list about Kickstart' Subject: RE: Multiple ks.cfg o a cdrom I think with 2.1 you must embed them in the initrd.img. That's what I do. Here's an example of my syslinux.cfg: root > cat boot/syslinux.cfg implicit 1 prompt 1 display reyboot.msg label i kernel vmlinuz append ks=file:/install.cfg initrd=initrd.img lang= devfs=nomount label r kernel vmlinuz append ks=file:/reload.cfg initrd=initrd.img lang= devfs=nomount install.cfg and reload.cfg are embedded in initrd.img: root > ls initrd bin etc linuxrc modules reload.cfg tmp dev install.cfg lost+found proc sbin var Donald E. Bodle, Jr., RHCT Sr. Systems Integration Engineer Platform Development The Reynolds and Reynolds Co. (937) 485-1954 Dazed and confused, but trying to continue... -----Original Message----- From: Christophe Sahut [mailto:csahut at lynuxtraining.com] Sent: Tuesday, April 20, 2004 5:30 AM To: kickstart-list at redhat.com Subject: Multiple ks.cfg o a cdrom Hi, I am using a RedHat AS 2.1. I would like to use several ks.cfg to boot : syslinux.cfg: ... label auto kernel vmlinuz append ks=hd:hdc:/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 label int kernel vmlinuz append ks=hd:hdc:/ks-int.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 ... When I choose "int" label in the boot.msg menu, ks.cfg is run by default. (ks-int.cfg is the same file as ks.cfg, but with "interactive") Same result when booting with this command line : text ks=hd:hdc:/ks-int.cfg These files are in the initrd's /tmp of the images/boot.img directory. Is it possible to choose which ks.cfg I can load ? Else, how can I do to choose if my installation will be interactive or not ? Other question : Is it possible to put ks.cfg and ks-int.cfg in a directory on the cdrom, for exemple "ADDONS" ? I tried several times with something like : label auto kernel vmlinuz append ks=hd:hdc:/ADDONS/ks.cfg initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 but this doesn't work. I tried other paths but the cdrom looks unavailable when being in the initrd boot sequence. I would like to put them on the cdrom "root" to modify them easily. Should i try to mount the cdrom inside the initrd ? (not really sexy). Thanks for help -- cs _______________________________________________ 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 phr at doc.ic.ac.uk Tue Apr 20 11:58:36 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Tue, 20 Apr 2004 12:58:36 +0100 (BST) Subject: Multiple ks.cfg o a cdrom In-Reply-To: <4084ED8E.2030909@lynuxtraining.com> References: <4084ED8E.2030909@lynuxtraining.com> Message-ID: On Tue, 20 Apr 2004, Christophe Sahut wrote: > I am using a RedHat AS 2.1. > > I would like to use several ks.cfg to boot : > >syslinux.cfg: >... >label auto > kernel vmlinuz > append ks=hd:hdc:/ks.cfg initrd=initrd.img lang= devfs=nomount >label int > kernel vmlinuz > append ks=hd:hdc:/ks-int.cfg initrd=initrd.img lang= devfs=nomount There are other locations which can be passed via the ks= argument, such as floppy or CD. See here: http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/custom-guide/s1-kickstart2-startinginstall.html Cheers, Phil From csahut at lynuxtraining.com Tue Apr 20 13:32:04 2004 From: csahut at lynuxtraining.com (Christophe Sahut) Date: Tue, 20 Apr 2004 15:32:04 +0200 Subject: Multiple ks.cfg o a cdrom In-Reply-To: <8CFE45BE48312B48940923D31F91BF1F071F6287@oh18ex06.reyrey.com> References: <8CFE45BE48312B48940923D31F91BF1F071F6287@oh18ex06.reyrey.com> Message-ID: <40852654.1000106@lynuxtraining.com> Bodle, Donald E wrote: > Sorry about the word wrap or cut and paste problem. Try this again: > > root > cat boot/syslinux.cfg > implicit 1 > prompt 1 > display reyboot.msg > label i > kernel vmlinuz > append ks=file:/install.cfg initrd=initrd.img lang= devfs=nomount > label r > kernel vmlinuz > append ks=file:/reload.cfg initrd=initrd.img lang= devfs=nomount > > install.cfg and reload.cfg are embedded in initrd.img: > > root > ls initrd > bin etc linuxrc modules reload.cfg tmp > dev install.cfg lost+found proc sbin var Thank you, it works now. The problem was that I read somewhere to put ks.cfg and others .cfg in the /tmp directory of the initrd. Which is wrong (at least on rh as, and probably on RH 7.x,maybe it's true for Redhat 9 and FC). It is stange because I'm sure I tried something like linux ks=hd:hdc:/tmp/ks.cfg which should do the same thing... (hdc is my cdrom drive) -- cs From James_Martin at ao.uscourts.gov Tue Apr 20 15:20:28 2004 From: James_Martin at ao.uscourts.gov (James_Martin at ao.uscourts.gov) Date: Tue, 20 Apr 2004 11:20:28 -0400 Subject: Install of rpm packages in %post - script Message-ID: Here's more elegant way doing of what you are trying to accomplish %post: %post updfstab mount /mnt/cdrom >>/tmp/mount.log 2>&1 cp -f /mnt/cdrom/custom.tar.gz /root cd /root gunzip custom.tar.gz tar -xf custom.tar rm custom.tar The updfstab updates the /etc/fstab on the system, creating the necessary entry for /mnt/cdrom so you don't have to type in all that extra stuff. You don't need the --nochroot. James S. Martin, RHCE Contractor Administrative Office of the United States Courts Washington, DC (202) 502-2394 "Martin Siddall" Sent by: kickstart-list-bounces at redhat.com 04/20/2004 05:47 AM Please respond to MSiddall; Please respond to Discussion list about Kickstart To: "'Discussion list about Kickstart'" cc: Subject: RE: Install of rpm packages in %post - script Many thanks to you all. I have got it working and thought I would let you all know the config in the ks.cfg file in case anyone else has the same problems. %post --nochroot ln -sv /dev/hdc /tmp/cdromsource mkdir -p /mnt/source mount -t iso9660 /tmp/cdromsource /mnt/source >>/tmp/mount.log 2>&1 cp -f /mnt/source/custom.tar.gz /mnt/sysimage/root cd /mnt/sysimage/root gunzip custom.tar.gz tar -xf custom.tar rm custom.tar HTH Cheers Martin -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Philip Rowlands Sent: 20 April 2004 10:26 To: Discussion list about Kickstart Subject: RE: Install of rpm packages in %post - script On Tue, 20 Apr 2004, Martin Siddall wrote: >When opening the shell in the %post section I tried the commands an got >an error from mount saying that the file does not exist. Having checked >the mnt/source and /tmp/cdrom I found that the device file cdrom had >been deleted. [snip] >How can I create the device in the /tmp dir. See mknod(1), which I believe is part of the busybox builtin. Cheers, Phil _______________________________________________ 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 daniel.kidger at quadrics.com Tue Apr 20 16:00:30 2004 From: daniel.kidger at quadrics.com (daniel.kidger at quadrics.com) Date: Tue, 20 Apr 2004 17:00:30 +0100 Subject: Install of rpm packages in %post - script Message-ID: <30062B7EA51A9045B9F605FAAC1B4F623E1FAA@tardis0.quadrics.com> I guess I would simplify that even more: %post updfstab mount /mnt/cdrom >>/tmp/mount.log 2>&1 cd /root tar xvfz /mnt/cdrom/custom.tar.gz umount /mnt/cdrom Yours, Daniel. -------------------------------------------------------------- Dr. Dan Kidger, Quadrics Ltd. daniel.kidger at quadrics.com One Bridewell St., Bristol, BS1 2AA, UK 0117 915 5505 ----------------------- www.quadrics.com -------------------- > -----Original Message----- > From: James_Martin at ao.uscourts.gov > [mailto:James_Martin at ao.uscourts.gov] > Sent: 20 April 2004 16:20 > To: Discussion list about Kickstart > Cc: MSiddall at imaginativeit.co.uk > Subject: RE: Install of rpm packages in %post - script > > > Here's more elegant way doing of what you are trying to > accomplish %post: > > %post > updfstab > mount /mnt/cdrom >>/tmp/mount.log 2>&1 > cp -f /mnt/cdrom/custom.tar.gz /root > cd /root > gunzip custom.tar.gz > tar -xf custom.tar > rm custom.tar > > The updfstab updates the /etc/fstab on the system, creating > the necessary > entry for /mnt/cdrom so you don't have to type in all that > extra stuff. > You don't need the --nochroot. > > James S. Martin, RHCE > Contractor > Administrative Office of the United States Courts > Washington, DC > (202) 502-2394 > > > > > "Martin Siddall" > Sent by: kickstart-list-bounces at redhat.com > 04/20/2004 05:47 AM > Please respond to MSiddall; Please respond to Discussion list about > Kickstart > > > To: "'Discussion list about Kickstart'" > > cc: > Subject: RE: Install of rpm packages in %post - script > > > Many thanks to you all. > > I have got it working and thought I would let you all know > the config in > the ks.cfg file in case anyone else has the same problems. > > > %post --nochroot > ln -sv /dev/hdc /tmp/cdromsource > mkdir -p /mnt/source > mount -t iso9660 /tmp/cdromsource /mnt/source >>/tmp/mount.log 2>&1 > cp -f /mnt/source/custom.tar.gz /mnt/sysimage/root > cd /mnt/sysimage/root > gunzip custom.tar.gz > tar -xf custom.tar > rm custom.tar > > > HTH > > Cheers > > Martin > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of > Philip Rowlands > Sent: 20 April 2004 10:26 > To: Discussion list about Kickstart > Subject: RE: Install of rpm packages in %post - script > > On Tue, 20 Apr 2004, Martin Siddall wrote: > > >When opening the shell in the %post section I tried the > commands an got > >an error from mount saying that the file does not exist. > Having checked > >the mnt/source and /tmp/cdrom I found that the device file cdrom had > >been deleted. > [snip] > >How can I create the device in the /tmp dir. > > See mknod(1), which I believe is part of the busybox builtin. > > > Cheers, > Phil > > > _______________________________________________ > 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 phr at doc.ic.ac.uk Tue Apr 20 16:35:26 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Tue, 20 Apr 2004 17:35:26 +0100 (BST) Subject: Install of rpm packages in %post - script In-Reply-To: <000701c426bc$77ea7de0$6800a8c0@internal.net> References: <000701c426bc$77ea7de0$6800a8c0@internal.net> Message-ID: On Tue, 20 Apr 2004, Martin Siddall wrote: >%post --nochroot >ln -sv /dev/hdc /tmp/cdromsource >mkdir -p /mnt/source >mount -t iso9660 /tmp/cdromsource /mnt/source >>/tmp/mount.log 2>&1 >cp -f /mnt/source/custom.tar.gz /mnt/sysimage/root >cd /mnt/sysimage/root >gunzip custom.tar.gz >tar -xf custom.tar >rm custom.tar I claim a two-liner! %post --nochroot mount /dev/hdc /mnt/source tar xvfz /mnt/source/custom.tar.gz -C /mnt/sysimage/root Cheers, Phil From MartinRobb at ieee.org Tue Apr 20 19:25:01 2004 From: MartinRobb at ieee.org (Martin Robb) Date: Tue, 20 Apr 2004 15:25:01 -0400 Subject: Fedora Core 2 Test 2 kickstart problems Message-ID: <4085790D.5060802@ieee.org> I have been using kickstart for some time to build selinux installs on a RHL7.1 base, and am trying to leapfrog forward to FC2 test 2, since selinux is being integrated onto that distribution. I am currently working with a minimal ks.cfg file, generated by the configurator. I am appending it to the bottom of this email. When I try to install with: linux ks=cdrom:/ks.cfg I get a "No driver found" window with the message "Unable to find any devices of the type needed for this installation type." I am fairly certain that anaconda is finding my ks.cfg file, because if I give it a bogus path, such as: linux ks=cdrom:/foo.bar I get an Error window with the message "Cannot find kickstart file on CDROM." To test whether the problem is with the way I built my install CD, I have also copied the ks.cfg to a diskette and booted from the FC2 test 2 disk 1 with the command: linux ks=floppy:/ks.cfg I get identical results, i.e. the "No driver found" window. Has anyone successfully used kickstart with Fedora Core 2? Can you give me any clues as to what's wrong? BTW, if anyone else is working with Fedora Core 2 I've noticed a couple of other nits that are worth passing along: - the disk 1 ISO image for test 2 is not bootable. Technically, when I tested with the standard install CDs, I initially booted with the FC2 test 1 disk 1 and then swapped to FC2 test 2. - The current anaconda genhdlist program wants to write to RedHat/base rather than Fedora/base. I've been getting around this by symbolically linking Fedora to RedHat before calling genhdlist, then removing the link before creating the ISO file. - It appears to me that we will need an "selinux" option similar to the "firewall" option in the ks.cfg file, with options to disable, warn or enable. Regards, Martin Robb MartinRobb at ieee.org My current ks.cfg file: #Generated by Kickstart Configurator #platform=x86, AMD64, or Intel EM64T #System language lang en_US #Language modules to install langsupport en_US #System keyboard keyboard us #System mouse mouse genericwheelps/2 #Sytem timezone timezone America/New_York #Root password rootpw 15:1AIsasih,ga #Reboot after installation reboot #Install OS instead of upgrade install #Use CDROM installation media cdrom #System bootloader configuration bootloader --location=mbr #Clear the Master Boot Record zerombr yes #Partition clearing information clearpart --all --initlabel #Disk partitioning information part / --fstype ext3 --size 1 --grow part swap --size 1024 #System authorization infomation auth --useshadow --enablemd5 #Firewall configuration firewall --disabled #Do not configure XWindows skipx #Package install information %packages --resolvedeps @ Core @ Dialup Networking Support @ Base From bdoctor at ps-ax.com Tue Apr 20 20:03:51 2004 From: bdoctor at ps-ax.com (Brad Doctor) Date: Tue, 20 Apr 2004 14:03:51 -0600 (MDT) Subject: Fedora Core 2 Test 2 kickstart problems In-Reply-To: <4085790D.5060802@ieee.org> Message-ID: <20040420200351.3A5963846@bigbox.ps-ax.com> No experience with the bulk of your issues, but genhdlist will take an argument as such: --productpath Fedora That eliminates the need for a work around. -brad [ Charset ISO-8859-1 unsupported, converting... ] > I have been using kickstart for some time to build selinux installs on a > RHL7.1 base, and am trying to leapfrog forward to FC2 test 2, since > selinux is being integrated onto that distribution. I am currently > working with a minimal ks.cfg file, generated by the configurator. I am > appending it to the bottom of this email. > > When I try to install with: > linux ks=cdrom:/ks.cfg > I get a "No driver found" window with the message "Unable to find any > devices of the type needed for this installation type." > > I am fairly certain that anaconda is finding my ks.cfg file, because if > I give it a bogus path, such as: > linux ks=cdrom:/foo.bar > I get an Error window with the message "Cannot find kickstart file on > CDROM." > > To test whether the problem is with the way I built my install CD, I > have also copied the ks.cfg to a diskette and booted from the FC2 test 2 > disk 1 with the command: > linux ks=floppy:/ks.cfg > I get identical results, i.e. the "No driver found" window. > > > Has anyone successfully used kickstart with Fedora Core 2? Can you give > me any clues as to what's wrong? > > BTW, if anyone else is working with Fedora Core 2 I've noticed a couple > of other nits that are worth passing along: > - the disk 1 ISO image for test 2 is not bootable. Technically, when I > tested with the standard install CDs, I initially booted with the FC2 > test 1 disk 1 and then swapped to FC2 test 2. > - The current anaconda genhdlist program wants to write to RedHat/base > rather than Fedora/base. I've been getting around this by symbolically > linking Fedora to RedHat before calling genhdlist, then removing the > link before creating the ISO file. > - It appears to me that we will need an "selinux" option similar to the > "firewall" option in the ks.cfg file, with options to disable, warn or > enable. > > Regards, > Martin Robb > MartinRobb at ieee.org > > My current ks.cfg file: > > #Generated by Kickstart Configurator > #platform=x86, AMD64, or Intel EM64T > > > #System language > lang en_US > #Language modules to install > langsupport en_US > #System keyboard > keyboard us > #System mouse > mouse genericwheelps/2 > #Sytem timezone > timezone America/New_York > #Root password > rootpw 15:1AIsasih,ga > #Reboot after installation > reboot > #Install OS instead of upgrade > install > #Use CDROM installation media > cdrom > #System bootloader configuration > bootloader --location=mbr > #Clear the Master Boot Record > zerombr yes > #Partition clearing information > clearpart --all --initlabel > #Disk partitioning information > part / --fstype ext3 --size 1 --grow > part swap --size 1024 > #System authorization infomation > auth --useshadow --enablemd5 > #Firewall configuration > firewall --disabled > #Do not configure XWindows > skipx > #Package install information > %packages --resolvedeps > @ Core > @ Dialup Networking Support > @ Base > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Brad Doctor, CISSP From bdoctor at ps-ax.com Tue Apr 20 20:10:23 2004 From: bdoctor at ps-ax.com (Brad Doctor) Date: Tue, 20 Apr 2004 14:10:23 -0600 (MDT) Subject: Fedora Core 2 Test 2 kickstart problems In-Reply-To: <20040420200351.3A5963846@bigbox.ps-ax.com> Message-ID: <20040420201023.6A1403846@bigbox.ps-ax.com> Actually, one other thing. The FC installers (core-1) have issue with some CDrom drives and I have had excellent luck appending allowcddma to the options, as shown in this isolinux.cfg: prompt 1 display general.msg label install kernel vmlinuz append ks=cdrom:/install_ks.cfg initrd=install_initrd.img lang= devfs=nomount ramdisk_size=8192 allowcddma The symptoms are that on certain hardware, the installation will fail at random times. With the allowcddma appended, the issues are gone and the installation goes a lot faster. No other compatibility issues have been noticed. -brad > No experience with the bulk of your issues, but genhdlist will take an > argument as such: > > --productpath Fedora > > That eliminates the need for a work around. > > -brad > > [ Charset ISO-8859-1 unsupported, converting... ] > > I have been using kickstart for some time to build selinux installs on a > > RHL7.1 base, and am trying to leapfrog forward to FC2 test 2, since > > selinux is being integrated onto that distribution. I am currently > > working with a minimal ks.cfg file, generated by the configurator. I am > > appending it to the bottom of this email. > > > > When I try to install with: > > linux ks=cdrom:/ks.cfg > > I get a "No driver found" window with the message "Unable to find any > > devices of the type needed for this installation type." > > > > I am fairly certain that anaconda is finding my ks.cfg file, because if > > I give it a bogus path, such as: > > linux ks=cdrom:/foo.bar > > I get an Error window with the message "Cannot find kickstart file on > > CDROM." > > > > To test whether the problem is with the way I built my install CD, I > > have also copied the ks.cfg to a diskette and booted from the FC2 test 2 > > disk 1 with the command: > > linux ks=floppy:/ks.cfg > > I get identical results, i.e. the "No driver found" window. > > > > > > Has anyone successfully used kickstart with Fedora Core 2? Can you give > > me any clues as to what's wrong? > > > > BTW, if anyone else is working with Fedora Core 2 I've noticed a couple > > of other nits that are worth passing along: > > - the disk 1 ISO image for test 2 is not bootable. Technically, when I > > tested with the standard install CDs, I initially booted with the FC2 > > test 1 disk 1 and then swapped to FC2 test 2. > > - The current anaconda genhdlist program wants to write to RedHat/base > > rather than Fedora/base. I've been getting around this by symbolically > > linking Fedora to RedHat before calling genhdlist, then removing the > > link before creating the ISO file. > > - It appears to me that we will need an "selinux" option similar to the > > "firewall" option in the ks.cfg file, with options to disable, warn or > > enable. > > > > Regards, > > Martin Robb > > MartinRobb at ieee.org > > > > My current ks.cfg file: > > > > #Generated by Kickstart Configurator > > #platform=x86, AMD64, or Intel EM64T > > > > > > #System language > > lang en_US > > #Language modules to install > > langsupport en_US > > #System keyboard > > keyboard us > > #System mouse > > mouse genericwheelps/2 > > #Sytem timezone > > timezone America/New_York > > #Root password > > rootpw 15:1AIsasih,ga > > #Reboot after installation > > reboot > > #Install OS instead of upgrade > > install > > #Use CDROM installation media > > cdrom > > #System bootloader configuration > > bootloader --location=mbr > > #Clear the Master Boot Record > > zerombr yes > > #Partition clearing information > > clearpart --all --initlabel > > #Disk partitioning information > > part / --fstype ext3 --size 1 --grow > > part swap --size 1024 > > #System authorization infomation > > auth --useshadow --enablemd5 > > #Firewall configuration > > firewall --disabled > > #Do not configure XWindows > > skipx > > #Package install information > > %packages --resolvedeps > > @ Core > > @ Dialup Networking Support > > @ Base > > > > > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > -- > Brad Doctor, CISSP > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Brad Doctor, CISSP From forrestx.taylor at intel.com Tue Apr 20 20:10:18 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 20 Apr 2004 13:10:18 -0700 Subject: Fedora Core 2 Test 2 kickstart problems In-Reply-To: <4085790D.5060802@ieee.org> References: <4085790D.5060802@ieee.org> Message-ID: <1082491817.12707.69.camel@bad.jf.intel.com> On Tue, 2004-04-20 at 12:25, Martin Robb wrote: > I have been using kickstart for some time to build selinux installs on a > RHL7.1 base, and am trying to leapfrog forward to FC2 test 2, since > selinux is being integrated onto that distribution. I am currently > working with a minimal ks.cfg file, generated by the configurator. I am > appending it to the bottom of this email. > > When I try to install with: > linux ks=cdrom:/ks.cfg > I get a "No driver found" window with the message "Unable to find any > devices of the type needed for this installation type." This looks like it is telling you that it cannot find the media for the installation. > I am fairly certain that anaconda is finding my ks.cfg file, because if > I give it a bogus path, such as: > linux ks=cdrom:/foo.bar > I get an Error window with the message "Cannot find kickstart file on > CDROM." > > Has anyone successfully used kickstart with Fedora Core 2? Can you give > me any clues as to what's wrong? > > BTW, if anyone else is working with Fedora Core 2 I've noticed a couple > of other nits that are worth passing along: > - the disk 1 ISO image for test 2 is not bootable. Technically, when I > tested with the standard install CDs, I initially booted with the FC2 > test 1 disk 1 and then swapped to FC2 test 2. This has been discussed many times on the fedora-list and the fedora-test-list. I haven't had a problem yet booting from test2, but you are certainly not alone. I have successfully used kickstart, but I don't have the non-booting CD-ROM problem, so that may be the difference. > - The current anaconda genhdlist program wants to write to RedHat/base > rather than Fedora/base. I've been getting around this by symbolically > linking Fedora to RedHat before calling genhdlist, then removing the > link before creating the ISO file. Use --productpath Fedora (or patch anaconda). > - It appears to me that we will need an "selinux" option similar to the > "firewall" option in the ks.cfg file, with options to disable, warn or > enable. Agreed. I thought I filed a bugzilla report, but I cannot find it. Test3 should be out soon, so I'll put this in bugzilla if it is not in test3. Forrest From MartinRobb at ieee.org Tue Apr 20 21:10:42 2004 From: MartinRobb at ieee.org (Martin Robb) Date: Tue, 20 Apr 2004 17:10:42 -0400 Subject: Fedora Core 2 Test 2 kickstart problems In-Reply-To: <1082491817.12707.69.camel@bad.jf.intel.com> References: <4085790D.5060802@ieee.org> <1082491817.12707.69.camel@bad.jf.intel.com> Message-ID: <408591D2.5070808@ieee.org> An HTML attachment was scrubbed... URL: From forrestx.taylor at intel.com Tue Apr 20 21:23:14 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 20 Apr 2004 14:23:14 -0700 Subject: Fedora Core 2 Test 2 kickstart problems In-Reply-To: <408591D2.5070808@ieee.org> References: <4085790D.5060802@ieee.org> <1082491817.12707.69.camel@bad.jf.intel.com> <408591D2.5070808@ieee.org> Message-ID: <1082496194.12707.90.camel@bad.jf.intel.com> On Tue, 2004-04-20 at 14:10, Martin Robb wrote: > At the moment, I'm leaning more towards a problem accessing the hard > disk. The anaconda-ks.cfg file works as is, but since the part and > clearpart options are commented out, it takes you through an > interactive install. When I uncomment the part and clearpart options, > it generates the "No driver found" window. Yes, that sounds correct. > Interesting. I tried both the FC2t2 disk 1 and my install CD on a > Proliant, the only alternative hardware I have readily available. The > FC2t2 disk 1 does boot. Both disks starve on a "Loading SCSI driver" > window with the message "Loading CCISS" driver. That is at least a > different message. Yes, this definitely looks like a hard drive driver issue. > Actually the Proliant platform is my desired target, but I've had a > good deal of trouble getting it to work with anything beyond RHL 7.x. Yeah, I had a bit of trouble after 7.x too. I think that there was some memory line that I used for 8.0 and 9, but IIRC, FC1 worked fine for me. > I'm not sure where to take it from here, except to try and scrounge up > some hardware that will install flawlessly from FC2t2 disk 1 and see > if it handles my install disk also. Does anyone think this is worth > escalating to bugzilla? Have you tried using a newer kernel? I would rebuild the discs with a newer kernel to see if that helped with the hard drive issue. If that doesn't FC2test3 should be out next week, so you may want to try that instead. Forrest From Thomas.Cameron at bankofamerica.com Wed Apr 21 17:30:13 2004 From: Thomas.Cameron at bankofamerica.com (Cameron, Thomas) Date: Wed, 21 Apr 2004 12:30:13 -0500 Subject: Fedora Core 2 Test 2 kickstart problems Message-ID: <1C455916B3418145B320711B21A2F04547A29B@ex2k.bankofamerica.com> > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com]On Behalf Of > Taylor, ForrestX > Sent: Tuesday, April 20, 2004 4:23 PM > To: Discussion list about Kickstart > Subject: Re: Fedora Core 2 Test 2 kickstart problems > > Actually the Proliant platform is my desired target, but I've had a > > good deal of trouble getting it to work with anything > beyond RHL 7.x. > > Yeah, I had a bit of trouble after 7.x too. I think that > there was some > memory line that I used for 8.0 and 9, but IIRC, FC1 worked > fine for me. See http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&edition=us&frame=right&th=9f79eae9cb81c7b&seekm=3BEF3A9D.1ECFA7A1%40rownetco.com#link2 for the correct syntax for the mem entry in grub.conf. -- Thomas Cameron, RHCE, CNE, MCSE, MCT Assistant Vice President Linux Design and Engineering Bank of America (972) 997-9641 The opinions expressed in this message are mine alone and do not necessarily reflect the opinions of my employer, Bank of America. From Neil at R-T-F-M.Org.Uk Wed Apr 21 17:57:44 2004 From: Neil at R-T-F-M.Org.Uk (Neil Stone) Date: Wed, 21 Apr 2004 18:57:44 +0100 Subject: LVM + Kickstart + rhel3-ES Message-ID: <4086B618.2010700@R-T-F-M.Org.Uk> I am having problems when trying to combine the above.. I know that the installer for rhel3 lets you configure LVM and install time.. that being the case you should be able to configure LVM in ks right ?? well i can't get it working.. The installer gets to the point wehre it would create the partitions and it falls over badly... even more annoying is the fact that the other partitions that were in place before have already been nuked... oops... Ho hum.. I look forward to answers on this... Neil From Robert.Wehner at McKesson.com Wed Apr 21 18:07:45 2004 From: Robert.Wehner at McKesson.com (Wehner, Robert) Date: Wed, 21 Apr 2004 14:07:45 -0400 Subject: LVM + Kickstart + rhel3-ES Message-ID: <157F156466315D47AFF21A4A40E2F1E10436A8AB@bldexc02ntms.clinicom.com> What does your ks.cfg look like? The partitioning part should have entries that look something like this sample (at least this works for me with RHEL ES 3.0): #/boot and swap can't be LVM part /boot --fstype ext3 --size=52 --asprimary part swap --size=2045 # here's the LVM stuff part pv.00 --size=10000 volgroup VG00 pv.00 logvol / --fstype ext3 --name=lvol0 --vgname=VG00 --size=1024 Etc. Robert -----Original Message----- From: Neil Stone [mailto:Neil at R-T-F-M.Org.Uk] Sent: Wednesday, April 21, 2004 11:58 AM To: kickstart-list at redhat.com Subject: LVM + Kickstart + rhel3-ES I am having problems when trying to combine the above.. I know that the installer for rhel3 lets you configure LVM and install time.. that being the case you should be able to configure LVM in ks right ?? well i can't get it working.. The installer gets to the point wehre it would create the partitions and it falls over badly... even more annoying is the fact that the other partitions that were in place before have already been nuked... oops... Ho hum.. I look forward to answers on this... Neil _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Neil at R-T-F-M.Org.Uk Thu Apr 22 10:53:13 2004 From: Neil at R-T-F-M.Org.Uk (Neil Stone) Date: Thu, 22 Apr 2004 11:53:13 +0100 Subject: LVM + Kickstart + rhel3-ES In-Reply-To: <157F156466315D47AFF21A4A40E2F1E10436A8AB@bldexc02ntms.clinicom.com> References: <157F156466315D47AFF21A4A40E2F1E10436A8AB@bldexc02ntms.clinicom.com> Message-ID: <4087A419.5070205@R-T-F-M.Org.Uk> Thanks for the help on this, I have worked out what was going on... The target drive had been used for a previous installation.. and even though I had ticked the partition clearing box.. there was residual data in place... dd if=/dev/zero of=/dev/hda bs=100M count=1024 seemed to clear the data.. I can't imagine why it didn't like working before this... Thanks :-) Neil From MartinRobb at ieee.org Thu Apr 22 15:53:03 2004 From: MartinRobb at ieee.org (Martin Robb) Date: Thu, 22 Apr 2004 11:53:03 -0400 Subject: Fedora Core 2 Test 2 kickstart problems In-Reply-To: <1C455916B3418145B320711B21A2F04547A29B@ex2k.bankofamerica.com> References: <1C455916B3418145B320711B21A2F04547A29B@ex2k.bankofamerica.com> Message-ID: <4087EA5F.1050606@ieee.org> An HTML attachment was scrubbed... URL: From bakins at web.turner.com Thu Apr 22 20:25:23 2004 From: bakins at web.turner.com (Brian Akins) Date: Thu, 22 Apr 2004 16:25:23 -0400 Subject: Specify just the first disk Message-ID: <40882A33.1090901@web.turner.com> Is it possible using the "part" options for kickstart just to use the first harddrive? Is there another way to determine if a box has hda or sda or ida/something? -- Brian Akins Senior Systems Engineer CNN Internet Technologies From dtegelaar at egenera.com Thu Apr 22 20:32:47 2004 From: dtegelaar at egenera.com (David Tegelaar) Date: Thu, 22 Apr 2004 16:32:47 -0400 Subject: Specify just the first disk In-Reply-To: <40882A33.1090901@web.turner.com> Message-ID: Maybe "--ondisk=sda" option to "part" to put it on first SCSI disk. Check out the ks options at: http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-kickst art2-options.html -dave -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com]On Behalf Of Brian Akins Sent: Thursday, April 22, 2004 4:25 PM To: Discussion list about Kickstart Subject: Specify just the first disk Is it possible using the "part" options for kickstart just to use the first harddrive? Is there another way to determine if a box has hda or sda or ida/something? -- Brian Akins Senior Systems Engineer CNN Internet Technologies _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From daikema at triumf.ca Fri Apr 23 00:54:27 2004 From: daikema at triumf.ca (David Aikema) Date: Thu, 22 Apr 2004 17:54:27 -0700 Subject: Specify just the first disk In-Reply-To: <40882A33.1090901@web.turner.com> References: <40882A33.1090901@web.turner.com> Message-ID: <1082681667.40886943ece83@trmail.triumf.ca> Quoting Brian Akins : > Is it possible using the "part" options for kickstart just to use the > first harddrive? Is there another way to determine if a box has hda or > sda or ida/something? I think that you can just drop the ondisk=whatever bit and it will pick the first it finds. David Aikema ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From tru at pasteur.fr Fri Apr 23 11:12:50 2004 From: tru at pasteur.fr (Tru Huynh) Date: Fri, 23 Apr 2004 13:12:50 +0200 Subject: ks=http://... limited lenght ? Message-ID: <20040423131250.A2151@xiii.bis.pasteur.fr> Hi, Did anyone notice that the lenght of the http:// provided kickstart file is limited (and truncated) to 74 characters? Tru From barjunk at attglobal.net Mon Apr 26 06:19:01 2004 From: barjunk at attglobal.net (Barsalou) Date: Sun, 25 Apr 2004 22:19:01 -0800 Subject: Booting from a SCSI using an Adaptec 7896 Message-ID: <1082960341.5918.32.camel@localhost> I am trying to use kickstart to install RedHat 9 on a machine using an Adaptec 7896. After failing several times, I tried installing it straight...this failed too! I have been able to successfully install Debian on this machine...what should I do to figure out why it works for Debian and not for RedHat? There are a few entries regarding this for 7.1, but I would have imagined that this has been resolved by now. It hangs right after it tries to install the adaptec module. Any ideas? Mike -- Barsalou From tobias at quova.com Mon Apr 26 18:41:13 2004 From: tobias at quova.com (Tobias Speckbacher) Date: Mon, 26 Apr 2004 11:41:13 -0700 Subject: Booting from a SCSI using an Adaptec 7896 Message-ID: Try booting it by passing the apci option to the kernel, I remember having this issue back in the day with 7.x . Basically when you get to bootloader type linux apci . -Tobias -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Barsalou Sent: Sunday, April 25, 2004 10:19 PM To: kickstart-list at redhat.com Subject: Booting from a SCSI using an Adaptec 7896 I am trying to use kickstart to install RedHat 9 on a machine using an Adaptec 7896. After failing several times, I tried installing it straight...this failed too! I have been able to successfully install Debian on this machine...what should I do to figure out why it works for Debian and not for RedHat? There are a few entries regarding this for 7.1, but I would have imagined that this has been resolved by now. It hangs right after it tries to install the adaptec module. Any ideas? Mike -- Barsalou _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From barjunk at attglobal.net Tue Apr 27 14:40:51 2004 From: barjunk at attglobal.net (mbox mbarsalou) Date: Tue, 27 Apr 2004 06:40:51 -0800 Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: References: Message-ID: <1083076851.5918.45.camel@localhost> OK, I will. Where would I find "" ? I didn't know there were any. Also, is it apci or apic? Mike On Mon, 2004-04-26 at 10:41, Tobias Speckbacher wrote: > Try booting it by passing the apci option to the kernel, I remember > having this issue back in the day with 7.x . > > Basically when you get to bootloader type linux apci options you want to use> . > > -Tobias > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Barsalou > Sent: Sunday, April 25, 2004 10:19 PM > To: kickstart-list at redhat.com > Subject: Booting from a SCSI using an Adaptec 7896 > > I am trying to use kickstart to install RedHat 9 on a machine using an > Adaptec 7896. After failing several times, I tried installing it > straight...this failed too! > > I have been able to successfully install Debian on this machine...what > should I do to figure out why it works for Debian and not for RedHat? > There are a few entries regarding this for 7.1, but I would have > imagined that this has been resolved by now. > > It hangs right after it tries to install the adaptec module. > > Any ideas? > > Mike From jeremy at broadware.com Tue Apr 27 15:51:12 2004 From: jeremy at broadware.com (Jeremy Silver) Date: Tue, 27 Apr 2004 08:51:12 -0700 Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: <1083076851.5918.45.camel@localhost> Message-ID: <001301c42c6f$7a8c8d00$a13c0a0a@slaptop> Mike, There may be other places but you can use the kernel-parameters.txt in kernel source documentation directories. I don't understand exactly what APIC does but it has to do with managing multiple CPUs; APCI deals with power management. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of mbox mbarsalou Sent: Tuesday, April 27, 2004 07:41 AM To: Discussion list about Kickstart Subject: RE: Booting from a SCSI using an Adaptec 7896 OK, I will. Where would I find "" ? I didn't know there were any. Also, is it apci or apic? Mike On Mon, 2004-04-26 at 10:41, Tobias Speckbacher wrote: > Try booting it by passing the apci option to the kernel, I remember > having this issue back in the day with 7.x . > > Basically when you get to bootloader type linux apci options you want to use> . > > -Tobias > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Barsalou > Sent: Sunday, April 25, 2004 10:19 PM > To: kickstart-list at redhat.com > Subject: Booting from a SCSI using an Adaptec 7896 > > I am trying to use kickstart to install RedHat 9 on a machine using an > Adaptec 7896. After failing several times, I tried installing it > straight...this failed too! > > I have been able to successfully install Debian on this machine...what > should I do to figure out why it works for Debian and not for RedHat? > There are a few entries regarding this for 7.1, but I would have > imagined that this has been resolved by now. > > It hangs right after it tries to install the adaptec module. > > Any ideas? > > Mike _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From forrestx.taylor at intel.com Tue Apr 27 16:29:54 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Tue, 27 Apr 2004 09:29:54 -0700 Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: <1083076851.5918.45.camel@localhost> References: <1083076851.5918.45.camel@localhost> Message-ID: <1083083394.4461.56.camel@bad.jf.intel.com> On Tue, 2004-04-27 at 07:40, mbox mbarsalou wrote: > OK, I will. > > Where would I find "" ? I didn't know there > were any. /usr/src/linux-2.4/Documentation/kernel-parameters.txt > Also, is it apci or apic? apic Forrest From tobias at quova.com Tue Apr 27 18:50:21 2004 From: tobias at quova.com (Tobias Speckbacher) Date: Tue, 27 Apr 2004 11:50:21 -0700 Subject: Booting from a SCSI using an Adaptec 7896 Message-ID: Sorry it of course is apic, its been a while since I had to use this. You may also need a different boot disk other than the cd, but I am a bit foggy on the specifics. If you google for it you can still find some references to the issue. -Tobias -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of mbox mbarsalou Sent: Tuesday, April 27, 2004 6:41 AM To: Discussion list about Kickstart Subject: RE: Booting from a SCSI using an Adaptec 7896 OK, I will. Where would I find "" ? I didn't know there were any. Also, is it apci or apic? Mike On Mon, 2004-04-26 at 10:41, Tobias Speckbacher wrote: > Try booting it by passing the apci option to the kernel, I remember > having this issue back in the day with 7.x . > > Basically when you get to bootloader type linux apci options you want to use> . > > -Tobias > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Barsalou > Sent: Sunday, April 25, 2004 10:19 PM > To: kickstart-list at redhat.com > Subject: Booting from a SCSI using an Adaptec 7896 > > I am trying to use kickstart to install RedHat 9 on a machine using an > Adaptec 7896. After failing several times, I tried installing it > straight...this failed too! > > I have been able to successfully install Debian on this machine...what > should I do to figure out why it works for Debian and not for RedHat? > There are a few entries regarding this for 7.1, but I would have > imagined that this has been resolved by now. > > It hangs right after it tries to install the adaptec module. > > Any ideas? > > Mike _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From bakins at web.turner.com Tue Apr 27 20:33:37 2004 From: bakins at web.turner.com (Brian Akins) Date: Tue, 27 Apr 2004 16:33:37 -0400 Subject: Proxy in http install Message-ID: <408EC3A1.3010600@web.turner.com> Is there anyway to specify a proxy server if doing an http install? -- Brian Akins Senior Systems Engineer CNN Internet Technologies From bakins at web.turner.com Tue Apr 27 20:35:35 2004 From: bakins at web.turner.com (Brian Akins) Date: Tue, 27 Apr 2004 16:35:35 -0400 Subject: Specify just the first disk In-Reply-To: <1082681667.40886943ece83@trmail.triumf.ca> References: <40882A33.1090901@web.turner.com> <1082681667.40886943ece83@trmail.triumf.ca> Message-ID: <408EC417.7090809@web.turner.com> David Aikema wrote: > >I think that you can just drop the ondisk=whatever bit and it will pick the >first it finds. > > But, If I have two disks, it insists on putting the swap on the second. I was using the ondisk stuff to force it to use the first disk. Now I have to support hda, ida/whatever instead of just sda. This is RHAS2.1, so using the pre and include trick I have found elsewhere doesnot work. -- Brian Akins Senior Systems Engineer CNN Internet Technologies From jkeating at j2solutions.net Tue Apr 27 20:46:38 2004 From: jkeating at j2solutions.net (Jesse Keating) Date: Tue, 27 Apr 2004 13:46:38 -0700 Subject: Specify just the first disk In-Reply-To: <408EC417.7090809@web.turner.com> References: <40882A33.1090901@web.turner.com> <1082681667.40886943ece83@trmail.triumf.ca> <408EC417.7090809@web.turner.com> Message-ID: <200404271346.38613.jkeating@j2solutions.net> On Tuesday 27 April 2004 13:35, Brian Akins wrote: > But, If I have two disks, it insists on putting the swap on the > second. I was using the ondisk stuff to force it to use the first > disk. Now I have to support hda, ida/whatever instead of just sda. > This is RHAS2.1, so using the pre and include trick I have found > elsewhere doesnot work. In the %pre section, use fdisk (or something like that) to probe which disks are present, awk out the actual disk fdisk -l |awk '/^Disk/ {print $2}' |awk -F "/" '{print $3}' |sed -e 's/://' Something similar to that. Then use this value (in a variable) for your --ondisk=${firstdisk} -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: signature URL: From dave at math.umn.edu Tue Apr 27 21:35:33 2004 From: dave at math.umn.edu (Dave Carlson) Date: Tue, 27 Apr 2004 16:35:33 -0500 Subject: Kickstart with ethernet aliases Message-ID: <200404271635.39674.dave@math.umn.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My current problem is that kickstart barfs on ethernet aliases, such as eth0:1. Is there a trick or a workaround to get these to work? If there is no workaround, is this a feature that might be added? - -- - -dave Dave Carlson Systems Administrator 8 Vincent Hall 612-625-4895 PGP Fingerprint: C3D0 9962 1E98 B742 132D 0E1A CE11 7C4B 5309 97A7 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAjtIrzhF8S1MJl6cRArphAJ9lgvs7pxbpA/Z4cDs4mYxzEspipwCePLsD Yh3qygxn/DtYKJ3NZ6IAf1c= =Jx0O -----END PGP SIGNATURE----- From barjunk at attglobal.net Wed Apr 28 05:37:53 2004 From: barjunk at attglobal.net (mbox mbarsalou) Date: Tue, 27 Apr 2004 21:37:53 -0800 Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: <1083083394.4461.56.camel@bad.jf.intel.com> References: <1083076851.5918.45.camel@localhost> <1083083394.4461.56.camel@bad.jf.intel.com> Message-ID: <1083130673.5918.59.camel@localhost> Is the only way to get this file to download the src rpm? Is there an online version somewhere? Mike On Tue, 2004-04-27 at 08:29, Taylor, ForrestX wrote: > On Tue, 2004-04-27 at 07:40, mbox mbarsalou wrote: > > OK, I will. > > > > Where would I find "" ? I didn't know there > > were any. > > /usr/src/linux-2.4/Documentation/kernel-parameters.txt > > > Also, is it apci or apic? > > apic > > Forrest > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From phr at doc.ic.ac.uk Wed Apr 28 07:52:47 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Wed, 28 Apr 2004 08:52:47 +0100 (BST) Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: <1083130673.5918.59.camel@localhost> References: <1083076851.5918.45.camel@localhost> <1083083394.4461.56.camel@bad.jf.intel.com> <1083130673.5918.59.camel@localhost> Message-ID: On Tue, 27 Apr 2004, mbox mbarsalou wrote: >Is the only way to get this file to download the src rpm? Is there an >online version somewhere? Several. Either ask Google, or go straight to the source: http://linux.bkbits.net:8080/linux-2.4/src/Documentation Unfortunately, I don't usually find kernel-parameters.txt all that useful nor current, whenever I have cause to refer to it. Cheers, Phil From barjunk at attglobal.net Wed Apr 28 06:15:23 2004 From: barjunk at attglobal.net (mbox mbarsalou) Date: Tue, 27 Apr 2004 22:15:23 -0800 Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: <1083083394.4461.56.camel@bad.jf.intel.com> References: <1083076851.5918.45.camel@localhost> <1083083394.4461.56.camel@bad.jf.intel.com> Message-ID: <1083132923.5918.90.camel@localhost> OK. I read the file, but I still am not sure what I should be doing. I see an entry for aic7xxx but there are no options listed there. Is there another place I should be looking at as well? BTW, I found an online place to look at the file, here: http://cvs.conectiva.com.br/cgi-bin/cvsweb.cgi/kernel-acme/ Although this may have the problem that it isn't RH/Fedora specific. Mike On Tue, 2004-04-27 at 08:29, Taylor, ForrestX wrote: > On Tue, 2004-04-27 at 07:40, mbox mbarsalou wrote: > > OK, I will. > > > > Where would I find "" ? I didn't know there > > were any. > > /usr/src/linux-2.4/Documentation/kernel-parameters.txt > > > Also, is it apci or apic? > > apic > > Forrest > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From tobias at quova.com Wed Apr 28 17:54:04 2004 From: tobias at quova.com (Tobias Speckbacher) Date: Wed, 28 Apr 2004 10:54:04 -0700 Subject: Booting from a SCSI using an Adaptec 7896 Message-ID: The issue I had 2 years back with this scsi controller related to the intel motherboard the controller was integrated in. I finally was able to locate the document that helped me solve the issue. http://people.redhat.com/dledford/440gx/ If you happen to not use this type of mobo unfortunately I don't know what the issue could be. Cheers, Tobias -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of mbox mbarsalou Sent: Tuesday, April 27, 2004 10:15 PM To: kickstart-list at redhat.com Subject: RE: Booting from a SCSI using an Adaptec 7896 OK. I read the file, but I still am not sure what I should be doing. I see an entry for aic7xxx but there are no options listed there. Is there another place I should be looking at as well? BTW, I found an online place to look at the file, here: http://cvs.conectiva.com.br/cgi-bin/cvsweb.cgi/kernel-acme/ Although this may have the problem that it isn't RH/Fedora specific. Mike On Tue, 2004-04-27 at 08:29, Taylor, ForrestX wrote: > On Tue, 2004-04-27 at 07:40, mbox mbarsalou wrote: > > OK, I will. > > > > Where would I find "" ? I didn't know there > > were any. > > /usr/src/linux-2.4/Documentation/kernel-parameters.txt > > > Also, is it apci or apic? > > apic > > Forrest > > > _______________________________________________ > 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 Rebecca.R.Hepper at seagate.com Wed Apr 28 19:27:02 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Wed, 28 Apr 2004 14:27:02 -0500 Subject: Kickstart using USB Flash Drive Message-ID: I am using RH 9. If I do a 'dd' to copy the bootdisk.img to my USB flash drive, I can kickstart a system successfully. I want to kickstart additional systems that require modules not available in the bootdisk.img although they are available in the drvnet.img. Is there a way to get both the bootdisk.img and drvnet.img on one USB flash drive so I don't have to utilize a separate driver disk? Or is there a way to increase whatever size limit is on the image file so I can add all the modules I need to the bootdisk.img then copy it to the USB flash drive? Thanks! From email at jasonkohles.com Wed Apr 28 19:41:16 2004 From: email at jasonkohles.com (Jason Kohles) Date: Wed, 28 Apr 2004 15:41:16 -0400 Subject: Kickstart using USB Flash Drive In-Reply-To: References: Message-ID: <20040428194116.GB11001@mail.jasonkohles.com> On Wed, Apr 28, 2004 at 02:27:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > I am using RH 9. If I do a 'dd' to copy the bootdisk.img to my USB flash > drive, I can kickstart a system successfully. I want to kickstart > additional systems that require modules not available in the bootdisk.img > although they are available in the drvnet.img. Is there a way to get both > the bootdisk.img and drvnet.img on one USB flash drive so I don't have to > utilize a separate driver disk? Or is there a way to increase whatever > size limit is on the image file so I can add all the modules I need to the > bootdisk.img then copy it to the USB flash drive? > I posted some instructions a while back on how to move drivers from the drivenet.img into the bootnet.img, they predated RH 9, but the process hasn't changed that much... https://listman.redhat.com/archives/kickstart-list/2003-March/msg00211.html -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ From Rebecca.R.Hepper at seagate.com Wed Apr 28 19:53:14 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Wed, 28 Apr 2004 14:53:14 -0500 Subject: Kickstart using USB Flash Drive Message-ID: Unfortunately, I need more modules than will fit in the bootdisk.img file. I didn't try your exact steps, Jason, but I have my own set of instructions that are quite similar. If I copy in all the modules I need, I fail in the last step when moving the initrd.img back to the bootdisk. Is there a way to increase whatever limits the size in this step? |---------+---------------------------------> | | Jason Kohles | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/28/2004 02:41 PM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: Kickstart using USB Flash Drive | >------------------------------------------------------------------------------------------------------------------------------| On Wed, Apr 28, 2004 at 02:27:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > I am using RH 9. If I do a 'dd' to copy the bootdisk.img to my USB flash > drive, I can kickstart a system successfully. I want to kickstart > additional systems that require modules not available in the bootdisk.img > although they are available in the drvnet.img. Is there a way to get both > the bootdisk.img and drvnet.img on one USB flash drive so I don't have to > utilize a separate driver disk? Or is there a way to increase whatever > size limit is on the image file so I can add all the modules I need to the > bootdisk.img then copy it to the USB flash drive? > I posted some instructions a while back on how to move drivers from the drivenet.img into the bootnet.img, they predated RH 9, but the process hasn't changed that much... https://listman.redhat.com/archives/kickstart-list/2003-March/msg00211.html -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From email at jasonkohles.com Wed Apr 28 20:30:53 2004 From: email at jasonkohles.com (Jason Kohles) Date: Wed, 28 Apr 2004 16:30:53 -0400 Subject: Kickstart using USB Flash Drive In-Reply-To: References: Message-ID: <20040428203053.GA3720@mail.jasonkohles.com> On Wed, Apr 28, 2004 at 02:53:14PM -0500, Rebecca.R.Hepper at seagate.com wrote: > > Unfortunately, I need more modules than will fit in the bootdisk.img file. > I didn't try your exact steps, Jason, but I have my own set of instructions > that are quite similar. If I copy in all the modules I need, I fail in the > last step when moving the initrd.img back to the bootdisk. Is there a way > to increase whatever limits the size in this step? > Have you tried using the pxeboot images, they are bigger and have all the network drivers already included. -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ From pantz at lqt.ca Wed Apr 28 20:37:43 2004 From: pantz at lqt.ca (Paul Pianta) Date: Wed, 28 Apr 2004 16:37:43 -0400 Subject: Kickstart using USB Flash Drive In-Reply-To: References: Message-ID: <40901617.9020203@lqt.ca> Rebecca.R.Hepper at seagate.com wrote: >Unfortunately, I need more modules than will fit in the bootdisk.img file. >I didn't try your exact steps, Jason, but I have my own set of instructions >that are quite similar. If I copy in all the modules I need, I fail in the >last step when moving the initrd.img back to the bootdisk. Is there a way >to increase whatever limits the size in this step? > > If your usb drive is bigger than a floppy (of course it is) then you should be able to create an empty "floppy" image that is much bigger than a regular one, and then put all of your stuff in that - I'm guessing ... I don't know the exact parameters to pass to 'dd' but it would be something like this: dd if=/dev/zero of=bigFloppy.img bs=1k count=3000 mkfs -t ext2 -F bigFloppy.img Then you can loop mount your bigFloppy.img and fill it with your goodies. This is all hypothetical and I have never tried it - just making some suggestions ... pantz -- Before you criticize someone, walk a mile in their shoes ... That way when you do criticize them, you're a mile away and you have their shoes! From Rebecca.R.Hepper at seagate.com Wed Apr 28 20:40:02 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Wed, 28 Apr 2004 15:40:02 -0500 Subject: Kickstart using USB Flash Drive Message-ID: I did look into doing PXE installs quite some time ago but it wasn't a viable option for my situation. I would rather stick the bootdisk.img plus any additional drivers on my USB flash drive if there is a way to do that. |---------+---------------------------------> | | Jason Kohles | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/28/2004 03:30 PM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: Kickstart using USB Flash Drive | >------------------------------------------------------------------------------------------------------------------------------| On Wed, Apr 28, 2004 at 02:53:14PM -0500, Rebecca.R.Hepper at seagate.com wrote: > > Unfortunately, I need more modules than will fit in the bootdisk.img file. > I didn't try your exact steps, Jason, but I have my own set of instructions > that are quite similar. If I copy in all the modules I need, I fail in the > last step when moving the initrd.img back to the bootdisk. Is there a way > to increase whatever limits the size in this step? > Have you tried using the pxeboot images, they are bigger and have all the network drivers already included. -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From email at jasonkohles.com Wed Apr 28 20:44:03 2004 From: email at jasonkohles.com (Jason Kohles) Date: Wed, 28 Apr 2004 16:44:03 -0400 Subject: Kickstart using USB Flash Drive In-Reply-To: References: Message-ID: <20040428204403.GA14637@mail.jasonkohles.com> On Wed, Apr 28, 2004 at 03:40:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > > I did look into doing PXE installs quite some time ago but it wasn't a > viable option for my situation. I would rather stick the bootdisk.img plus > any additional drivers on my USB flash drive if there is a way to do that. > My point wasn't to do pxe installs, it was that the pxe boot image is an oversized floppy image that is basically a combination of the bootdisk.img and drvnet.img, stick it on your usb drive and you probably won't need to do anything else. -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ From forrestx.taylor at intel.com Wed Apr 28 20:50:19 2004 From: forrestx.taylor at intel.com (Taylor, ForrestX) Date: Wed, 28 Apr 2004 13:50:19 -0700 Subject: Kickstart using USB Flash Drive In-Reply-To: References: Message-ID: <1083185419.21649.72.camel@bad.jf.intel.com> On Wed, 2004-04-28 at 12:53, Rebecca.R.Hepper at seagate.com wrote: > Unfortunately, I need more modules than will fit in the bootdisk.img file. > I didn't try your exact steps, Jason, but I have my own set of instructions > that are quite similar. If I copy in all the modules I need, I fail in the > last step when moving the initrd.img back to the bootdisk. Is there a way > to increase whatever limits the size in this step? This size is created in the anaconda-runtime script mk-images.i386. In FC1, Red Hat started creating a boot.iso image that contained everything: # now make a boot iso mkdir -p $TOPDESTPATH/images/isopath cp -rl $TOPDESTPATH/isolinux $TOPDESTPATH/images/isopath mkisofs -o $TOPDESTPATH/images/boot.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -V "$PRODUCT" -T $TOPDESTPATH/images/isopath rm -rf $TOPDESTPATH/images/isopath That should work for RHL9 as well... Forrest From sflory at rackable.com Thu Apr 29 00:15:54 2004 From: sflory at rackable.com (Samuel Flory) Date: Wed, 28 Apr 2004 17:15:54 -0700 Subject: Kickstart using USB Flash Drive In-Reply-To: References: Message-ID: <4090493A.8080701@rackable.com> Rebecca.R.Hepper at seagate.com wrote: > I am using RH 9. If I do a 'dd' to copy the bootdisk.img to my USB flash > drive, I can kickstart a system successfully. I want to kickstart > additional systems that require modules not available in the bootdisk.img > although they are available in the drvnet.img. Is there a way to get both > the bootdisk.img and drvnet.img on one USB flash drive so I don't have to > utilize a separate driver disk? Or is there a way to increase whatever > size limit is on the image file so I can add all the modules I need to the > bootdisk.img then copy it to the USB flash drive? > This is really easy. You can just use syslinux, and the initrd with every module. 1)Format the usb stick drive as one big fat32 partition.* 2)copy everything in the cdrom's isolinux directory to the base directory of the usb stick. (You don't need isolinux.bin, boot.cat, and TRANS.TBL) 3)rename isolinux.cfg to syslinux.cfg 4)Optional you may want to use the initrd-everthing out of the images/pxe directory on the cdrom. 5)Install syslinux on the usb stick drive. syslinux /dev/(device). * I find that mkdosfs doesn't like to format an entire device. So you may need to do the following: cat /dev/sd(whatever) >usb.stick mkdosfs usb.stick cat usb.stick > /dev/sd(whatever) -- There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory From ryangolhar at verizon.net Thu Apr 29 01:03:38 2004 From: ryangolhar at verizon.net (Ryan Golhar) Date: Wed, 28 Apr 2004 21:03:38 -0400 Subject: Kickstart using USB Flash Drive In-Reply-To: <20040428194116.GB11001@mail.jasonkohles.com> Message-ID: <005a01c42d85$cec62950$4122db82@GOLHARMOBILE1> You know, there is no more bootnet.img, at least not that I can find on CD 1 of Enterprise Linux. I take it I just need to combine bootdisk.img and drvnet.img to get the necessary NIC card drivers? ----- Ryan Golhar Computational Biologist The Informatics Institute at The University of Medicine & Dentistry of NJ Phone: 973-972-5034 Fax: 973-972-7412 Email: golharam at umdnj.edu -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Jason Kohles Sent: Wednesday, April 28, 2004 3:41 PM To: Discussion list about Kickstart Subject: Re: Kickstart using USB Flash Drive On Wed, Apr 28, 2004 at 02:27:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > I am using RH 9. If I do a 'dd' to copy the bootdisk.img to my USB > flash drive, I can kickstart a system successfully. I want to > kickstart additional systems that require modules not available in the > bootdisk.img although they are available in the drvnet.img. Is there > a way to get both the bootdisk.img and drvnet.img on one USB flash > drive so I don't have to utilize a separate driver disk? Or is there > a way to increase whatever size limit is on the image file so I can > add all the modules I need to the bootdisk.img then copy it to the USB > flash drive? > I posted some instructions a while back on how to move drivers from the drivenet.img into the bootnet.img, they predated RH 9, but the process hasn't changed that much... https://listman.redhat.com/archives/kickstart-list/2003-March/msg00211.h tml -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From barjunk at attglobal.net Thu Apr 29 04:49:37 2004 From: barjunk at attglobal.net (mbox mbarsalou) Date: Wed, 28 Apr 2004 20:49:37 -0800 Subject: Booting from a SCSI using an Adaptec 7896 In-Reply-To: References: Message-ID: <1083214176.5918.107.camel@localhost> It does happen to be that board, however, the information provided didn't seem to help. However, I was able to install RedHat on an IDE drive and then load the module by hand. This worked fine. Wouldn't this imply that it is the module in the initrd that is having the problem? Or could there possibly need to be a different module loaded along with the aic7xxx? What could I do now that would possibly allow me to install the system on this SCSI drive? Mike On Wed, 2004-04-28 at 09:54, Tobias Speckbacher wrote: > The issue I had 2 years back with this scsi controller related to the > intel motherboard the controller was integrated in. I finally was able > to locate the document that helped me solve the issue. > > http://people.redhat.com/dledford/440gx/ > > If you happen to not use this type of mobo unfortunately I don't know > what the issue could be. > > Cheers, > > Tobias > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of mbox mbarsalou > Sent: Tuesday, April 27, 2004 10:15 PM > To: kickstart-list at redhat.com > Subject: RE: Booting from a SCSI using an Adaptec 7896 > > OK. I read the file, but I still am not sure what I should be doing. I > see an entry for aic7xxx but there are no options listed there. Is > there another place I should be looking at as well? > > BTW, I found an online place to look at the file, here: > > http://cvs.conectiva.com.br/cgi-bin/cvsweb.cgi/kernel-acme/ > > Although this may have the problem that it isn't RH/Fedora specific. > > Mike > > On Tue, 2004-04-27 at 08:29, Taylor, ForrestX wrote: > > On Tue, 2004-04-27 at 07:40, mbox mbarsalou wrote: > > > OK, I will. > > > > > > Where would I find "" ? I didn't know > there > > > were any. > > > > /usr/src/linux-2.4/Documentation/kernel-parameters.txt > > > > > Also, is it apci or apic? > > > > apic > > > > Forrest > > > > > > _______________________________________________ > > 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 Rebecca.R.Hepper at seagate.com Thu Apr 29 12:46:20 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Thu, 29 Apr 2004 07:46:20 -0500 Subject: Kickstart using USB Flash Drive Message-ID: Thanks for the clarification. I'm still a bit confused though. On the RH 9 CDs, the pxeboot dir contains initrd.img and vmlinuz. The initrd.img has all the modules I require. If I 'dd' only the initrd.img to my USB flash drive, the computer won't boot off it - the computer boots up as normal. What else do I need to 'dd' to the flash drive? Where do my syslinux.cfg and boot.msg files go when utilizing the pxe boot image? |---------+---------------------------------> | | Jason Kohles | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/28/2004 03:44 PM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: Kickstart using USB Flash Drive | >------------------------------------------------------------------------------------------------------------------------------| On Wed, Apr 28, 2004 at 03:40:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > > I did look into doing PXE installs quite some time ago but it wasn't a > viable option for my situation. I would rather stick the bootdisk.img plus > any additional drivers on my USB flash drive if there is a way to do that. > My point wasn't to do pxe installs, it was that the pxe boot image is an oversized floppy image that is basically a combination of the bootdisk.img and drvnet.img, stick it on your usb drive and you probably won't need to do anything else. -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From ryangolhar at verizon.net Thu Apr 29 14:06:06 2004 From: ryangolhar at verizon.net (Ryan Golhar) Date: Thu, 29 Apr 2004 10:06:06 -0400 Subject: Kickstart using USB Flash Drive In-Reply-To: Message-ID: <00a501c42df3$1d649390$4122db82@GOLHARMOBILE1> I believe you need to dd the whole disk image and not just initrd.img. vmlinuz needs to be located on the first sector to boot. ----- Ryan Golhar Computational Biologist The Informatics Institute at The University of Medicine & Dentistry of NJ Phone: 973-972-5034 Fax: 973-972-7412 Email: golharam at umdnj.edu -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Rebecca.R.Hepper at seagate.com Sent: Thursday, April 29, 2004 8:46 AM To: kickstart-list at redhat.com Subject: Re: Kickstart using USB Flash Drive Thanks for the clarification. I'm still a bit confused though. On the RH 9 CDs, the pxeboot dir contains initrd.img and vmlinuz. The initrd.img has all the modules I require. If I 'dd' only the initrd.img to my USB flash drive, the computer won't boot off it - the computer boots up as normal. What else do I need to 'dd' to the flash drive? Where do my syslinux.cfg and boot.msg files go when utilizing the pxe boot image? |---------+---------------------------------> | | Jason Kohles | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/28/2004 03:44 PM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >----------------------------------------------------------------------- -------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: Kickstart using USB Flash Drive | >----------------------------------------------------------------------- -------------------------------------------------------| On Wed, Apr 28, 2004 at 03:40:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > > I did look into doing PXE installs quite some time ago but it wasn't a > viable option for my situation. I would rather stick the bootdisk.img plus > any additional drivers on my USB flash drive if there is a way to do that. > My point wasn't to do pxe installs, it was that the pxe boot image is an oversized floppy image that is basically a combination of the bootdisk.img and drvnet.img, stick it on your usb drive and you probably won't need to do anything else. -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ _______________________________________________ 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 Rebecca.R.Hepper at seagate.com Thu Apr 29 14:05:00 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Thu, 29 Apr 2004 09:05:00 -0500 Subject: Kickstart using USB Flash Drive Message-ID: Wow! This is great! It worked perfectly for me. When I used 'mkdosfs -F 32 /dev/(device)' to format the flash drive, I also had problems so I used your alternative formatting instructions. Thanks to everyone for their suggestions! |---------+---------------------------------> | | Samuel Flory | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/28/2004 07:15 PM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: Kickstart using USB Flash Drive | >------------------------------------------------------------------------------------------------------------------------------| Rebecca.R.Hepper at seagate.com wrote: > I am using RH 9. If I do a 'dd' to copy the bootdisk.img to my USB flash > drive, I can kickstart a system successfully. I want to kickstart > additional systems that require modules not available in the bootdisk.img > although they are available in the drvnet.img. Is there a way to get both > the bootdisk.img and drvnet.img on one USB flash drive so I don't have to > utilize a separate driver disk? Or is there a way to increase whatever > size limit is on the image file so I can add all the modules I need to the > bootdisk.img then copy it to the USB flash drive? > This is really easy. You can just use syslinux, and the initrd with every module. 1)Format the usb stick drive as one big fat32 partition.* 2)copy everything in the cdrom's isolinux directory to the base directory of the usb stick. (You don't need isolinux.bin, boot.cat, and TRANS.TBL) 3)rename isolinux.cfg to syslinux.cfg 4)Optional you may want to use the initrd-everthing out of the images/pxe directory on the cdrom. 5)Install syslinux on the usb stick drive. syslinux /dev/(device). * I find that mkdosfs doesn't like to format an entire device. So you may need to do the following: cat /dev/sd(whatever) >usb.stick mkdosfs usb.stick cat usb.stick > /dev/sd(whatever) -- There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Rebecca.R.Hepper at seagate.com Thu Apr 29 14:11:16 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Thu, 29 Apr 2004 09:11:16 -0500 Subject: Kickstart using USB Flash Drive Message-ID: I am utilizing the pxeboot image now. When I used the instructions Samuel sent to create a bootable flash drive, I used the initrd.img from the pxeboot directory rather than the usual initrd.img. Thanks for the assistance! |---------+---------------------------------> | | "Ryan Golhar" | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/29/2004 09:06 AM | | | Please respond to | | | golharam; Please | | | respond to Discussion | | | list about Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: "'Discussion list about Kickstart'" | | cc: | | Subject: RE: Kickstart using USB Flash Drive | >------------------------------------------------------------------------------------------------------------------------------| I believe you need to dd the whole disk image and not just initrd.img. vmlinuz needs to be located on the first sector to boot. ----- Ryan Golhar Computational Biologist The Informatics Institute at The University of Medicine & Dentistry of NJ Phone: 973-972-5034 Fax: 973-972-7412 Email: golharam at umdnj.edu -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Rebecca.R.Hepper at seagate.com Sent: Thursday, April 29, 2004 8:46 AM To: kickstart-list at redhat.com Subject: Re: Kickstart using USB Flash Drive Thanks for the clarification. I'm still a bit confused though. On the RH 9 CDs, the pxeboot dir contains initrd.img and vmlinuz. The initrd.img has all the modules I require. If I 'dd' only the initrd.img to my USB flash drive, the computer won't boot off it - the computer boots up as normal. What else do I need to 'dd' to the flash drive? Where do my syslinux.cfg and boot.msg files go when utilizing the pxe boot image? |---------+---------------------------------> | | Jason Kohles | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/28/2004 03:44 PM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >----------------------------------------------------------------------- -------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: Kickstart using USB Flash Drive | >----------------------------------------------------------------------- -------------------------------------------------------| On Wed, Apr 28, 2004 at 03:40:02PM -0500, Rebecca.R.Hepper at seagate.com wrote: > > I did look into doing PXE installs quite some time ago but it wasn't a > viable option for my situation. I would rather stick the bootdisk.img plus > any additional drivers on my USB flash drive if there is a way to do that. > My point wasn't to do pxe installs, it was that the pxe boot image is an oversized floppy image that is basically a combination of the bootdisk.img and drvnet.img, stick it on your usb drive and you probably won't need to do anything else. -- Jason Kohles A witty saying proves nothing. email at jasonkohles.com -- Voltaire (1694 - 1778) http://www.jasonkohles.com/ _______________________________________________ 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 kjsmith at nortelnetworks.com Thu Apr 29 17:55:51 2004 From: kjsmith at nortelnetworks.com (Kristen Smith) Date: Thu, 29 Apr 2004 12:55:51 -0500 Subject: mounting non-install cd in %post cd Message-ID: Been digging around for a while now and can't seem to figure this out. Is there anyway to eject the install cd in a %post section and then mount a newly inserted cd? I have tried various methods of using mount/eject/umount in the %post sections, but can't seem to get it to work. Has anyone had any success doing this? I have multiple CDs with data that need to be installed after the kickstart rpms are installed (unfortunately, I can't make the contents of the CDs rpms and I have to use multiple CDs for this part). I would like to keep from doing the kickstart, rebooting the system and then prompting for the new cds - instead would like to reboot only after everything has been installed - after I have done the kickstart and installed the data from the other CDs. Thanks for the help, Kristen Smith Nortel Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Wehner at McKesson.com Thu Apr 29 18:04:15 2004 From: Robert.Wehner at McKesson.com (Wehner, Robert) Date: Thu, 29 Apr 2004 14:04:15 -0400 Subject: mounting non-install cd in %post cd Message-ID: <157F156466315D47AFF21A4A40E2F1E10436A901@bldexc02ntms.clinicom.com> Using some of the tips mentioned on this list, I've been experimenting with something like this in the %post section. It doesn't eject the RH install CD (I don't believe it is mounted once you hit %post). The user just needs to pull the CD out. Hope this helps. ================ # use pid to get FDs, not "self" myPid=$$ # TTY we'll use for user input tty_num=8 user_tty=/dev/tty$tty_num # Store original file descriptors stdin=$(ls -l /proc/$myPid/fd/0 | awk '/^l/ {print $11}') stdout=$(ls -l /proc/$myPid/fd/1 | awk '/^l/ {print $11}') # change to new virtual terminal and set FDs there exec < $user_tty > $user_tty chvt $tty_num echo -n "Insert the next CD and then press 'Enter'. " read ans echo "Mounting CD..." updfstab if (mount /mnt/cdrom); then #check that cd is correct; error if not disc_label=$(head -1 /mnt/cdrom/.discinfo) if [ $disc_label = "uniqueString" ]; then # unpack CD contents. else echo "This isn't the right CD. Please try again." # handle the please try again part fi cd / umount /mnt/cdrom eject else # Error out. CD wouldn't mount, try again echo "Error out. CD wouldn't mount, try again" eject fi #change back the FDs exec < $stdin > $stdout echo "Done with CD file transfers" Robert -----Original Message----- From: Kristen Smith [mailto:kjsmith at nortelnetworks.com] Sent: Thursday, April 29, 2004 11:56 AM To: 'kickstart-list at redhat.com' Subject: mounting non-install cd in %post cd Been digging around for a while now and can't seem to figure this out. Is there anyway to eject the install cd in a %post section and then mount a newly inserted cd? I have tried various methods of using mount/eject/umount in the %post sections, but can't seem to get it to work. Has anyone had any success doing this? I have multiple CDs with data that need to be installed after the kickstart rpms are installed (unfortunately, I can't make the contents of the CDs rpms and I have to use multiple CDs for this part). I would like to keep from doing the kickstart, rebooting the system and then prompting for the new cds - instead would like to reboot only after everything has been installed - after I have done the kickstart and installed the data from the other CDs. Thanks for the help, Kristen Smith Nortel Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: From jglass at liquidweb.com Thu Apr 29 18:11:23 2004 From: jglass at liquidweb.com (Joseph Glass) Date: Thu, 29 Apr 2004 14:11:23 -0400 Subject: Using perl in %pre Message-ID: <1083262283.2203.354.camel@apathy.liquidweb.com> Hi everyone, What is the easiest way to use '%pre --interpreter /usr/bin/perl' using a RedHat 9 boot CD? Thanks. -- Joseph Glass Systems Administrator Liquid Web Inc. 800.580.4985 x227 From joden at lee.k12.nc.us Thu Apr 29 19:03:12 2004 From: joden at lee.k12.nc.us (James Olin Oden) Date: Thu, 29 Apr 2004 15:03:12 -0400 (EDT) Subject: Using perl in %pre In-Reply-To: <1083262283.2203.354.camel@apathy.liquidweb.com> References: <1083262283.2203.354.camel@apathy.liquidweb.com> Message-ID: On Thu, 29 Apr 2004, Joseph Glass wrote: > Hi everyone, > > What is the easiest way to use '%pre --interpreter /usr/bin/perl' using > a RedHat 9 boot CD? > There is no easy way that I know of. %pre operates from the anaconda boot image that does not have perl on it (anaconda is written in python). If you really wanted to do this you would need to rebuild the boot image with perl in it, and you probably would want to rebuild perl to make it smaller (i.e. don't compile with every extension and certainly don't put every library in the boot image). I would love for someone to tell me I am wrong, but I do believe that this is the case. Cheers...james > Thanks. > > From mikem at redhat.com Thu Apr 29 20:27:30 2004 From: mikem at redhat.com (Mike McLean) Date: Thu, 29 Apr 2004 16:27:30 -0400 Subject: ks=http://... limited lenght ? In-Reply-To: <20040423131250.A2151@xiii.bis.pasteur.fr> References: <20040423131250.A2151@xiii.bis.pasteur.fr> Message-ID: <40916532.8050306@redhat.com> Tru Huynh wrote: > Hi, > > Did anyone notice that the lenght of the http:// provided kickstart > file is limited (and truncated) to 74 characters? Hmm, which version? I'm pretty sure I've used longer urls than that. Could you be hitting the cmdline length limit? (1024 bytes I think) From phr at doc.ic.ac.uk Thu Apr 29 21:26:59 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Thu, 29 Apr 2004 22:26:59 +0100 (BST) Subject: Using perl in %pre In-Reply-To: <1083262283.2203.354.camel@apathy.liquidweb.com> References: <1083262283.2203.354.camel@apathy.liquidweb.com> Message-ID: On Thu, 29 Apr 2004, Joseph Glass wrote: >What is the easiest way to use '%pre --interpreter /usr/bin/perl' using >a RedHat 9 boot CD? %pre gives you the contents of initrd.img and stage2.img. Perl is not part of either of these, so your best bet is to provide it via an NFS share, or rewrite the script in Python (not a bad perl-a-like interpreted language, I've recently discovered.). Otherwise, make the perl script/app available as a CGI on your install server, and call out from %pre over the network. Cheers, Phil From tru at pasteur.fr Thu Apr 29 22:25:09 2004 From: tru at pasteur.fr (Tru Huynh) Date: Fri, 30 Apr 2004 00:25:09 +0200 Subject: ks=http://... limited lenght ? In-Reply-To: <40916532.8050306@redhat.com>; from mikem@redhat.com on Thu, Apr 29, 2004 at 04:27:30PM -0400 References: <20040423131250.A2151@xiii.bis.pasteur.fr> <40916532.8050306@redhat.com> Message-ID: <20040430002509.A32701@xiii.bis.pasteur.fr> On Thu, Apr 29, 2004 at 04:27:30PM -0400, Mike McLean wrote: > Tru Huynh wrote: > > Hi, > > > > Did anyone notice that the lenght of the http:// provided kickstart > > file is limited (and truncated) to 74 characters? > > Hmm, which version? > anaconda-9.1-8.centos.6 rebuild from anaconda-9.1-8.RHEL.src.rpm here is the grub.conf I am using to kickstart: title centos3 rescue console root (hd0,0) kernel /centos3.kernel devfs=nomount ramdisk_size=9216 rescue ks=http://www.pasteur.fr/recherche/unites/Binfs/ks/centos3.x86_64-install.cfg console=tty0 console=ttyS0,9600n8 initrd /centos3.img > I'm pretty sure I've used longer urls than that. Could you be hitting > the cmdline length limit? (1024 bytes I think) I don't think so. I can "wget http://www.pasteur.fr/recherche/unites/Binfs/ks/centos3.x86_64-install.cfg" but the kickstarting machine does not :( If I make http://www.pasteur.fr/recherche/unites/Binfs/ks/centos3.x86_64-install.cf file available, it downloads it fine and install properly. Don't try to get this file, the access is restricted to our internal network ;) Tru From jglass at liquidweb.com Thu Apr 29 23:13:22 2004 From: jglass at liquidweb.com (Joseph Glass) Date: Thu, 29 Apr 2004 19:13:22 -0400 Subject: Providing ks.cfg with dhcp Message-ID: <1083280401.2206.692.camel@apathy.liquidweb.com> Hi everyone, I'm trying to provide my ks.cfg over dhcp so I only need to type 'linux ks' at the boot prompt. The dhcpd/kickstart server are on the same machine (192.168.0.1.) dhcp works, as well as kickstart if I run the following command manually: linux ks=nfs:192.168.0.1:/home/kickstart/rh9.cfg In my dhcpd.conf file, I added following line in the subnet {} section: filename "/home/kickstart/ks.cfg"; My /etc/exports file contains the following: /home/kickstart *(ro) The error I get is: bootp: no bootfile received Then it proceeds to look for the kickstart file at nfs:192.168.0.1:/kickstart/kickstart-192.168.0.18 Any suggestions? Thanks for helping me with the question about using perl in %pre. Since you can't use perl in %pre from just the install CD, I ended up porting my script to python which works well. And I learned a new programming language in the process :). Thank you. -- Joseph Glass Systems Administrator Liquid Web Inc. 800.580.4985 x227 From barjunk at attglobal.net Fri Apr 30 04:33:52 2004 From: barjunk at attglobal.net (Barsalou) Date: Thu, 29 Apr 2004 20:33:52 -0800 Subject: all modules initrd and kickstart Message-ID: <1083299632.5918.123.camel@localhost> Is there a way to use the all modules initrd during kickstart? How would I do that? Mike -- Barsalou From phr at doc.ic.ac.uk Fri Apr 30 04:44:23 2004 From: phr at doc.ic.ac.uk (Philip Rowlands) Date: Fri, 30 Apr 2004 05:44:23 +0100 (BST) Subject: all modules initrd and kickstart In-Reply-To: <1083299632.5918.123.camel@localhost> References: <1083299632.5918.123.camel@localhost> Message-ID: On Thu, 29 Apr 2004, Barsalou wrote: >Is there a way to use the all modules initrd during kickstart? Yes. >How would I do that? Depends how you're booting. Let's rule out floppy disks for size reasons, which leaves CD-ROM, PXE, or hard disk (or USB key, if you're feeling adventurous). CD-ROM is the easiest of these if starting from scratch. Cheers, Phil From barjunk at attglobal.net Fri Apr 30 06:39:44 2004 From: barjunk at attglobal.net (mbox mbarsalou) Date: Thu, 29 Apr 2004 22:39:44 -0800 Subject: all modules initrd and kickstart In-Reply-To: References: <1083299632.5918.123.camel@localhost> Message-ID: <1083307184.5918.135.camel@localhost> Let's assume for the ease of discussion I am using a CD...the main RedHat CD without changes. How would I boot it so that it would use the all modules initrd? Mike On Thu, 2004-04-29 at 20:44, Philip Rowlands wrote: > On Thu, 29 Apr 2004, Barsalou wrote: > > >Is there a way to use the all modules initrd during kickstart? > > Yes. > > >How would I do that? > > Depends how you're booting. Let's rule out floppy disks for size > reasons, which leaves CD-ROM, PXE, or hard disk (or USB key, if you're > feeling adventurous). CD-ROM is the easiest of these if starting from > scratch. > > > Cheers, > Phil > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From blin at na.uni-tuebingen.de Fri Apr 30 10:56:47 2004 From: blin at na.uni-tuebingen.de (Kai Blin) Date: Fri, 30 Apr 2004 12:56:47 +0200 Subject: Providing ks.cfg with dhcp In-Reply-To: <1083280401.2206.692.camel@apathy.liquidweb.com> References: <1083280401.2206.692.camel@apathy.liquidweb.com> Message-ID: <200404301256.47999.blin@na.uni-tuebingen.de> On Friday 30 April 2004 01:13, Joseph Glass wrote: > I'm trying to provide my ks.cfg over dhcp so I only need to type 'linux > ks' at the boot prompt. The dhcpd/kickstart server are on the same > machine (192.168.0.1.) dhcp works, as well as kickstart if I run the > following command manually: > > linux ks=nfs:192.168.0.1:/home/kickstart/rh9.cfg ^^^^^^^ > In my dhcpd.conf file, I added following line in the subnet {} section: > > filename "/home/kickstart/ks.cfg"; ^^^^^^^ is ks.cfg a link to rh9.cfg? Does that file exist at all? [...] > Then it proceeds to look for the kickstart file at > nfs:192.168.0.1:/kickstart/kickstart-192.168.0.18 > > Any suggestions? It looks like that's some built-in default it tries after the dhcp file failed. -- Kai Blin, Sysop Dept. of Numerical Algebra, University of T?bingen, Germany From Rebecca.R.Hepper at seagate.com Fri Apr 30 11:53:04 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Fri, 30 Apr 2004 06:53:04 -0500 Subject: all modules initrd and kickstart Message-ID: Here is a link to instructions I received a few days ago and have been using for kickstart via a USB key. You can choose to use whatever initrd.img you want. https://www.redhat.com/archives/kickstart-list/2004-April/msg00085.html |---------+---------------------------------> | | mbox mbarsalou | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/30/2004 01:39 AM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: all modules initrd and kickstart | >------------------------------------------------------------------------------------------------------------------------------| Let's assume for the ease of discussion I am using a CD...the main RedHat CD without changes. How would I boot it so that it would use the all modules initrd? Mike On Thu, 2004-04-29 at 20:44, Philip Rowlands wrote: > On Thu, 29 Apr 2004, Barsalou wrote: > > >Is there a way to use the all modules initrd during kickstart? > > Yes. > > >How would I do that? > > Depends how you're booting. Let's rule out floppy disks for size > reasons, which leaves CD-ROM, PXE, or hard disk (or USB key, if you're > feeling adventurous). CD-ROM is the easiest of these if starting from > scratch. > > > Cheers, > Phil > > > _______________________________________________ > 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 kjsmith at nortelnetworks.com Fri Apr 30 13:52:01 2004 From: kjsmith at nortelnetworks.com (Kristen Smith) Date: Fri, 30 Apr 2004 08:52:01 -0500 Subject: mounting non-install cd in %post cd Message-ID: Thanks for the script - however, I still have the same problem. I looks like the cd is not being unmounted in the %post section - I am using RedHat AS 2.1 if that makes a difference. In the case of your script below, I am unable to eject the CD manually. During a post section, I change into vt2 and in the shell, do a mount and I see that the cdrom is mounted on /mnt/source. I can't umount from the shell - I get a device or resource busy. I tried putting a umount of /mnt/source in the kickstart.py file right before the %post scripts run, but same thing - "device or resource busy". It must be possible to change disks since kickstart can do it during the rpm install - guess I will have to dig around in the kickstart code a bit more. Thanks again for the help. -----Original Message----- From: Wehner, Robert [mailto:Robert.Wehner at McKesson.com] Sent: Thursday, April 29, 2004 1:04 PM To: 'Discussion list about Kickstart' Subject: RE: mounting non-install cd in %post cd Using some of the tips mentioned on this list, I've been experimenting with something like this in the %post section. It doesn't eject the RH install CD (I don't believe it is mounted once you hit %post). The user just needs to pull the CD out. Hope this helps. ================ # use pid to get FDs, not "self" myPid=$$ # TTY we'll use for user input tty_num=8 user_tty=/dev/tty$tty_num # Store original file descriptors stdin=$(ls -l /proc/$myPid/fd/0 | awk '/^l/ {print $11}') stdout=$(ls -l /proc/$myPid/fd/1 | awk '/^l/ {print $11}') # change to new virtual terminal and set FDs there exec < $user_tty > $user_tty chvt $tty_num echo -n "Insert the next CD and then press 'Enter'. " read ans echo "Mounting CD..." updfstab if (mount /mnt/cdrom); then #check that cd is correct; error if not disc_label=$(head -1 /mnt/cdrom/.discinfo) if [ $disc_label = "uniqueString" ]; then # unpack CD contents. else echo "This isn't the right CD. Please try again." # handle the please try again part fi cd / umount /mnt/cdrom eject else # Error out. CD wouldn't mount, try again echo "Error out. CD wouldn't mount, try again" eject fi #change back the FDs exec < $stdin > $stdout echo "Done with CD file transfers" Robert -----Original Message----- From: Kristen Smith [mailto:kjsmith at nortelnetworks.com] Sent: Thursday, April 29, 2004 11:56 AM To: 'kickstart-list at redhat.com' Subject: mounting non-install cd in %post cd Been digging around for a while now and can't seem to figure this out. Is there anyway to eject the install cd in a %post section and then mount a newly inserted cd? I have tried various methods of using mount/eject/umount in the %post sections, but can't seem to get it to work. Has anyone had any success doing this? I have multiple CDs with data that need to be installed after the kickstart rpms are installed (unfortunately, I can't make the contents of the CDs rpms and I have to use multiple CDs for this part). I would like to keep from doing the kickstart, rebooting the system and then prompting for the new cds - instead would like to reboot only after everything has been installed - after I have done the kickstart and installed the data from the other CDs. Thanks for the help, Kristen Smith Nortel Networks -------------- next part -------------- An HTML attachment was scrubbed... URL: From barjunk at attglobal.net Fri Apr 30 14:05:49 2004 From: barjunk at attglobal.net (mbox mbarsalou) Date: Fri, 30 Apr 2004 06:05:49 -0800 Subject: all modules initrd and kickstart In-Reply-To: References: Message-ID: <1083333948.5918.137.camel@localhost> Doesn't this require that I burn a neww CD? I was wondering if there was a way to use the existing RedHat CD. Mike On Fri, 2004-04-30 at 03:53, Rebecca.R.Hepper at seagate.com wrote: > Here is a link to instructions I received a few days ago and have been > using for kickstart via a USB key. You can choose to use whatever > initrd.img you want. > https://www.redhat.com/archives/kickstart-list/2004-April/msg00085.html > > > > |---------+---------------------------------> > | | mbox mbarsalou | > | | | | > | > | | Sent by: | > | | kickstart-list-bounces| > | | @redhat.com | > | | No Phone Info | > | | Available | > | | | > | | 04/30/2004 01:39 AM | > | | Please respond to | > | | Discussion list about | > | | Kickstart | > | | | > |---------+---------------------------------> > >------------------------------------------------------------------------------------------------------------------------------| > | | > | To: Discussion list about Kickstart | > | cc: | > | Subject: Re: all modules initrd and kickstart | > >------------------------------------------------------------------------------------------------------------------------------| > > > > > Let's assume for the ease of discussion I am using a CD...the main > RedHat CD without changes. How would I boot it so that it would use the > all modules initrd? > > Mike > > On Thu, 2004-04-29 at 20:44, Philip Rowlands wrote: > > On Thu, 29 Apr 2004, Barsalou wrote: > > > > >Is there a way to use the all modules initrd during kickstart? > > > > Yes. > > > > >How would I do that? > > > > Depends how you're booting. Let's rule out floppy disks for size > > reasons, which leaves CD-ROM, PXE, or hard disk (or USB key, if you're > > feeling adventurous). CD-ROM is the easiest of these if starting from > > scratch. > > > > > > Cheers, > > Phil > > > > > > _______________________________________________ > > 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 MartinRobb at ieee.org Fri Apr 30 15:30:58 2004 From: MartinRobb at ieee.org (Martin Robb) Date: Fri, 30 Apr 2004 11:30:58 -0400 Subject: kickstart under Fedora Core 2 Test 3 Message-ID: <40927132.7030608@ieee.org> Mostly good news. Kickstart (both ks=cdrom and ks=floppy) is working better for me under FC2t3 than it was under FC2t2! Flaw 1: (major) though kickstart is still not quite working for me, I'm getting much farther than under t1 and t2 and I'm getting consistent behavior on several different platforms. In t1 and t2 I was being asked to load additional drivers by kickstart even though an interactive install using the same CD sailed right through. Under t3 I'm sailing right past that point and getting through most of the install. However, the install eventually dies with an "error installing at-3.1.8-52" dialog box. This happens consistently on different architectures and with different install CDs. The at rpm installs cleanly in an interactive install using the same install CDs. Flaw 2: (minor) The automatically built /root/anaconda-ks.cfg file is close but not quite there. It listed the following clearpart and part lines: #clearpart --linux #part / --fstype ext3 --onpart hda5 #part swap --noformat --onpart hda6 #part /sandbox --fstype ext3 --onpart hda7 Simply uncommenting these lines causes the install to fail with a "requested partition does not exist ... hda5" error. However, using the lines: clearpart --all --initlabel part / --fstype ext3 --size 4096 part /sandbox --fstype ext3 --size 1 --grow part swap --size 1024 everything partitions cleanly. As an aside, FC2t3 is installing cleanly (without kickstart) on the HP Proliant platform -- under t1 and t2 I was getting the dreaded "loading cciss drivers" hang. With kickstart it is at least giving me consistent behavior with my other platforms. Marty MartinRobb at ieee.org From Rebecca.R.Hepper at seagate.com Fri Apr 30 15:35:14 2004 From: Rebecca.R.Hepper at seagate.com (Rebecca.R.Hepper at seagate.com) Date: Fri, 30 Apr 2004 10:35:14 -0500 Subject: all modules initrd and kickstart Message-ID: This is for using a USB keychain device, not a CD-ROM. I thought I'd throw it out there since Phil mentioned a USB keychain. |---------+---------------------------------> | | mbox mbarsalou | | | | | | Sent by: | | | kickstart-list-bounces| | | @redhat.com | | | No Phone Info | | | Available | | | | | | 04/30/2004 09:05 AM | | | Please respond to | | | Discussion list about | | | Kickstart | | | | |---------+---------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Discussion list about Kickstart | | cc: | | Subject: Re: all modules initrd and kickstart | >------------------------------------------------------------------------------------------------------------------------------| Doesn't this require that I burn a neww CD? I was wondering if there was a way to use the existing RedHat CD. Mike On Fri, 2004-04-30 at 03:53, Rebecca.R.Hepper at seagate.com wrote: > Here is a link to instructions I received a few days ago and have been > using for kickstart via a USB key. You can choose to use whatever > initrd.img you want. > https://www.redhat.com/archives/kickstart-list/2004-April/msg00085.html > > > > |---------+---------------------------------> > | | mbox mbarsalou | > | | | | > | > | | Sent by: | > | | kickstart-list-bounces| > | | @redhat.com | > | | No Phone Info | > | | Available | > | | | > | | 04/30/2004 01:39 AM | > | | Please respond to | > | | Discussion list about | > | | Kickstart | > | | | > |---------+---------------------------------> > > ------------------------------------------------------------------------------------------------------------------------------| > | | > | To: Discussion list about Kickstart | > | cc: | > | Subject: Re: all modules initrd and kickstart | > > ------------------------------------------------------------------------------------------------------------------------------| > > > > > Let's assume for the ease of discussion I am using a CD...the main > RedHat CD without changes. How would I boot it so that it would use the > all modules initrd? > > Mike > > On Thu, 2004-04-29 at 20:44, Philip Rowlands wrote: > > On Thu, 29 Apr 2004, Barsalou wrote: > > > > >Is there a way to use the all modules initrd during kickstart? > > > > Yes. > > > > >How would I do that? > > > > Depends how you're booting. Let's rule out floppy disks for size > > reasons, which leaves CD-ROM, PXE, or hard disk (or USB key, if you're > > feeling adventurous). CD-ROM is the easiest of these if starting from > > scratch. > > > > > > Cheers, > > Phil > > > > > > _______________________________________________ > > 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 _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From kbbrown at cs.ucsd.edu Fri Apr 30 17:18:54 2004 From: kbbrown at cs.ucsd.edu (Kelly Brown) Date: Fri, 30 Apr 2004 10:18:54 -0700 (PDT) Subject: Providing ks.cfg with dhcp In-Reply-To: <1083280401.2206.692.camel@apathy.liquidweb.com> References: <1083280401.2206.692.camel@apathy.liquidweb.com> Message-ID: Assuming that you didn't do a typo with the rh9.cfg/ks.cfg thing... You might want to try this in your dhcpd.conf host your_hostname { hardware ethernet your_ethernet_address; filename "/home/kickstart/ks.cfg"; } dhcpd should log to your messages log with syslog so if it's not working it might give you a clue. The alternate file it's looking for is a default location that ks looks for so you could always create a link there and leave all of file stuff out of dhcp. Also you don't need to type 'linux ks' apparently it works but 'ks' is enough. Hope this helps. -Kelly On Thu, 29 Apr 2004, Joseph Glass wrote: > Hi everyone, > > I'm trying to provide my ks.cfg over dhcp so I only need to type 'linux > ks' at the boot prompt. The dhcpd/kickstart server are on the same > machine (192.168.0.1.) dhcp works, as well as kickstart if I run the > following command manually: > > linux ks=nfs:192.168.0.1:/home/kickstart/rh9.cfg > > In my dhcpd.conf file, I added following line in the subnet {} section: > > filename "/home/kickstart/ks.cfg"; > > My /etc/exports file contains the following: > > /home/kickstart *(ro) > > The error I get is: > > bootp: no bootfile received > > Then it proceeds to look for the kickstart file at > nfs:192.168.0.1:/kickstart/kickstart-192.168.0.18 > > Any suggestions? > > Thanks for helping me with the question about using perl in %pre. Since > you can't use perl in %pre from just the install CD, I ended up porting > my script to python which works well. And I learned a new programming > language in the process :). > > Thank you. > > -- > Joseph Glass > Systems Administrator > Liquid Web Inc. > 800.580.4985 x227 > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list >