From: "D. Hazelton" <dhazelton@enter.net>
To: Denis Vlasenko <vda@ilport.com.ua>
Cc: Andrew Morton <akpm@osdl.org>,
Yaroslav Rastrigin <yarick@it-territory.ru>,
andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
Date: Tue, 10 Jan 2006 23:57:01 -0500 [thread overview]
Message-ID: <200601102357.02502.dhazelton@enter.net> (raw)
In-Reply-To: <200601101526.24786.vda@ilport.com.ua>
On Tuesday 10 January 2006 08:26, Denis Vlasenko wrote:
> On Tuesday 10 January 2006 10:33, D. Hazelton wrote:
> > On Tuesday 10 January 2006 02:33, Denis Vlasenko wrote:
> > <snip>
> >
> > > Andrew, I think this is a rare (on lkml at least) case when guy
> > > does not want to participate in development in a Linux way
> > > but wants to just pay for development instead:
> > > "I want this <hardware> to work good under Linux. I want to pay
> > > up to <sum> to whoever will agree to do that. Anybody?"
> > >
> > > Do not dismiss him lightly. There are LOTS of people which aren't
> > > hackish at all. An order of magniture more than 'us' computer geeks.
> > > M$ is successful because it uses this resource.
> > > We may want to think how can we use it too.
> > >
> > > No, I don't think you, or someone else on this list can efficiently
> > > use it, but distros, being more commercially oriented, maybe can.
> >
> > This is true. The types of bounties I have seen in OS development do not
> > usually reach much beyond $500. If distro's were to get behind this and
> > start offering bounties of large sums for _working_ code for hardware
> > there might be a response.
>
> I meant a different thing. Distro is a commercial entity.
> Users can buy services from businesses. "Write (or fix) me a driver"
> is a service.
>
> People inclined to just pay for code instead of helping with coding
> may have greater success talking to distros.
>
> Of course, distros then will hire someone from lkml crowd to actually do
> it.
>
> If there will be enough of cash flow from such requests, this can
> becode somebody's full time job.
Almost exactly what I meant. Truth is, though, that I mentioned the "bounty"
system because its flexible enough that the distro's wouldn't have to hire
someone full-time. However, I can see that it would make a difference in
several respects. Statement withdrawn.
D. Hazelton
next prev parent reply other threads:[~2006-01-11 4:46 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 7:54 Why the DOS has many ntfs read and write driver,but the linux can't for a long time Boxer Gnome
2006-01-09 8:06 ` Erik Andersen
2006-01-09 8:21 ` Boxer Gnome
2006-01-09 8:53 ` Jim Crilly
2006-01-09 9:07 ` Yaroslav Rastrigin
2006-01-09 10:22 ` Alistair John Strachan
2006-01-09 11:03 ` Yaroslav Rastrigin
2006-01-09 12:45 ` CaT
2006-01-09 13:34 ` Yaroslav Rastrigin
2006-01-10 13:29 ` Helge Hafting
2006-01-10 16:29 ` Randy.Dunlap
2006-01-11 2:29 ` David Nicol
2006-01-11 2:56 ` Lee Revell
2006-01-12 18:53 ` David Nicol
2006-01-12 21:05 ` Lee Revell
2006-01-09 13:36 ` Kasper Sandberg
2006-01-09 13:56 ` Yaroslav Rastrigin
2006-01-09 16:07 ` Alan Cox
2006-01-09 16:15 ` Lee Revell
2006-01-09 16:34 ` Alan Cox
2006-01-09 16:34 ` Olivier Galibert
2006-01-09 19:24 ` Diego Calleja
2006-01-09 19:33 ` Lee Revell
2006-01-09 13:54 ` Lee Revell
2006-01-09 14:51 ` [OT?] " Yaroslav Rastrigin
2006-01-09 15:15 ` Lee Revell
2006-01-09 15:36 ` Randy.Dunlap
2006-01-14 9:55 ` Pavel Machek
2006-01-09 15:17 ` Pekka Enberg
2006-01-09 14:32 ` Bernd Petrovitsch
2006-01-09 15:22 ` Denis Vlasenko
2006-01-09 19:07 ` Diego Calleja
2006-01-09 22:49 ` Dave Airlie
2006-01-10 12:00 ` Pavel Machek
2006-01-09 13:56 ` Lee Revell
2006-01-10 7:13 ` Andrew Morton
2006-01-10 7:33 ` Denis Vlasenko
2006-01-10 8:33 ` D. Hazelton
2006-01-10 10:49 ` Diego Calleja
2006-01-10 13:26 ` Denis Vlasenko
2006-01-11 4:57 ` D. Hazelton [this message]
2006-01-10 9:32 ` Yaroslav Rastrigin
2006-01-10 9:20 ` Yaroslav Rastrigin
2006-01-10 10:50 ` Diego Calleja
2006-01-09 16:32 ` Bernd Petrovitsch
[not found] <5t06S-7nB-15@gated-at.bofh.it>
[not found] ` <5t34G-3Zu-21@gated-at.bofh.it>
[not found] ` <5t5pU-7tD-37@gated-at.bofh.it>
[not found] ` <5t5JU-7Sn-11@gated-at.bofh.it>
2006-01-09 14:18 ` Robert Hancock
2006-01-09 14:28 ` Oliver Neukum
2006-01-09 15:15 ` Lee Revell
2006-01-09 16:02 ` Oliver Neukum
2006-01-09 16:04 ` Lee Revell
2006-01-09 16:14 ` Oliver Neukum
2006-01-09 16:19 ` Lee Revell
2006-01-09 16:29 ` Bernd Petrovitsch
2006-01-09 16:41 ` Lee Revell
2006-01-09 16:53 ` Oliver Neukum
2006-01-09 16:56 ` Lee Revell
2006-01-09 17:14 ` Olivier Galibert
2006-01-09 17:28 ` Lee Revell
2006-01-09 19:35 ` Anton Altaparmakov
2006-01-09 17:14 ` Bernd Petrovitsch
2006-01-09 17:31 ` Alan Cox
2006-01-09 16:45 ` Jeff V. Merkey
2006-01-09 17:33 ` Lee Revell
2006-01-09 18:11 ` Marcin Dalecki
2006-01-09 17:45 ` Oliver Neukum
2006-01-09 16:59 ` Bernd Petrovitsch
2006-01-10 1:44 ` Alistair John Strachan
2006-01-10 4:30 ` Lee Revell
2006-01-10 10:13 ` Jakob Oestergaard
2006-01-10 10:34 ` Jesper Juhl
-- strict thread matches above, loose matches on Subject: below --
2006-01-10 23:48 Lukas Hejtmanek
2006-01-10 23:57 ` Lee Revell
2006-01-11 0:02 ` Lukas Hejtmanek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601102357.02502.dhazelton@enter.net \
--to=dhazelton@enter.net \
--cc=akpm@osdl.org \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@ilport.com.ua \
--cc=yarick@it-territory.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox