[comp.os.minix] Eeeeeerm, er, DOS's fdisk

cs304pal@rata.vuw.ac.nz (Lloyd Parkes) (10/11/89)

In my previous posting, I may have appeared quite pleased with the way I
got DOS's fdisk 3.3 to handle my miniz partitions. Well, last night I
booted up minix (I have been rearranging all my DOS backups over the last
few days, hence try to find another few megs for DOS on my hard drive), and
I got the message mount: /dev/hd7 invalid file system.

After swearing profusely, I decided perhaps it's the system id byte in the
partition table. Nope, tested that, no go. So I had a look at the contents
of hd7, no magics numbers anywhere, and some suspiciously DOS looking
pieces of text. I think oh dear did I put the DOS partition on hd7 instead
of hd6? But no, it wasn't that, then I noticed that hd6 (created by DOS),
overlapped hd7 (already there, created by??) by one cylinder.

This is not so bad, except that I filled up hd6, this trashed the
super-block, the inode map and the zone map. Obviously, this isn't my root
partition, instead it's the device I mount on /u :-( bad karma.

I have everything on DOS floppies somewhere, but this is obviously a pain
in the backside.

The moral(s) of this story.

	1) Do not use DOS's fdisk.
	2) Do not put DOS on your hard drive.
	3) Use DOS to play Jet & your Infocom games only.
	4) Shoot a microsoft programmer today.

					Lloyd


Quick, send your money to cs304pal@rata.vuw.ac.nz now!

If you think anyone believes what I have just said,
then you must be daft in the head!