Date: Fri, 9 Jul 2004 23:01:27 -0400 From: Brian Fundakowski Feldman <green@freebsd.org> To: Stephen Hurd <shurd@sasktel.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Locking: kern/50827 Message-ID: <20040710030127.GG1626@green.homeunix.org> In-Reply-To: <20040704160645.39a0c0d8.shurd@sasktel.net> References: <20040624174919.46160f9e.shurd@sasktel.net> <20040628192935.GF5635@green.homeunix.org> <20040630192041.1d9c5348.shurd@sasktel.net> <20040704181347.GE997@green.homeunix.org> <20040704160645.39a0c0d8.shurd@sasktel.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 04, 2004 at 04:06:45PM -0600, Stephen Hurd wrote: > > Right, if you just make it cross-platform in the first place using > > higher- level primitives you don't have to worry what the specific > > kernel and operating system and file system you are using provides. > > It's my opinion tha there won't be other people adopting this API for > > file locking since it is by definition not meant to work like the > > standardized APIs. > > > > I don't think that there's no value in having more useful locking > > primitives, but they probably don't benefit much from being implemented > > in the kernel unless they conform to a portable API. I certainly always > > have my own various kernel modifications that I find useful, but aren't > > very standard :) > > This sounds a lot like "Well, there's no point in doing something better > since nobody else is doing it.". strlcpy() and friends are an example of > non-standard stuff that just Makes Sense(tm). If you're trying to create a new "standard", I think -standards or -arch is the more appropriate FreeBSD list. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040710030127.GG1626>