From: Marcos Dione <mdione@except.com.ar>
To: linux-hotplug@vger.kernel.org
Subject: udevd is not receiving events
Date: Tue, 08 May 2007 21:10:17 +0000 [thread overview]
Message-ID: <20070508211017.GA6681@except.com.ar> (raw)
hi all. I'm setting up a thin client that load its root fs from nfs.
for that puporse, I compiled my own kernel that does not have any module
(all compiled in-kernel) with my nic, nfs and nfsroot. that part works
fine.
but then udevd stalls. I'm basing the nfsroot from a ubuntu dapper
system, which has udev 079. as anyone knows, udev doesn't create the
system devices, so they must be replayed. under ubuntu that's done by
udevplug, which echoes "add" into all the uevent files found under
/sys. this should, but it does not, force udevd to create the proper
devices. thing is, udev is not receiving them.
I ran all the /etc/init.d/rcS script under strace just to detect
that udevd sits waiting in a select (udevd.c:996), waiting froma a pipe,
a unix socket and a netlink socket. none moves. I don't know exactly how
those events are supposed to appear from that end, but I can infer
they're not doing it.
my kernel has sysfs, unix sockets, support for hotplug devices (even
if I know that's not needed), tmpfs, networking (remember this is
nfsroot!), but mostly it's a stripepd down kernel with only what I need.
so, what could be happening here? I almos lost all my hair here
trying to figure it out. first I thought it was inotify, which I didn't
include at fisrt; it wasn't. then I tried to add this and that, but the
kernel cannot grow to big because I'm booting from a diskette.
one thing I can tell is that yes, I hate initrd images, so I'm
working without them, so I'm not doing all the things ubuntu does in
their initrd images. anyways, with udevplug -v I can see that al lthe
righjt devices events are replayed, or tried to, but udevd still sits in
the said select() call.
I don't know what else to include. I will appreciate any hint you
could give to me. TIA
Marcos.
--
Marcos Dione
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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
reply other threads:[~2007-05-08 21:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070508211017.GA6681@except.com.ar \
--to=mdione@except.com.ar \
--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).