From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Fw: ircomm
Date: Mon, 28 Mar 2005 20:23:34 +0000 [thread overview]
Message-ID: <1112041414.5336.70.camel@localhost.localdomain> (raw)
In-Reply-To: <000c01c533cf$649f3750$52794e3e@helloe5c845c4c>
On Mon, 2005-03-28 at 22:50 +0300, carina bengs wrote:
> ----- Original Message -----
> From: "Jean Tourrilhes" <jt@hpl.hp.com>
> To: "carina bengs" <carinabengs@home.se>
> Sent: Monday, March 28, 2005 8:20 PM
> Subject: Re: ircomm
>
>
> > On Mon, Mar 28, 2005 at 12:11:34PM +0300, carina bengs wrote:
> >>
> >> a.. Create the IrDA devices :
> >> > mknod /dev/ircomm0 c 161 0
> >> > mknod /dev/ircomm1 c 161 1
> >> > mknod /dev/irlpt0 c 161 16
> >> > mknod /dev/irlpt1 c 161 17
> >> > mknod /dev/irnet c 10 187
> >> > chmod 666 /dev/ir*
> >> And all work finea.. but when Ia.. Reboot
> >> a.. All /dev/ir* is gone
Your /dev may be on a tmpfs if udev is used to manage your /dev
directory and therefore manually created nodes will not survive a
reboot.
Don't know if ircomm integrates with the kernel driver model and you get
hotplug events for these device. You may ask Jean back about this. :)
If there are no hotplug events for these devices, udev can't do anything
and you need to run a makedev script with every reboot.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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-03-28 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:50 Fw: ircomm carina bengs
2005-03-28 19:54 ` carina bengs
2005-03-28 20:23 ` Kay Sievers [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=1112041414.5336.70.camel@localhost.localdomain \
--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).