Yes. The build_ks config file just gets translated into a comps file for RH < 8 and a comps.xml file for RH 8+. The build_ks config file allows you to specify exactly which versions of the RPMs in your RPM repository you want to be in a build. You can have an RPM repository called production and one called testing with newer RPMs. To test an RPM in your kickstart, just include the new version in the build_ks config file and rerun build_ks. You can also use annex files. An annex file adds to or changes a build_ks config file. For example, you can have Linux 1.0-7.3 which includes a bunch of your common RPMs. For a special image, you could have an annex file called "XD2". Then you might have a Linux 1.0.XD2-7.3 which would include Ximian Desktop 2 :) Of course, this is just an example. For our internal use, I am integrating XD2 into our RH 7.3 image for release in a few weeks. Users will perform a kickstart and they'll have XD2 already installed with Evolution 1.4. I'm also trying to integrate the KDE 3.1.2 RPMs from kde-redhat.sf.net since we're stuck on RH 7.3 kernel for most of our development tools, Clearcase, etc. /Brian/ > Thanks Brian > > I finally finished setting up all rpms the way I want it and resolved > all their dependencies. > > Now I am on to making my build_ks.conf file. > > Is it possible to mention all my packages as a 'package' directive under > one single group named 'Full Install' and not break it down in groups > like base, X Windows, Gnome and so on? > > Thanks > > AR > > On Tue, 2003-08-05 at 08:52, Brian Long wrote: > > You can alter this to your heart's content :) We have a completely > > different system than Brett, but the tools should work in any > > environment. > > > > /Brian/ > > > > On Mon, 2003-08-04 at 14:52, Alexander Rau (private) wrote: > > > Brian: > > > > > > Just found it. Thanks > > > > > > Reading the web pages it looks like I need to follow the tree specs > > > mentioned > > > > > > /export/linux/ALLRPMS/redhat /*.rpm > > > /cisco /*.rpm > > > /vendorsup /*.rpm > > > /publicdomain/*.rpm > > > > > > Is this a must or can this be done using a directory tree as explained > > > by Brett in > > > > > > http://www.linuxjournal.com/article.php?sid=6473 > > > > > > i.e. > > > > > > /RH80/ONE_CD/RedHat/RPMS > > > > > > Thanks > > > > > > AR > > > > > > -----Original Message----- > > > From: Brian Long [mailto:brilong@xxxxxxxxx] > > > Sent: Monday, August 04, 2003 2:40 PM > > > To: Alexander Rau > > > Cc: 'Chan, Dominic'; anaconda-devel-list@xxxxxxxxxx > > > Subject: Re: How to Create a Custom Bootable Redhat 9.0 CD on a single > > > CD > > > > > > Alexander, > > > > > > The only web-based tool is the make_bootdisk page which allows your end > > > users to kickstart Linux all by themselves. > > > > > > If you just want my logic from build_ks, look in /usr/bin/build_ks :) > > > > > > /Brian/ > > > > > > On Mon, 2003-08-04 at 14:00, Alexander Rau wrote: > > > > Thanks for the link. It sounds promising and is probably the solution > > > to all > > > > my troubles. > > > > > > > > I have installed the kickstart-tools. I needed to install apache and > > > some > > > > perl add-ons. > > > > > > > > Does this mean this is a web based application? If so, how do I access > > > it? > > > > > > > > Thanks > > > > > > > > AR > > > > ----- Original Message ----- > > > > From: "Brian Long" <brilong@xxxxxxxxx> > > > > To: "Alexander Rau (private)" <alexander_rau@xxxxxxxxx> > > > > Cc: "'Chan, Dominic'" <DWC@xxxxxxxxxxxx>; > > > <anaconda-devel-list@xxxxxxxxxx> > > > > Sent: Monday, August 04, 2003 10:24 AM > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a single > > > CD > > > > > > > > > > > > > You might consider looking at the "build_ks" script that is part of > > > > > http://kickstart-tools.sf.net. If you grab the latest version from > > > CVS > > > > > (or install the RPM), you can hack the code to generate comps.xml > > > for > > > > > you. > > > > > > > > > > This is Perl-based code we use to make our own internal releases. > > > We > > > > > use a flat config file with each RPM-version-release so we can > > > revision > > > > > control our releases down to the exact version and release of each > > > RPM > > > > > (this is required to reconstruct a kickstart from 2+ years ago). > > > > > > > > > > build_ks was recently improved to support generation of comps.xml > > > for RH > > > > > 9, so give it a whirl or hack it up to do what you need. > > > > > > > > > > /Brian/ > > > > > > > > > > On Sun, 2003-08-03 at 15:07, Alexander Rau (private) wrote: > > > > > > I'm not so sure. The comps.xml file is where I am stuck at right > > > now, > > > > > > too. > > > > > > > > > > > > >From reading Brett's article I understand that you do not have to > > > > > > rebuild the comps.xml file if you just use the packages as they > > > are in > > > > > > the original comps.xml file. I also don't think you need to > > > rebuild the > > > > > > comps.xml file if you change it to include/exclude packages that > > > > > > originally are in the comps.xml file (not sure about this point > > > but it > > > > > > makes sense). > > > > > > > > > > > > Where it gets dicey is when you want to include new packages with > > > their > > > > > > dependencies. This is where I am at right now; I have added new > > > packages > > > > > > that are not mentioned in the comps.xml file and now I think I > > > need to > > > > > > rebuild it. I was on the > > > http://rhlinux.redhat.com/anaconda/comps.html > > > > > > site it is more confusing than helpful. > > > > > > > > > > > > I referred to the post by RobertP.J.Day from January 2003 > > > > > > > > > https://www.redhat.com/archives/anaconda-devel-list/2003-January/msg0005 > > > > > > 6.html > > > > > > > > > > > > And I run into the same problems. > > > > > > > > > > > > Any help with the comps.xml file is greatly appreciated. > > > > > > > > > > > > Thanks in advance > > > > > > > > > > > > AR > > > > > > > > > > > > -----Original Message----- > > > > > > From: anaconda-devel-list-admin@xxxxxxxxxx > > > > > > [mailto:anaconda-devel-list-admin@xxxxxxxxxx] On Behalf Of Chan, > > > Dominic > > > > > > Sent: Sunday, August 03, 2003 4:01 AM > > > > > > To: Alexander Rau (private); anaconda-devel-list@xxxxxxxxxx > > > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a > > > single > > > > > > CD > > > > > > > > > > > > I am at a very begin stage of making a custom CD. Still trying to > > > work > > > > > > out hdlist and comps.xml. Can you tell me if you install the full > > > > > > package in the @core and @base group? In my case, I didn't > > > install all > > > > > > of the packages in neither both @core or @base. I also added > > > couple > > > > > > others. I include a list of all packages that were install below > > > from > > > > > > my ks.cfg. I was just wondering when do I have to rebuild > > > comps.xml? > > > > > > > > > > > > %packages > > > > > > -anacron > > > > > > -apmd > > > > > > -ash > > > > > > -at > > > > > > -bc > > > > > > -cyrus-sasl-plain > > > > > > -dhclient > > > > > > -dos2unix > > > > > > -dump > > > > > > -fbset > > > > > > -finger > > > > > > file > > > > > > -gmp > > > > > > -gpm > > > > > > -hotplug > > > > > > -irda-utils > > > > > > -isdn4k-utils > > > > > > -jfsutils > > > > > > -kernel-pcmcia-cs > > > > > > -krbafs > > > > > > -ksymoops > > > > > > -lftp > > > > > > -lha > > > > > > -libwvstreams > > > > > > -lilo > > > > > > -lokkit > > > > > > -lrzsz > > > > > > -MAKEDEV > > > > > > -minicom > > > > > > -mtools > > > > > > -mtr > > > > > > -mt-st > > > > > > -nfs-utils > > > > > > nss_ldap > > > > > > -pam_krb5 > > > > > > -pam_smb > > > > > > -parted > > > > > > -pax > > > > > > -ppp > > > > > > -pyOpenSSL > > > > > > -python > > > > > > -python-optik > > > > > > -pyxf86config > > > > > > -raidtools > > > > > > -rdate > > > > > > -rdist > > > > > > -redhat-config-mouse > > > > > > -redhat-config-network-tui > > > > > > -reiserfs-utils > > > > > > -rhnlib > > > > > > -rhpl > > > > > > -rmt > > > > > > -rpm-python > > > > > > -rp-pppoe > > > > > > -rsync > > > > > > -setserial > > > > > > -specspo > > > > > > -star > > > > > > -statserial > > > > > > -stunnel > > > > > > -talk > > > > > > -tcsh > > > > > > #-time > > > > > > -unix2dos > > > > > > -up2date > > > > > > -usbutils > > > > > > -whois > > > > > > -wireless-tools > > > > > > -wvdial > > > > > > -ypbind > > > > > > -yp-tools > > > > > > > > > > > > # Additional Package > > > > > > #anaconda-runtime > > > > > > bind > > > > > > caching-nameserver > > > > > > gd > > > > > > freetype > > > > > > #kernel-source > > > > > > mgetty > > > > > > mrtg > > > > > > perl-CGI > > > > > > perl-URI > > > > > > ntp > > > > > > libcap > > > > > > pine > > > > > > psacct > > > > > > redhat-rpm-config > > > > > > rpmdb-redhat > > > > > > symlinks > > > > > > sysreport > > > > > > vlock > > > > > > xinetd > > > > > > > > > > > > # Developer Package > > > > > > #-aspell > > > > > > autoconf > > > > > > automake > > > > > > binutils > > > > > > bison > > > > > > byacc > > > > > > cpp > > > > > > dev86 > > > > > > flex > > > > > > gcc > > > > > > gcc-c++ > > > > > > gcc-objc > > > > > > glibc-devel > > > > > > glibc-kernheaders > > > > > > glibc-profile > > > > > > #-libjpeg > > > > > > libjpeg > > > > > > libobjc > > > > > > #-libpng > > > > > > libpng > > > > > > #-libpng10 > > > > > > libstdc++-devel > > > > > > libtool > > > > > > #-libtool-libs > > > > > > m4 > > > > > > #-make > > > > > > patch > > > > > > #-pspell > > > > > > rpm-build > > > > > > > > > > > > dwc > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Alexander Rau (private) [mailto:alexander_rau@xxxxxxxxx] > > > > > > Sent: Friday, August 01, 2003 5:17 PM > > > > > > To: Chan, Dominic; anaconda-devel-list@xxxxxxxxxx > > > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a > > > single > > > > > > CD > > > > > > > > > > > > I used that link and mostly this mailing list and articles on the > > > > > > internet. I have the whole file at home. I can send you some more > > > links > > > > > > during the weekend. > > > > > > > > > > > > Mostly trial and error and then asking this list brought me to > > > where I > > > > > > am now (Miles from where I want to be but closer is better than > > > > > > nothing). > > > > > > > > > > > > I have included kickstart (ks.cfg) but have not been really > > > successful > > > > > > with it. This is the next hurdle to master. > > > > > > > > > > > > What have you accomplished so far? > > > > > > > > > > > > AR > > > > > > > > > > > > -----Original Message----- > > > > > > From: Chan, Dominic [mailto:DWC@xxxxxxxxxxxx] > > > > > > Sent: Friday, August 01, 2003 5:11 PM > > > > > > To: anaconda-devel-list@xxxxxxxxxx > > > > > > Cc: Alexander Rau (private) > > > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a > > > single > > > > > > CD > > > > > > > > > > > > Cool, did you following the direction on the link you send me? Do > > > you > > > > > > have your own write up on this? Did you embed kickstart with your > > > CD? > > > > > > > > > > > > dwc > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Alexander Rau (private) [mailto:alexander_rau@xxxxxxxxx] > > > > > > Sent: Friday, August 01, 2003 4:33 PM > > > > > > To: Chan, Dominic > > > > > > Cc: anaconda-devel-list@xxxxxxxxxx > > > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a > > > single > > > > > > CD > > > > > > > > > > > > Please use the list, too, when you reply > > > anaconda-devel-list@xxxxxxxxxx > > > > > > > > > > > > Anyways, I have it down to one CD so far including the Base, Core > > > and > > > > > > X-Window system. > > > > > > > > > > > > Next I would like to add Gnome. > > > > > > > > > > > > AR > > > > > > > > > > > > > > > > > > Alexander Rau, Dipl.-Betriebswirt, A+, MCP, MCSA, MCSE > > > > > > > > > > > > Customer and Agent Relations & IT Manager > > > > > > > > > > > > Schleese Saddlery Service Ltd > > > > > > > > > > > > Phone: 1-800-225-2242 ext. 29 > > > > > > > > > > > > Fax: 1-905-898-8399 > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Chan, Dominic [mailto:DWC@xxxxxxxxxxxx] > > > > > > Sent: Friday, August 01, 2003 4:24 PM > > > > > > To: Alexander Rau (private) > > > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a > > > single > > > > > > CD > > > > > > > > > > > > How far did you get? At this point in time, I would be happy to > > > trim > > > > > > down from 3 cd and a floppy to just one cd and a floppy. I don't > > > ever > > > > > > care if the ks.cfg is on the cd or not > > > > > > > > > > > > dwc > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Alexander Rau (private) [mailto:alexander_rau@xxxxxxxxx] > > > > > > Sent: Friday, August 01, 2003 1:47 PM > > > > > > To: Chan, Dominic; anaconda-devel-list@xxxxxxxxxx > > > > > > Subject: RE: How to Create a Custom Bootable Redhat 9.0 CD on a > > > single > > > > > > CD > > > > > > > > > > > > I am/was having the same problem Unfortunately I wasn't able to > > > find a > > > > > > how-to geared to RH0 either. > > > > > > > > > > > > However this article here > > > > > > http://www.linuxjournal.com/article.php?sid=6473 > > > > > > > > > > > > Was the most helpful so far. > > > > > > > > > > > > > > > > > > AR > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: anaconda-devel-list-admin@xxxxxxxxxx > > > > > > [mailto:anaconda-devel-list-admin@xxxxxxxxxx] On Behalf Of Chan, > > > Dominic > > > > > > Sent: Friday, August 01, 2003 1:34 PM > > > > > > To: anaconda-devel-list@xxxxxxxxxx > > > > > > Subject: How to Create a Custom Bootable Redhat 9.0 CD on a single > > > CD > > > > > > > > > > > > I am having trouble getting information on how to create a custom > > > > > > bootable CD for RedHat 9.0 I find few article for 7.3 and > > > earlier, but > > > > > > RedHat don't use the same comps file structure anymore. In any > > > case, do > > > > > > anyone know of any site or article that will show you how to > > > create a > > > > > > custom redhat 9.0 CD. > > > > > > > > > > > > What I have done so far is create a kickstart configuration. I am > > > able > > > > > > to an automatic install with the stock RedHat 9.0 CD and a floppy > > > > > > without a problem. Since our install contain only 188 packages, I > > > would > > > > > > like to create a single CD that contain all of the RPM that is > > > require > > > > > > from disc 1, 2, and 3 (also the core). And if possible, put my > > > ks.cfg > > > > > > file on the cd also (but this part for me right now would be > > > consider a > > > > > > bonus). > > > > > > > > > > > > >From what I gather so far, I have create a build directory under > > > /var > > > > > > call LZBuild > > > > > > > > > > > > Inside my /var/LZBuild, I have copy all of the contents from the > > > 1st CD > > > > > > to its (include the .discinfo file). Afterward, I copy the > > > missing RPM > > > > > > I need with my kickstart install from Disc 2 and Disc 3 into the > > > same > > > > > > RPMS folder under /var/LZBuild (the absolute path is > > > > > > /var/LZBuild/RedHat/RPMS/) > > > > > > > > > > > > Afterward, I delete some of the RPMS I didn't need from my new > > > > > > /var/LZBuild/RedHat/RPMS/ folders. Afterward, the folder size for > > > > > > /var/LZBuild is under 650 Meg. > > > > > > > > > > > > I then run the following command to update the hdlist file inside > > > my > > > > > > /var/LZBuild/RedHat/base/ folder (before I execute the command, I > > > delete > > > > > > the original hdlist and hdlist2 just to be sure. > > > > > > > > > > > > /usr/lib/anaconda-runtime/genhdlist --withnumbers --hdlist > > > > > > /var/LZBuild/RedHat/base/hdlist /var/LZBuild > > > > > > > > > > > > After this part, I am lose! How do I update the Comps file? What > > > > > > command/syntax do I use? I could use all the help I could get > > > please > > > > > > > > > > > > Dwc > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Anaconda-devel-list mailing list > > > > > > Anaconda-devel-list@xxxxxxxxxx > > > > > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Anaconda-devel-list mailing list > > > > > > Anaconda-devel-list@xxxxxxxxxx > > > > > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Anaconda-devel-list mailing list > > > > > > Anaconda-devel-list@xxxxxxxxxx > > > > > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > > > > -- > > > > > Brian Long | | | > > > > > Americas IT Hosting Sys Admin | .|||. .|||. > > > > > Cisco Linux Developer | ..:|||||||:...:|||||||:.. > > > > > Phone: (919) 392-7363 | C i s c o S y s t e m s > > > > > > > > > > > > > > > _______________________________________________ > > > > > Anaconda-devel-list mailing list > > > > > Anaconda-devel-list@xxxxxxxxxx > > > > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > > > > > _______________________________________________ > > Anaconda-devel-list mailing list > > Anaconda-devel-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > -- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s
