Re: Automatic setup of partitions

[Gaby vanhegan <gaby_(_at_)_vanhegan_(_dot_)_net>]

From Nick Holland:


> > The problem arises when, if going on to a brand new machine, that  
> the
> > disk size may be different than the original it is restoring.  As
> > part of the installer (in the OpenBSD install environment, booted  
> off
> > an openbsd installer CD) I'd like to read the size of the disk and
> > partition the disk accordingly.  would I need to generate all of  
> this
> > information?
>
> Using your strategy, you would have to generate the info.
>
> Here's a (I think) better idea...
> Rather than trying to partition out percentages, just put in what you
> need...
>   /    100M
>   swap 512M
>   /usr   4G
>   /var   1G
>   /tmp 100M
>   ...
> and so on.
> And (here's the shocker) leave the REST OF THE DRIVE UNALLOCATED!

Unsure why I didn't get this reply directly, seems the email never  
made it to me.  An eminently sensible solution, alongside the  
suggestion to grow partitions.  I suppose my only question now is this:

After assigning a default disklabel (to a blank disk), can I just  
feed disklabel the partition information?  ie, just this part:

16 partitions:
    a:  2048193       63    4.2BSD     1024  8192    16   # (Cyl.     
0*- 203
  b:   524160  2048256      swap                        # (Cyl. 2032  
- 2551)
  c: 117187500        0    unused        0     0        # (Cyl.    0  
- 116257*)
  d: 114605694  2572416    4.2BSD     1024  8192    16  # (Cyl. 2552  
- 116248*)

Using disklabel -R, instead of the whole file:

type: ESDI
disk: ESDI/IDE disk
label: IC35L060AVER07-0
yadda...
16 partitions:
#        size   offset    fstype   [fsize bsize   cpg]
  a:  2048193       63    4.2BSD     1024  8192    16   # (Cyl.     
0*- 2031)
yadda...

Gaby

--
Junkets for bunterish lickspittles since 1998!
gaby_(_at_)_vanhegan_(_dot_)_net
http://weblog.vanhegan.net