Date: Tue, 27 Jul 2004 12:36:41 -0400 From: Sergey Babkin <babkin@bellatlantic.net> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: freebsd-arch@freebsd.org Subject: Re: some PRs Message-ID: <41068499.CACDAEB0@bellatlantic.net> References: <20040718184008.GC57678@darkness.comp.waw.pl> <20040719075952.GG57678@darkness.comp.waw.pl> <200407191855.19885.max@love2party.net> <4105987E.5FC50517@bellatlantic.net> <20040727084324.GM3001@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy wrote: > > [ /dev/full ] > On Mon, 2004-Jul-26 19:49:18 -0400, Sergey Babkin wrote: > >I'm about a week behind :-) but here are my 2 cents: it's a VERY useful > >device for testing. > > Maybe. There are lots of other error numbers that are equally useful > for testing. If you really want a way to inject known errors into I think any one error is good enough. Especially that EPERM and ENOENT would be returned from open(), not write(). > Overall, IMHO, the benefits are minimal and don't warrant the effort > of implementing and maintaining the code. Oh, come on: the code is already implemented by someone and requires zero maintenance. I mean, when was the last time someone touched the implementation of /dev/null? BTW, probably an easy implementation would be to just add one more minor to the null driver. -SB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41068499.CACDAEB0>