The current situation with error codes sent back to a netlink application is unsatisfactory. Most often, the application receives EINVAL but has no idea what was wrong. Here is my plan: Introduce som
I think its a good idea. so, questions: classical ABI issues a) old kernel vs new app b) new kernel vs old app i.e: The use of existing error codes is still valuable. Existing apps will do: errno = m
* jamal <1094866738.1042.53.camel@xxxxxxxxxxxxxxxx> 2004-09-10 21:38 Outdated error string table should result in a unknown error like in strerror. 2^16 errno codes should be sufficient forever. The