Re: Minix crash

[q-funk@citenet.net (Martin-Eric Racine)]

 >On Tue, 26 Aug 1997, Martin-Eric Racine wrote:
 >
 >>  >There's no FAT problem on your minix partition, simply because minix 
 >>  >has no FATs. For repairing you can use fsck.ttp under MiNT (I guess the 
 >>  >usage is 'fsck.ttp X:' where X is the GEMDOS name of minix partition).
 >>  >
 >>  >But with KGMD it's easier to reinstall everything from scratch, I think.
 >> 
 >> Precisely why I never will install Minix.  If/when a problem
 >> happens, you're dead meat; you data is lost for good. Not so
 >> under FAT, because there is a plethora of recovery utilities
 >> for standard TOS (ie: DOS) partitions.
 >
 >Not entirely correct. You have fsck to fix up the filesystem, and
 >mfsdefrag to defrag it. I have found that fsck usually fixes all
 >problems without loosing data, although it *can* make a total mess of
 >the filesystem as well! It must be run frequently to avoid serious
 >errors to occur, if you do this (KGMD does it at every boot) you're
 >pretty safe.

I'm not a Linux freak (I HATE commandlines),
so I never installed KGMD. 

I only need MultiTOS, MiNTnet and GlueSTiK.

MultiTOS will soon be replaced by N.AES and Thing.

One question:

How big of a partition can one format under TOS 3.06?
I will soon change my old Seagate ST157N for a larger
hard-disk and want as few partitions as possible. 


-----------------------------------------------------------------
From: Martin-Eric Racine FUNKYWARE http://www.megacom.net/~q-funk
Atari TT030 4/24/50 NVDI 4.11, MiNT 1.14, GlueSTiK 0.2b4, AES 4.1
-----------------------------------------------------------------
    "By the year 2000 we will, I hope, raise our children to
     believe in human potential, not God." -- Gloria Steinem
-----------------------------------------------------------------