I have a *large* repository of rpm updates on an ftp server that i use
to update my RedHat ES3 servers after the OS install, I use the command


rpm -Uvh ftp://server/path/to/*.rpm


problem is, the number of rpm files has grown enormously, I am sure a
lot of them are not being installed.


is there a way to tell which rpms were actually installed, so that i
can delete the unneeded ones from the ftp server?


thanks

tsiwut@yahoo.com wrote:

> I have a *large* repository of rpm updates on an ftp server that i use
> to update my RedHat ES3 servers after the OS install, I use the command
>
>
> rpm -Uvh ftp://server/path/to/*.rpm
>
>
> problem is, the number of rpm files has grown enormously, I am sure a
> lot of them are not being installed.

How do you know?

>
>
> is there a way to tell which rpms were actually installed, so that i
> can delete the unneeded ones from the ftp server?

rpm -qa

>
>
> thanks

<tsiwut@yahoo.com> wrote in message
news:1105172936.675955.50820@c13g2000cwb.googlegro ups.com...
>I have a *large* repository of rpm updates on an ftp server that i use
> to update my RedHat ES3 servers after the OS install, I use the command
>
>
> rpm -Uvh ftp://server/path/to/*.rpm
>
>
> problem is, the number of rpm files has grown enormously, I am sure a
> lot of them are not being installed.

ES 3 is out? Good.

> is there a way to tell which rpms were actually installed, so that i
> can delete the unneeded ones from the ftp server?

Dude, you need to lean to use yum. It's available in Fedora Core, it's
available for RedHat Enterprise [add meanlingless suffix] at lots of mirror
sites, and it's very handy for both generating a list of the up-to-date
packages, managing their dependencies, and for doing such large updates as a
single line command from an FTP site *efficiently*.

"Nico Kadel-Garcia" <nkadel@comcast.net> wrote in message
news:JqGdnelKLbreUELcRVn-qA@comcast.com...
>
> <tsiwut@yahoo.com> wrote in message
> news:1105172936.675955.50820@c13g2000cwb.googlegro ups.com...
>>I have a *large* repository of rpm updates on an ftp server that i use
>> to update my RedHat ES3 servers after the OS install, I use the command
>>
>>
>> rpm -Uvh ftp://server/path/to/*.rpm
>>
>>
>> problem is, the number of rpm files has grown enormously, I am sure a
>> lot of them are not being installed.
>
> ES 3 is out? Good.

Excuse me, ES 3 has been out for a while. I've been waiting on ES 4, which
has been slow in arrival.

tsiwut@yahoo.com wrote:

> I have a *large* repository of rpm updates on an ftp server that i use
> to update my RedHat ES3 servers after the OS install, I use the command
>
>
> rpm -Uvh ftp://server/path/to/*.rpm
>
>
> problem is, the number of rpm files has grown enormously, I am sure a
> lot of them are not being installed.
>
>
> is there a way to tell which rpms were actually installed, so that i
> can delete the unneeded ones from the ftp server?
>
>
> thanks


Use the rpm -F (freshen) instead of the -U. The -F will only update packages
that are installed the -U will install anything that is not install and
update ones that are.

Nico Kadel-Garcia wrote:
> "Nico Kadel-Garcia" <nkadel@comcast.net> wrote in message
> news:JqGdnelKLbreUELcRVn-qA@comcast.com...
>
>><tsiwut@yahoo.com> wrote in message
>>news:1105172936.675955.50820@c13g2000cwb.googleg roups.com...
>>
>>>I have a *large* repository of rpm updates on an ftp server that i use
>>>to update my RedHat ES3 servers after the OS install, I use the command
>>>
>>>
>>>rpm -Uvh ftp://server/path/to/*.rpm
>>>
>>>
>>>problem is, the number of rpm files has grown enormously, I am sure a
>>>lot of them are not being installed.
>>
>>ES 3 is out? Good.
>
>
> Excuse me, ES 3 has been out for a while. I've been waiting on ES 4, which
> has been slow in arrival.
>
>
How slow? IIRC, ES3 came out in late 2003. One of the features of the RHEL
distributions is their long life. They do not come out with frequent new
releases. Their customers want stability, not the latest bells and
whistles. Here is part of what they say about it:

> Stability
>
> 12-18 month release cycle and seven years of support for every version.
> Upgradeability
>
> Upgrades to new versions are included with every Red Hat Enterprise Linux subscription.


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 14:20:00 up 8 days, 3:39, 3 users, load average: 4.16, 4.08, 4.08

> Dude, you need to lean to use yum.

Nod.

Right now your ftp command is downloading every single RPM every single
time and then stepping through each one to determine if it needs to
upgrade or not. If there are intermediate updates (you are on 1.1 and
there are .2 and 1.3 on your FTP site) it will do all the intermediate
updates (most unecessary).

When you initialize a yum repository, it builds an index on the server
(FTP or HTTP). THe client downloads only the index and then downloads
only the RPMS it needs (and the dependencies) to get the job done.
http://linux.duke.edu/yum/

thornton

