| PLEX86 | ||
|
DVD Players 4242-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SendKeys" equivalent in Linux On Mon, 25 Jul 2005 02:10:07 +0200, Wolfgang Draxinger staggered into the Black Sun and said: Aye. You don't need to mess around at that low of a...
As a Free Software programmer, I can tell you that it's not a nightmare. It's not much of a big deal at all, in reality. If you write portable code, you generally have code that works on any there are tools like autoconf that can handle this for you. Portability between different Linux distributions is a much simpler problem than portability between different UNIX vendors' systems, yet the majority of free software already works on most contemporary UNIX systems. In short, it's a non-problem for all but a few exceptional programs, which might be tied to various kernel or libc versions (typically linux kernel support utilities e.g. modutils) They contribute the driver to the Linux kernel maintainers, it gets included in the kernel mainline, and all the distributions distribute it. If a manufacturer wants to release a binary-only driver, that's their support problem. Binary-only drivers *are* a support nightmare. This is why no company does this unless they are masochists. Releasing the driver as source and getting it included in the kernel pushes the support onto the kernel and distribution maintainers, which is a better plan all round. That's why most people don't build from source. For those that do, they can generally build their distribution's packages from source (in Debian, this is what package build dependencies are for). If you want to build directly from the release tarballs, you do need a clue. Regards, Roger - -- Roger Leigh GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU-Linux) iD8DBQFC5BHKVcFcaSW-uEgRAoKTAJ9vsH0ruJQCXF17LGP2-+PiR9cGdACeIFg7 YToTrQv14SDlBpzCIdYKveg= =4aEJ -----END PGP SIGNATURE-----
|
||||
Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||