Re: Upgrading Kernel on a Remote Server
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 user mode or anything. Just have a look to this URL; I allready read that this works flawless: http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/ Jos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Upgrading Kernel on a Remote Server
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 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading Kernel on a Remote Server
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, 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. If you want 7.0, why not just ask the host to install that instead of 6.3. It can't cost them any more - may $0.50 for a CD blank. That way, you are starting off on the desired foot anyway. Of course, you should still csup to the latest source and build it and install it and csup to the latest ports and docs before you do any ports installation. I don't know about wrinkles in doing it remotely because I have always had the servers available to touch. But, as long as you don't do something to lock yourself out, then you should be OK. Hopefully others with remote experience will respond to that. jerry Thanks for any suggestions/help/etc, ~Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading Kernel on a Remote Server
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: [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 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading Kernel on a Remote Server
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 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 A nice trick for easily recovering from unbootable kernels is nextboot(8). Try man nextboot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading Kernel on a Remote Server
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 *very* worthwhile looking into! Thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
