From: Tru64 User (tru64user@yahoo.com)
Date: Wed Apr 17 2002 - 15:02:27 EDT
Thanks to the zillion replies i received.
The easiest is diskconfig, used that.
I was more concerned with cyl
part............calculating it,
that happens to be just a comment.
it was for a 4.0g system, advfs
--- alan@nabeth.cxo.cpqcorp.net wrote:
>
> There are a couple of ways to do this, depending on
> the
> version (information you didn't provide). On
> recent
> versions there is a graphic disklabel maintenance
> program,
> but I don't use it. The other choice, suitable for
> all
> version is "disklabel -e".
>
> First, you need to get rid of that AdvFS domain on
> the
> C partition:
>
> o Backup the content(s).
> o Unmount the file system(s).
> o Use rmfset to remove the fileset(s)
> o Use rmfdmn to remove the domain.
>
> On modern versions that will change the fstype back
> to
> "unused". If you're certain the earlier steps have
> already been done, you can edit the label directly
> to
> change the type back to "unused". To change the C
> partition, you have to open the label using the A
> partition:
>
> # disklabel -e /dev/rre#a
>
> When that done, you can edit the label again to
> setup the
> partitions you want. This time, you need to use
> the C
> partition so that you can change A:
>
> # disklabel -e /dev/rre#c
>
> If you're going to use the disk for a root file
> system,
> it may be wise to clear the label and write a new
> initial
> label again to ensure the disk has the right boot
> blocks.
>
> # disklabel -z /dev/rre#c
> # disklabel -wr -t advfs /dev/rre#c whatever
>
> (Read the manual page to double check my options).
>
> Also, if using the disk for a system disk you'll
> probably
> want page/swap space on the disk. You'll need to
> decide
> how big to make that. 2-3 times physical memory is
> an old
> rule of thumb, but is obviously a poor idea in the
> face of
> very large memory systems. Something large than
> the expected
> virtual memory load or at least enough to boot the
> system
> and then add more from other devices is a better
> general
> suggestion.
>
> As for the labeling, it is pretty simple
> arithmetic. You
> want ~1 GB for the root:
>
> A (root): offset = 0, length = 2097152
> B (swap): offset = 2097152, length = "x"
>
> Generally, /usr ends up on G. No particular reason
> that I
> know of, just convention. The math is a bit more
> complicated
> but not very:
>
> G (usr): offset = 2097152 + x, length = 16756736 -
> x - 2097152
>
> The offset is simply the first available sector
> after the
> end if of B (or whatever you use for page/swap
> space). Add
> The length and offset of A to get the offset of B
> and then
> the offset and length of B to get the offset of G.
>
> For the length, it is whatever is left over. Since
> C is
> generally, the length of the whole disk, just
> subtract
> the length of the other partitions from C. The
> cylinder
> ranges will be calculated for you. When you create
> the
> domains for the root and /usr on the disk, mkfdmn
> will
> fill in the fstype.
=====
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:38 EDT