This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: Gotchas From: Graham Hemmings <gh-work@netcomuk.co.uk> Date: Mon, 06 Dec 1999 23:48:03 +0000 At 21:01 06/12/99 +1100, you wrote: >Maybe there is a third solution..... a combination of the both > >perhaps you could keep the errata section of the redhat website, and also >have a service release section... that way people like myself who go to >the errata section and see a huge ammount of files, and are a tad unsure >of what there doing can go for the service release every few months and >download all the fixes in one huge rpm maybe :] (can rpm's contain several >rpms ??) > >If that was the case, it would only mean throwing the current rpms from >the last service release into a file and posting it - which to me sounds >like a dream for the consumer. specially people who want to have things >fixed properly, but cant spare the time to go searching for updated files >in directory every day to see whats new. There are plenty of tools that automate this process. My current favorite is autorpm. RH6.1 also ships with an auto-update tool but this requires X and Netscape - I prefer to stick with CLI tools. === Subject: Re: future Redhat security-patches updating policy ? From: Simon Epsteyn <seva@null.cc.uic.edu> Date: Fri, 1 Oct 1999 13:28:14 -0500 (CDT) > The ideal would be to have a little client on every RH distro shipped which ie > polls the REDHAT's central webserver (or maybe a custom server, the protocol > doesn't matter here), and retrieves information about which rpms have to be > updated, with flags describing the security urgency. Check out Kirk Bauer's AutoRPM: http://www.kaybee.org/~kirk/html/linux.html Kirk is on this list and will probably comment on it as well ;) ===