From owner-freebsd-current Fri Apr 7 17:45: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id F1D6337BBD6 for ; Fri, 7 Apr 2000 17:45:04 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA26183; Fri, 7 Apr 2000 20:45:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA35707; Fri, 7 Apr 2000 20:44:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 7 Apr 2000 20:44:33 -0400 (EDT) To: "David E. Cross" Cc: freebsd-current@freebsd.org Subject: Re: lockd-0.2 released! In-Reply-To: <200004080007.UAA51276@cs.rpi.edu> References: <200004080007.UAA51276@cs.rpi.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14574.32380.49809.847803@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This might be a bit touchy, but I'm rather curious -- how will the BSDI merger affect your lockd work? It seems like your work on lockd (esp. client side & statd interoperation issues) could be speeded up if you had access to the BSDI sources.. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message