22 Oct
2013
22 Oct
'13
11:48 a.m.
On Oct 22, 2013, at 2:27 PM, Jochen Kunz <jkunz at unixag-kl.fh-kl.de> wrote:
True. My statement was oversimplified. It does rely on being
able to partition the drive, which is not something every OS
really does.
That's the same conclusion I came to, with the same data. Good
to know I'm not totally nuts, but I was mostly wondering if
anyone had specific experience with it before I go plundering my
dwindling cache of 50-pin SCSI drives.
- Dave
Earlier 3100s
have a 1.0something limit on the size of the boot
drive because the firmware only issues the older, shorter SCSI
commands which can only address that many blocks. You can use
any size you'd like for the drives used once it's booted, since
the OS usually has no such problem (it's not a problem with the
SCSI controller itself).
AFAIK you can get away with making the boot partition
smaller then
1 GB. Then you can use disks larger 1 GB even asd boot drive. My
recollection is that it's essentially a reboxed version of
the 4000/60, which does not (none of the 4000s do, IIRC). I'll
try it out sometime soon regardless, but it would be nice to
have an idea before I dive in.
MV3k1m80 and VS4k60 are Mariah based:
http://www.netbsd.org/docs/Hardware/Machines/DEC/vax/vaxstations.html#vaxst…
http://www.netbsd.org/docs/Hardware/Machines/DEC/vax/microvaxes.html#microv…
So most likely the MV3k1m80 is not affected by that problem.