Thanks for all the quick responses! Most people said they did
similar configs without the need for an existing disktab entry from
version 1.2 on up. Selden Ball provided a detailed response that was
enlightening - I've included it below.
Now for the second order of business - HUMBLE apologies for the
screwed up "from:" field in my original message. My hosts file said
142.12.2.110 ucad1 ucad1.uccb.ns.ca ... which should have read
142.12.2.110 ucad1.uccb.ns.ca ucad1 so my mail software only picked
up the "ucad1" with no domain. When some people received it their mailers
filled in THEIR domains which got a few knickers in a twist! On the
bright side, every day I learn something new about unix...thanks again!
b.
Brian McMahon, CAD/CAM System Analyst | voice: (902)539-5300
UCCB CAD/CAM Center | fax: (902)562-0119
P.O. Box 5300 | mcmahon_at_cad.uccb.ns.ca
Sydney, Nova Scotia |
Canada, B1P 6L2 |
On Sun, 5 Mar 1995, Selden E Ball Jr wrote:
> Brian,
>
> You wrote to "alpha-osf-managers_at_sws1.ctd.ornl.gov" asking
>
> > I'd like to put a barracuda 4.3 gb drive on a 3000/300 running
> >osf/1 v2.0. I was under the impression that the label info would be sucked
> >off the disk, but a recent post refered to, in a similar situation, this
> >being an option with v3.0. Do I need the disktab entry for v2.0? And if
> >so can someone tell me where I might find it? Thanks in advance
>
> DEC accidentally broke disklabel's reading of disk parameters
> in one of the releases. I don't recall which one.
> It doesn't really matter: you can use a disklabel spec that's "close"
> find out the right numbers using scu ( "man scu" for details)
> and edit the label to make it right. ( "man disklabel" for details)
>
> briefly:
>
> disklabel -rw rz? xyzzy new_disk
>
> where ? should be replaced by the actual unit number
> xyzzy is a dummy disk type
> and new_disk should be replaced by the disk name you want to put on it.
>
> That will create DEC's default partitioning:
> a,b,c,g are as for a "system" disk, d,e,f,h are zero
>
> If that fails, you could specify any large disk that's described in
> /etc/disktab -- e.g. the rz26 partitioning posted recently
>
> disklabel -rw rz? rz26 new_disk
>
> then use scu to find the real capacity
> scu -f /dev/rrz?
> show capacity
>
> then edit the disklabel to set the max size and c partitions correctly
> (both should be the value shown by scu)
> If you're going to use partitions other than c (the entire disk),
> you'll have to do the arithmetic to determine where they start and stop.
>
> disklabel -e rz?
> uses vi by default (ed if in single user mode), but you can set the
> environment variable EDITOR to specify your favorite editor instead.
> Note that disklabel's columns are reversed when compared to the
> entries in /etc/disktab.
>
> Since all modern SCSI disks use zoned recording,
> sector/track/cylinder information is meaningless. Only the
> absolute block numbers matter. disklabel always recalculates the
> (irrelevant) cylinder numbers of the last columns. You shouldn't.
>
> I hope this helps.
>
> Selden
> ======
Received on Mon Mar 06 1995 - 10:55:54 NZDT