On 2011-04-30, Nick Holland <n...@holland-consulting.net> wrote: > On 04/30/11 05:53, David Steiner wrote: >> can the upgrade process via bsd.rd be automated? i'm thinking of >> upgrading remote machines, which are only available via ssh . >> >> like this: fetch the latest bsd.rd from ftp. replace /bsd.rd. >> echo 'boot bsd.rd' >> /etc/boot.conf >> reboot >> >> from here on, i'd like to automate the upgrade process, by proving >> standard answers to the questions. > > um... > bsd.rd assumes console. > > If you want to do a remote upgrade, how about using the (shudder) > *suggested* process in the upgradeXX.html docs? I think that process > lends itself much better to scripting and automating then a > roll-your-own custom kernel. Keep in mind, most of the steps in that > document have to be followed with a bsd.rd upgrade, too. > > http://www.openbsd.org/faq/upgrade49.html
With release around the corner it's a good time for a reminder: If you're doing this for the upgrade to 4.9 be very careful to do the untarring exactly as suggested: backup /sbin/reboot first, and untar in the order suggested with base49 last. Don't use sudo, do this in a root shell. I'll add some suggestions: do not use tab completion when you're running /sbin/oreboot, and keep a spare logged-in root shell open. The majority of 4.9 binaries *will not* run on a 4.8 (or earlier) kernel.
