From owner-freebsd-hackers Thu Mar 5 09:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11039 for freebsd-hackers-outgoing; Thu, 5 Mar 1998 09:13:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA11018 for ; Thu, 5 Mar 1998 09:12:54 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yAdui-00040w-00; Thu, 5 Mar 1998 08:54:32 -0800 Date: Thu, 5 Mar 1998 08:54:20 -0800 (PST) From: Tom To: Niall Smart cc: "Ron G. Minnich" , Alex Povolotsky , hackers@FreeBSD.ORG Subject: Re: Cluster? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Mar 1998, Niall Smart wrote: > > DNS? DNS already has excellent fault-tolerant capabilities. > > I should have mentioned that I was had dynamic DNS in mind, in this > scenario the two (or n) DNS servers could share the data structures in a > shared memory region so that an update by any would be reflected in the BIND can do this with NOTIFY too. > address spaces of all the others. I agree that DNS has fault tolerant > capabilities but I wouldn't call them excellent, its annoying to have to > wait for requests to the primary to time out before the resolver library > starts hitting on the secondaries. Speak for your own resolver. I can't even tell if a primary fails. ... > Hmm, thats an interesting one, can most cards be programmed to accept > frames with specific MAC's? I don't know about PCs, but on Sun hardware, the MAC address was programmed in PROM on the motherboard, and the kernel would configure all cards with the MAC address on init. This was handy for diskless workstations, as the workstations MAC address would never change even ethernet cards were swapped. > Niall Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message