Probably not the cleverest way of doing it, but it works for me: I've implemented mrepo, which synchronises updates with RHN. Then I configure my servers to point at mrepo for updates. You can then make mrepo synch, test the latest updates and update production servers after testing. Then synch mrepo to get the next bunch of updates, test, and deploy to production, etc etc. -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Shaughnessy, Kevin Sent: 27 August 2009 22:06 To: redhat-list@xxxxxxxxxx Subject: Re: Linux system administration methodology or best practice I am also looking for hands-on advice for Red Hat administration, specifically regarding updates: - I'd like a sandbox system to apply them, and test them. Do I have to buy the same level of support for this "trash able" system? (I've already ruled out Fedora and CentOS, as I need to maintain compatibility with EMC PowerPath and Oracle.) - By the time I've evaluated a set of updates, there are new ones, and yum always pulls the newest. How do I migrate my 'approved' set from sandbox to development to production? - How often do you apply updates to your production servers? Security updates? Thanks, -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
