strings /usr/sbin/fdisk output on OS X Tiger PowerPC 10.4.11

__dyld_mod_term_funcs
__dyld_make_delayed_module_initializer_calls
__dyld_image_count
__dyld_get_image_name
__dyld_get_image_header
__dyld_NSLookupSymbolInImage
__dyld_NSAddressOfSymbol
libobjc
__objcInit
The kernel support for the dynamic linker is not present to run this program.
In memory copy is initialized to:
Offset: %d
Use 'write' to update disk.
usage: auto <style>
  where style is one of:
Change disk geometry?
BIOS Cylinders
BIOS Heads
BIOS Sectors
Invalid argument: %s <partition number>
Invalid partition number.
Partition id ('0' to disable)
Partition %d is disabled.
Do you wish to edit in CHS mode?
BIOS Starting cylinder
BIOS Starting head
BIOS Starting sector
BIOS Ending cylinder
BIOS Ending head
BIOS Ending sector
Partition offset
Partition size
Partition %d is not an extended partition.
Loop to offset 0!  Not selected.
Selected extended partition %d
New MBR at offset %d.
Writing MBR at offset %d.
Machine code updated.
Partition %d marked active.
/usr/bin/less
PAGER
%s is not a character device or a regular file
Could not get disk metrics
BIOS fixup botch (%d sectors)
Disk: %s
geometry: %d/%d/%d [%d sectors]
geometry: <none>
usage: %s [-ieu] [-f mbrboot] [-c cyl -h head -s sect] [-S size] [-r] [-a style] disk
-i: initialize disk with new MBR
-u: update MBR code, preserve partition table
-e: edit MBRs on disk interactively
-f: specify non-standard MBR template
-chs: specify disk geometry
-S: specify disk size
-r: read partition specs from stdin (implies -i)
-a: auto-partition with the given style
-d: dump partition table
-y: don't ask any questions
-t: test if disk is partitioned
`disk' is of the form /dev/rdisk0.
auto-partition styles:
/usr/standalone/i386/boot0
Cylinder argument out of range.
Head argument out of range.
Sector argument out of range.
ieuf:c:h:s:S:ra:dyt
-i and -u cannot be specified simultaneously
Please specify a full geometry with [-chs].
Can't get disk geometry, please use [-chs] to specify.
Can't specify both -r and -a
could not open MBR file %s
could not read MBR code
error initializing disk
Signature: 0x%X
You must specify both start and size, or neither
Either all CHS arguments must be specified, or none
You must specify either start sector and size or CHS
%d,%d,0x%02X,%c,%d,%d,%d,%d,%d,%d
%s [%X - %X]: [%X]
%s [%d - %d]: [%d]
(? for help)
'%s' is not a valid number.
'%d' is out of range.
%s [%c]
%s%s%s%c
/dev/
%s%s%s
unused
Primary DOS with 12 bit FAT
XENIX / filesystem
XENIX /usr filesystem
Primary DOS with 16 bit FAT
Extended DOS
Primary 'big' DOS (> 32MB)
OS/2 HPFS, QNX-2 or Advanced UNIX
AIX filesystem
AIX boot partition or Coherent
OS/2 Boot Manager or OPUS
Primary Win95 w/ 32-bit FAT
Primary Win95 w/ 32-bit FAT LBA-mapped
Primary DOS w/ 16-bit FAT, CHS-mapped
Extended DOS LBA-mapped
OPUS
OS/2 BM: hidden DOS 12-bit FAT
Compaq Diagnostics
OS/2 BM: hidden DOS 16-bit FAT <32M or Novell DOS 7.0 bug
OS/2 BM: hidden DOS 16-bit FAT >=32M
OS/2 BM: hidden IFS
AST Windows swapfile
Willowtech Photon coS
Willowsoft OFS1
NEC DOS
Theos
Plan 9
VENIX 286 or LynxOS
Linux/MINIX (sharing disk with DRDOS) or Personal RISC boot
SFS or Linux swap (sharing disk with DRDOS)
Linux native (sharing disk with DRDOS)
QNX 4.2 Primary
QNX 4.2 Secondary
QNX 4.2 Tertiary
DM (disk manager)
DM6 Aux1 (or Novell)
CP/M or Microport SysV/AT
DM6 Aux3
Ontrack
EZ-Drive (disk manager)
Golden Bow (disk manager)
Priam Edisk (disk manager)
SpeedStor
ISC, System V/386, GNU HURD or Mach
Novell Netware 2.xx
Novell Netware 3.xx
Novell 386 Netware
Novell
DiskSecure Multi-Boot
PCIX
Minix 1.1 ... 1.4a
Minix 1.4b ... 1.5.10
Linux swap
Linux filesystem
Amoeba filesystem
Amoeba bad block table
OS/2 hidden C: drive
Linux extended
NT FAT volume set
NTFS volume set or HPFS mirrored
Mylex EISA SCSI
BSDI BSD/OS
Phoenix NoteBIOS save-to-disk
FreeBSD
OpenBSD
NEXTSTEP
Darwin UFS partition
NetBSD
Darwin boot partition
Darwin HFS+ partition
BSDI BSD/386 filesystem
BSDI BSD/386 swap
CTOS
DRDOS/sec (FAT-12)
DRDOS/sec (FAT-16, < 32M)
DRDOS/sec (FAT-16, >= 32M)
Syrinx (Cyrnix?) or HPFS disabled
Concurrent CPM or C.DOS or CTOS
DOS access or SpeedStor 12-bit FAT extended partition
DOS R/O or SpeedStor or Storage Dimensions
SpeedStor 16-bit FAT extended partition < 1024 cyl.
BeOS for Intel
SpeedStor or Storage Dimensions
DOS 3.3+ Secondary
SpeedStor >1024 cyl. or LANstep or IBM PS/2 IML
Xenix Bad Block Table
Choose from the following Partition id values:
%02X %s   %02X %s   %02X %s
   %02X %s
Cylinder values are modified to fit in CHS.
Warning CHS values out of bounds only saving LBA values
         Starting       Ending
 #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
------------------------------------------------------------------------
%c%1d: %.2X %4d %3d %3d - %4d %3d %3d [%10d - %10d] %s
Start of partition #%d after end!
help
Command help list
manual
Show entire man page for fdisk
reinit
Re-initialize loaded MBR (to defaults)
auto
Auto-partition the disk with a partition style
setpid
Set the identifier of a given table entry
disk
Edit current drive stats
edit
Edit given table entry
erase
Erase current MBR
flag
Flag given table entry as bootable
update
Update machine code in loaded MBR
select
Select extended partition table entry MBR
print
Print loaded MBR partition table
write
Write loaded MBR to disk
exit
Exit edit of current MBR, without saving changes
quit
Quit edit of current MBR, saving current changes
abort
Abort program without saving current changes
Do you wish to write new MBR?
Do you wish to write new MBR and partition table?
-----------------------------------------------------
------ ATTENTION - UPDATING MASTER BOOT RECORD ------
-----------------------------------------------------
MBR is unchanged
The signature for this MBR is invalid.
Would you like to initialize the partition table?
Enter 'help' for information
fdisk:%c%d>
Invalid command '%s'.  Try 'help'.
Writing current MBR to disk.
MBR was modified; really quit without saving?
Aborting changes to current MBR.
boothfs
8Mb boot plus HFS+ root partition
bootufs
8Mb boot plus UFS root partition
Entire disk as one HFS+ partition
Entire disk as one UFS partition
Entire disk as one DOS partition
raid
Entire disk as one 0xAC partition
 (default)
  %-10s  %s%s
No such auto-partition style %s
Disk size must be greater than 16Mb
<Unknown ID>
FDISK(8)                  BSD System Manager's Manual                 FDISK(8)
     f
k -- DOS partition maintenance program
     f
k [-
u] [-
e] [-
s] [-
s] [-
s] _
     In order for the BIOS to boot the kernel, certain conventions must be
     adhered to.  Sector 0 of a bootable hard disk must contain boot code, an
     MBR partition table, and a magic number (0xAA55).  These MBR partitions
     (also known as BIOS partitions) can be used to break the disk up into
     several pieces.
     The BIOS loads sector 0 of the boot disk into memory, verifies the magic
     number, and begins executing the code at the first byte.  The normal DOS
     MBR boot code searches the MBR partition table for an ``active'' parti-
     tion (indicated by a `*' in the first column), and if one is found, the
     boot block from that partition is loaded and executed in place of the
     original (MBR) boot block.
     The options are as follows:
     -
