Skip to content

Latest commit

 

History

History
137 lines (112 loc) · 5.63 KB

README.md

File metadata and controls

137 lines (112 loc) · 5.63 KB
Raw

parti - Partition Information

About

parti shows partition and file system details for

It shows the complete information and not only the interpreted data (unlike partitioning tools like fdisk or parted).

So it can be used to verify the data your favorite partitioning tool has actually written.

Downloads

Get the latest version from the openSUSE Build Service.

openSUSE Development

To build, simply run make. Install with make install.

Basically every new commit into the master branch of the repository will be auto-submitted to all current SUSE products. No further action is needed except accepting the pull request.

Submissions are managed by a SUSE internal jenkins node in the InstallTools tab.

Each time a new commit is integrated into the master branch of the repository, a new submit request is created to the openSUSE Build Service. The devel project is system:install:head.

*.changes and version numbers are auto-generated from git commits, you don't have to worry about this.

The spec file is maintained in the Build Service only. If you need to change it for the master branch, submit to the devel project in the build service directly.

Development happens exclusively in the master branch. The branch is used for all current products.

You can find more information about the changes auto-generation and the tools used for jenkis submissions in the linuxrc-devtools documentation.

Example

Here's what parti says about the openSUSE-Tumbleweed installation ISO:

cd.iso: 9023488 sectors
- - - - - - - - - - - - - - - -
file system:
  fs "iso9660", label "openSUSE-Tumbleweed-DVD-x86_6411", uuid "2018-04-25-14-35-10-00"
- - - - - - - - - - - - - - - -
mbr id: 0x7322d96d
  sector size: 512
  isolinux.bin: 22924, "/boot/x86_64/loader/isolinux.bin"
  mbr partition table (chs 4406/64/32):
  1    3648 - 11459 (size 7812), chs 1/50/1 - 5/38/4
       type 0xef (efi)
       fs "vfat", uuid "732E-5C88", "/boot/x86_64/efi"
       fat12:
         sector size: 512
         bpb[62], oem "mkfs.fat", media 0xf8, drive 0xff, hs 4/63
         vol id 0x732e5c88, label "NO NAME", fs type "FAT12"
         fs size 7812, hidden 0, data start 45
         cluster size 4, clusters 1941
         fats 2, fat size 6, fat start 1
         root entries 512, root size 32, root start 13
  2  * 11460 - 9023487 (size 9012028), chs 5/38/5 - 1023/63/32
       type 0x17 (ntfs hidden)
       fs "iso9660", label "openSUSE-Tumbleweed-DVD-x86_6411", uuid "2018-04-25-14-34-34-00"
- - - - - - - - - - - - - - - -
el torito:
  sector size: 512
  boot catalog: 80
  0    type 0x01 (validation entry)
       platform id 0x00, crc 0x0000 (ok), magic ok
       manufacturer[15] "SUSE LINUX GmbH"
  1  * type 0x88 (initial/default entry)
       boot type 0 (no emulation)
       load address 0x00000, system type 0x00
       start 22924, size 4, "/boot/x86_64/loader/isolinux.bin"
       selection criteria 0x01 "Legacy (x86_64)"
  2    type 0x91 (last section header)
       platform id 0xef, name[0] ""
       entries 1
  3  * type 0x88 (initial/default entry)
       boot type 0 (no emulation)
       load address 0x00000, system type 0x00
       start 3648, size 7812, "/boot/x86_64/efi"
       selection criteria 0x01 "UEFI (x86_64)"
       fs "vfat", uuid "732E-5C88", "/boot/x86_64/efi"
       fat12:
         sector size: 512
         bpb[62], oem "mkfs.fat", media 0xf8, drive 0xff, hs 4/63
         vol id 0x732e5c88, label "NO NAME", fs type "FAT12"
         fs size 7812, hidden 0, data start 45
         cluster size 4, clusters 1941
         fats 2, fat size 6, fat start 1
         root entries 512, root size 32, root start 13

You see 3 sections:

  1. the image has a file system on it (ISO9660)
  2. there's an MBR with 2 partitions - partition 1 with a FAT file system (the UEFI system partition) - partition 2 with an ISO9660 file system - Notes
    • the MBR has a link to isolinux.bin - a peculiarity of isolinux used to locate itself when the image is booted as a disk
    • partition 1 is also accessible as /boot/x86_64/efi in the ISO9660 file system 3. an El Torito boot record with 2 bootable entries (marked with a *) - entry 1 used for leagcy BIOS booting (points to isolinux.bin) - entry 3 used for UEFI booting (points to a FAT image - this is partition 1, btw) - Note
    • block size for output is 512 for consistency

And what does this tell us?

The image is both as disk (has MBR) and DVD (El Torito) bootable, via legacy BIOS and UEFI, because

  • as disk it is legcay BIOS bootable (via special MBR boot code that locates isolinux.bin and loads it)
  • as disk it is UEFI bootable as it has an EFI System Partition
  • as DVD it is legacy BIOS bootable as it has a suitable El Torito record
  • as DVD it is UEFI bootable as it has another El Torito record suitable for UEFI