From: "carina bengs" <carinabengs@home.se>
To: linux-hotplug@vger.kernel.org
Subject: Fw: ircomm
Date: Mon, 28 Mar 2005 19:50:19 +0000 [thread overview]
Message-ID: <000c01c533cf$649f3750$52794e3e@helloe5c845c4c> (raw)
----- 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
>> a.. nothing left in /dev/ir*
>> a.. that is wrong?
>> a.. I have mandrake 10.1
>>
>> /etc/sysconfig/irda
>> IRDA=yes
>> DEVICE=/dev/ttyS0
>> DONGLE=tekram
>> DISCOVERY=yes
>>
>> carinabengs@home.se
>
> If you are using udev -> complain to the udev mailing list.
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
> If you are using devfs, make sure ircomm module is loaded.
> If none of the above apply, then I would be surprised.
>
> Jean
it seems to be udev-030-24.installd by defauts.
>
>
-------------------------------------------------------
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
next reply other threads:[~2005-03-28 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 19:50 carina bengs [this message]
2005-03-28 19:54 ` Fw: ircomm carina bengs
2005-03-28 20:23 ` Kay Sievers
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='000c01c533cf$649f3750$52794e3e@helloe5c845c4c' \
--to=carinabengs@home.se \
--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