On Tue, Dec 01, 2009 at 05:35:49PM +0000, Steve Blinkhorn wrote: > Three years ago I got badly bitten trying to upgrade a remote colo > server from 1.6 to 3.0. There were two sources of difficulty: the > first was to do with the introduction of PAM; but what really did it > was the system call incompatibility introduced that meant that 3.0 > binaries would not interoperate with a 1.6 kernel, so I ended up > unable to finish the business of copying all the 3.0 files (including > pam.d) into place. So I had to go to the server farm and install > manually. Are you really saying that you're upset that 3.0 binaries were not meant to be run with a 1.6 kernel? > The time has come to do another round of upgrades, so I'm > understandably concerned not to run into any similar issues. Is > there a document somewhere that lists potential issues of this kind? Well, I'm pretty sure everything that describes how to update a system include booting a new kernel first... And then running etcupdate of course; you probably wouldn't have been hit so hard with PAM if you had done that. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "See the look on my face from staying too long in one place [...] every time the morning breaks I know I'm closer to falling" KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
Attachment:
pgp9RiYcmsmx1.pgp
Description: PGP signature