Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 2009 00:49:21 -0500
From:      Garance A Drosihn <drosih@rpi.edu>
To:        freebsd-ppc@freebsd.org
Subject:   Re: Best options for disk-formatting on PowerPC? (mac-mini)
Message-ID:  <p06240816c59b0efb2397@[128.113.24.47]>
In-Reply-To: <p06240814c59afc49c1f7@[128.113.24.47]>
References:  <p0624080fc59a619b816f@[128.113.24.47]> <p06240814c59afc49c1f7@[128.113.24.47]>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:14 AM -0500 1/20/09, Garance A Drosihn wrote:
>At 6:13 PM -0500 1/19/09, Garance A Drosihn wrote:
>>
>>What I have is a new-to-me MacMini, with a brand new disk in it, and
>>nothing installed on that disk.  I also have an external FW drive
>>which has all the freebsd filesystems from my other Mac-Mini install.
>>I've just updated the system on that drive so it is the up-to-date
>>version of FreeBSD 7.1-STABLE.

>I'll define another device-alias in the new MM, once I figure out
>how I want the disk partitioned.

Okay, now I can finally get to writing the real question that I had,
before I got bogged down in what I expected to be *simple* steps...

What I wanted to end up with is filesystems such as:

Filesystem    1K-blocks     Used    Avail Capacity  Mounted on
/dev/disk1s3   33842792    35092 33807700     0%    /Volumes/MmP15_10p4T
/dev/disk1s5   10414889        8  9894137     0%    /Volumes/7x-root
/dev/disk1s7   11776292        8 11187470     0%    /Volumes/8x-root
/dev/disk1s9    3140772        8  2983726     0%    /Volumes/fb_swap
/dev/disk1s11   1515374        8  1439598     0%    /Volumes/7x-var
/dev/disk1s13   1718486        8  1632554     0%    /Volumes/8x-var
/dev/disk1s15   8006984        8  7606627     0%    /Volumes/fb_mkobj
/dev/disk1s17   6635601        8  6303813     0%    /Volumes/fb_Users
/dev/disk1s19  38456984    35232 38421752     0%    /Volumes/MmP15_10p5L

Actually I would have liked to end up with even more freebsd filesystems
than that, but there's a problem which comes up.  The above is how the
filesystems were listed by 'df -kl' under MacOS, right after I had
finished partitioning the new disk with DiskUtility.app .

While that is what MacOS *shows*, you can see a glimpse of the problem.
Notice that the device names are "disk1s3", "disk1s5", "disk1s7", etc.
For every unix partition that I ask DiskUtility.app, it really creates
two partitions, thus throwing away one partition-slot which I can not
really use in freebsd.  The unix command 'diskutil list /dev/disk1'
(under MacOS) shows:

/dev/disk1
    #:                   type name               size     identifier
    0: Apple_partition_scheme                 *111.8 GB    disk1
    1:    Apple_partition_map                   31.5 KB    disk1s1
                                    ( no entry listed for "disk1s2" )
    2:              Apple_HFS MmP15_10p4T       32.3 GB    disk1s3
    3:             Apple_Boot                    8.5 MB    disk1s4
    4:              Apple_UFS 7x-root            9.9 GB    disk1s5
    5:             Apple_Boot                    8.5 MB    disk1s6
    6:              Apple_UFS 8x-root           11.2 GB    disk1s7
    7:             Apple_Boot                    8.5 MB    disk1s8
    8:              Apple_UFS fb_swap            3.0 GB    disk1s9
    9:             Apple_Boot                    8.5 MB    disk1s10
   10:              Apple_UFS 7x-var             1.4 GB    disk1s11
   11:             Apple_Boot                    8.5 MB    disk1s12
   12:              Apple_UFS 8x-var             1.6 GB    disk1s13
   13:             Apple_Boot                    8.5 MB    disk1s14
   14:              Apple_UFS fb_mkobj           7.6 GB    disk1s15
   15:             Apple_Boot                    8.5 MB    disk1s16
      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   16:              Apple_UFS fb_Users           6.3 GB    disk1s17
   17:              Apple_HFS MmP15_10p5L        36.7 GB   disk1s19

It's all those 8.5-meg "Apple_Boot" partitions which are screwing
things up on me.  The problem is that disklabel on FreeBSD will
only show me the first sixteen of the partitions that it finds (it
stops where that dotted line is).  So, I can't actually *use* the
partition which I created as "fb_users".

So, finally, my freebsd-partitioning question:

Is there something I could do with GEOM and gpart such that I could
tell MacOS I want "just one" unix partition, and then on the freebsd
side of things I could carve that "one" partition into several ones.
I can see dedicating MacOS-visible partitions for 7x-root and 8x-root,
since I assume openfirmware needs to have some idea of those to boot
up.  And it's fine to dedicate another MacOS-visible partition for
swap.  But after that it'd be mighty convenient if I could create
just one more MacOS-visible partition, and then use something on
freebsd to split that into 7x-var, 8x-var, fb_mkobj, and fb_users.

Or is there some way to get FreeBSD to notice more than 16 of these
partitions that MacOS wants to create?  We couldn't get freebsd to
skip over all those  8.5-meg "Apple_Boot" partitions, could we?

-- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06240816c59b0efb2397>