[leave disk dirty if it was opened for writing]
>> But the main question I have about this is: how does fsck get
>> exempted from this?  It opens the device for writing, after all.
> securelevel < 0 when fsck runs in /etc/rc.

(I think it's ==0, but the difference doesn't matter for the moment.)

So I take it then that your proposal is that opens for writing when
securelevel<1 don't count?

So after the machine comes up multi-user, I log in as root, fsck a
filesystem, mount it, then when I unmount it it stays dirty?

And how does this interact with removable media (and vnds, which amount
to the same thing, where the "media change" is reconfiguration of the
vnd)?

					der Mouse

			    mouse@collatz.mcrcim.mcgill.edu