From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev vs. devfs
Date: Thu, 16 Jun 2005 19:29:01 +0000 [thread overview]
Message-ID: <200506161229.02188.david-b@pacbell.net> (raw)
In-Reply-To: <BAY19-F8BE196D4CCF42A9E246A6B9F50@phx.gbl>
On Thursday 16 June 2005 8:07 am, Pelle Svensson wrote:
> Can't somebody tell me what I need to get udev up and running from scratch.
>
> I'm building a ARM system with 2.6 kernel from scratch so I only need the
> most basic stuff to get a 'dev' list.
The latest buildroot, plus the br2-udev-v2.patch from
http://bugs.uclibc.org/view.php?id)0
Works fine for me on a couple ARM systems, modulo hotplug not behaving
for anything yet (much less CF cards, but that's coming soon). I've
told it to use gcc 3.4.3 FWIW; also module-init-tools instead of the
stuff built-in to busybox, since I want modprobe $MODALIAS and such.
- Dave
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&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:[~2005-06-16 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 15:07 udev vs. devfs Pelle Svensson
2005-06-16 17:10 ` Vassilis Virvilis
2005-06-16 18:37 ` Greg KH
2005-06-16 19:29 ` David Brownell [this message]
2005-06-17 12:42 ` Pelle Svensson
2005-06-17 12:58 ` Kay Sievers
2005-06-17 13:15 ` Pelle Svensson
2005-06-17 16:05 ` Greg KH
2005-06-17 19:21 ` David Brownell
2005-06-17 19:26 ` David Brownell
2005-06-20 12:52 ` Pelle Svensson
2005-06-23 16:59 ` Vassilis Virvilis
2005-06-28 11:24 ` Vassilis Virvilis
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=200506161229.02188.david-b@pacbell.net \
--to=david-b@pacbell.net \
--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).