mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Per Jessen" <per@computer.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Mark H. Wood" <mwood@IUPUI.Edu>,
	"Dave Rattay [ITeX]" <Dave.Rattay@itexinc.com>
Subject: RE: Dlink DSL PCI Card
Date: Sat, 23 Feb 2002 14:10:28 +0100	[thread overview]
Message-ID: <3C7793D8000013C1@freesurfmta01.sunrise.ch> (raw)

On Sat, 23 Feb 2002 07:42:10 -0500 (EST), Mark H. Wood wrote:

>> comes out from Microsoft (such as XP) we are given beta copies 6 months
>> in advance so that our drivers hit the market along side the new OS
>> release.  This just doesn't happen with Linux.
>
>Sure it does.  It happens right here on LKML and some other lists.  You
>can get early-release images of Linux 2.5 right now.  The distribution
>builders won't pick up 2.5 for many months.

Isn't/wasn't 2.5 meant as a development release ? And 2.4 was meant as production, 
but certainly had more iterations than you would have expected of such.
If 2.5 is a development-release, I would not expect distros to pick it up
any time soon - just like they never shipped anything with 2.3. Even when
SuSE started shipping 2.4.0, the distro carried a clear recommendation of
using 2.2.18.

There are significant differences in the way Linux development happens and 
the way in which commercial software is release-managed. It's a fact. 
If Linux kernel development were to stick with the initial idea that odd releases 
are development, even are production, then it might be easier to keep up. In 
which case itexcinc would perhaps now be looking at 2.5x with an aim of releasing
drivers for 2.6.
\v
>
>(Stores need to understand this too.  A lot of sales have gone to one
>rather than another because store B told me what chipset was used in a
>board-level product, and store A would not.)

Wishful thinking - people who understand the importance of which chipset on which
board are usually not employed as shop-assistants.


/Per
PS: I'm all for the main point that's being argued here - but I do understand 
itexcinc's point of view.

regards,
Per Jessen, Zurich
http://www.enidan.com - home of the J1 serial console.

Windows 2001: "I'm sorry Dave ...  I'm afraid I can't do that."



             reply	other threads:[~2002-02-23 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23 13:10 Per Jessen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-22 23:27 Dave Rattay [ITeX]
2002-02-22 23:39 ` Erik Andersen
2002-02-23 12:42 ` Mark H. Wood
2002-02-22 23:00 Dave Rattay [ITeX]
2002-02-22 22:33 Dave Rattay [ITeX]
2002-02-22 22:49 ` Benjamin LaHaise
2002-02-23  0:00   ` Michal Jaegermann
2002-02-22 23:15 ` Stephan von Krawczynski
2002-02-20  0:36 Andrew Hatfield
2002-02-20  1:57 ` Andrew Hatfield
2002-02-20 18:50 ` S W
2002-02-20 19:53   ` Alan Cox
2002-02-20 20:14     ` S W
2002-02-22 16:36     ` Benjamin LaHaise
2002-02-22 17:19     ` Stephan von Krawczynski

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=3C7793D8000013C1@freesurfmta01.sunrise.ch \
    --to=per@computer.org \
    --cc=Dave.Rattay@itexinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwood@IUPUI.Edu \
    /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

all inboxes | Powered by JetHome®