linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Trying to compile udev + libsysfs
Date: Thu, 12 Jan 2006 06:53:19 +0000	[thread overview]
Message-ID: <20060112065319.GA32241@kroah.com> (raw)
In-Reply-To: <20060105173502.GA2408@kroah.com>

On Fri, Jan 06, 2006 at 09:56:30AM +0100, Wolfgang Klein wrote:
> Greg KH wrote:
> 
> > 
> > Why do you want to upgrade udev?  It's such a low-level part of a Linux
> 
> Because without upgrading it I still would be stuck with kernel version
> 2.6.10 (or 11?) and without upgrading udev the SuSE system refused to
> run a newer kernel version. The "old" kernel version caused some trouble
> concerning my hardware, eg: suspending the system. And let's not forget
> security issues.
> 
> Upgrading to udev 058 I was finally able to use kernel 2.6.14 and now I
> want to use 2.6.15, but the changelog says that at least udev 071 will
> be needed for that.

Ok, that makes sense.  Problem is, it's hard to upgrade kernel versions
these days on distros that are not set up to handle it.  9.2 wasn't the
best example of a release that could handle updated kernels (to be fair,
that's what I use on one of my boxes, and I got it working, but it was
hard...)

> > Sorry to hear that.  But you might find that the 10.0 release is a lot
> > nicer in regards to udev usage, now that SuSE has a few of us working
> > for them :)
> 
> That's what I am hoping for. ;-)
> 
> Before I updated to SuSE 9.2 I was using 9.0 and I remember that this
> distri wouldn't even run a kernel newer than 2.6.4 or something. So I
> had no chance to use hardware features that require a recent kernel version.
> 
> I don't want to be forced to update my entire system any time I just
> want to install a new kernel version. That's why I am still looking for
> a distribution that will allow me to use it for more than a year and
> that will be useable with recent kernel version in the future as long as
> possible. Do you think SuSE 10 will be able to be such a system?

I don't know.  Some things are getting more and more tightly bound to
speific kernel versions in userspace, as we try to intergrate things
better (which makes users happier.)  In general, users do not ever
upgrade their kernels on their own, but rely on the disto to support
them.  This is the case for the SuSE 10.0 release, and almost all others
(fedora 3 and older, etc.)

But some distros are better able to accept updated kernels, although you
loose some intregration and increase the complexity of parts of the
system.  OpenSuSE, Fedora 4, Debian unstable, Gentoo, etc. are all
examples of distros that can handle updated kernels easier.

Also, you don't want to use udev at all, feel free to upgrade your
kernel, and switch back to a static /dev.

Hope this helps,

greg k-h


-------------------------------------------------------
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

  parent reply	other threads:[~2006-01-12  6:53 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 [this message]
2006-01-12 17:52 ` linas
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=20060112065319.GA32241@kroah.com \
    --to=greg@kroah.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).