linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josua Dietze <digidietze@draisberghof.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Environment woes
Date: Tue, 10 Aug 2010 06:28:24 +0000	[thread overview]
Message-ID: <4C60F188.2010404@draisberghof.de> (raw)
In-Reply-To: <4C608323.5010502@draisberghof.de>

Am 10.08.2010 06:37, schrieb Kay Sievers:

> On Tue, Aug 10, 2010 at 00:37, Josua Dietze<digidietze@draisberghof.de>  wrote:
>> Up to now I have used a rule to add a symlink to the "right" port; the check
>> is done by a script via "PROGRAM". If the port is not right, the result of
>> the script is empty, thus no symlink:
>>
>> ACTION="add", KERNEL="ttyUSB*", PROGRAM="<script>  %p", SYMLINK="%c"
>
> Who needs these custom links? Why don't you just use the stuff in
> /dev/serial/ which should already work?


There is a symlink to *every* port in the /dev/serial folders. Again, 
only *one* of them is usable for connecting through 
wvdial/umtsmon/networkmanager. The latter often auto-selects a wrong 
port, BTW.

I add *one* symlink called "gsmmodem[x]" to make life easier for users.

Examples:
Huawei E160	ttyUSB0,1,2	gsmmodem -> ttyUSB0
ZTE MF110	ttyUSB0,1,2	gsmmodem -> ttyUSB2

These interfaces all have a class of 0xff. Some are even accepting AT 
commands, but are only intended for diagnostic purposes, misleading 
users and probers.


Thanks,
Josua Dietze

  parent reply	other threads:[~2010-08-10  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 22:37 Environment woes Josua Dietze
2010-08-10  4:37 ` Kay Sievers
2010-08-10  6:28 ` Josua Dietze [this message]
2010-08-10 19:30 ` Greg KH
2010-08-10 20:02 ` Josua Dietze
2010-08-10 20:14 ` 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=4C60F188.2010404@draisberghof.de \
    --to=digidietze@draisberghof.de \
    --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).