I'm trying to narrow down which options I need to pick in the initial installation for the following rpm's

lm_sensor
net_snmp
php_snmp
php_gd
icu

I think the lm_sensor and net_snmp are the net_snmp_utils option but I'm at a loss on the php's and icu. I select php but doesn't have either of those but there is about 5 other php choices I haven't tried yet. As for ICU I'm clueless on. Is there any master list or anything anywhere that tells what each option in the menu actually installs?

It would be of great help for us if you would tell us the distro, version, and arch of the system you are running(F8 64bit). Without that information it is pretty difficult to answer any question.

Sorry it's Oracle Enterprise but I'm also trying on RH 5. Oracle is 64-bit and RH I'm trying on a VM on my laptop is 32. The install is basically the same and my VM loads alot quicker for me to try things. I was able to figure out that the net-snmp-utils did take care of my lm_sensors and net-snmp but still can't find the other 3.

Ok is it RH5 or RHEL5? RH5 is very old, support for it was dropped about 2000(?). RHEL5 is still supported (current). You should be able to use "yum provides whateveryouneed" and it should spit out the name of the package that contains it. You will need different packages(versions)for the 64bit than you will for the 32bit.

LOL yeah RHEL5. Yum doesn't seem to tell me what I'm looking for.

yum install php-snmp

yum install php-gd

yum install icu

They are all three in the standard repo.

Right I know how to install them after the initial install but I'm trying to find these in the install. I'm trying to document this for future install for my guys in the field and trying to make this as simple as possible. Installing RPM's after the fact is what I'm trying to avoid.

I will take a guess that you have not worked with rpms (or linux)very much? The purpose of rpm is so that the users does not have to be concerned with where on the system all the parts are installed. You can just manually grab the rpms via browser if you are just looking for the rpms and then install them locally via "yum localinstall package". In order to keep the system up to date (secure) you are going to regularly install rpms. So trying to avoid installing rpms in the field is really self defeating.

This situation is a little different as this group is just doing the initial install and not maintaining the system, that will be handled by another department. And to try to keep some consistancy in all our various versions and product installs we do I'm trying to avoid any RPM installation after the install. Some of the guys are windows guys and command line stuff is a little tricky at times for them. Our installs are fairly stripped down with the gnome and such not installed so it's all command line driven and in most situations the customer is not allowing access to the internet or outside world, so our support department will handle which updates are necessary. So far from our previous install document I've found about 12 RPM's that were excluded and found all except the 3 in the initial installation package options.

well it looks like those 3 are aren't an option from the initial install. I got frustrated and tried a lengthy install of every option that was possible and it didn't install those three so I guess install them after the fact is the only option. Thanks for the help.

Usually what is done with machines like this is a private repo is built. You only place the rpms that your have approved (tested) in the repos. Building a private repo is relatively simple just take a look at the createrepo package. I hope you meant that you will not be installing any more software rather than any more rpms. Installing software on a rpm based system without using rpms will (long term) create many more problems than it will solve.