Re: [MiNT] Questions about minixfs and mintne

[Frank Naumann <fnaumann@prinz-atm.CS.Uni-Magdeburg.De>]

Hi!

> I don't know if we really need this many INIT levels, but maybe
> introducing an FSCK level that goes before everything else and
> acts as a single-user would fix those "cannot sync or lock drive"?

The problem is, that the fsck doesn't inform the kernel about changes on 
the disk if the Dlock() method fail.

> Btw, one thing that _is_ fixed since Frank's MinixFS is that doing
> an FSCK on other drives beyond the one where the root is mounted
> doesn't result in "inode not written when drive locked" error that
> we used to have. 

This was a bug in the kernel (fixed since 1.15.0). Dlock() must sync 
before it reserves the partition.

> However, that new MinixFS often gives me errors after a 'grep'
> on a whole directory (ie:  grep "string" *.c) and I dunno why.

What errors?


Tschuess
   ...Frank

--
ATARI FALCON 040
--------------------------------------
Internet: fnaumann@cs.uni-magdeburg.de
Mausnet:  Frank Naumann @ L2