Re: upgrade 3.6 -> 3.7
Erwin Zbinden wrote: > Hi > > I am upgrading a i386 box from 3.6 to 3.7. In the upgrade guide I miss any > hint to mergemaster. > > Is it obsolete? > > Tia > > Erwin > Mergemaster is not a part of the base system. OpenBSD is and should be a "complete" system, the set of CDs, and in fact, the base download, should be all you need to use it and maintain it. Therefore, the upgradeXX.html documents are written to use obscure and sophisticated commands like cp(1) and mv(1). :) I've got nothing against Mergemaster, people whom I respect greatly use it and recommend it. But unless or until it goes into the base system (and it won't due to OTHER dependencies, as I recall), the official upgrade process won't include it. Feel free to write your own upgrade guide using whatever tools you want. :) Nick.
upgrade 3.6 -> 3.7
Hi I am upgrading a i386 box from 3.6 to 3.7. In the upgrade guide I miss any hint to mergemaster. Is it obsolete? Tia Erwin -- 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse f|r Mail, Message, More +++
Re: Planning remote upgrade 3.6-3.7, ssh work after new kernel?
Steve Williams wrote: > Hi, > > I have been working with OpenBSD since the 2.7 days. Strangely enough, I > have never had to try to remotely upgrade a system. I have always had > "hands on". Now I am looking at upgrading a server from 3.6 to 3.7 > remotely (through ssh). > > In preparation, I am going over: > http://www.openbsd.org/faq/upgrade37.html > in minute detail to make sure I do NOT miss anything. > > I am following the "Upgrading without install media" portion, as I need to > do this over SSH. > > The first step is to install the new kernel and firmware. It then says to > reboot. > > The FAQ says "reboot now.as usually, the new kernel will run old > userland apps". It's the "USUALLY" that caught my eye. I am 99% sure > sshd will run or it would have been mentioned in the FAQ. But I have > found it's those 1%'s in life that really bite hard. > > Obviously, there are no guarantees in life, but can I, with a high level > of certainty know that I will still be able to SSH into the system after > the reboot? > > Thanks for any information. > Steve Two answers to that question. one: Yes, ssh will work. two: if it is your first remote upgrade, practice locally via ssh, where you can fix it if something goes wrong. Set up your system locally as close as you can make it to your remote machine, so you can experience whatever glitches may happen, or whatever user errors you might make. The "USUALLY" is there to cover my butt in case you find an exception. However, I do test the upgradeXX.html remote upgrade process before committing it, both on test machines and production systems. Other apps may not work, pfctl may not be able to load a ruleset (Default is pass all, so you can still ssh to it), so you might want to shut down any "soft" apps that are going to come up unprotected. Nick.
Planning remote upgrade 3.6-3.7, ssh work after new kernel?
Hi, I have been working with OpenBSD since the 2.7 days. Strangely enough, I have never had to try to remotely upgrade a system. I have always had "hands on". Now I am looking at upgrading a server from 3.6 to 3.7 remotely (through ssh). In preparation, I am going over: http://www.openbsd.org/faq/upgrade37.html in minute detail to make sure I do NOT miss anything. I am following the "Upgrading without install media" portion, as I need to do this over SSH. The first step is to install the new kernel and firmware. It then says to reboot. The FAQ says "reboot now.as usually, the new kernel will run old userland apps". It's the "USUALLY" that caught my eye. I am 99% sure sshd will run or it would have been mentioned in the FAQ. But I have found it's those 1%'s in life that really bite hard. Obviously, there are no guarantees in life, but can I, with a high level of certainty know that I will still be able to SSH into the system after the reboot? Thanks for any information. Steve