i      Initialize the MBR sector.
     -
             Specify an automatic partitioning style.
     -
e      Edit existing MBR sectors.
     -
             Specifies an alternate MBR template file.
     -
u      Update MBR code, preserving existing partition table.
     -
y      Do not ask for confirmation before writing.
     -
d      Dump partition table in a format readable by the -r option.
     -
r      Read a partition table from the standard input.
     -
t      Test if the disk is partitioned.
     -
s, -
s, -
             Specifies an alternate BIOS geometry for f
k to use.
     -
             Specify the disk size in blocks.
     The DOS f
k program can be used to divide space on the disk into parti-
     tions and set one active.  This f
k program serves a similar purpose to
     the DOS program.  When called with no special flags, it prints the MBR
     partition table of the specified device, i.e.,
         # fdisk fd0
         Disk: fd0       geometry: 80/2/18 [2880 sectors]
         Offset: 0       Signature: 0xAA55
                  Starting        Ending
          #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
         ----------------------------------------------------------------------
         *1: A6    0   0   1 -   79   1  18 [         0 -       2880] OpenBSD
          2: 00    0   0   0 -    0   0   0 [         0 -          0] unused
          3: A7    0   0   2 -   79   1  18 [         1 -       2879] NEXTSTEP
          4: 00    0   0   0 -    0   0   0 [         0 -          0] unused
     The geometry displayed is a synthetic geometry unless another geometry
     has been selected using the -
