From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need help to get udev/hotplug working for extra module inearly
Date: Thu, 17 Jul 2008 08:38:52 +0000 [thread overview]
Message-ID: <20080717083852.GC23332@kroah.com> (raw)
In-Reply-To: <4873789D.2080609@meinberg.de>
On Thu, Jul 17, 2008 at 09:39:36AM +0200, Holland, John wrote:
> > > Hi,
> > >
> > > nobody here who can give me a hint? Should I ask this on the kernel
> > > mailing list instead?
> >
> > Probably no one really cares about such old and unmaintained systems
> > anymore, sorry.
>
> That's not necessarily true. Many embedded systems continue to use older
> kernels, even for new development. The devices with which I'm continually
> confronted, use kernels 2.6.1[23] the newest of which is 2.6.19.
And that's their own fault, the kernel community has long had the
opinion that this is not a good thing to do.
If you are using such a kernel, then you need to rely on the support
from your vendor, the community can't help you out, sorry.
> You may want to check out mdev of a recent busybox version.
I don't see how that is relevant to the issue addressed here. mdev is
just what udev was 2-3 years ago, nothing more.
thanks,
greg k-h
next prev parent reply other threads:[~2008-07-17 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 14:24 Need help to get udev/hotplug working for extra module in early 2.6 Martin Burnicki
2008-07-15 10:21 ` Need help to get udev/hotplug working for extra module in early Martin Burnicki
2008-07-17 7:13 ` Need help to get udev/hotplug working for extra module in Greg KH
2008-07-17 8:38 ` Greg KH [this message]
2008-07-17 13:12 ` Need help to get udev/hotplug working for extra module Greg KH
2008-07-17 13:58 ` AW: Need help to get udev/hotplug working for extra module inearly2.6 Martin Burnicki
2008-07-17 14:27 ` Martin Burnicki
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=20080717083852.GC23332@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.