Date: Fri, 06 Jun 2008 07:22:26 +0300 From: Manolis Kiagias <sonicy@otenet.gr> To: freebsd-questions@freebsd.org Subject: Re: Upgrading Kernel on a Remote Server Message-ID: <4848BB82.8050901@otenet.gr> In-Reply-To: <943022.25318.qm@web63903.mail.re1.yahoo.com> References: <943022.25318.qm@web63903.mail.re1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4848BB82.8050901>