From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, patmans@us.ibm.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
mdharm-kernel@one-eyed-alien.net, zwane@holomorphy.com
Subject: Re: IDs
Date: Tue, 7 Jan 2003 11:55:00 +0100 (MET) [thread overview]
Message-ID: <UTC200301071055.h07At0T09202.aeb@smtp.cwi.nl> (raw)
> But, we don't have to truncate, we should just allocate as many bytes as
> we need, and store the information.
> And, the sysfs name should not store the id.
OK. It seems that we are in total agreement.
Time for the next question.
An id is constructed, that in many cases identifies something.
How do you plan to use this? Is it already in use somewhere?
The sysfs tree does not contain device nodes.
Do you plan a user space utility that figures out that
the ID "SHP CD-Writer+ 8200 [" belongs to /dev/hdd
which also is /dev/sr0?
The id is not suitable as a user space name. Moreover,
it is a heuristic only, and user space needs unambiguous names.
What user space names do you want to use?
Andries
next prev reply other threads:[~2003-01-07 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 2:19 IDs Andries.Brouwer
2003-01-07 3:15 ` IDs Patrick Mansfield
2003-01-07 10:55 ` Andries.Brouwer [this message]
2003-01-07 17:07 ` IDs Greg KH
2003-01-07 18:02 ` IDs Patrick Mansfield
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 18:54 IDs Andries.Brouwer
2003-01-07 20:02 ` IDs Patrick Mansfield
2003-01-07 0:00 IDs Andries.Brouwer
2003-01-07 2:13 ` IDs Patrick Mansfield
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=UTC200301071055.h07At0T09202.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mdharm-kernel@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
--cc=zwane@holomorphy.com \
/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