*BSD News Article 64505


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.nla.gov.au!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!yarrina.connect.com.au!news.mel.connect.com.au!news.syd.connect.com.au!gidora.kralizec.net.au!not-for-mail
From: bde@zeta.org.au (Bruce Evans)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Howto Add a 2nd SCSI Disk, example
Date: 29 Mar 1996 19:42:49 +1100
Organization: Kralizec Dialup Unix
Lines: 71
Message-ID: <4jg7q9$bms@godzilla.zeta.org.au>
References: <315A80A3.41C67EA6@mindspring.com> <4jf6bf$lqj@times.tfs.com>
NNTP-Posting-Host: godzilla.zeta.org.au

In article <4jf6bf$lqj@times.tfs.com>,
Julian Elischer <julian@mailhub.tfs.com> wrote:
>EEEK!
>Several things need correcting here!
>
>In article <315A80A3.41C67EA6@mindspring.com>,
>Ron Bolin  <rlb@mindspring.com> wrote:
>>...
>>1. Figure out your disk parameters and make an entry in /etc/disktab.
>>   For me it was a st12400n.
>
>ok.. what I do is use the entry for the floppy and then use
>disklabel -e to interactively edit it after install to correct
>all the figures.

That's what I usually do too.  It works because you're expanding the
partitions.  A (usually) better initial label can (usually) be obtained
by asking the driver for defaults:

	disklabel /dev/rsd2 >/tmp/foo

This label can be applied using

	disklabel -R -w sd2 /tmp/foo

after you have edited it.  The default label isn't quite usable without
any editing because it has bogus values for the rpm and interleave, and
most of the sizes in the label need to be adjusted if the label is for
part of the disk (the default label is for the whole disk).

>>3. fdisk -u /dev/rsd2, and update necessary info in the partition
>>   you wish to use. I used partion 3 (aka /dev/sd2c).
>weeellllll sd2c is by definition whichever slice of 
>sd2 is the BSD slice..
>
>if you used slice 0 it would still be sd2c
>
>the 'c' partition is 'special' in that is always reflects the entire BSD part
>of the disk.

Not the entire BSD part of the disk, only the entire _first_ BSD slice.

>what you are thinging of is possibly. sd2s2
>(disk 2, 3rd slice) If this is a BSD slice it iis functionally equivalent
>to sd2c.
>here I need to digress into disk naming:
>
>sd0 ..................whole disk of sd0
>sd0s0 ................first 'slice' of sd0
>sd0s0a ...............first BSD psrtition on first slice
>sd0a   ...............'nickname' for partition 'a' on the FIRST BSD SLICE

Most of the slice numbers in the quoted article are off by 1.  There is
no slice s0.  s1 is the first slice.

>___________________________________________________________________
>|      sd0                                                        |
>-------------------------------------------------------------------
>___________________________________________________________________
>|      sd0s0         |     sd0s1    |  sd0s2      |   sd0s3       |
>-------------------------------------------------------------------
        sd0s1               sd0s2       sd0s3          sd0s4 ... sd0s30

s30 is the last slice.

>You know we gotta have a dozen docs in people's home dir describing this..
>it's been done enough.....

One doc with all the numbers correct would be preferable :-).
-- 
Bruce Evans  bde@zeta.org.au