Well, generally I aggree. However there is some packages you like to update but not really make it without a comple update. Like the apache packet 1.3.6 (6.2) to 1.3.9 (6.3), unfortunately this update wasn't as smooth as you could wish as there was other packages as well needed from the Base. But generally you are right. On the other hand, if you stay behind sooner or later you come in a much more risky situation for upgrade when there been several releases inbetween. Then you might have to rebuild the whole server to get it right, and safely get all users, domains etc. with you still working as before... well that can be something of a workload. If you have several boxes it might be easier just to transfer the masse. Joakim Jon Pennington skrev:
On Tue, 15 Feb 2000, Joakim Schramm wrote:
I would like to know of an other, real "hard core" reason. I have 500Km to go updating my server, and I don't like it to be as last time... when I cam back from my second "Update trip" of 6.2, 6.3 was on my desk waiting for me.
Not to be trite or anything, but `If it ain't broke, don't fix it' is the metaphor to be applied here. Keep up on suse-security, ssh into the box to update necessary RPMs, but don't bother with complete updates; you'll kill yourself trying. :)
-- -=|JP|=- Jon Pennington | Atipa Linux Solutions -o) jpennington@atipa.com | Kansas City, MO /\\ 816-241-2641 x107 | http://www.atipa.com _\_V
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- -------------------------------------------------------------------------------------------- If I wouldn't have to accept the (f)act of being a human... I would just love the (f)act of being a god! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/