[openbeosstorage] Re: [Open-beos-cvs]CVS:current/src/tests/add-ons/kernel/disk_scanner DiskScannerTest.cpp,1.7,1.8

On Mon, 20 Jan 2003, Axel =?iso-8859-1?q?D=F6rfler ?= wrote:

> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > > Added a comment about from where to start that application.
> > > If get=5Fnth=5Fpartition/session=5Finfo() returns with anything else than
> > > a
> > > B=5FENTRY=5FNOT=5FFOUND, an error message is printed out.
> > > The device name can now be specified on the command line, added
> > > shortcuts
> > > to identify a particular device, i.e. "cd-1-slave" or "slave1-cd"
> > > or
> > > "1-atapi-slave" would be expanded to /dev/disk/ide/atapi/1/slave/0/
> > > raw.
> > Thanks, I also thought of doing something like, but, er, well, was
> > too
> > lazy. ;-)
>
> No problem - I just wanted to check out how it works ;-)
> BTW I really think the session module shouldn't return B=5FBAD=5FFILE if
> everything worked okay.

Yep, the other modules return B_ENTRY_NOT_FOUND when the supplied index is
out of range, which is probably more appropriate (though the strerror()
translation doesn't fit that well).

CU, Ingo

PS: Can anyone tell me, why I put the whole disk_scanner FS module
API into headers/private? We don't want to officially disallow creation of
third party session/partition(/FS) modules, do we?
BTW, that raises the question of versioning.

Other related posts: