From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to create the nodes dynamically - simple char driver
Date: Thu, 02 Feb 2006 16:17:18 +0000 [thread overview]
Message-ID: <20060202161718.GA2121@vrfy.org> (raw)
In-Reply-To: <3AEC1E10243A314391FE9C01CD65429B28C755@mail.esn.co.in>
On Thu, Feb 02, 2006 at 09:59:35AM -0600, Linas Vepstas wrote:
> On Thu, Feb 02, 2006 at 03:43:25PM +0530, Srinivas G. was heard to remark:
> > My question is:
> > Is there any way to create the nodes automatically after restarting the
> > system if the module exists?
>
> udev is erasing the files.
/dev is on tmpfs, that does not survice a reboot.
> On boot, it will copy any static device
> nodes from /etc/udev (or somewhere like that) to /dev.
It is /lib/udev/devices/.
> The "correct" thing to do would have been to write the appropriate udev
> rule, but since this sounds like a prototype board, a hack like
> /etc/udev might be approrate.
Huh no, both is definitely not "correct". Just use the kernel driver core
functions and register your class device with the right name and udev will
create the node automatically when the device shows up.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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:[~2006-02-02 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 10:25 How to create the nodes dynamically - simple char driver Srinivas G.
2006-02-02 15:59 ` Linas Vepstas
2006-02-02 16:17 ` Kay Sievers [this message]
2006-02-02 16:50 ` Greg KH
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=20060202161718.GA2121@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 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).