c, -
h, and -
s options.  In the future, f
     will read the BIOS geometry from the IOKit registry.
     In this example, the disk is divided into two partitions that happen to
     fill the disk.  The first partition overlaps the third partition.  (Used
     for debugging purposes.)
     _
#           Number of partition table entry.  A ``*'' denotes the
                 bootable partition.
     _
d          System identifier.  OpenBSD reserves the magic number 166
                 decimal (A6 in hex).  If no 166 partition is found, it will
                 use an older FreeBSD partition (with a magic number of 165 or
                 A5 in hex).
     _
c  These fields provide the starting and ending address of the
                 partition in BIOS geometry
     _
e  These fields provide the starting sector and size in sectors
                 of the partition in linear block addresses.
     _
E: The sectors field is ``1 based'', and the start field is ``0
     based''.  The CHS values may need to be in the BIOS's geometry for older
     systems to be able to boot and use the drive correctly; most modern sys-
     tems prefer the starting sector and size in preference to the CHS values.
     The -
i flag is used to indicate that the partition data is to be initial-
     ized.  In this mode, f
k will completely overwrite the primary MBR and
     partition table, either using the default MBR template, or the one speci-
     fied by the -
f flag.
     In the default template, partition number 1 will be configured as a Dar-
     win boot partition spanning from cylinder 0, head 1, sector 1, and
     extending for 8 megabytes.  Partition number 2 will be configured as a
     Darwin HFS partition spanning the rest of the disk.  This mode is
     designed to initialize an MBR the very first time, or when it has been
     corrupted beyond repair.
     You can specify other default partition styles with the -
a flag.  The
     available styles are:
     _
s     Creates an 8Mb boot partition (type AB hex) and makes the
                 rest of the disk a Darwin HFS partition (type AF hex).
     _
s     Creates an 8Mb boot partition (type AB hex) and makes the
                 rest of the disk a Darwin UFS partition (type A8 hex).
     _
s         Makes the entire disk one Darwin UFS partition (type A8 hex).
     _
s         Makes the entire disk one HFS+ partition (type AF hex).
     _
s         Makes the entire disk one DOS partition (type 0C hex).
     _
d        Makes the entire disk one type AC hex partition.
     The -
u flag is used to update the MBR code on a given drive.  The MBR
     code extends from offset 0x000 to the start of the partition table at
     offset 0x1BE.  It is similar to the -
i flag, except the existing parti-
     tion table is preserved. This is useful for writing new MBR code onto an
     existing drive, and is equivalent to the DOS command ``FDISK /MBR''.
     Note that this option will overwrite the NT disk signature, if present.
     The -
u and -
i flags may not be specified together.
     The flag -
e is used to modify a partition table using a interactive edit
     mode of the f
k program.  This mode is designed to allow you to change
     any partition on the drive you choose, including extended partitions.  It
     is a very powerful mode, but is safe as long as you do not execute the
     _
e command, or answer in the negative (the default) when f
k asks
     you about writing out changes.
     When you first enter this mode, you are presented with a prompt, that
     looks like so: _
>.  This prompt has two important pieces of infor-
     mation for you.  It will tell you if the in-memory copy of the boot block
     has been modified or not.  If it has been modified, the prompt will
     change to look like: _
>.  The second piece of information pertains
     to the number given in the prompt.  This number specifies the disk offset
     of the currently selected boot block you are editing.  This number could
     be something different that zero when you are editing extended parti-
     tions.  The list of commands and their explanations are given below.
     _
