Mark Mielke <mark@mark.mielke.cc>> On Wed, Jun 12, 2002 at 09:00:08AM -0400, jamal wrote:> > On Wed, 12 Jun 2002, Lincoln Dale wrote:> > > At 08:33 AM 12/06/2002 -0400, jamal wrote:> > > >If 3 people need it, then i would like to ask we add lawn mower> > > >support that my relatives have been asking for the last 5 years.> > > lawn-mower support sounds like a userspace application to me.> > But we need a new system call support> > This is another non-argument not dissimilar to the method of arguing that> David has used up to this point.> > If lawn-mower support (whatever that is) is something that people> would use, then perhaps it *should* be added, even if it needs a new> system call. You have not shown a valid argument against your own> sarcastic suggestion, other than an implicit sneer.

Linux development has _always_ worked by:

1) You have a problem2) You come up with a solution3) Others use your patch, perhaps refine it4) A discussion ensues on the worthyness of the patch5) The community (or at least the halfgods in charge of keeping the Holy Source ;-) sees that the patch is worthwile, tested, and has enough users6) After some further cleanups and fixes the patch is accepted into the kernel7) The code is carried as part of the standard kernel, and updated with it

Being halfway through (2) or going on (3) and whining that _others_ do thework to take care of finishing implementing a solution and then maintainingit for you (jumping to (7)) won't get you anywehere. Guaranteed.

Perhaps your proposed solution is subobtimal.

Perhaps your problem is so outlandish that a solution has no place in thestandard kernel.