> On Thursday 03 October 2002 09:51, Alexander Viro wrote:
> > On Thu, 3 Oct 2002, Kevin Corry wrote:
> > > > IOW, the real question is what are you going to do with that list of
> > > > gendisks?
> > >
> > > EVMS will try to read volume metadata from each device and activate
> > > volumes if it finds any pertinent metadata.
> >
> > _Ouch_. "Each" as in...? E.g. do you want to do that for floppies?
> > Cdroms? EVMS volumes themselves? Things like /dev/loop? (and if yes, at
> > which point do you do that?)
>
> EVMS can filter out devices that don't make sense to probe for volumes.
> Currently it ignores such things as floppies and cd-roms, as well as EVMS
> volumes. We have actually added the ability to probe loop devices, though,
> since we had several requests for that functionality.
How does it recognize cdroms? Explicit list of majors? Doesn't work for
IDE and I'm fairly sure that it doesn't catch all exotic ones. Basically,
I don't believe that any methods based on keeping a registry of bad device
numbers are viable - if that information belongs anywhere, it's in drivers.
IMO the right way is to have driver set properties of gendisk and stuff
like partition-related devfs/driverfs code, RAID, evms, etc. to check
that. _If_ we handle that stuff in the kernel, that is.
The question being, what property are you looking for? "I'm suitable for
EVMS" is not an answer, obviously...
As for the loop... At which point do you want to notice it? Notice that
it can be opened earlier than anything could be read from it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/