> Which part dont you understand?
>
> Youve been told about 1000 times already, but let me shout:
>
> YOU CAN GET THE INFORAMTION YOU WANT IF YOU USE NETLINK.
Calm down. Please. This discussion is about portability. I'm not
striving to turn Linux into FreeBSD, and neither is Wietse.
Not personally addressed to anyone, but for all Linux hackers to
consider are the following parts:
See it from the user-space programmer's point of view. Imagine you're
developing your software on FreeBSD or Solaris, or whatever. Now imagine
a client/user asks you about Linux support. You figure Linux does an
ioctl differently than BSD - that's all you see in the first place. You
start wondering, tracking, debugging, end up reading kernel sources, and
you see the difference. You go for support, and all you hear is "well,
we want to keep this non-portable for egoistic compatibility reasons,
use netlink instead". As to netlink, "go get ip of iproute2 and see how
it does things".
The programmer of a portable application is annoyed and frustrated
because it's just another fucking subtle API difference, and it
coincides with a boggled and outdated netdevice(7) man page.
It's not a sign of quality if Linux man pages are updated months after
the code either.
Does anyone think these issues help Linux or get Linux anywhere except
to bad reputation?
There are a lot of competent people with their hands on Linux, and
generally, Linux works well, and people are helpful, but sometimes,
developers seem to lose the more global view. Linux is not longer an end
in itself. Please don't let portability slip from your view.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/