From owner-freebsd-hackers Fri Mar 29 19:16:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA08688 for hackers-outgoing; Fri, 29 Mar 1996 19:16:18 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA08682 for ; Fri, 29 Mar 1996 19:16:14 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id OAA22757; Sat, 30 Mar 1996 14:11:56 +1100 Date: Sat, 30 Mar 1996 14:11:56 +1100 From: Bruce Evans Message-Id: <199603300311.OAA22757@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@lambert.org Subject: Re: fdisk and partition info Cc: freebsd-hackers@FreeBSD.org Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >You have lucked out, then. The factory defaults from AT&T/NCR are >"sparing enabled". Mostly because the original SVR4 code's soft >bad sectoring sucked. 8-(. Mine seems to have come from the WD factory :-). The Installation Guide says "[WD1007V-SE1/SE2 ... Copyright 1989 WDC ... Part No. 79-000367-000 WD0027S 8/89]". >> I don't see any such assumption. I have 3 SCSI controllers: U34F, >> BT445C and SC200. I've only used the U34F with 64/32 geometry. >> The BT445C and the SC200 work with assorted drives in assorted >> translation modes giving 64/32, 128/32 and 255/63 geometries. >What happens if you turn of translation on the things? (yes, I >know this is not a possibility for Adaptec). I haven't tried it. It should fail iff the weaker translation mode can't handle the geometry that the partition table was configured for. Perhaps if the geometry isn't 64/32. >... >> >Right... that's why you would use directories for population. >> >> Try explaining it to a user who thinks he has one disk. >How does the same user deal with having a "C:" and "D:" drive on his >DOS box with one disk without going into mental-meltdown? They've had 14 years to get used to it :-). The drive letters are visible at all levels because there's no mount step to produce a seamless directory tree, so users have to get used to it (SUBST and JOIN are little used and don't work well). >He handles it because there's a front-end program and he doesn't >have to deal with devices at the INT 13 device ID level. This program is called `export EDITOR=your_favourite_editor; disklabel -e' in BSD. It provides the same amount of support for DOS drives as DOS fdisk does for BSD partitions (none). >UNIX systems export the moral equivalent of INT 13 device ID's >(0x00 -- floppy A:, 0x01 -- floppy B:, 0x80 -- disk C:, 0x81 -- >disk D:, etc.). The confuse comes because the user doesn't have >a nice, clean, unified view of logical devices in UNIX (like he >does in DOS). I would have thought that the user doesn't have a nice, clean, unified view of logic devicies in DOS (like he does in UNIX) :-). Bruce