FreeLists / openbeosstorage / [openbeosstorage] Re: API Extensions

["Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>]

"Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
> > > typedef bool (*partition=3D5Fidentify=3D5Fmodule=3D5Fhook)(const char *
> > > identifier, 
> > > uint32 version);
> > > typedef status=3D5Ft (*partition=3D5Fpartition=3D5Fhook)(int deviceFD, 
> > > const 
> > > struct 
> > > session=3D5Finfo *session, void *parameters, size=3D5Ft paramLen);
> > The information should be queryable through an ioctl - so you can 
> > ask 
> > the device which partition system it is using.
> I guess, one would make devfs intercept this ioctl and ask the 
> disk=5Fscanner and friends=3F

Or the disk scanner just adds that information when it creates the 
partitions in the kernel.

> > 2) Is there support for hidden partitions=3D3F
> > We might also have special driver settings for the partition 
> > modules, 
> > although I am not yet sure where we can use it (to hide intel 
> > partitions for example).
> The extended=5Fpartition=5Finfo structure has a fields `flags' which can 
> have the bit B=5FHIDDEN=5FPARTITION set (it was a `bool hidden' in the DS 
> add-on partition=5Fdata structure, IIRC). The partition add-ons are 
> supposed to set that bit, if the partition is a non-data partition 
> (e.g. an extended one). But I suspect, I are driving at something 
> else, 
> aren't you=3F

I think I referred to the partitions containing meta data about volume 
spanning, partition resize/move operations, etc. - those probably 
shouldn't be too visible to the user (at least Tracker shouldn't make 
them visible in the mount menu).

Adios...
   Axel.