Linux drivers management
Quoted 6 lines
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.
Signature · 1 line
Nicolas Mailhot
Hi,
Quoted 6 lines · Nicolas Mailhot
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.
Huh...
Quoted 2 lines
Do you really think us end-users enjoy hunting your drivers all over the net because you never bothered pushing them to mainline ?
He don't needs to "bother". He wrote the drivers. And you never paid him. (Take it, "this software is beer-free" overusers, straight in your face).
Quoted 1 line
[Loads of "I'm actually proving his point, but I want to be in mainstream, so..." skipped]
You have just nicely proved all the stable API pros. 'Cause when interfaces are clearly defined, described and implemented according to documentation, you won't need to even recompile (in case of ABI compatibility) or
search for newer driver version, if your current version works nicely. You don't need to lay burden of sifting through and fixing metric boatloads of code when internals change onto changemaker's shoulders, 'cause everything what he needs to be concerned about is API compatibility. And if some particular driver worked with 2.x.xx but the same driver source fails to work on 2.x.xx+1 - you know where to search and what to do. And driver vendors could concentrate on improving driver cores,
instead of rewriting interfaces. And kernel developers could concentrate on developing kernel features, instead of thinking "I'll introduce changes in this subsystem, this change will certainly affect IDE, SCSI, networking and may touch firewalling code" and spending O(N!) time modifying all affected device drivers' source by himself, instead of O(N)/O(1). And average patchset size will shrink by order of magnitude for medium changes. And...
Quoted 3 lines
But do not invoke end-users. Or end users will answer you.
They ARE answering already.
Signature · 1 line
Managing your Territory since the dawn of times ...
Quoted 7 lines · Nicolas Mailhot
Quoted 5 lines
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.
I heartily agree with this!!
I use two products that use out-of-tree drivers. VMWare and NVidia cards. Fortunately, the build processes for both are rather painless, but there have been times when it has *not* been, and it was extremely frustrating. I remember when VMWare was not doing a good job of supporting 2.6 kernels and I spent the better part of two days trying to track down a solution. I finally did, but it was a third party, non-VMWare, patch to the VMWare code that fixed it so it would compile and run. That's not what I consider convenience for the non-technical user. A non-technical user would not have been able to do what I did, especially when they just want their software to work.
Quoted 3 lines
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 ?
I want to install my machine and have everything work. Don't make me chase all over the net trying to find a driver for my hardware. If it's a network (i.e. ethernet device) the driver had *better* be in the tree. Trying to download the driver to another computer, transferring, etc, is enough to make me find another brand of network card.
Quoted 3 lines
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 ?
Latest kernel == latest driver. No need for me to try to keep all my drivers up to date.
Quoted 4 lines
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 ?
See comment about VMWare above.
Quoted 2 lines
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 ?
I sometimes delay kernel updates because I don't want to mess with updating my NVidia and VMWare drivers. This is *not* good for security.
Quoted 1 line
But do not invoke end-users. Or end users will answer you.
So I did. Please put your driver in the tree. It will be better for all concerned.
j----- k-----
Signature · 3 lines
Joshua Kugler PGP Key: http://pgp.mit.edu/ CDE System Administrator ID 0xDB26D7CE http://distance.uaf.edu/
Hi,
Quoted 12 lines
I heartily agree with this!!
I use two products that use out-of-tree drivers. VMWare and NVidia cards. Fortunately, the build processes for both are rather painless, but there have been times when it has *not* been, and it was extremely frustrating. I remember when VMWare was not doing a good job of supporting 2.6 kernels and I spent the better part of two days trying to track down a solution. I finally did, but it was a third party, non-VMWare, patch to the VMWare code that fixed it so it would compile and run. That's not what I consider convenience for the non-technical user. A non-technical user would not have been able to do what I did, especially when they just want their software to work.
And then think, why do you need to _build_ drivers in the first place.
Wouldn't it be better to have one vmware.ko which insmod's with all 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain" away completely ?
Quoted 3 lines
I want to install my machine and have everything work. Don't make me chase all over the net trying to find a driver for my hardware. If it's a network
All over the net ? Again, you're proving stable API/ABI supporters nicely.
If kernel has stable ABI, basic/default driver is included on installation CD, and all you need to do is to launch ./install-linux.sh from CD in your shell or click OK and enter your root password in GUI box. Newer/better driver - just go to device manufacturer's website, download installation package and install this driver. Without rebuilding.
Quoted 3 lines
(i.e. ethernet device) the driver had *better* be in the tree. Trying to download the driver to another computer, transferring, etc, is enough to make me find another brand of network card.
And what to do if you've bought new hardware, installed it and _voila_ - NO IN-TREE DRIVER exists ?
Do you want every Linux user going for shopping to nearest WalMart carry full linux hardware compatibility list printed out ? Or intree driver list ?
Quoted 2 lines
Latest kernel == latest driver. No need for me to try to keep all my drivers up to date.
Wrong. Latest kernel is latest kernel. Latest driver is latest driver. They are different entities, and don't mix'em.
Quoted 3 lines
I sometimes delay kernel updates because I don't want to mess with updating my NVidia and VMWare drivers. This is *not* good for security.
So who to blame ? Maybe, just look at those who don't want stable driver API ?
Quoted 2 lines
So I did. Please put your driver in the tree. It will be better for all concerned.
Please, don't force your preferences over others'
Signature · 1 line
Managing your Territory since the dawn of times ...
Hello!
Quoted 4 lines
And then think, why do you need to _build_ drivers in the first place. Wouldn't it be better to have one vmware.ko which insmod's with all 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain" away completely ?
Well, you want the vmware.ko to contain machine code for at least 17 different architecture the kernel runs on? ;-)
Quoted 2 lines
If kernel has stable ABI, basic/default driver is included on installation CD, and all you need to do
[...]
... and I'm screwed if I happen to use a 2 years old network card with written for a 2.4.x kernel, while I am running on 2.6.x.
Quoted 4 lines
is to launch ./install-linux.sh from CD in your shell or click OK and enter your root password in GUI box. Newer/better driver - just go to device manufacturer's website, download installation package and install this driver. Without rebuilding.
While now, I don't need to install or rebuild anything, just use the stock kernel which already contains the drivers :)
Quoted 2 lines
And what to do if you've bought new hardware, installed it and _voila_
- NO IN-TREE DRIVER exists ?
The same like what I do if I buy new hardware and no Linux driver exist -- call myself an uninformed ignoramus, because that's who I am.
Quoted 1 line
Please, don't force your preferences over others'
Doesn't this sentence apply to you as well? ;-)
Have a nice fortnight
Signature · 3 lines
Martin `MJ' Mares <[email protected]> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth It said, "Insert disk #3," but only two will fit!
Quoted 7 lines · Martin Mares
Quoted 4 lines
And then think, why do you need to _build_ drivers in the first place. Wouldn't it be better to have one vmware.ko which insmod's with all 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain" away completely ?
Well, you want the vmware.ko to contain machine code for at least 17 different architecture the kernel runs on? ;-)
I think we will first need to hack binutils. The last time I heared about it, Fat Binaries weren't implemented (only containing object code for two different architectures), let alone for _all_ architectures...
Even getting all GCCs to compile with the same version would be an adventure...
MfG, JBG
Signature · 4 lines
Jan-Benedict Glaw [email protected] . +49-172-7608481 _ O _ "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Quoted 9 lines · Yaroslav Rastrigin
Quoted 9 lines
I use two products that use out-of-tree drivers. VMWare and NVidia cards. Fortunately, the build processes for both are rather painless, but there have been times when it has *not* been, and it was extremely frustrating. I remember when VMWare was not doing a good job of supporting 2.6 kernels and I spent the better part of two days trying to track down a solution. I finally did, but it was a third party, non-VMWare, patch to the VMWare code that fixed it so it would compile and run. That's not what I consider convenience for the non-technical user. A non-technical user would not have been able to do what I did, especially when they just want their software to work.
Quoted 3 lines
And then think, why do you need to _build_ drivers in the first place.
Wouldn't it be better to have one vmware.ko which insmod's with all 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain" away completely ?
This would only work if we sacrified the freedom to change something. The kernel code base changes. A lot, actually. If it didn't, there eg. wouldn't be suspend2whatever, because the API was plain missing back in those days. So sacrifice evolution for backwards compatibility?
These days (and it has always been that way) kernel development is a quite active process. If core-APIs need to be changed, the person who does it usually also updates all users of the given API. That won't work if the drivers are not in the codebase, no chance to grep for something on 3rd vendor's websites...
Quoted 7 lines
Quoted 2 lines
I want to install my machine and have everything work. Don't make me chase all over the net trying to find a driver for my hardware. If it's a network
All over the net ? Again, you're proving stable API/ABI supporters nicely.
If kernel has stable ABI, basic/default driver is included on installation CD, and all you need to do is to launch ./install-linux.sh from CD in your shell or click OK and enter your root password in GUI box. Newer/better driver - just go to device manufacturer's website, download installation package and install this driver. Without rebuilding.
Not everybody is using RedHar, SuSE, Debian or whatever. Consider I was building a custom QBus-to-PCI bridge to use some ATI/NVidia graphics board in my 15y old VAX. If my hardware hack required broadening some in-kernel API, do you really think some guy at NVidia (only to name an example:-) would cross-compile their stuff for a VAX? Given a userbase of exactly _one_ person?
Quoted 6 lines
Quoted 3 lines
(i.e. ethernet device) the driver had *better* be in the tree. Trying to download the driver to another computer, transferring, etc, is enough to make me find another brand of network card.
And what to do if you've bought new hardware, installed it and _voila_ - NO IN-TREE DRIVER exists ?
Do you want every Linux user going for shopping to nearest WalMart carry full linux hardware compatibility list printed out ? Or intree driver list ?
Usually, it's quite simple to buy correct hardware. Look for something that's a tad more intelligent (SCSI scanners in favour of USB/parport, postscript printers, ...) and offloads the host CPU.
Quoted 3 lines
Quoted 2 lines
I sometimes delay kernel updates because I don't want to mess with updating my NVidia and VMWare drivers. This is *not* good for security.
So who to blame ? Maybe, just look at those who don't want stable driver API ?
The Linux kernel is a project (or hundreds actually) that have choosen their way of operation. That's evolution with not a lot of looking-back. If you want to have a stable API, heck, just prepare another fork and implement it. If this is what users want, they'll take it.
Quoted 3 lines
Quoted 2 lines
So I did. Please put your driver in the tree. It will be better for all concerned.
Please, don't force your preferences over others'
My (personal!) view is that Linux isn't actually about the users. It's about the developers. Developers develop what they have a use for (or become famous.) Sometimes, regular users can make good use of it, once distributions prepared all the userland.
So if you're a developer, try to become famous for implementing a stable API.
If you're a user, stop fighting against an operating system's kernel and start looking for a system _you_ want to use. Maybe some WinXP variant?
MfG, JBG
Signature · 4 lines
Jan-Benedict Glaw [email protected] . +49-172-7608481 _ O _ "Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Quoted 17 lines · Yaroslav Rastrigin
Hi,
Quoted 12 lines
I heartily agree with this!!
I use two products that use out-of-tree drivers. VMWare and NVidia cards. Fortunately, the build processes for both are rather painless, but there have been times when it has *not* been, and it was extremely frustrating. I remember when VMWare was not doing a good job of supporting 2.6 kernels and I spent the better part of two days trying to track down a solution. I finally did, but it was a third party, non-VMWare, patch to the VMWare code that fixed it so it would compile and run. That's not what I consider convenience for the non-technical user. A non-technical user would not have been able to do what I did, especially when they just want their software to work.
And then think, why do you need to _build_ drivers in the first place.
Wouldn't it be better to have one vmware.ko which insmod's with all 2.6 versions , from 2.6.0 to 2.6.16-rc2 , and throw "upgrade pain" away completely ?Quoted 1 line
Quoted 5 lines
Quoted 2 lines
I want to install my machine and have everything work. Don't make me chase all over the net trying to find a driver for my hardware. If it's a network
All over the net ? Again, you're proving stable API/ABI supporters nicely.
If kernel has stable ABI, basic/default driver is included on installation CD, and all you need to do is to launch ./install-linux.sh from CD in your shell or click OK and enter your root password in GUI box.
Why should I have to bother with that?
It's a lot more convenient that my new kernel just "magically" includes the driver for my hardware, and the latest version of that driver even. No inserting cd, run install script, navigate through installer etc crap.
Quoted 1 line
Newer/better driver - just go to device manufacturer's website, download installation package and install this driver.
1. You are assuming all users have internet connections and can do that - not true.
2. Again, why should I have to go through the trouble of first finding the manufacturers website, then find out where they keep the drivers, then download and figure out how to install the driver?
3. What if the manufacturer goes out of business and the website disappears?
4. What happens when the manufacturer stops updating the driver? Even with an almost 100% frozen driver API changes *will* happen over time and the driver will eventually stop working - or, if the driver API is kept *100%* frozen then the core kernel will steadily aquire a huge amount of backwards compatibility cruft which will eventually become a maintainance nightmare.
Quoted 1 line
Without rebuilding.
Users of distro kernels already have the in-kernel drivers prebuild for them. Users of custom kernels have to build the core kernel anyway, buildign a driver or two at the same time is no big deal.
Quoted 4 lines
Quoted 3 lines
(i.e. ethernet device) the driver had *better* be in the tree. Trying to download the driver to another computer, transferring, etc, is enough to make me find another brand of network card.
And what to do if you've bought new hardware, installed it and _voila_ - NO IN-TREE DRIVER exists ?
Then you bought the wrong hardware.
Quoted 2 lines
Do you want every Linux user going for shopping to nearest WalMart carry full linux hardware compatibility list printed out ? Or intree driver list ?
Users who prefer not to have hardware trouble would be wise to check compatibility before purchasing. This goes not only for Linux, but for any OS - and don't say "all hardware has manufacturer supplied drivers for Windows" 'cos that's not true, and there are several incompatible windows versions, just try loading WinXP drivers on Windows98 or a WinNT driver on Windows Server 2003 or any other fun combination.
Quoted 4 lines
Quoted 2 lines
Latest kernel == latest driver. No need for me to try to keep all my drivers up to date.
Wrong. Latest kernel is latest kernel. Latest driver is latest driver. They are different entities, and don't mix'em.
Quoted 1 line
When the driver is maintained in-tree, latest kernel == latest driver.
Quoted 3 lines
Quoted 2 lines
I sometimes delay kernel updates because I don't want to mess with updating my NVidia and VMWare drivers. This is *not* good for security.
So who to blame ?
NVidia and VMWare obviously for not submitting Open Source drivers for inclusion in mainline.
Quoted 4 lines
Maybe, just look at those who don't want stable driver API ?
Quoted 2 lines
So I did. Please put your driver in the tree. It will be better for all concerned.
Please, don't force your preferences over others'
Nobody is forcing anybody to do anything. We are just not bending over backwards for people who refuse to work with us in-tree. If someone wants to maintain drivers out-of-tree they are perfectly free to do so, they just don't get the bennefit of having their drivers auto-updated when API's change and they don't get the bennefit of many develoers improving their drivers, they have to do *all* the work themselves - but that's their choice, noone forced it on them.
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
On Mon, 2006-02-06 at 22:17 +0300, Yaroslav Rastrigin wrote:
[...]
Quoted 1 line
All over the net ? Again, you're proving stable API/ABI supporters nicely.
Not necessarily since there are other solutions like "submit the driver into the kernel".
And exactly then you get the best of both worlds: The driver is "up to date" and not even distributors have care (well, at least for almost all of them).
Quoted 1 line
If kernel has stable ABI, basic/default driver is included on installation CD, and all you need to do
Have fun done *doing* this.
Quoted 2 lines
And what to do if you've bought new hardware, installed it and _voila_ - NO IN-TREE DRIVER exists ?
Do you want every Linux user going for shopping to nearest WalMart carry full linux hardware compatibility list printed out ?
It worked years ago that way. So what?
Bernd
Signature · 3 lines
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and ServicesQuoted 56 lines · Joshua Kugler
Quoted 7 lines · Nicolas Mailhot
Quoted 5 lines
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.
I heartily agree with this!!
I use two products that use out-of-tree drivers. VMWare and NVidia cards. Fortunately, the build processes for both are rather painless, but there have been times when it has *not* been, and it was extremely frustrating. I remember when VMWare was not doing a good job of supporting 2.6 kernels and I spent the better part of two days trying to track down a solution. I finally did, but it was a third party, non-VMWare, patch to the VMWare code that fixed it so it would compile and run. That's not what I consider convenience for the non-technical user. A non-technical user would not have been able to do what I did, especially when they just want their software to work.
Quoted 3 lines
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 ?
I want to install my machine and have everything work. Don't make me chase all over the net trying to find a driver for my hardware. If it's a network (i.e. ethernet device) the driver had *better* be in the tree. Trying to download the driver to another computer, transferring, etc, is enough to make me find another brand of network card.
Quoted 3 lines
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 ?
Latest kernel == latest driver. No need for me to try to keep all my drivers up to date.
Quoted 4 lines
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 ?
See comment about VMWare above.
Quoted 2 lines
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 ?
I sometimes delay kernel updates because I don't want to mess with updating my NVidia and VMWare drivers. This is *not* good for security.
Quoted 1 line
But do not invoke end-users. Or end users will answer you.
So I did. Please put your driver in the tree. It will be better for all concerned.
Quoted 6 lines
j----- k-----
--
Joshua Kugler PGP Key: http://pgp.mit.edu/
CDE System Administrator ID0xDB26D7CE
http://distance.uaf.edu/
Maybe it would be better for no drivers to be in the tree! Something along the lines of an automatic FTP site that interacts with a configuration program. You end up downloading the drivers that you need. In the case where you don't have an Internet connection, a distribution company would put the mirror on a CD or DVD.
Right now, there are really too many drivers in the kernel. The kernel should have a stable API for drivers and they should be in a separate tree, either on the Web or on a distribution disc. There are many drivers that are as old as Linux! The 3c501.c and 3c503.c are examples. You can't remove them from the kernel without invoking a thousand angry responses. These boards and the ne*.c network boards just won't go away!
This means that the amount of drivers will continue to increase to, eventually, an unmanagable amount. This is why they really need to be seperately managed!
Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.66 BogoMips). Warning : 98.36% of all statistics are fiction.
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
Quoted 8 lines · linux-os (Dick Johnson)
Maybe it would be better for no drivers to be in the tree! Something along the lines of an automatic FTP site that interacts with a configuration program. You end up downloading the drivers that you need. In the case where you don't have an Internet connection, a distribution company would put the mirror on a CD or DVD.
Regardless of whether or not the idea is practical, where would the funding come from? Who is going to donate their time? What if they get bored of it and nobody wants to pick up?
There are enough of us working for free on this stuff, and those that get paid already have enough on their plate. What you're asking for is something that just isn't practical.
When I first read this, I thought you were joking... unfortunately, it looks like you are being serious.
Quoted 10 lines
Right now, there are really too many drivers in the kernel. The kernel should have a stable API for drivers and they should be in a separate tree, either on the Web or on a distribution disc. There are many drivers that are as old as Linux! The
3c501.cand3c503.care examples. You can't remove them from the kernel without invoking a thousand angry responses. These boards and the ne*.c network boards just won't go away!
Why would we WANT to remove them? Linux is just about the only operating system that will run well on all old machines. If we were to remove these drivers from the kernel, we might as well all throw our old hardware into the garbage.
Quoted 5 lines
This means that the amount of drivers will continue to increase to, eventually, an unmanagable amount. This is why they really need to be seperately managed!
That's part of what subsystems and subsystem maintainers are for. Looks like somebody thought ahead. ;-)
FYI, v4l/dvb drivers can be built separately from the kernel as modules, directly from our mercurial repository, and we try to keep them all backwards compatable with older vanilla kernels. Surely there are other subsystems that do something similar.
Quoted 3 lines
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
^^^ I'm sure you've been flamed about this already, so I won't say it....
Cheers,
Michael Krufky
Le lundi 06 février 2006 à 14:21 -0500, linux-os (Dick Johnson) a écrit :
Quoted 8 lines
Right now, there are really too many drivers in the kernel. The kernel should have a stable API for drivers and they should be in a separate tree, either on the Web or on a distribution disc. There are many drivers that are as old as Linux! The
3c501.cand3c503.care examples. You can't remove them from the kernel without invoking a thousand angry responses. These boards and the ne*.c network boards just won't go away!
This is another proof in-kernel maintenance is cheaper.
If out-of-tree drivers where lower maintenance like it's claimed, they'd have a lower attrition rate than in-kernel stuff.
Signature · 1 line
Nicolas Mailhot
Quoted 7 lines · Nicolas Mailhot
Quoted 5 lines
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.
So will I, but this message says it better than one of my rants would. So I'll just second it and add:
Get used to it David, you are NOT going to change it with anything resembling your current arguments, which IMO do nothing but waste bandwidth, and busy peoples time. Go away, way away. Go sabotage a winderz project and leave us the hell alone.
Quoted 43 lines
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.
Signature · 7 lines
Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.