From: raid517 <raid517@ukonline.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: UDEV and new hardware?
Date: Thu, 20 Oct 2005 17:50:19 +0000 [thread overview]
Message-ID: <4357E6A2.1010508@ukonline.co.uk> (raw)
In-Reply-To: <4356BC73.9000506@ukonline.co.uk>
Thanks I will certainly give that a go - although in the end I just
wrote a small bash script and had it create the symlink and then added
this to my system startup scripts. This should hopefully survive and
upgrades to Udev in the future too. (Although having the capacity to
create persiant 'on the fly' symlinks in /dev (just as I used to be able
to do) would still be neat too.
GJ
Kay Sievers wrote:
>On Wed, Oct 19, 2005 at 09:36:51PM +0000, raid517 wrote:
>
>
>>Hi I installed a modem driver for the Intel Corporation 536EP Data Fax
>>Modem. But in order to use it I need to create a link from it (it is
>>called 536ep0 in /dev) to /dev/modem. I need to do this specifically so
>>that KPPP can see it.
>>
>>The only thing is that everything in /dev/ gets deleted and rebuilt each
>>time I reboot.
>>
>>I have been led to believe (rightly or wrongly) that it is udev that is
>>responsible for this. So the question is how can I make a symlink from
>>/dev/536ep0 to /dev/modem that will remain in place and will persist
>>even after a reboot?
>>
>>
>
>Try adding:
> KERNEL="536ep0", SYMLINK+="modem"
>
>to a rules file in:
> /etc/udev/rules.d/
>
>Kay
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by:
>Power Architecture Resource Center: Free content, downloads, discussions,
>and more. http://solutions.newsforge.com/ibmarch.tmpl
>_______________________________________________
>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
>
>
>
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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-10-20 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 21:36 UDEV and new hardware? raid517
2005-10-20 17:35 ` Kay Sievers
2005-10-20 17:50 ` raid517 [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=4357E6A2.1010508@ukonline.co.uk \
--to=raid517@ukonline.co.uk \
--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).