Re: ENOATTR vs ENODATA

To: martin%duskware.de@localhost (Martin Husemann)
Subject: Re: ENOATTR vs ENODATA
From: manu%netbsd.org@localhost (Emmanuel Dreyfus)
Date: Mon, 30 Apr 2012 15:57:18 +0200

Martin Husemann <martin%duskware.de@localhost> wrote:

> I don't know - you could nuke ENOATTR from NetBSD and just make the kernel
> return ENODATA.

I think this is the best way : ENOATTR does not seem to exist in any
standard. We only use it in extended attribute code, and there is no
situationa system call could return ENOATTR or ENODATA.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu%netbsd.org@localhost

Follow-Ups:
- Re: ENOATTR vs ENODATA
  - From: Iain Hibbert
- Re: ENOATTR vs ENODATA
  - From: Jean-Yves Migeon

References:
- Re: ENOATTR vs ENODATA
  - From: Martin Husemann

Prev by Date: Re: Modularizing net80211 (was: link_set info needed)
Next by Date: Re: add disk size to "struct disk"?
Previous by Thread: Re: ENOATTR vs ENODATA
Next by Thread: Re: ENOATTR vs ENODATA
Indexes:

Home | Main Index | Thread Index | Old Index