Hello Martin WHEELER <[EMAIL PROTECTED]>,
Sometimes, you know, there'll be security advisory or update packages available, say openssh or libzip, and you need to immediately update your production machines to aviod known vulnerability. However, you can't just apt-get upgrade if you do not run the stable release. What method is recommended to keep the testing or unstable release update and free from security vulnerability? On Tue, 12 Mar 2002 15:43:10 +0000 (UTC) Martin WHEELER <[EMAIL PROTECTED]> wrote: > On Tue, 12 Mar 2002, Patrick Hsieh wrote: > > > I wish I could use testing release > > packages with rapid packages update support. Is it possible? > > Yes. (I do.) > > A good idea is to keep your production environment 2-3 days behind the > latest updates in case of unforeseen 'gotchas'; and run today's upgrades > on a totally separate machine -- e.g. a laptop, or a quarantine machine > -- until you're sure they're not going to blow anything up. > Then move the upgrades to the production environment. > > This works well for me. > > msw > -- > Martin Wheeler <[EMAIL PROTECTED]> gpg:1024D/01269BEB the.earth.li > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Patrick Hsieh <[EMAIL PROTECTED]> GPG public key http://pahud.net/pubkeys/pahudatpahud.gpg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
