Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosstorage] || [Date Prev] [12-2002 Date Index] [Date Next] || [Thread Prev] [12-2002 Thread Index] [Thread Next]

[openbeosstorage] Re: First C Device API Draft

  • From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
  • To: openbeosstorage@xxxxxxxxxxxxx
  • Date: Fri, 20 Dec 2002 00:57:49 -0800

On 2002-12-17 at 09:53:38 [-0800], openbeosstorage@xxxxxxxxxxxxx wrote:
> 
> On Tue, 17 Dec 2002, Axel =?iso-8859-1?q?D=F6rfler ?= wrote:
> 
> > Tyler Dauwalder <tyler@xxxxxxxxxxxxx> wrote:
> > > > partscan (for partition scanner, better suggestions are welcome 
> > > > :-)
> > > How about diskscan (more general, considering sessions)=3F Or
> > > storage=5Fdevice=5Fscanner (descriptive, though long)=3F
> >
> > What about just disk=5Fscanner=3F Anyway, I like diskscan and
> > storage=5Fdevice=5Fscanner both more than partscan :-)
> 
> Damn, naming is always the hardest part -- coding is so much easier. 
> ;-)
> If nobody minds, I will decide for one of the names before I check the
> stuff in (solved my ssh problem). This won't probably be before Friday
> night, though. If anyone feels like checking it in earlier, just go 
> ahead.

I think I'll just leave the blame for the name to you this time. :)

> > I haven't got any time right now, but I'll try to do some useful
> > replies tomorrow!
> 
> At least for me it's not that urgent. Tomorrow I will take a day off 
> for a
> trip to the mountains and on Thursday I'll fly back to Germany, 
> arriving
> at home Friday night.
> 
> Tyler, if you have time and can't wait to do something ;-), I think, 
> it wouldn't be a bad idea to write a BFS and a CD session module, so 
> that we have at least one module of each kind for testing. In case we
> change the module API, they won't be too hard to adjust.

I have a skeleton BFS module working now, and will probably be able to 
finish it tomorrow. 

-Tyler





[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.