From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: tiny udev on ARM
Date: Thu, 16 Jun 2005 19:21:27 +0000 [thread overview]
Message-ID: <200506161221.27485.david-b@pacbell.net> (raw)
In-Reply-To: <BAY19-F57063FD1AFDBA03036EC7B9F30@phx.gbl>
On Tuesday 14 June 2005 8:39 am, Pelle Svensson wrote:
>
> What is the minimum I need for a simple set-up?
I've got a pretty minimal setup getting generated from "buildroot"
lately, completely replacing devfs. Get the latest from SVN then
apply the patch "br2-udev-v2.patch" from the entry in bugthing.
> I have following now, but it is not working... need some help.
> Do I need all this?
>
> /sbin/udev 39388 bytes
> /sbin/udevd 22468 bytes
> /sbin/udevend 5588 bytes
> /sbin/udevstart 39356 bytes
> /usr/bin/udevinfo 27028 bytes
> /usr/bin/udevtest 38820 bytes
That is, pretty much what udev-058 installs.
Probably only "udev" and "udevstart" are really
essential in the current install setup ... but
I didn't want to play too many games just now.
> /udev emphty
... I made buildroot completely replace /dev, using ramfs and
populating it with "udevstart".
> /etc/udev/udev.conf 321 bytes rw-r--r--
> /etc/udev/rules.d/50-udev.rules 1531 bytes rw-r--r--
That looks like the default rules. I made buildroot use the
rules from "frugalware" since the defaults use nasty permissions,
like "/dev/zero" and "/dev/null" not being world-readable (so
that many programs can't start or run).
> /etc/rc.d/rc.start_udev 627 bytes rwxr-xr-x (copied from extras)
> call rc.start during inittab
I trimmed down the "start_udev" a bit, but yes it wanted to
be started from inittab (before "mount -a").
One thing that's also missing is a really trimmed-down hotplug.
Yes, some of that can come from making "udev" itself replace
the /sbin/hotplug, but that won't modprobe. Plus, the new
"pcmcia-utils" (cardmgr vanishing at last, yay!) currently
wants some hotplug support.
- 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
prev parent reply other threads:[~2005-06-16 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 15:39 tiny udev on ARM Pelle Svensson
2005-06-14 17:59 ` Kay Sievers
2005-06-15 9:22 ` Pelle Svensson
2005-06-16 19:21 ` David Brownell [this message]
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=200506161221.27485.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 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.