From: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Persistent USB to rs232 serial converter device name patch
Date: Thu, 03 Jul 2008 11:15:04 +0000 [thread overview]
Message-ID: <486CB4B8.7030009@kadzban.is-a-geek.net> (raw)
In-Reply-To: <1215069705l.1824l.1l@mofo>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Karl O. Pinc wrote:
> The patches generate udev rules, in extras/rule_generator/, like the
> process that generates persistent nic names, only for ttyUSB devices.
Why not make it act like persistent-storage and persistent-input, and
add symlinks? The persistent-net stuff can't do that because there is
no such thing as a symlink to a net_device (and even if there was, the
IFNAMSIZ constant in the kernel is too small to handle the longer names
this would generate, and IFNAMSIZ is part of the userspace ABI). The
persistent-cd stuff can't do that because its symlinks are named e.g.
"cdrom1", and don't have the serial # or path in them, and it needs to
have "cdrom1" always be the same device.
But persistent-storage creates a /dev/disk/by-id/ link that's named with
the disk's SCSI or ATA (or whatever) identifying information, along with
several other /dev/disk/by-*/ links using other info. I don't see any
reason you couldn't do the same with e.g. /dev/ttyUSB/by-path/ and
/dev/ttyUSB/by-id/ links. Of course ttyUSB could change; that's just
the first name that came to mind.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIbLS4S5vET1Wea5wRAxdcAJ9utojzdBFUjYi4p7OsiKq1qyY4NwCg1FvS
pD+srRu2KkfYhmeqk8Ka+j4=l1PR
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-07-03 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 7:21 Persistent USB to rs232 serial converter device name patch Karl O. Pinc
2008-07-03 11:15 ` Bryan Kadzban [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=486CB4B8.7030009@kadzban.is-a-geek.net \
--to=bryan@kadzban.is-a-geek.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.