Thanks for all the advice.
It's been working well for 3.6 -> 3.9.
On 2006/09/22 13:42, Daniel Ouellet wrote:
> Chris Cappuccio wrote:
> >doing it all in one step is trivial.
>
> Please guys. Nick spend a lots of time trying to make the process very
> clear and exact for everyone. He put many warning in there and even with
> that, some users find ways to sh
Chris Cappuccio wrote:
doing it all in one step is trivial.
Please guys. Nick spend a lots of time trying to make the process very
clear and exact for everyone. He put many warning in there and even with
that, some users find ways to shoot themselves in the foot by using none
standard, s
doing it all in one step is trivial.
Bernd Schoeller [EMAIL PROTECTED] wrote:
> On Fri, 22 Sep 2006 08:44:30 +0200, Christopher Vance <[EMAIL PROTECTED]>
> wrote:
>
> >It might not be the 'right' way to do things, but I've had no trouble
> >upgrading machines remotely. YMMV, depending on ho
With OpenBSD-binary-upgrade you can do it in one swift upgrade:
http://www.xs4all.nl/~hanb/software/OpenBSD-binary-upgrade/
Though I recommend you disable the firewall on boot since your
rules will probably not work.
# Han
On 2006/09/22 16:31, Bernd Schoeller wrote:
> remote installation through an SSH connection directly onto a local disk
> (assuming you have created an identical disk layout first) [*]. You might
> probably want to exclude /usr/src, /usr/ports and other directories that
> you can not cause any
On Fri, 22 Sep 2006 15:35:17 +0200, Nick Holland
<[EMAIL PROTECTED]> wrote:
[...] Build out a machine as similar to your
remote machine as you can (and I don't just mean just the OpenBSD
version[*]), back it up. Now, put it in another room, and upgrade it.
If it works, restore, try it again.
Bernd Schoeller wrote:
> On Fri, 22 Sep 2006 08:44:30 +0200, Christopher Vance <[EMAIL PROTECTED]>
> wrote:
>
>> It might not be the 'right' way to do things, but I've had no trouble
>> upgrading machines remotely. YMMV, depending on how busy the thing is.
>>
>> What I would do is:
>
> Please,
On Friday 22 September 2006 00:39, you wrote:
>I have a machine running OpenBSD 3.6 on a remote location that I would
>like to upgrade. I only have ssh access unless I buy myself an
> expensive plane ticket. I wondered if there's a safe way to upgrade
> remotely or should I just wait until I get a
On Fri, 22 Sep 2006 08:44:30 +0200, Christopher Vance <[EMAIL PROTECTED]>
wrote:
It might not be the 'right' way to do things, but I've had no trouble
upgrading machines remotely. YMMV, depending on how busy the thing is.
What I would do is:
Please, that is not the recommended way of doing
It might not be the 'right' way to do things, but I've had no trouble
upgrading machines remotely. YMMV, depending on how busy the thing is.
What I would do is:
Download the relevant *37.tgz and bsd files.
Comment stuff out of rc.conf.local and/or rc.local to reduce what gets
started on boot. In
11 matches
Mail list logo
