mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Carlson <carlsj@yahoo.com>
To: jerome lacoste <jerome.lacoste@gmail.com>,
	Edgar Hucek <hostmaster@ed-soft.at>
Cc: Jean Delvare <khali@linux-fr.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: New Linux Development Model
Date: Sun, 6 Nov 2005 08:50:48 -0800 (PST)	[thread overview]
Message-ID: <20051106165048.44786.qmail@web34203.mail.mud.yahoo.com> (raw)
In-Reply-To: <5a2cf1f60511060252t55e1a058o528700ea69826965@mail.gmail.com>



--- jerome lacoste <jerome.lacoste@gmail.com> wrote:

> On 11/5/05, Edgar Hucek <hostmaster@ed-soft.at>
> wrote:
> > Hi.
> >
> > Sorry for not posting my Name.
> >
> > Maybe you don't understand what i wanted to say or
> it's my bad english.
> > The ipw2200 driver was only an example. I had also
> problems with, vmware,
> > unionfs...
> > What i mean ist, that kernel developers make
> incompatible changes to the
> > header
> > files, change structures, interfaces and so on.
> Which makes the kernel
> > releases
> > incompatible.
> 
> I will ask you just one question: as a user, why did
> you want to
> upgrade your kernel?
> 
> On a server you want stability. So you don't
> upgrade. On a desktop,
> there are probably a bunch of out of kernel modules
> that will need
> upgrading with each new kernel modules. Just on the
> laptop I am using
> right now, I will have to upgrade the vmware bridge,
> nvidia driver,
> madwifi wireless driver, etc. And that's normal. The
> new development
> model didn't change that.
> 
> I avoid touching my kernel on boxes I do real work
> with. I do build a
> new kernel for test purposes and to give feedback if
> there's an issue.
> But most of the time I skip 2-3 versions before
> finding a very
> compelling reason to upgrade. And I stick with my
> distribution kernel
> as much as I can.
> 
> As for kernel/drivers developers, it's another
> story.
> 
> If it ain't broken, don't fix it.
> 
> Jerome
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Another method, the one I use, is to keep a small
drive with a minimum system on it to test/update the
kernel.  After updating the kernel and any modules
required on the test driver, its then a simple matter
to move them, if there are no problems, to my working
system.

Jack


John Carlson
<carlsj@yahoo.com>


		
__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

  parent reply	other threads:[~2005-11-06 16:50 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-05  9:42 hostmaster
2005-11-05 10:29 ` Francois Romieu
2005-11-05 11:29 ` Jean Delvare
2005-11-05 13:19   ` Edgar Hucek
2005-11-05 13:44     ` Adrian Bunk
2005-11-05 13:47     ` Alistair John Strachan
2005-11-05 22:23       ` Mark Lord
2005-11-06  0:28         ` Alistair John Strachan
2005-11-05 14:34     ` Jesper Juhl
2005-11-05 14:48       ` Oliver Neukum
2005-11-05 14:56         ` Fawad Lateef
2005-11-05 15:28         ` Adrian Bunk
2005-11-06 10:52     ` jerome lacoste
2005-11-06 11:55       ` Edgar Hucek
2005-11-06 12:39         ` Adrian Bunk
2005-11-06 12:57         ` Bernd Petrovitsch
2005-11-06 17:38         ` Jean Delvare
     [not found]       ` <436DEEFC.4020301@ed-soft.at>
2005-11-06 13:43         ` jerome lacoste
2005-11-09  0:11           ` caszonyi
2005-11-09  0:23             ` Con Kolivas
2005-11-09  7:00               ` Diego Calleja
2005-11-09 12:30             ` jerome lacoste
2005-11-09 14:03               ` caszonyi
2005-11-09 15:45                 ` Marcos Marado
2005-11-06 16:50       ` John Carlson [this message]
2005-11-06 18:17     ` Bernd Petrovitsch
2005-11-09  0:16       ` caszonyi
2005-11-06 15:22 ` Jim Nance
2005-11-06 16:55   ` John Carlson
2005-11-09  1:47 Ian Kumlien
2005-11-09 11:08 ` Marcos Marado
2005-11-09 11:30   ` Ian Kumlien
2005-11-09 12:03     ` Wed, 9 Nov 2005 13:03:07 +0100
2005-11-09 15:49       ` Ian Kumlien
2005-11-09 15:58         ` Al Viro
2005-11-09 16:32           ` Ian Kumlien
2005-11-09 12:37     ` Marcos Marado
2005-11-09 16:01       ` Ian Kumlien
2005-11-10  0:55         ` Alistair John Strachan
2005-11-10 15:10           ` Mark Lord
2005-11-10 19:29             ` Alistair John Strachan
2005-11-10 19:47               ` Ian Kumlien
2005-11-09 19:05   ` Bill Davidsen
2005-11-09 20:10     ` Marcos Marado
2005-11-10  0:57       ` Alistair John Strachan
2005-11-10 20:08         ` Bill Davidsen
2005-11-10 20:21           ` Alistair John Strachan
2005-11-12 13:45       ` Bill Davidsen

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=20051106165048.44786.qmail@web34203.mail.mud.yahoo.com \
    --to=carlsj@yahoo.com \
    --cc=hostmaster@ed-soft.at \
    --cc=jerome.lacoste@gmail.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®