Re: [PATCH,HURD] ptrace: use __hurd_fail for EOPNOTSUPP

2012-10-25 Thread Roland McGrath
OK

Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported

2012-10-25 Thread Roland McGrath
We don't generally handle MIG_BAD_ID. That error indicates a server not implementing the protocol for which it's being used, which is a server bug. If anything, we'd translate that to EGRATUITOUS in the general case, and perhaps to EOPNOTSUPP in particular cases where it's not an ironclad part of

Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported

2012-10-25 Thread Samuel Thibault
Roland McGrath, le Thu 25 Oct 2012 09:49:51 -0700, a écrit : > We don't generally handle MIG_BAD_ID. That error indicates a server not > implementing the protocol for which it's being used, which is a server bug. Pino, in which case did you actually get MIG_BAD_ID precisely? Samuel

Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported

2012-10-25 Thread Svante Signell
On Thu, 2012-10-25 at 19:47 +0200, Samuel Thibault wrote: > Roland McGrath, le Thu 25 Oct 2012 09:49:51 -0700, a écrit : > > We don't generally handle MIG_BAD_ID. That error indicates a server not > > implementing the protocol for which it's being used, which is a server bug. > > Pino, in which c