Re: ignoring EOPNOTSUPP and ENOTTY

2009-08-31 Thread Pádraig Brady
Bruno Haible wrote: > Pádraig Brady wrote: >> I was wondering about this general issue a couple of days ago when pondering: >> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=2bc0f3c >> >> At the application level we often want to check for this >> "not supported" condition while

Re: ignoring EOPNOTSUPP and ENOTTY

2009-08-31 Thread Jim Meyering
Bruno Haible wrote: > Pádraig Brady wrote: >> I was wondering about this general issue a couple of days ago when pondering: >> http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=2bc0f3c >> >> At the application level we often want to check for this >> "not supported" condition whil

Re: ignoring EOPNOTSUPP and ENOTTY

2009-08-30 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 8/30/2009 6:03 PM: >> case EOPNOTSUPP: /* Operation not supported */ >> case ENOTSUP:/* Operation not supported */ POSIX states that ENOTSUP==EOPNOTSUPP is permissible, so you can't do this with a case stat

Re: ignoring EOPNOTSUPP and ENOTTY

2009-08-30 Thread Bruno Haible
Pádraig Brady wrote: > I was wondering about this general issue a couple of days ago when pondering: > http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=2bc0f3c > > At the application level we often want to check for this > "not supported" condition while not caring where the fail