From owner-freebsd-questions Wed Jul 5 13:53:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from home.offwhite.net (home.offwhite.net [156.46.35.30]) by hub.freebsd.org (Postfix) with ESMTP id B5BC737B5A0 for ; Wed, 5 Jul 2000 13:53:33 -0700 (PDT) (envelope-from brennan@offwhite.net) Received: from localhost (brennan@localhost) by home.offwhite.net (8.9.1/8.9.3) with ESMTP id PAA56900; Wed, 5 Jul 2000 15:50:18 -0500 (CDT) Date: Wed, 5 Jul 2000 15:50:18 -0500 (CDT) From: BWS - Offwhite To: Kenneth Wayne Culver Cc: Gabriel Ambuehl , Christoph Sold , Lysenko Alexey Victorovich , freebsd-questions@FreeBSD.ORG Subject: Re: Re[4]: I need Your advice In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would probably be more likely that a system would migrate all current processes and threads to an identical box to maintain 100% uptime. You can do this with Java servlets and other systems already, but I am not aware of an entire OS migrating itself to a host box while the home box is upgraded and rebooted. If you did clone a boxes current OS with complete libraries to a host box, I bet it would be possible to freeze all systems, including a snapshot of the kernel to the temporary host, but you need to have an exact copy of that systems resources. Does anyone know a cluster manages this? I have not had a good reason to run a cluster yet and have not done it yet, but wonder if a cluster could allow a node to reboot without disrupting the cluster. And what if the master node needed to reboot and get upgraded? What is the prefered method here? Brennan Stehling - web developer and sys admin projects: www.greasydaemon.com | www.onmilwaukee.com | www.sncalumni.com Microsoft: Will you get a macro virus today? http://www.greasydaemon.com/noms/ <- Why avoid MS? On Wed, 5 Jul 2000, Kenneth Wayne Culver wrote: > > So updating from 3.4 to 3.5 takes a reboot as well if one decides to > > change the Kernel. Not a big difference. I think the other problems > > which can occur during the update from 3 to 4 are way bigger (wrong > > configfiles etc.). The ability to change the Kernel without rebooting > > would be very interesting (and a big advantage over Linux, if that's > > worth anything to you guys ;-), though. > > > Well, that will most likely not happen anytime soon, and I think it's > unlikely to happen at all. Yes, updating a kernel with 1 changed source > file even requires a reboot. The only time rebooting after recompiling > anything that has to do with the kernel is not needed is if you recompile > the kernel module for the driver in question, then reload that module. > However, I'm not sure that a 3.5 module will work with a 3.4 kernel in all > cases, and you are generally better off just rebooting. It should not take > that long to reboot anyway; it only takes me about a minute when I'm > starting httpd and some other extra daemons at startup (smbd, nmbd, named, > sendmail, etc...). > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message