From: Jeff Garzik <jgarzik@pobox.com>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.7 block ramblings (was Re: DMA for ide-scsi?)
Date: Sun, 14 Sep 2003 13:30:20 -0400 [thread overview]
Message-ID: <3F64A5AC.8020901@pobox.com> (raw)
In-Reply-To: <20030914181201.E3371@pclin040.win.tue.nl>
Andries Brouwer wrote:
> Such things are infinitely difficult.
> Moreover, great care is needed - one has to define precisely what it
> is this GUID is supposed to be an ID of.
Absolutely agreed.
> (Is it the ZIP drive? Or is it the ZIP disk?
> The 2.4 USB code is broken because it remembers a GUID and thinks that
> identical GUID implies identical disk.)
>
> I have a handful of CF/SM cardreaders.
> Some of them have no form of ID. Others have an ID.
>
> Then one can insert a CF or SM card into the reader.
> Some of these cards have an ID. Some have not.
>
> On the card one usually finds a FAT filesystem.
> There may be a label. Or there may not be.
>
> This describes a 3-level situation.
> I have also 4-level situations, where the reader is filled with
> one of four auxiliary adapters (each with an own ID) and the
> adapter then get a CF/SM/SD/... card.
Using an adapter's ID would be a mistake. You want to use the media's
unique ID, assuming it has one.
> So, yes, we love IDs. And we can always provide them ourselves
> as label or UUID or so in the filesystem.
Not all filesystems have them :)
Further, some sites may prefer block-level GUIDs to fs-level ones.
Sites using raw partitions instead of filesystems, for one.
We must leave this up to the sysadmin -- within the bounds of technology
of course. The sysadmin is out of luck if they purchase a media that
does not support some sort of labelling or UUID.
> But finding an unformatted unlabeled disk is difficult.
You sound like you're agreeing with me ;-)
Jeff
next prev parent reply other threads:[~2003-09-14 17:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 20:16 2.7 block ramblings (was Re: DMA for ide-scsi?) James Bottomley
2003-09-13 21:27 ` Jeff Garzik
2003-09-14 11:15 ` Justin Cormack
2003-09-14 15:02 ` Alan Cox
2003-09-14 16:55 ` Kevin P. Fleming
2003-09-14 17:01 ` Andries Brouwer
2003-09-14 17:24 ` Jeff Garzik
2003-09-14 18:55 ` Alan Cox
2003-09-16 2:38 ` Thomas Molina
2003-09-16 13:56 ` Alan Cox
2003-09-14 17:20 ` Jeff Garzik
2003-09-14 16:12 ` Andries Brouwer
2003-09-14 17:30 ` Jeff Garzik [this message]
2003-09-13 2:11 ` Matt Domsch
2003-09-14 22:26 ` Alan Cox
2003-09-13 6:05 ` Matt Domsch
2003-09-15 22:16 ` Matt Domsch
2003-09-15 3:23 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 11:01 DMA for ide-scsi? Mikael Pettersson
2003-09-13 18:04 ` Alan Cox
2003-09-13 18:49 ` 2.7 block ramblings (was Re: DMA for ide-scsi?) Jeff Garzik
2003-09-13 19:01 ` Jeff Garzik
2003-09-13 19:06 ` Jeff Garzik
2003-09-15 7:34 ` Jens Axboe
2003-09-16 19:49 ` Jeff Garzik
2003-09-16 19:55 ` Jens Axboe
2003-09-20 18:28 ` Jeff Garzik
2003-09-20 22:16 ` Alan Cox
2003-09-20 22:22 ` Jeff Garzik
2003-09-20 22:46 ` Alan Cox
2003-09-21 9:23 ` Jens Axboe
2003-09-13 19:24 ` Bartlomiej Zolnierkiewicz
2003-09-13 19:57 ` Jeff Garzik
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=3F64A5AC.8020901@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@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