From mboxrd@z Thu Jan  1 00:00:00 1970
From: Josua Dietze <digidietze@draisberghof.de>
Date: Tue, 10 Aug 2010 06:28:24 +0000
Subject: Re: Environment woes
Message-Id: <4C60F188.2010404@draisberghof.de>
List-Id: <linux-hotplug.vger.kernel.org>
References: <4C608323.5010502@draisberghof.de>
In-Reply-To: <4C608323.5010502@draisberghof.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

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