From owner-freebsd-questions@FreeBSD.ORG Sat May 7 13:31:37 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A288E16A4DB for ; Sat, 7 May 2005 13:31:37 +0000 (GMT) Received: from top.daemonsecurity.com (FW-182-254.go.retevision.es [62.174.254.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2379343DAC for ; Sat, 7 May 2005 13:31:35 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [192.168.0.32] (charm.daemonsecurity.com [192.168.0.32]) by top.daemonsecurity.com (Postfix) with ESMTP id A7F20FD067; Sat, 7 May 2005 15:31:33 +0200 (CEST) Message-ID: <427CC32E.9020703@locolomo.org> Date: Sat, 07 May 2005 15:31:26 +0200 From: =?ISO-8859-1?Q?Erik_N=F8rgaard?= Organization: Locolomo.ORG User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050314 X-Accept-Language: en, en-us, en-gb, da, fr, de, it, es MIME-Version: 1.0 To: Stevan Tiefert References: <42713B77.5020000@aixa.rot-1.de> In-Reply-To: <42713B77.5020000@aixa.rot-1.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: longest uptime X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 May 2005 13:31:37 -0000 Stevan Tiefert wrote: > if I want to do a uptime-record I have always the possiblity to shut > down daemons (when needed) and start them again, without rebooting the > system! That is very nice! I had many days and weeks running my nicely > freebsd-server. BUT every time I updated the patchlevel (in example > 5.2.1-RELEASE to 5.2.1-RELEASE-p14) I had to reboot my system. But then > the counter of uptime is starting at zero again :-( > > Question: Is there a possiblity to run the system inclusive patching it, > without rebooting? Goal is to run a system maybe longer than a year!!! If the patches are applied to a loadable kernel module only, then it should (at least in theory) be enough to rebuild/install the kernel as usual and then just reload the kernel module instead of rebooting. Reloading the module requires that the given service is not in use, which is why it may be easier to just reboot. Taking this idea to the extreme, there is a number of other projects, non-FBSD, that work on micro/nanokernel technology. I can't recommend you one over another - I haven't tried them - QNX is a commercial product, also there is open-source LSE/OS, just to get you started. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2