[Coco] RBF and LSN0

Mike Pepe lamune at doki-doki.net
Tue Sep 23 11:31:19 EDT 2008


Chuck Youse wrote:
> So I've written two RBF drivers in recent weeks, and a thought has a
> occurred to me, and I'm wondering if anyone can shed light on this.  If
> Boisy is lurking he's probably the guy with the answer.
> 
> So RBF drivers are required to update their drive tables with the LSN0
> "superblock" information every time that LSN0 is read; this is so that
> RBF can consult the drive table to find out useful filesystem
> information, like the size in sectors, etc.  So every RBF driver is
> required to take a special action on reading LSN 0, and perform
> essentially the same task.
> 
> It seems like a lot of duplication of code.  RBF knows when it's reading
> LSN0, and it knows where the drive tables are kept in the driver's
> static data area; so why is this functionality pushed off to the driver?
> It seems RBF has all the information required to do this itself.. it's
> RBF-specific information, anyway -- if you're using a different file
> manager, this action is probably superfluous.
> 
> So anyone know why this was designed this way?
> 
> C.
> 
> 
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 

Chuck, is it possible that it re-reads LSN0 to make sure that you didn't 
swap floppies from underneath it?

That's the only reason I can think of offhand.



More information about the Coco mailing list