From owner-freebsd-questions Mon Jul 17 12:04:22 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA16663 for questions-outgoing; Mon, 17 Jul 1995 12:04:22 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA16656 for ; Mon, 17 Jul 1995 12:04:20 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA20469; Mon, 17 Jul 95 12:54:43 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9507171854.AA20469@cs.weber.edu> Subject: Re: FreeBSD 2.0.5 Software compatibilities To: didier@omnix.fr.org (Didier Derny) Date: Mon, 17 Jul 95 12:54:42 MDT Cc: msmith@atrad.adelaide.edu.au, questions@freebsd.org In-Reply-To: <199507170709.JAA27028@zapata.omnix.fr.org> from "Didier Derny" at Jul 17, 95 09:09:24 am X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@freebsd.org Precedence: bulk > > I wonder if it would be a hard work to rewrite the NFS lock code for > freeBSD. Specia for the server code. There are some very old ISO standards that cover NFS locking; they are old enough that they are not usefule. The lockd itself is pretty trivial if you have a sniffer. The statd stuff is much harder. Some changes were suggested to the lock mechanisms for support of NFS host ID as part of the hash index on lookup for F_[SG]ETLCK{W}. These would need to go in before any implementation could really make any progress. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.