No. GPT disks are self-identifying. All the information needed to interpret the partitioning scheme of a GPT disk is completely contained in structures in specified locations on the physical media.

The GUID Partition Table (GPT) was introduced as part of the Extensible Firmware Interface (EFI) initiative. GPT provides a more flexible mechanism for partitioning disks than the older Master Boot Record (MBR) partitioning scheme that has been common to PCs. A partition is a contiguous space of storage on a physical or logical disk that functions as though it were a physically separate disk. Partitions are visible to the system firmware and the installed operating systems.

Chapter 16 of the Extensible Firmware Interface (EFI) specification defines the GPT format. This document is available at http://developer.intel.com/ technology/ efi/ download.htm .

The specification allows an almost unlimited number of partitions, but the Windows implementation restricts this to 128 partitions. The number of partitions is limited by the amount of space reserved for partition entries in the GPT.

If this occurred, you must have used an MBR-only-aware disk tool to access the GPT disk. See answers #8 through #10, earlier.

Disk space: GMT contains some 100,000 lines of code. On a Linux workstation the executables take up about 15-50 Mb depending on use of shared libraries. In addition there are support data such as GSHHS coastlines, rivers, and political boundaries. The default distribution of these data includes intermediate, low and crude resolution versions which together takes up another 5 Mb of space. These are sufficient for most regional map applications.

No. The Disk and Partition GUIDs will no longer be unique. This must never happen. You can make a sector-by-sector copy of the contents of ESP or basic data partitions.

Yes; however, there are some key caveats. The OEM Preinstallation Kit (OPK) initializes the Disk and Partition GUIDs to zero. On first boot of Windows, the operating system generates unique GUIDs. The OPK only supports generation of ESP, MSR, and basic data partitions. If an application has recorded any Disk or Partition GUIDs it may break.

According to a paper present by Dan Hamel of Transarc, at the Decorum conference in February 1994, the following can be used as rough guidelines: end-user machines: Each dce_login creates new credential files, which can build up. Space usage can range from less than 1k to over 100k. The security server as shipped by the Open Group keeps all security registry information resident in main memory, which means that the security host machine needs memory as well as disk.

Floppy disks are available for purchase in the bookstore. In case of emergency, the IC Help Desk has loaner floppy disks, which must be returned to the Help Desk when you are done with them. IC Staff recommends that students invest in a USB Flash Drive to store their files.

an example, consider a file of 100,000 lines with an integer and text description on each line. Suppose the text string avergages twenty bytes in length. The flat file would be 2.8 MB. The size of the PostgreSQL database file containing this data can be estimated as 5.

You can probably cram the basics (i.e. base and etc distribution sets) into 80 MB or less, but here are some words of wisdom from Bill Studenmund (wrstuden@loki.stanford.edu): 100 meg would get you going for a root partition, but depending upon the toys, you'll want more. My setup is ~100 Meg for my root partition, and ~350 Meg for my USR partition.

SNAP Health Center requires an average of 50KB per student. PSNI has designed a database that has very little redundant stored data- data is stored once but accessed where it is needed.

GPT disks can grow to a very large size. The number of partitions on a GPT disk is not constrained by temporary schemes such as container partitions as defined by the MBR Extended Boot Record (EBR). The GPT disk partition format is well defined and fully self-identifying. Data critical to platform operation is located in partitions and not in unpartitioned or "hidden" sectors.

The entire contents of the tape are just over 1.4Gb. We have split the tape into 3 tar archives, which can be unloaded separately: The documentation archive is so large because it includes the documentation in 10 languages. The installation instructions describe how to extract the files for only a single language, thereby reducing the amount of disk space required to unload the distribution.

This depends upon the nature of your program. X11 applications typically need more disk space than a daemon or a character-based application. The MKS NuTCRACKER Workstation requires around 4Mb of disk space. The NuTCRACKER Deployment Wizard will estimate how much disk space you will need, based on the components you need to redistribute.