> I think I am in a different position like you guys, I've been work with > Linux from programmer level to Linux promotion . My goal is not just > focus on Linux technical or programming, I would like to promote this > operating system to not just for programmers, but also non-technical > end-users . Since you invoke end-users I'll answer. This end-user is mad at hell at people like you that advocate separating drivers from mainline. Do you really think us end-users enjoy hunting your drivers all over the net because you never bothered pushing them to mainline ? Do you really think we enjoy clicking though boatloads of HTML/js/flash forms that will inform us about vastly important things like your custom license, the mirror list you want us to master or your dog's birthday ? Do you really think we enjoy learning all your out-of-tree driver release and build processes because you couldn't be bothered with using the same one as the kernel ? Do you really think we enjoy locating the patch that will "fix" your driver for our kernel because you do not bother testing anything else than a few kernel releases, and that only for a few months after a you wrote your driver ? Do you really think we enjoy having out out-of-tree drivers stomp on each-other in their eagerness to downgrade parts our working kernel to whatever broken and obsolete version the developer happened to test ? Do you really think we enjoy navigating support forums to find out who's responsible for the mess ? Do you really think we enjoy leaving in fear of a system update because the first thing to break will be your out-of-tree drivers ? When a driver is part of mainline it'll be in the distro kernel. It'll be autosetup by distro tools. It'll be auto-updated by system tools. Me the end user won't even have to know there is a driver involved - everything will "just work". Be honest and invoke developer laziness if you want. Invoke the utter lack of interest of some developers in packaging or making their stuff working on anything but their own box. Invoke their fear of a thorough review process. Point out that they are paid to deliver a pile of code by companies that care little if it's used or not. There are loads of actual (bad) reasons for your demand. But do not invoke end-users. Or end users will answer you. -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
- Follow-Ups:
- Re: Linux drivers management
- From: Gene Heskett <[email protected]>
- Re: Linux drivers management
- From: Joshua Kugler <[email protected]>
- Re: Linux drivers management
- From: Yaroslav Rastrigin <[email protected]>
- Re: Linux drivers management
- Prev by Date: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
- Next by Date: Re: EVMS & SATA failure
- Previous by thread: Re: Linux drivers management
- Next by thread: Re: Linux drivers management
- Index(es):
 |