p    Display a list of commands that f
k understands in the interac-
             tive edit mode.
     _
l  Display this manual page.
     _
t  Initialize the currently selected, in-memory copy of the boot
             block.
     _
o    Partition the disk with one of the automatic partition styles.
     _
k    Display the current drive geometry that f
k has probed.  You
             are given a chance to edit it if you wish.
     _
t    Edit a given table entry in the memory copy of the current boot
             block.  You may edit either in BIOS geometry mode, or in sector
             offsets and sizes.
     _
d  Change the partition identifier of the given partition table
             entry.  This command is particularly useful for reassigning an
             existing partition to OpenBSD.
     _
g    Make the given partition table entry bootable.  Only one entry
             can be marked bootable.  If you wish to boot from an extended
             partition, you will need to mark the partition table entry for
             the extended partition as bootable.
     _
e  Update the machine code in the memory copy of the currently
             selected boot block.  Note that this option will overwrite the NT
             disk signature, if present.
     _
t  Select and load into memory the boot block pointed to by the
             extended partition table entry in the current boot block.
     _
t   Print the currently selected in-memory copy of the boot block and
             its MBR table to the terminal.
     _
e   Write the in-memory copy of the boot block to disk.  You will be
             asked to confirm this operation.
     _
t    Exit the current level of f
k, either returning to the previ-
             ously selected in-memory copy of a boot block, or exiting the
             program if there is none.
     _
t    Exit the current level of f
k, either returning to the previ-
             ously selected in-memory copy of a boot block, or exiting the
             program if there is none.  Unlike _
t it does write the modified
             block out.
     _
t   Quit program without saving current changes.
     The automatic calculation of starting cylinder etc. uses a set of figures
     that represent what the BIOS thinks is the geometry of the drive.  These
     figures are by default taken from the in-core disklabel, or values that
     _
t has passed to the kernel, but f
k gives you an opportunity to
     change them if there is a need to.  This allows the user to create a
     bootblock that can work with drives that use geometry translation under a
     potentially different BIOS.
     If you hand craft your disk layout, please make sure that the OpenBSD
     partition starts on a cylinder boundary.  (This restriction may be
     changed in the future.)
     Editing an existing partition is risky, and may cause you to lose all the
     data in that partition.
     You should run this program interactively once or twice to see how it
     works.  This is completely safe as long as you answer the ``write'' ques-
     tions in the negative.
     /usr/mdec/mbr  default MBR template
     pdisk(8)
     There are subtleties f
k detects that are not explained in this manual
     page.  As well, chances are that some of the subtleties it should detect
     are being steamrolled.  Caveat Emptor.
BSD                             January 3, 2002                            BSD
unused
DOS FAT-12
XENIX /
XENIX /usr
DOS FAT-16
Extended DOS
DOS > 32MB
HPFS/QNX/AUX
AIX fs
AIX/Coherent
OS/2 Bootmgr
Win95 FAT-32

Win95 FAT32L
DOS FAT-16
Extended LBA
OPUS
OS/2 hidden
Compaq Diag.
OS/2 hidden
OS/2 hidden
OS/2 hidden
AST swap
Willowtech
 Willowsoft
$NEC DOS
8Theos
9Plan 9
@VENIX 286
ALin/Minux DR
BLinuxSwap DR
CLinux DR
MQNX 4.2 Pri
NQNX 4.2 Sec
OQNX 4.2 Ter
PDM
QDM
RCP/M or SysV
SDM
TOntrack
UEZ-Drive
VGolden Bow
\Priam
aSpeedStor
cISC, HURD, *
dNetware 2.xx
eNetware 3.xx
fNetware 386
gNovell
hNovell
iNovell
pDiskSecure
uPCIX
Minix (old)
Minix (new)
Linux swap
Linux files*
Amoeba file*
Amoeba BBT
OS/2 hidden
Linux ext.
NT FAT VS
NTFS VS
Amoeba FS
Amoeba BBT
Mylex
BSDI
NotebookSave
FreeBSD
OpenBSD
NEXTSTEP
Darwin UFS
NetBSD
Darwin Boot
HFS+
BSDI filesy*
BSDI swap
CTOS
DRDOSs FAT12
DRDOSs < 32M
DRDOSs >=32M
HPFS Disbled
CPM/C.DOS/C*
SpeedStor
SpeedStor
SpeedStor
BeOS/i386
SpeedStor
DOS 3.3+ Sec
SpeedStor
Xenix BBT