From owner-freebsd-hackers Tue Oct 31 8: 5:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id AC63037B479 for ; Tue, 31 Oct 2000 08:05:21 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id e9VG5IL18693; Tue, 31 Oct 2000 08:05:18 -0800 (PST) (envelope-from dillon) Date: Tue, 31 Oct 2000 08:05:18 -0800 (PST) From: Matt Dillon Message-Id: <200010311605.e9VG5IL18693@earth.backplane.com> To: Terry Lambert Cc: dufault@hda.com (Peter Dufault), tlambert@primenet.com (Terry Lambert), ryan@sasknow.com (Ryan Thompson), freebsd-hackers@FreeBSD.ORG Subject: Re: Filesystem holes References: <200010311427.HAA27852@usr06.primenet.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :to hold a write lock on the range you didn't want rewritten; so :long as it honors the advisory locks, there'd be no chance of it :screwing up, unless you got bit by the stupid POSIX lock close :semantics. Stupid POSIX; that's the other one I'd put in: the :ability to: : : int i = 1; : : fcntl( fd, F_NONPOSIX, &i); : :It would help out the NFS locking daemon to no end... : : Terry Lambert : terry@lambert.org We could implement this trivially, and I'm pretty sure we could implement some sort of free-space semantics trivially too, at least for UFS, using a struct flock to pass the parameters to a fcntl. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message