> 
> Why do you need to use the actual FFS code?  If this is for a boot
> program, use the FFS reading package in libsa.

	I also want UFS, and ext2fs, and maybe LFS in the future.
Having the booter do a mountroot() in exactly the same way as the
kernel does it will be best, since device names will match, et c.


> You could certainly also add simple write support to the libsa FFS
> package.  I mean, it's not like you have to interact with the buffer
> cache, deal with the vnode layer, etc. in a boot block :-)

	Looking at the (lack of) speed of the current Installer, the
buffer cache is _exactly_ what we need!

-- 
| Nigel Pearson, nigel@ind.tansu.com.au | "reality  is  that  which  |
|  Telstra IN&IND, Sydney, Australia.   |  doesn't go away when you  |
| Office: 9206 3468    Fax:  9212 6329  |  stop  believing  in  it." |
| Mobile: 0408 664435  Home: 9579 3293  |       Philip K. Dick       |