From: linas@austin.ibm.com (linas)
To: linux-hotplug@vger.kernel.org
Subject: Re: Trying to compile udev + libsysfs
Date: Thu, 12 Jan 2006 17:52:45 +0000 [thread overview]
Message-ID: <20060112175245.GT26221@austin.ibm.com> (raw)
In-Reply-To: <20060105173502.GA2408@kroah.com>
On Thu, Jan 12, 2006 at 01:33:20PM +0100, Wolfgang Klein was heard to remark:
>
> Like I told you before: if I waited for SuSE to update the kernel
> version I would still be stuck with kernel 2.6.4 or something.
2.6.5 actually. However, that kernel has hundreds of patches applied,
including backports from a variety of stuff that went into 2.6.6
thorugh 2.6.15. The other potential advantage is that (for the
hardware that I work with) it gets far more testing than the mainline
kernel. Specifically, there are entire depts of people here at IBM
whose only job is to stress-test the SUSE kernels into oblivion on
the entire spectrum of IBM hardware, old and new. By contrast, any
testing of mainline is haphazard, being the effort of a few kernel
developers hacking on a few boxes. e.g. right now, I'm working on
a bug in today's mainline, which was never a bug in SUSE.
I suspect the same is true for other big hardware vendors (HP, etc)
but probably not for misc retail white-box PC's.
--linas
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-01-12 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 17:35 Trying to compile udev + libsysfs Greg KH
2006-01-05 23:25 ` Greg KH
2006-01-06 20:10 ` Gioele Barabucci
2006-01-09 16:06 ` Kay Sievers
2006-01-12 6:53 ` Greg KH
2006-01-12 17:52 ` linas [this message]
2006-01-12 19:51 ` Greg KH
2006-01-12 19:56 ` Greg KH
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=20060112175245.GT26221@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).