[openbeosstorage] Re: The New Device API (tm)
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Thu, 30 Jan 2003 10:50:09 +0100 CET
Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> On Tue, 28 Jan 2003, Tyler Dauwalder wrote:
> > > The most simple way is to always publish all (non-empty, non-
> > > hidden)
> > > partitions, but that's probably not what you are looking for=3F
> > Is there a good reason *not* to always publish all of them=3F
> None I know of.
Well, it takes time - it requires the kernel to initially scan all
attached devices for partition data. And of course, that information
might never be needed at all.
But AFAICT that (and the little amount of memory to keep that
information) is the only drawback.
Adios...
Axel.
- References:
- [openbeosstorage] Re: The New Device API (tm)
- From: Ingo Weinhold
Other related posts:
- » [openbeosstorage] The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- » [openbeosstorage] Re: The New Device API (tm)
- [openbeosstorage] Re: The New Device API (tm)
- From: Ingo Weinhold