PRs for manpage 'dump(8)'
This is an experimental report containing PRs for manpage 'dump(8)' as of Fri May 30 07:36:54 2014 UTC. See notes.
PRs for manpage 'dump(8)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2009/02/13 | docs/131626 | doc | [patch] dump(8) "recommended" cache option confusing |
| o | 2007/04/17 | kern/111782 | fs | [ufs] dump(8) fails horribly for large filesystems |
| s | 2004/05/05 | kern/66270 | [hang] dump(8) causes machine freeze | |
| o | 2002/02/22 | bin/35214 | obrien | dump(8) program hangs while exiting |
| o | 2001/11/14 | bin/31987 | [patch] allow dump(8) to notify operators by mail(1) | |
| o | 2000/08/09 | bin/20501 | [patch] dump(8) extra flag to dump to offline autoloaders at EOT | |
| o | 2000/05/01 | bin/18319 | dump(8) fails with "cannot reopen disk: interrupted system call" |
Notes
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 linimon@FreeBSD.org. 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.