DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=mKaOtdK7iCTeWNe8oob5wW3qrTEs+f86Z/muwwbSOPeboajDVIIPHRKoCzY2bXCdHQ
         kDZbH45UbnlXOOj5sngpYJgByz/B1hPe1MaICxV19H3kkwhAEf3vC+l3v600zPHqDOcT
         +CYveO7jUBlTSO784qstSV7LpvVva4jPhtfIc=
MIME-Version: 1.0
Date: Thu, 16 Apr 2009 16:39:45 -0400
Message-ID: <cf4f48500904161339n627e2127k7e9b4abeb0621c28@mail.gmail.com>
Subject: Basic rundown of udev?
From: John Moser <john.r.moser@gmail.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 757
Lines: 15

I'm currently reading through umm... udevd.c for udev-141.  Trying to
figure out how this thing works.

Anyone care to give me a brief map?  It would help.  I'm just trying
to figure out how udev talks to the kernel-- i.e. what facilities
would I have to implement to re-implement the kernel side of udev,
let's say if I was to run udevd as-is on Darwin or NetBSD or
something.  How does it talk to the kernel?  And if you know off the
top of your head, which source files (and functions?) am I looking at
here?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/