Re: some PRs
From: Peter Jeremy (PeterJeremy_at_optushome.com.au)
Date: 07/27/04
- Previous message: Giorgos Keramidas: "Re: some PRs"
- In reply to: Sergey Babkin: "Re: some PRs"
- Next in thread: Sergey Babkin: "Re: some PRs"
- Reply: Sergey Babkin: "Re: some PRs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 27 Jul 2004 18:43:24 +1000 To: Sergey Babkin <babkin@bellatlantic.net>
[ /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/O system calls, why not go the whole hog and implement a virtual
filesystem that returns the required error:
.../EPERM just returns EPERM
.../ENOENT just returns EPERM
etc
Of course, you've then got to decide which of open(), close(), read()
write(), ioctl(), fcntl() etc should succeed and which should return
an error. This rapidly becomes unworkable.
Overall, IMHO, the benefits are minimal and don't warrant the effort
of implementing and maintaining the code.
-- Peter Jeremy _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Giorgos Keramidas: "Re: some PRs"
- In reply to: Sergey Babkin: "Re: some PRs"
- Next in thread: Sergey Babkin: "Re: some PRs"
- Reply: Sergey Babkin: "Re: some PRs"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]