"Jean-David Beyer" <jdbeyer@exit109.com> wrote in message
news:10u0d5cglnphl3e@corp.supernews.com...
> Nico Kadel-Garcia wrote:
>> "Nico Kadel-Garcia" <nkadel@comcast.net> wrote in message
>> news:JqGdnelKLbreUELcRVn-qA@comcast.com...
>>
>>><tsiwut@yahoo.com> wrote in message
>>>news:1105172936.675955.50820@c13g2000cwb.google groups.com...
>>>
>>>>I have a *large* repository of rpm updates on an ftp server that i use
>>>>to update my RedHat ES3 servers after the OS install, I use the command
>>>>
>>>>
>>>>rpm -Uvh ftp://server/path/to/*.rpm
>>>>
>>>>
>>>>problem is, the number of rpm files has grown enormously, I am sure a
>>>>lot of them are not being installed.
>>>
>>>ES 3 is out? Good.
>>
>>
>> Excuse me, ES 3 has been out for a while. I've been waiting on ES 4,
>> which has been slow in arrival.
> How slow? IIRC, ES3 came out in late 2003. One of the features of the RHEL
> distributions is their long life. They do not come out with frequent new
> releases. Their customers want stability, not the latest bells and
> whistles. Here is part of what they say about it:

It's been over a year. The 2.6 kernel is a big deal for server grade
hardware, especially SMP and drivers for recent devices, and they need to
move forward with that to provide corporate support. for it. I recognize
that Fedora Core is where they do their bleeding edge work, and that's just
fine. But I'm actually suggesting Beowulf users use Fedora Core rather than
RHEL because of the tardiness of the performance updates for heavy-duty iron
in RHEL.


>> Stability
>>
>> 12-18 month release cycle and seven years of support for every version.
>> Upgradeability
>>
>> Upgrades to new versions are included with every Red Hat Enterprise Linux
>> subscription.

Well, yes. And if the next version isn't out until 18 months or 24 months
after a major feature change such as the 2.6 kernel, theree's no point in
ever getting it for new hardware, since any hardware that RHEL will actually
run on is near the end of its useful life as high end hardware.

18 months is too damn long for a modern release cycle, and their lack of ISO
updates makes it a nightmare to install on even slightly more recent
hardware. I bless to all the heavens the guy doing whiteboxlinux.org, who
takes RHEL SRPM's and all the updates and cleanly rebundles them. RedHat
should absolutely hire him to do this for RHEL commercially.

"Thornton Prime" <theoszi@gmail.com> wrote in message
news:1105219462.964683.201620@c13g2000cwb.googlegr oups.com...
>> Dude, you need to lean to use yum.
>
> Nod.
>
> Right now your ftp command is downloading every single RPM every single
> time and then stepping through each one to determine if it needs to
> upgrade or not. If there are intermediate updates (you are on 1.1 and
> there are .2 and 1.3 on your FTP site) it will do all the intermediate
> updates (most unecessary).
>
> When you initialize a yum repository, it builds an index on the server
> (FTP or HTTP). THe client downloads only the index and then downloads
> only the RPMS it needs (and the dependencies) to get the job done.
> http://linux.duke.edu/yum/

Yuppers. Yum is very sweet, and looks in the main OS repository, update
repositories, and any add-on repositories you tell it to look at. I tend to
mirror the dag and dries repositories for just that reason, to get the xine
and video tools available in Fedora Core 1 through 3.

And if you can't use yum because you don't control the FTP server enough to
generate the yum header tables, try autorpm at www.autorpm.org. It's not as
sweet, but it still works.

Nico Kadel-Garcia wrote:

[...]
>> How slow? IIRC, ES3 came out in late 2003. One of the features of the
>> RHEL distributions is their long life. They do not come out with frequent
>> new releases. Their customers want stability, not the latest bells and
>> whistles. Here is part of what they say about it:
>
> It's been over a year. The 2.6 kernel is a big deal for server grade
> hardware, especially SMP and drivers for recent devices, and they need to
> move forward with that to provide corporate support. for it. I recognize
> that Fedora Core is where they do their bleeding edge work, and that's
> just fine. But I'm actually suggesting Beowulf users use Fedora Core
> rather than RHEL because of the tardiness of the performance updates for
> heavy-duty iron in RHEL.
>

Please, tell that Oracle, EMC and other vendors who certify software for
RHEL but for some reasons not for FC.

>
>>> Stability
>>>
>>> 12-18 month release cycle and seven years of support for every version.
>>> Upgradeability
>>>
>>> Upgrades to new versions are included with every Red Hat Enterprise
>>> Linux subscription.
>
> Well, yes. And if the next version isn't out until 18 months or 24 months
> after a major feature change such as the 2.6 kernel, theree's no point in
> ever getting it for new hardware, since any hardware that RHEL will
> actually run on is near the end of its useful life as high end hardware.
>

really? I am working for a company which produces hardware among other
things and all servers, new and old, are supported and most of them are
certified for RHEL.

> 18 months is too damn long for a modern release cycle, and their lack of
> ISO updates makes it a nightmare to install on even slightly more recent
> hardware.

You probably mean lack of "free" ISO updates?

> I bless to all the heavens the guy doing whiteboxlinux.org, who
> takes RHEL SRPM's and all the updates and cleanly rebundles them. RedHat
> should absolutely hire him to do this for RHEL commercially.

As long as you are able, willing and have enough time and money to test all
combination of hardware and software - you are welcome to roll your own
distribution. Unfortunately, most enterprises (and RHEL is meant for them)
just want it up and running. And if does not work they want support which
you rarely get for free.

=arvi=