Subject: SCSI/disklabel questions
To: None <port-hp300@NetBSD.ORG>
From: Michael Wolfson <mbw@fatmac.ee.cornell.edu>
List: port-hp300
Date: 06/28/1998 12:29:10
Hi folks,

Thanks for your answers so far.  I still haven't gotten any info on the
bootblock/disklabel questions.  I'd really appreciate if someone could
explain it to me.

As for the SCSI speed business, I should've been a little more clear:
I've never seen more than ~700 KB/s under normal usage (tar, cp, mv, ftp).
Using dd to read and write null data, I can indeed get 1.5 MB/s, but
that's still 1/2 the thruput I get on other platforms.  

In any case, David Brownlee mentioned that SCSI could be noticably faster
once we get the machine independent SCSI drivers ported to hp300.  So,
this is kind of moot if that happens anytime soon.  Same goes for the DAT
issue (i.e. apparently most DAT drives would be supported with MI SCSI).

Thanks,
  -- MW


---------- Forwarded message ----------
Date: Mon, 22 Jun 1998 20:41:57 -0400 (EDT)
From: Michael Wolfson <mbw@fatmac.ee.cornell.edu>
To: port-hp300@netbsd.org
Subject: SCSI/disklabel questions

How are the bootblocks and disklabel arranged?  As best as I can
    determine, the label sits at sector 1, and the boot blocks surround it
    at sector 0 and 2 thru whatever.  This would make sense since improperly
    installed boot blocks can be wiped out by disklabel and vice versa.

The install notes recommend ofsetting the a partition by one cylinder,
    which is fine for disks with small cylinder sizes, but how much space
    is really necessary for SCSI disks?

What other NetBSD platforms can/can't write disklabel and bootblocks for 
    hp300 machines (I know sun3x, sun3, and sparc can't)?

And, lastly, can anyone comment on why the HP-IB isn't available when one
    or more SCSI devices are attached (i.e. can't use HP-IB drives or
    tapes if a SCSI drive is plugged into my 400s)?  This used to work
    thru NetBSD-1.1.

TIA,
  -- MW