Schiz0 wrote:
The host is installing 6.3-RELEASE. I'd like to upgrade to
7.0-RELEASE, as well as compile in some kernel options for various
things. What's the best way to do this on a remote system, minimizing
compiling a bad kernel and causing it not to boot? I wouldn't have
access to single
Date: Thu, 5 Jun 2008 12:15:44 -0400
From: [EMAIL PROTECTED]
To: Freebsd-questions@freebsd.org
CC:
Subject: Upgrading Kernel on a Remote Server
Hey,
I recently ordered a FreeBSD server from a hosting company. This would
be the first time I do not have physical access to a FreeBSD
On Thu, Jun 05, 2008 at 12:15:44PM -0400, Schiz0 wrote:
Hey,
I recently ordered a FreeBSD server from a hosting company. This would
be the first time I do not have physical access to a FreeBSD system.
I'm looking for any hints/tricks/suggestions for managing and
upgrading it safely (as in,
, some genius out there has
figured out a way to do it without a reboot.
Just my two cents,
Camilo
Bono Vince Malum
Date: Thu, 5 Jun 2008 12:35:43 -0400
From: Sean Cavanaugh
Subject: RE: Upgrading Kernel on a Remote Server
To:
Message-ID:
Content-Type: text/plain; charset=iso-8859-1
Camilo Reyes wrote:
I don't have much experience with this other than once I ran a server from home
and remotely ssh'ed to it to do maintenance. One of the things I learned from
that experience was that you can easily patch your services any time there is a
new threat, all you have to do is
A nice trick for easily recovering from unbootable kernels is
nextboot(8). Try man nextboot
I certainly concur with Sean on the co-ordinate a time theory,
especially if it includes them being on standby for a clean recovery,
but this nextboot(8) tactic that I never knew about before seems
