87651 30-MAY 20:42 System Modules (6809)
From: WDTV5 To: ALL
I’m in the middle of doing a fresh ramdisk for the os-9′ers, based VERY
loosely on the devpack version but capable of useing ram up to the amount
in the machine even if its a 2 megger!
I started on this because the compiler chokes if /r0 isn’t iniz’ed first,
thinking that was a bug. Well it is and it isn’t. OS-9 is doing that to
us as it does its own “iniz” on the module if it hasn’t been already,
then allows the write of a file to the ramdisk without reporting any
errors. Unforch, if it self initialized it, it also de-inits it at the
end of the write! So the file is lost, and c.pass1 (ansifront) can’t
find the output from c.prep. I want to stop that, effectivly making the
ramdisk refuse to deinit if the directory isn’t empty. I’m torn between
using the regular error paths to report it, or just outputting the
phrase “the root dir isn’t empty” on stderr. If I use an error number,
then the compiler and other progs will probably choke on it anyway when
in fact they could keep on truckin! So I need some input, what do tou
all (you) want it to do. The choices are to ignore it without errors, and
let you folks learn to delete all files before deiniting, haveing an
error mesage pop up at odd times, or returning a process killing error.
What’ll it be folks?
Cheers all, Gene