--Perry
> > Haha, the toothbrush strikes again (thought of this solution while
> > brushing my teeth). The solution is that we want the physical
> > layout of the device directories to mirror the disk, ideally.
> > However, since Solaris and BSD put their partition data in physical
> > partitions, the solution is to register the partition scheme as a
> > child of another partition scheme. EG:
> >
> > You have 6 modules for 6 partition schemes:
> >
> > hfs
> > iso
> > dsp
> > p
> > s
> > bsd
> >
> > The hfs, iso, dsp, and p all register themselves as child of
> > 'DEVICE'. Solaris and BSD do:
> >
> > parent=get_management_scheme("partition");
> >
> > register_management_scheme(child_of=partition, name=solaris);
> >
> > And the kernel would automatically create the appropriate
> > subdirectory for managing those devices. It uses the same exact
> > subdir scheme recursively to represent devices. The reason that I
> > even wanted a hiearchy like this, is so I could mount a CD with
> > hfs, iso, music, Solaris, multisession, photoCD, xa, etc tracks on
> > it. This method allows that the music tracks, etc would be labeled
> > consistently from one disk to the other; this 'protocol' ensures
> > consistency among devices and partitioning schemes.
>
> Hm. Interesting proposal. It's adding a significant conceptual
> layer. This is not really a devfs issue, it's a more general issue for
> handling partitions/labels/sessions. Why not throw it at the kernel
> list and stand back?
>
> Regards,
>
> Richard....
>
-- Perry Harrington Linux rules all OSes. APSoft () email: perry@apsoft.com Think Blue. /\