Description of problem:
The parted manual page lists the available partition flags as the options to the
set partition flag state
change the state of the flag on partition to state. Flags supported are:
"boot", "root", "swap", "hidden", "raid", "lvm", "lba" and "palo".
state should be either "on" or "off"
In the info docs, the type of partition table / disk label that the flag applies
to is also listed:
-- Command: set NUMBER FLAG STATE
Changes a flag on the partition with number NUMBER. A flag can be
either "on" or "off". Some or all of these flags will be
available, depending on what disk label you are using:
(Mac, MS-DOS, PC98) - should be enabled if you want to boot
off the partition. The semantics vary between disk labels.
For MS-DOS disk labels, only one partition can be bootable.
If you are installing LILO on a partition that partition must
be bootable. For PC98 disk labels, all ext2 partitions must
be bootable (this is enforced by Parted).
(MS-DOS) - this flag can be enabled to tell MS DOS, MS
Windows 9x and MS Windows ME based operating systems to use
Linear (LBA) mode.
[... etc etc ...]
This can be confusing for users who only check the man page & then attempt to
apply a flag to an innapropriate partition table type.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Read the fine manual (man parted)
Partition flags that are specific to certain partition table types are not
listed as such.
Partition flags that are specific to certain partition table types are clearly
Created attachment 156259 [details]
add partition table types to man page flags description
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Fixed in parted-1.8.1-13.el5, moving to MODIFIED.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.