From owner-freebsd-current  Tue Aug  8 02:13:42 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id CAA10639
          for current-outgoing; Tue, 8 Aug 1995 02:13:42 -0700
Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id CAA10626
          for <freebsd-current@freebsd.org>; Tue, 8 Aug 1995 02:13:38 -0700
Received: from localhost (localhost [127.0.0.1])
	  by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id KAA00598
	  ; Tue, 8 Aug 1995 10:12:46 +0100
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
cc: jkh@time.cdrom.com, freebsd-current@freebsd.org,
        joerg_wunsch@uriah.heep.sax.de
Subject: Re: workaround for talk's address problem 
In-reply-to: Your message of "Mon, 07 Aug 1995 17:43:16 PDT."
             <199508080043.RAA02014@gndrsh.aac.dev.com> 
Date: Tue, 08 Aug 1995 10:12:46 +0100
Message-ID: <596.807873166@palmer.demon.co.uk>
From: Gary Palmer <gary@palmer.demon.co.uk>
Sender: current-owner@freebsd.org
Precedence: bulk

In message <199508080043.RAA02014@gndrsh.aac.dev.com>, "Rodney W. Grimes" write
s:
>Yes, but leads to a simple fix, running a cacheing name server on all
>NFS servers, and point your clients to that name server.

Can you run named on a multi-homed Novell server? :-)

Gary