At 12:44 PM 12/2/02, you wrote:
Mark Lane wrote:
Perhaps the ultimate would be a system where RH went to a central repository
and pulled current RPMs when it first installed.
Our network install of Red Hat already basically does this. A cronjob
downloads the updates and puts them into the redhat install directory and
updates the file list. So when we do the next install we don't have to
update the packages as they already are updated.
System admins would love the use of RedHat's up2date for keeping
workstations updated. Freshmeat lists 2 projects that act as replacement
for RedHat's up2date servers: Current
<http://www.biology.duke.edu/computer/unix/current/> and NRH-up2date
<http://www.nrh-up2date.org/>.
There's an easier way than using up2date. We have a script that will list
which updates apply for your architecture. That list can be used as an
argument to rpm -Fvh and all updates will be installed. To automatic this
you could just use a cronjob.
--
*Richard Plana, B.Sc., CCNA*
Secretary
Calgary Linux Users' Group
--
Mark Lane
Hard Data Ltd.
mailto:[EMAIL PROTECTED]
Telephone: 01-780-456-9771
FAX: 01-780-456-9772
11060 - 166 Avenue
Edmonton, AB, Canada
T5X 1Y3
http://www.harddata.com/
--> Ask me about our Affordable Alpha Systems! <--
BEGIN:VCARD
VERSION:2.1
N:Lane;Mark
FN:Mark Lane
ORG:Hard Data Ltd.
TITLE:Sales
TEL;WORK;BUSINESS:780-456-9771
TEL;WORK;VOICE:780-456-9771
TEL;WORK;FAX:780-456-9772
ADR;WORK:;;11060 - 166 Avenue;Edmonton;AB;T5X1Y3;Canada
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:11060-166 Avenue=0D=0AEdmonton, AB T5X1Y3=0D=0ACanada
URL;WORK:http://www.harddata.com
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20010222T231737Z
END:VCARD
