On 16 Dec 2005 14:41:38 -0800, Randal L. Schwartz <[email protected]> wrote: > >>>>> "Theo" == Theo de Raadt <[EMAIL PROTECTED]> writes: > > Theo> If you get stuck doing an upgrade build, please do a standard upgrade > Theo> or reinstall. > > Theo> We have never promised that such builds will work perfectly, nor can we > Theo> dedicate 3-4 developers full-time to making sure they do. Which is > Theo> pretty much what it would take. > > I understand that. However, I'm hoping that someone else reading this > mailing list will have tried the paragraph given in the FAQ, and either > succeeded with a workaround, or discovered the futility as well. > > I'm upgrading a remote box, so a "standard upgrade" is not an option, > nor is a reinstall. There was no warning in the FAQ that the > information was definitely broken. It must have worked for *someone* > or it wouldn't have been put in the FAQ, I presume. >
First off, I fail to see how extracting the install sets via ssh can't be done, as that's mentioned in the FAQ as one upgrade method. Second, the source upgrade stuff has worked for people in the past, but they usually know enough about the system to actually fix something if it breaks. A source upgrade probably has less of a chance of working as extracting the install sets via ssh as mentioned in the FAQ, so you're running a risk either way. My suggestion, get the box shipped back to you or ship out a new hard drive with the new install on it, and all the other data copied over. Since OpenBSD is compiled to work on all i386 boxes, it shouldn't really matter which box you install it on, as long as you properly set the network config how it should be on the remote box. Jason
