> Charles Shattuck wrote: > > I did some experiments with BLOCK, UPDATE, and FLUSH. I notice that if > > I update and flush say block 1, having started in a directory with no > > BLOCKS.FB file, the directory isn't updated until blocks.fb is closed, > > either explicitly or by saying BYE to gforth. My question is based on > > not knowing much about operating systems (Linux in this case). When > > does the updated an flushed block actually go onto the disk? If Linux > > were to crash before blocks.fb were closed, would I find my data on > > the disk later after rebooting? > > Not necessarily. There are several levels of buffering involved here: <snip> > I had that problem with F83s a few years ago. We decided to write a Save-Buffers Forth word that closed the file and reopened it instantly to be sure everything was written to disk. Since this command was part of the editing, save, compile cycle, speed did not matter and was unnoticeable any way and we wanted our program data to be safely saved.
John Peters --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
