From owner-freebsd-questions@FreeBSD.ORG Fri Jun 6 03:07:46 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E296106567C for ; Fri, 6 Jun 2008 03:07:46 +0000 (UTC) (envelope-from camiloreyes82@yahoo.com) Received: from web63903.mail.re1.yahoo.com (web63903.mail.re1.yahoo.com [69.147.97.118]) by mx1.freebsd.org (Postfix) with SMTP id B12B88FC0A for ; Fri, 6 Jun 2008 03:07:45 +0000 (UTC) (envelope-from camiloreyes82@yahoo.com) Received: (qmail 25926 invoked by uid 60001); 6 Jun 2008 03:07:45 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=j4eA/zvS3DIWnuGy/kqvAHjSP1OBqU24yfIcbtAWuw8DhLHVdTsHppx05a5PlvZnPvUoi34zTKRB0lzuMzU5E9Q1T6cPck9m7VQ2QAvJ+ebp4rdMUwdOlVo8xbkwwXtVwFVtPm6BTQ6LHltP4HEBwcVpjxKSmEgubqU3p3gt49g=; Received: from [98.201.146.8] by web63903.mail.re1.yahoo.com via HTTP; Thu, 05 Jun 2008 20:07:44 PDT X-Mailer: YahooMailRC/975.41 YahooMailWebService/0.7.199 Date: Thu, 5 Jun 2008 20:07:44 -0700 (PDT) From: Camilo Reyes To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <943022.25318.qm@web63903.mail.re1.yahoo.com> Subject: Re: Upgrading Kernel on a Remote Server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2008 03:07:46 -0000 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 patch your code, recompile, and restart service. If you are not sure it will ever come back up when you restart, you can leave it patched and restart it when you are more comfortable. When it comes to the kernel, don't upgrade it unless it's ABSOLUTELY necessary because you have to reboot each time; unless of course, 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" > > > > Date: Thu, 5 Jun 2008 12:15:44 -0400 > > From: schiz0phrenic21@gmail.com > > 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 system. > > I'm looking for any hints/tricks/suggestions for managing and > > upgrading it safely (as in, not locking myself out or having boot > > errors). The host does not offer KVM/IP or serial port access. > > > > 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 user mode or anything. > > > > Thanks for any suggestions/help/etc, > > ~Steve > > do you have control of the whole box? most places I know that have online > hosting like that run you inside a jail as a VPS style system. > > to answer your original comments, I would say to contact their tech support > department and see if you can coordinate with them to have it upgraded to 7.0. > If they dont support it, then you are going to be on your own with the install > and may have to have them reimage it if you get a bad install. Some places will > be willing to do a local base install for your or at least help get over any > hurdles with upgrading. > > -Sean