Svante Signell, le Fri 26 Oct 2012 08:03:43 +0200, a écrit :
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
Alle venerdì 26 ottobre 2012, Samuel Thibault ha scritto:
Svante Signell, le Fri 26 Oct 2012 08:03:43 +0200, a écrit :
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
Pino Toscano, le Fri 26 Oct 2012 18:30:39 +0200, a écrit :
Alle venerdì 26 ottobre 2012, Samuel Thibault ha scritto:
Svante Signell, le Fri 26 Oct 2012 08:03:43 +0200, a écrit :
On Thu, 2012-10-25 at 19:47 +0200, Samuel Thibault wrote:
Roland McGrath, le Thu 25 Oct 2012 09:49:51 -0700, a
On Fri, Oct 26, 2012 at 07:07:02PM +0200, Samuel Thibault wrote:
Oh? I wonder how that produces MIG_BAD_ID: libtrivfs (used by pflocal)
is supposed to be returning EOPNOTSUPP when there is no underlying node,
which should be the case here.
Not really, as pflocal uses libtrivfs only for its
Richard Braun, le Fri 26 Oct 2012 19:15:02 +0200, a écrit :
On Fri, Oct 26, 2012 at 07:07:02PM +0200, Samuel Thibault wrote:
Oh? I wonder how that produces MIG_BAD_ID: libtrivfs (used by pflocal)
is supposed to be returning EOPNOTSUPP when there is no underlying node,
which should be the
AIUI, POSIX says there can be other, implementation-defined errors.
That's true. But when POSIX specifies a particular error code for a
particular condition, then you must yield the specified error code for that
situation. If this is arising for something like using a file-oriented
call on an
