From owner-freebsd-current Tue Apr 21 09:32:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07968 for freebsd-current-outgoing; Tue, 21 Apr 1998 09:32:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07947 for ; Tue, 21 Apr 1998 16:32:28 GMT (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id JAA23806; Tue, 21 Apr 1998 09:31:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Kenneth D. Merry" cc: syssgm@dtir.qld.gov.au (Stephen McKay), freebsd-current@FreeBSD.ORG Subject: Re: NFS corruption In-reply-to: Your message of "Tue, 21 Apr 1998 10:22:54 MDT." <199804211622.KAA23401@panzer.plutotech.com> Date: Tue, 21 Apr 1998 09:31:39 -0700 Message-ID: <23801.893176299@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that these NFS problems aren't getting much closer to being fixed, at least not over the period of time that it's been clearly unstable, nor would volunteer labor appear to be sufficient to get it fixed here. Therefore.... If there are people here who feel confident that they could make substantial inroads with NFS if only it were a paying job AND are in a position to accept such contract work, please contact me. I'm pretty sure that I can find the funds but not so sure that I can find the personnel. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message