From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: tiny udev on ARM
Date: Tue, 14 Jun 2005 17:59:18 +0000 [thread overview]
Message-ID: <20050614175918.GA31113@vrfy.org> (raw)
In-Reply-To: <BAY19-F57063FD1AFDBA03036EC7B9F30@phx.gbl>
On Tue, Jun 14, 2005 at 05:39:14PM +0200, Pelle Svensson wrote:
>
> Hi
>
> What is the minimum I need for a simple set-up?
>
> 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
> /udev emphty
> /etc/udev/udev.conf 321 bytes rw-r--r--
> /etc/udev/rules.d/50-udev.rules 1531 bytes rw-r--r--
> /etc/rc.d/rc.start_udev 627 bytes rwxr-xr-x (copied from extras)
> call rc.start during inittab
Well nobody can tell you. It completely depends on what you want to do.
You can do anything from just using /sbin/udev invoked from the kernel-forked
hotplug-helper or in contrast serialize everything through the udevsend/udevd
daemon to get "managed" events or disable kernel-event forking completely
and use netlink instead.
Or do hotplug event replay from initramfs instead of using udevstart, and so
on...
Kay
-------------------------------------------------------
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-14 17:59 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 [this message]
2005-06-15 9:22 ` Pelle Svensson
2005-06-16 19:21 ` David Brownell
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=20050614175918.GA31113@vrfy.org \
--to=kay.sievers@vrfy.org \
--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.