Michael Phipps <mphipps1@xxxxxxxxxxxxxxxx> wrote: > > Depends. Of course, we want to have an automated build, but it's > > probably not > > possible to build an image file containing an OpenBeOS installation > > that you > > could use right away with Bochs - the BeOS cache doesn't allow this > > to work > > reliably, unfortunately. > > > > However, it will be possible to install OpenBeOS on a mounted > > volume using > > Jam. That one you can use directly to boot from, but again, you > > won't be able > > to use it in Bochs until a reboot due to the BeOS cache. There is > > not much we > > can do about it. > So /bin/sync doesn't fully flush the cache? The problem stems from the fact, that if you mount a file system on an image, the file system will disable the cache for the file system underneath. That alone wouldn't be a problem, but the BeOS cache doesn't have a function to invalidate blocks (or remove blocks from the cache), and it doesn't do so when the cache is turned off. When you unmount the image again, the cache is turned on again, but Bochs will see the blocks that were in the cache before, rather than those written in between. Bye, Axel.