Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for manpage 'fdisk(8)'

This is an experimental report containing PRs for manpage 'fdisk(8)' as of Fri May 30 07:36:59 2014 UTC. See notes.

PRs for manpage 'fdisk(8)':
o2012/04/17bin/167036ambigious output of fdisk(8)
o2010/07/09bin/148471fdisk(8) prompts with negative partition size [regression]
o2010/01/31bin/143389[2tb] [patch] fdisk(8) cannot handle above 1TB under i386 system.
o2007/01/11bin/107829fs[2TB] fdisk(8): invalid boundary checking in fdisk / wraps value of > 2TB filesystem.
o2005/12/08bin/90093geomfdisk(8) incapable of altering in-core geometry
o2005/08/09bin/84705fdisk(8) program warning about sector number is misleading
o2004/01/25bin/61890sysinstallsysinstall(8): fdisk(8) uses incorrect calculations for disk geometry guessing and validation
o2002/07/15bin/40597[patch] add fdisk(8) ability of showing extended partition tables
8 problems total.


GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.

Please give feedback on this report to Thanks.

Bugs can be in one of several states:

o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.