[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Re: [LUG] udev rules for persistent serial device naming
- To: list@xxxxxxxxxxxxx
- Subject: Re: [LUG] udev rules for persistent serial device naming
- From: Robin Cornelius <robin.cornelius@xxxxxxxxx>
- Date: Thu, 22 Mar 2018 10:12:49 +0000
- Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dclug.org.uk; s=1507453562; h=Sender:Content-Transfer-Encoding:Content-Type:Reply-To:List-Subscribe:List-Help:List-Post:List-Unsubscribe:List-Id:Subject:To:Message-ID:Date:From:References:In-Reply-To:MIME-Version; bh=j9uQiESp9izeRmZpHOeuoKjBGY/uAU+Yhvk4vNY5xlA=; b=KgYs98EkWbIUkAxQOZ2YCZg/4DBIC1oqgakaBhoZWA9zhf68uMygmw9+rXh9riviuJ5/jVSLFmwZnAvxjTVc/GLSq8CWiXejuh+7AtNwrfZVAT2P1+/a3oAPYtovwSWVJDgt84Lzl8KY4cLa6su3V7NLA0V1zs0V0f3RUrKZBAo=;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=mWI14Ckv+0viyAOPF6A+0Oo4bWmvZl1SclF23ECQkxs=; b=Jwdeki3V5V7/LDGaEcSh6KgCScXcrO6NyyQ5X2unGb7I7n3F6LDFgTbuZl/WHV6QIF 1ZijRgQuazjo3iUferaggPieRFKpnE06oIIC6xwMiZE3rbwW/7IlbmcN7ByIUoTELMjA T5hHgD943ry/bQMjXt5yCjG5ST5KPdzc/tA81e+YveMpkwZK383l8uqlqraIpf434KJU rdiFxh3T3IdCmD+uaoLRip0sVUu6+LLkAUAf6fygAZ/EyDlbrBJ7vwu6izLbaHdyI79M kTL3MJtgdUKyi53XoekUcU7tyiRBg+wMxiFky0JgZ8BM5ZeZIygie8m66Rg+Qnik6mx9 0JQA==
> Specifically I believe you need to use the "NAME=" syntax to control
> where in the /dev/ tree you want your new device to appear as well as
> the "SYMLINK=" argument. I think you're running into issues where some
> of your arguments will unnecessarily match both instances which is "not
> kosher" for some reason: try matching just SUBSYSTEM=="tty" and the
> serials, you're not gaining anything by matching the idVendor and idProduct.
I'll give that a try thanks
>
> udev rules are one of those things that never really worked quite as
> well as everyone hoped they would...
Its a shame, as its quite useful and solves a number of my use cases
(when it works) such as this problem and setting correct
permissions/groups for our own custom devices.
Thanks
Robin
--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
