From sr at genyosha.net Wed Dec 6 22:27:40 2006 From: sr at genyosha.net (Steve Rikli) Date: Wed, 6 Dec 2006 22:27:40 +0000 (UTC) Subject: determine VGA vs. ttyS* console in %pre ? Message-ID: Is there a way during %pre to determine what the console is? My PXE setup has several options for installation, one of which is booting kernel with "append console=ttyS0" for serial installation, rather than VGA -- the person doing the install can choose. At the moment, to use the different console configurations I specify a different ks.cfg file with different bootloader args, e.g. a PXE with the above console setting would use this: bootloader --append="console=tty0 console=ttyS0,9600n8" whereas a PXE with no serial console specified might just use: bootloader or other similar permutations in each ks.cfg file. If something could be done in %pre to determine what the booted kernel believes is the console, I imagine an %include file could be constructed based on the result, which would be populated with "bootloader " appropriate for the type of installation console being used. I was poking around e.g. in /proc/tty/ but nothing I see there seems to be applicable to this purpose. In a nutshell, I'm trying to craft a modular ks.cfg file rather than separate ks.cfg files for VGA and serial console. Same sort of idea as many others have done in %pre , e.g. to derive disk number/type/size and build a %include file with "part ". Hints/ideas/etc. welcome. Cheers, sr. -- || Steve Rikli ||| You can use all the quantitative data you || || Systems Administrator ||| can get, but you still have to distrust || || ||| it and use your own intelligence and || || sr at genyosha.net ||| judgment. - Alvin Toffler || From Arnaud.Gomes at ircam.fr Wed Dec 6 22:41:34 2006 From: Arnaud.Gomes at ircam.fr (Arnaud Gomes-do-Vale) Date: Wed, 06 Dec 2006 23:41:34 +0100 Subject: determine VGA vs. ttyS* console in %pre ? In-Reply-To: (Steve Rikli's message of "Wed, 6 Dec 2006 22:27:40 +0000 (UTC)") References: Message-ID: Hi, sr at genyosha.net (Steve Rikli) writes: > Is there a way during %pre to determine what the console is? The easiest (only?) way would be parsing /proc/cmdline. -- Arnaud From sr at genyosha.net Thu Dec 7 00:47:22 2006 From: sr at genyosha.net (Steve Rikli) Date: Thu, 7 Dec 2006 00:47:22 +0000 (UTC) Subject: determine VGA vs. ttyS* console in %pre ? References: Message-ID: In article , Arnaud Gomes-do-Vale wrote: >sr at genyosha.net (Steve Rikli) writes: > >> Is there a way during %pre to determine what the console is? > >The easiest (only?) way would be parsing /proc/cmdline. Yes, excellent! I ought to be able to make use of that -- thanks. Cheers, sr. -- || Steve Rikli ||| || || Systems Administrator ||| If we knew what we were doing, it || || ||| wouldn't be research. || || sr at genyosha.net ||| || From debian at herakles.homelinux.org Thu Dec 7 01:22:00 2006 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 07 Dec 2006 10:22:00 +0900 Subject: determine VGA vs. ttyS* console in %pre ? In-Reply-To: References: Message-ID: <45776CB8.4070506@herakles.homelinux.org> Steve Rikli wrote: > In article , > Arnaud Gomes-do-Vale wrote: > >>sr at genyosha.net (Steve Rikli) writes: >> >> >>>Is there a way during %pre to determine what the console is? >> >>The easiest (only?) way would be parsing /proc/cmdline. > > > Yes, excellent! I ought to be able to make use of that -- thanks. I'm mildly confused... What you will see in the commandline is those console arguments. It's how the kernel knows what to use. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ Please do not reply off-list From andre.ruiz at gmail.com Thu Dec 7 16:07:16 2006 From: andre.ruiz at gmail.com (Andre Ruiz) Date: Thu, 7 Dec 2006 13:07:16 -0300 Subject: determine VGA vs. ttyS* console in %pre ? In-Reply-To: <45776CB8.4070506@herakles.homelinux.org> References: <45776CB8.4070506@herakles.homelinux.org> Message-ID: <68d97fc90612070807i58bac8a1oee88a650ea4ce11b@mail.gmail.com> What about the tty command? $ tty /dev/pts/0 I have no idea what it would output on each case, but it is worth a try. You may have to put the tty binary on the cd if it's not already on the installer. Finally, you could analyse it and mimic it's behavior (if it's just looking up something in /proc). andre On 12/6/06, John Summerfield wrote: > Steve Rikli wrote: > > In article , > > Arnaud Gomes-do-Vale wrote: > > > >>sr at genyosha.net (Steve Rikli) writes: > >> > >> > >>>Is there a way during %pre to determine what the console is? > >> > >>The easiest (only?) way would be parsing /proc/cmdline. > > > > > > Yes, excellent! I ought to be able to make use of that -- thanks. > > I'm mildly confused... What you will see in the commandline is those > console arguments. It's how the kernel knows what to use. > > > > -- > > Cheers > John > > -- spambait > 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu > Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ > > Please do not reply off-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Andre Ruiz Curitiba, PR, Brasil From sr at genyosha.net Fri Dec 8 21:12:25 2006 From: sr at genyosha.net (Steve Rikli) Date: Fri, 8 Dec 2006 21:12:25 +0000 (UTC) Subject: determine VGA vs. ttyS* console in %pre ? References: <45776CB8.4070506@herakles.homelinux.org> Message-ID: In article <45776CB8.4070506 at herakles.homelinux.org>, John Summerfield wrote: >Steve Rikli wrote: >> In article , >> Arnaud Gomes-do-Vale wrote: >>>sr at genyosha.net (Steve Rikli) writes: >>> >>>>Is there a way during %pre to determine what the console is? >>> >>>The easiest (only?) way would be parsing /proc/cmdline. >> >> Yes, excellent! I ought to be able to make use of that -- thanks. > >I'm mildly confused... What you will see in the commandline is those >console arguments. It's how the kernel knows what to use. Exactly -- and that's what I was after. `grep console= /proc/cmdline` and playing sed games with a script during %pre gives me the "console=" stuff which was appended to the kernel during PXE. I.e. my script could return something like "ttyS0,9600n8" for a serial console install, and "" for a VGA install. That script in %pre builds a very simple %include file which contains a "bootloader --append=" string, which I then use in the general section of ks.cfg . One less bit of hardcoded data in all my ks.cfg files -- thanks to all! cheers, sr. -- || Steve Rikli ||| It's kind of fun to do the impossible. || || Systems Administrator ||| || || ||| - Walt Disney || || sr at genyosha.net ||| || From debian at herakles.homelinux.org Fri Dec 8 21:37:23 2006 From: debian at herakles.homelinux.org (John Summerfield) Date: Sat, 09 Dec 2006 06:37:23 +0900 Subject: determine VGA vs. ttyS* console in %pre ? In-Reply-To: References: <45776CB8.4070506@herakles.homelinux.org> Message-ID: <4579DB13.10001@herakles.homelinux.org> Steve Rikli wrote: >> >>I'm mildly confused... What you will see in the commandline is those >>console arguments. It's how the kernel knows what to use. > > > Exactly -- and that's what I was after. > > `grep console= /proc/cmdline` and playing sed games with a script > during %pre gives me the "console=" stuff which was appended > to the kernel during PXE. > > I.e. my script could return something like "ttyS0,9600n8" for a > serial console install, and "" for a VGA install. > > That script in %pre builds a very simple %include file which contains > a "bootloader --append=" string, which I then use in the general > section of ks.cfg . > > One less bit of hardcoded data in all my ks.cfg files -- thanks to all! When you want answers to Qs like this, it's a good idea to switch to the shell on tty2 and have a look around. There's useful stuff in /proc (commandline for the kernel, maybe some stuff for processes), there's the environment - the console stuff may be there too. You _can_ find your server if you're doing ftp/http (nfs too I think), and potentially get more info there, perhaps a profile or script that makes futher customisations. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From aleahy at knox.edu Fri Dec 8 22:24:48 2006 From: aleahy at knox.edu (Andrew Leahy) Date: Fri, 08 Dec 2006 16:24:48 -0600 Subject: What's wrong with this ks.cfg? Message-ID: <4579E630.9050700@knox.edu> Greetings, I've been using kickstart to configure a small computing lab since FC2. Generally, I've had great luck with it, but I'm having a heck of a time trying to update my ks.cfg file (attached) to FC6. From what I can tell, at least three things are failing in the script: 1. The root password never gets written. 2. authconfig fails with the error message (on VT1): "authconfig: unexpected argument" 3. xconfig will not work configure xorg.conf, complaining that the "requested resolution 1280x1024 is not supported . . . " I'm guessing that #1 occurs because of #2. Here's my syntax for authconfig: authconfig --enableshadow --enablemd5 --enablecache --enableldap --enableldapauth --ldapserver=leibniz.lab.knet.edu --ldapbasedn="o=knox college,c=us" --enablekrb5 --krb5realm=KNOX.EDU --krb5kdc=knoxsrdr.knox.edu --krb5adminserver=knoxsrdr.knox.edu authconfig from the commandline will fail with the same error _if_ the quotation marks around the ldapbasedn argument are removed and, low and behold, when I look at the anaconda-ks.cfg that is generated from the installation that is exactly how the authconfig line is written--without the quotes. Is this a known bug? Is there any way around it? I'm equally flummoxed by the xconfig problems. Here are the relevant lines from ks.cfg. xconfig --driver=nv --depth=24 --resolution=1280x1024 --defaultdesktop=KDE --startxonboot --videoram=65535 monitor --monitor="HP A4033A 21-inch Display" I've also tried an alternative monitor line with --hsync and --vsync specified manually. Same luck. Again, I can configure the system with no problem using system-config-display. Any ideas? Thanks for your help. Andrew Leahy -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ks.cfg-stripped URL: From sr at genyosha.net Fri Dec 8 23:09:32 2006 From: sr at genyosha.net (Steve Rikli) Date: Fri, 8 Dec 2006 23:09:32 +0000 (UTC) Subject: determine VGA vs. ttyS* console in %pre ? References: <45776CB8.4070506@herakles.homelinux.org> <4579DB13.10001@herakles.homelinux.org> Message-ID: In article <4579DB13.10001 at herakles.homelinux.org>, John Summerfield wrote: >Steve Rikli wrote: > >> ... >> Exactly -- and that's what I was after. >> >> `grep console= /proc/cmdline` and playing sed games with a script >> during %pre gives me the "console=" stuff which was appended >> to the kernel during PXE. >> >> I.e. my script could return something like "ttyS0,9600n8" for a >> serial console install, and "" for a VGA install. >> >> That script in %pre builds a very simple %include file which contains >> a "bootloader --append=" string, which I then use in the general >> section of ks.cfg . >> >> One less bit of hardcoded data in all my ks.cfg files -- thanks to all! > >When you want answers to Qs like this, it's a good idea to switch to the >shell on tty2 and have a look around. Indeed -- that's just what I had been doing, but simply hadn't looked in the "right" places -- e.g. /proc/tty/ et al, as I mentioned in the original post. The hint about /proc/cmdline/ took me right where I needed to go. For this, and other potentially useful information. :-) > There's useful stuff in /proc >(commandline for the kernel, maybe some stuff for processes), there's >the environment - the console stuff may be there too. Some, but nothing else I've seen so far has proved as useful as /proc/cmdline/ for this particular "what's the console?" purpose. One of the first things I did when starting Kickstart work was run a handful of simple things in %post to figure out "what's available"; e.g. the shell environment, as you mentioned, and basic commands like 'df' and 'ps' and 'env' and etc., just to look for interesting things to make use of during the install. >You _can_ find your server if you're doing ftp/http (nfs too I think), >and potentially get more info there, perhaps a profile or script that >makes futher customisations. Exactly -- the basic routine I've seen here and elsewhere, and have happily taken advantage of: - run a small script (or just shell commands) in %pre - use that to build a customized %include - use %include in general or %post is a very useful notion for many types of cat-skinning. :) Cheers, sr. -- || Steve Rikli ||| || || Systems Administrator ||| Good, fast, cheap: choose any two. || || ||| || || sr at genyosha.net ||| || From ahopcroft at uk.ibm.com Sat Dec 9 04:00:14 2006 From: ahopcroft at uk.ibm.com (Alex Hopcroft) Date: Sat, 9 Dec 2006 04:00:14 +0000 Subject: Alex Hopcroft/UK/IBM is out of the office. Message-ID: I will be out of the office starting 07/12/2006 and will not return until 11/12/2006. For issues regarding ongoing projects please contact the Unified Unix Team Leader, Sue Emmerson (44-113-390-1575) who will be able to assit. Alternatively I will respond to your message when I return. From mrowley at esoft.com Wed Dec 13 23:53:42 2006 From: mrowley at esoft.com (mat) Date: Wed, 13 Dec 2006 16:53:42 -0700 Subject: Bootable kickstart CD Message-ID: <45809286.1000103@esoft.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am in the process of creating a bootable cd which uses kickstart to automatically install a set of software then reboots the machines. I have encountered many problems, and want all packages to be included on the CD. I have not seen any manuals, or how-to guides anywhere. If has any they can point me to, it would be very appreciated. One last question I have, what happened to the 'genhdlist' in anaconda-runtime package for Fedora Core 6? (I know this is a redhat list, and sorry if that question was off topic) Thanks in advance! - -- \\ Mathew Rowley \\ eSoft Inc. \\ email: echo 'kpmujcw>cqmdr,amk'|perl -pe 's/(.)/chr(ord($1)+2)/ge;' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFgJKG47s/xIwy7o0RAgnjAJ91e/o6BjySyoYq9t+3FNOcfMVWawCghl2v EKVwb2niUVUhtMdrxCpzPWc= =mPoY -----END PGP SIGNATURE----- From mrowley at esoft.com Wed Dec 13 23:57:52 2006 From: mrowley at esoft.com (mat) Date: Wed, 13 Dec 2006 16:57:52 -0700 Subject: Dep list Message-ID: <45809380.2030109@esoft.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there an easy way, given an rpm, to see the list of DEPS from the original spec file? Or, even better, a tool that will create a list of dependant packages given one package? Im trying to get a list of RPMS which i need to include to install one specific application. Thanks. - -- \\ Mathew Rowley \\ eSoft Inc. \\ email: echo 'kpmujcw>cqmdr,amk'|perl -pe 's/(.)/chr(ord($1)+2)/ge;' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFgJN/47s/xIwy7o0RAplPAJ9/bi6XuZMXwe8oYR5b2a3ElSAHKACfULqU TH2/jqLv/niXTuhnOqUnV8I= =E9oA -----END PGP SIGNATURE----- From andre.ruiz at gmail.com Thu Dec 14 04:08:55 2006 From: andre.ruiz at gmail.com (Andre Ruiz) Date: Thu, 14 Dec 2006 02:08:55 -0200 Subject: Dep list In-Reply-To: <45809380.2030109@esoft.com> References: <45809380.2030109@esoft.com> Message-ID: <68d97fc90612132008i56727a94o5ae55e0a53ce1561@mail.gmail.com> rpm -qpR file.rpm ? On 12/13/06, mat wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Is there an easy way, given an rpm, to see the list of DEPS from the > original spec file? Or, even better, a tool that will create a list of > dependant packages given one package? Im trying to get a list of RPMS > which i need to include to install one specific application. Thanks. > > > - -- > > > \\ Mathew Rowley > \\ eSoft Inc. > \\ email: echo 'kpmujcw>cqmdr,amk'|perl -pe 's/(.)/chr(ord($1)+2)/ge;' > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iD8DBQFFgJN/47s/xIwy7o0RAplPAJ9/bi6XuZMXwe8oYR5b2a3ElSAHKACfULqU > TH2/jqLv/niXTuhnOqUnV8I= > =E9oA > -----END PGP SIGNATURE----- > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Andre Ruiz Curitiba, PR, Brasil From john.j.poole at usa-spaceops.com Thu Dec 14 17:06:19 2006 From: john.j.poole at usa-spaceops.com (Poole, John J) Date: Thu, 14 Dec 2006 12:06:19 -0500 Subject: Bootable kickstart CD Message-ID: <5599C9E027D65D4DB3CB4C053953314260378C@usaflcms03.usa-spaceops.ksc.nasa.gov> For all packages, I use: %packages --resolvedeps @everything -----Original Message----- From: mat [mailto:mrowley at esoft.com] Sent: Wednesday, December 13, 2006 6:54 PM To: kickstart-list at redhat.com Subject: Bootable kickstart CD -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am in the process of creating a bootable cd which uses kickstart to automatically install a set of software then reboots the machines. I have encountered many problems, and want all packages to be included on the CD. I have not seen any manuals, or how-to guides anywhere. If has any they can point me to, it would be very appreciated. One last question I have, what happened to the 'genhdlist' in anaconda-runtime package for Fedora Core 6? (I know this is a redhat list, and sorry if that question was off topic) Thanks in advance! - -- \\ Mathew Rowley \\ eSoft Inc. \\ email: echo 'kpmujcw>cqmdr,amk'|perl -pe 's/(.)/chr(ord($1)+2)/ge;' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFgJKG47s/xIwy7o0RAgnjAJ91e/o6BjySyoYq9t+3FNOcfMVWawCghl2v EKVwb2niUVUhtMdrxCpzPWc= =mPoY -----END PGP SIGNATURE----- From Keith.Harner at freescale.com Thu Dec 14 17:23:30 2006 From: Keith.Harner at freescale.com (Harner Keith-FKH006) Date: Thu, 14 Dec 2006 10:23:30 -0700 Subject: Bootable kickstart CD In-Reply-To: <5599C9E027D65D4DB3CB4C053953314260378C@usaflcms03.usa-spaceops.ksc.nasa.gov> Message-ID: Slightly off topic, but.... How do I determine the name to use to disable a specific package? Is it in the XML package listing? Is there an easier way? Keith Harner Engineering Compute Phone: 480-413-8625 Pager: 7393862 at skytel.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Poole, John J Sent: Thursday, December 14, 2006 10:06 AM To: Discussion list about Kickstart Subject: RE: Bootable kickstart CD For all packages, I use: %packages --resolvedeps @everything -----Original Message----- From: mat [mailto:mrowley at esoft.com] Sent: Wednesday, December 13, 2006 6:54 PM To: kickstart-list at redhat.com Subject: Bootable kickstart CD -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am in the process of creating a bootable cd which uses kickstart to automatically install a set of software then reboots the machines. I have encountered many problems, and want all packages to be included on the CD. I have not seen any manuals, or how-to guides anywhere. If has any they can point me to, it would be very appreciated. One last question I have, what happened to the 'genhdlist' in anaconda-runtime package for Fedora Core 6? (I know this is a redhat list, and sorry if that question was off topic) Thanks in advance! - -- \\ Mathew Rowley \\ eSoft Inc. \\ email: echo 'kpmujcw>cqmdr,amk'|perl -pe 's/(.)/chr(ord($1)+2)/ge;' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFFgJKG47s/xIwy7o0RAgnjAJ91e/o6BjySyoYq9t+3FNOcfMVWawCghl2v EKVwb2niUVUhtMdrxCpzPWc= =mPoY -----END PGP SIGNATURE----- _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From debian at herakles.homelinux.org Fri Dec 15 14:17:43 2006 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 15 Dec 2006 23:17:43 +0900 Subject: Bootable kickstart CD In-Reply-To: <45809286.1000103@esoft.com> References: <45809286.1000103@esoft.com> Message-ID: <4582AE87.5030403@herakles.homelinux.org> mat wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I am in the process of creating a bootable cd which uses kickstart to > automatically install a set of software then reboots the machines. I > have encountered many problems, and want all packages to be included on > the CD. I have not seen any manuals, or how-to guides anywhere. If has > any they can point me to, it would be very appreciated. One last > question I have, what happened to the 'genhdlist' in anaconda-runtime > package for Fedora Core 6? (I know this is a redhat list, and sorry if > that question was off topic) I did something very like this, but for a network install. Here's what I think will work. 1. Loop-mount the ISO (or mount the boot disk), 2. Find the relevant initial ramdisk in the isolinux directory. 3. Copy it to somewhere you can read/write. 4. Uncompress it using gunzip: mv initrd initrd.gz gunzip initrd You now have a file with the original name, you can play with it, and you don't _have_ to compress it. 5. Unpack the initial ramdisk; it's a cpio archive, easily done. 6. Put your ks file into the inird root directory 7. Create a new file initrd using cpio 8. Optionally, copy the isolinux are to where you can edit it. Change the boot params. Note, it might be simplest to unpack the entire ISO:-) 9. Use a magic incantation as you use mkisofs to make a new ISO image. Note, I mostly do network installs. My procedure is necessarily a little different from what you want, as I use a PXE layout that generally has my kernel etc outside my install tree, so I don't have to worry about putting it all back togetner. Here are some useful fragments gleamed from my .bash_history: cd /tftpboot/PXE/linux-install/RHEL/4.90/initrd cpio --extract --make-directories --preserve-modification-time \ --numeric-uid-gid <../initrd.img.orig find . | sort | cpio --help >../initrd.img label jerry kernel /linux-install/RHEL/4.90/vmlinuz append initrd=/linux-install/RHEL/4.90/initrd.img \ ramdisk_size=8192 ksdevice=link vga=6 ks=file:///jerry.ks upgradeany Note the ks= - this specifies the ks file inside the initrd image. pushd initrd;find . | sort | cpio --create -c | gzip -9 \ > ../initrd.img ;popd;ls -l Oh, I did compress it! -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From rh-kickstart at matthouse.com Wed Dec 27 19:07:14 2006 From: rh-kickstart at matthouse.com (Matt Sturtz) Date: Wed, 27 Dec 2006 12:07:14 -0700 (MST) Subject: Pear-down RPMS dir Message-ID: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> Hi-- I wanted pear down the RPMS directory after I was done editing comps.xml to fit my needs. A lot of packages are no longer required, and I wanted to eliminate them. I started with a script that simply removes all packages that aren't mentioned in my customized comps.xml -- but that eliminates packages like bind-libs, which I know is needed to satisfy a dependancy, even though it isn't mentioned in comps.xml (bind-utils depends on libdns, which is provided by bind-libs). Anybody know of a tool I can use to remove the packages that aren't required while leaving those that are, and those that satisfy dependancies for those that are? The idea of querying dependancies for every single package doesn't thrill me... Kickstarting a box, and then removing all the packages that didn't end up on that box sounds even worse... -Matt- From mrowley at esoft.com Wed Dec 27 19:06:59 2006 From: mrowley at esoft.com (Mathew Rowley) Date: Wed, 27 Dec 2006 12:06:59 -0700 Subject: Pear-down RPMS dir In-Reply-To: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> References: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> Message-ID: <1GzeWi-0007QY-7E@mrowley> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I came into a similar problem, and wrote this php script that you can run via command line; it will give you all deps based on rpm -qpR and rpm -qR commands. Although i never used it, feel free to do what you like with it. Hope it helps. On Wed, 27 Dec 2006 12:07:14 -0700 (MST) "Matt Sturtz" wrote: > Hi-- > > I wanted pear down the RPMS directory after I was done editing > comps.xml to fit my needs. A lot of packages are no longer required, > and I wanted to eliminate them. I started with a script that simply > removes all packages that aren't mentioned in my customized comps.xml > -- but that eliminates packages like bind-libs, which I know is > needed to satisfy a dependancy, even though it isn't mentioned in > comps.xml (bind-utils depends on libdns, which is provided by > bind-libs). > > Anybody know of a tool I can use to remove the packages that aren't > required while leaving those that are, and those that satisfy > dependancies for those that are? The idea of querying dependancies > for every single package doesn't thrill me... Kickstarting a box, > and then removing all the packages that didn't end up on that box > sounds even worse... > > -Matt- > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list - -- \\ Mathew Rowley \\ eSoft Inc. \\ email: echo 'kpmujcw>cqmdr,amk'|perl -pe 's/(.)/chr(ord($1)+2)/ge;' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFksRX47s/xIwy7o0RAvubAJ94wcGyB1VAMw5/FZZd947lC9Ar7wCcD4T7 7JV+CVwVcJZNEimhG7T8WPk= =VSDN -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: rpmRecurDep.php Type: application/x-php Size: 2150 bytes Desc: not available URL: From herrold at owlriver.com Wed Dec 27 19:50:50 2006 From: herrold at owlriver.com (R P Herrold) Date: Wed, 27 Dec 2006 14:50:50 -0500 (EST) Subject: Paring a pair of pears; was: Pear-down RPMS dir In-Reply-To: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> References: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> Message-ID: On Wed, 27 Dec 2006, Matt Sturtz wrote: > Anybody know of a tool I can use to remove the packages that aren't > required while leaving those that are, and those that satisfy dependancies > for those that are? The idea of querying dependancies for every single > package doesn't thrill me... Kickstarting a box, and then removing all > the packages that didn't end up on that box sounds even worse... Almost all can be done hands off. 1. do an install; 2. pare to taste on an automated basis; http://www.owlriver.com/tips/tiny-centos/ 3. verify completeness: http://www.owlriver.com/tips/broken-system/ 4. run and capture to file: rpm -qa --qf '%{name}\n' | sort 5. walk that list amd make sure all listed packages are present ... note -- as %pre and %post elements are not dependency checked, and are able to hold Turing complete aspects, TEST - Russ Herrold From ahopcroft at uk.ibm.com Wed Dec 27 20:02:52 2006 From: ahopcroft at uk.ibm.com (Alex Hopcroft) Date: Wed, 27 Dec 2006 20:02:52 +0000 Subject: Alex Hopcroft/UK/IBM is out of the office. Message-ID: I will be out of the office starting 25/12/2006 and will not return until 02/01/2007. For issues regarding ongoing projects please contact the Unified Unix Team Leader, Sue Emmerson (44-113-390-1575) who will be able to assit. Alternatively I will respond to your message when I return. From debian at herakles.homelinux.org Wed Dec 27 22:25:39 2006 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 28 Dec 2006 07:25:39 +0900 Subject: Pear-down RPMS dir In-Reply-To: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> References: <3850.165.236.183.1.1167246434.squirrel@raven.ontheside.net> Message-ID: <4592F2E3.6050101@herakles.homelinux.org> Matt Sturtz wrote: > Hi-- > > I wanted pear down the RPMS directory after I was done editing comps.xml I was wondering what the heck you were talking about;-) Pare, not pear. Pear is fruit (unless it's PHP-related software). Pare is "trim." The easiest way I know to discover whar files (including but not only rpms) is to do an http install, then peruse the log. You can also (if you do things a little differently) use the log to optimise the order in the ISO. > to fit my needs. A lot of packages are no longer required, and I wanted > to eliminate them. I started with a script that simply removes all > packages that aren't mentioned in my customized comps.xml -- but that > eliminates packages like bind-libs, which I know is needed to satisfy a > dependancy, even though it isn't mentioned in comps.xml (bind-utils > depends on libdns, which is provided by bind-libs). > > Anybody know of a tool I can use to remove the packages that aren't > required while leaving those that are, and those that satisfy dependancies > for those that are? The idea of querying dependancies for every single > package doesn't thrill me... Kickstarting a box, and then removing all > the packages that didn't end up on that box sounds even worse... -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list