AFF Development Task List - Revision history

Jpg at 10:22, 3 October 2007

2007-10-03T10:22:38Z

Jpg at 10:17, 3 October 2007

2007-10-03T10:17:06Z

Jpg at 10:16, 3 October 2007

2007-10-03T10:16:38Z

Jessek: /* High Priority */ - The library does not compile on 64-bit versions of Fedora Core 7 Linux.

2007-09-24T18:41:03Z

‎High Priority: - The library does not compile on 64-bit versions of Fedora Core 7 Linux.

Jpg: /* High Priority */

2007-08-03T14:39:17Z

‎High Priority

Jpg: /* High Priority */

2007-08-01T16:55:40Z

‎High Priority

Simsong: /* Medium Priority */

2007-07-25T20:13:13Z

‎Medium Priority

Jessek: /* High Priority */ - afcat usage message

2007-07-25T18:07:38Z

‎High Priority: - afcat usage message

Jessek: /* High Priority */

2007-07-24T18:35:48Z

‎High Priority

Jessek: Added more bugs

2007-07-24T18:22:47Z

Added more bugs

@@ Line 1: / Line 1: @@
 == High Priority ==
-* When afinfo -a is run on a non-AFF file, it notes it is a "Raw" file, but continues to attempt to process segments. It should exit if it does not find valid AFF segments.
+* When afinfo -a is run on a non-AFF file, it notes it is a "Raw" file, but continues to attempt to process segments. It should exit if it does not find valid AFF segments. For example, running it against a raw image of a 40GB disk created with aimage, afinfo -a reported 2,386 segments then finished with the error message "Cannot calculate missing pages."
 * The library does not compile on 64-bit versions of Fedora Core 7 Linux.

@@ Line 1: / Line 1: @@
 == High Priority ==
-* When afinfo -a is run on a non-AFF file, it notes it is a "Raw" file, but continues to attempt to process segments. It should exit if it
+* When afinfo -a is run on a non-AFF file, it notes it is a "Raw" file, but continues to attempt to process segments. It should exit if it does not find valid AFF segments.
-  does not find valid AFF segments.
 * The library does not compile on 64-bit versions of Fedora Core 7 Linux.

← Older revision		Revision as of 10:16, 3 October 2007
Line 1:		Line 1:
	== High Priority ==		== High Priority ==
		+
		+	* When afinfo -a is run on a non-AFF file, it notes it is a "Raw" file, but continues to attempt to process segments. It should exit if it
		+	does not find valid AFF segments.

	* The library does not compile on 64-bit versions of Fedora Core 7 Linux.		* The library does not compile on 64-bit versions of Fedora Core 7 Linux.

← Older revision		Revision as of 18:41, 24 September 2007
Line 1:		Line 1:
	== High Priority ==		== High Priority ==
		+
		+	* The library does not compile on 64-bit versions of Fedora Core 7 Linux.

	* Create man pages and/or documentation for AFF toolkit. To wit:		* Create man pages and/or documentation for AFF toolkit. To wit:

@@ Line 23: / Line 23: @@
 * Document that <tt>af_write</tt> may not be called without first setting the <tt>image_pagesize</tt> value inside of the <tt>AFFILE</tt> structure. Not doing so causes a divide by zero error. Perhaps we should 1. Check that <tt>image_pagesize</tt> is not zero and 2. Set <tt>image_pagesize</tt> to a known good default value when opening a new AFF file for writing.
-* Check aimage ability to write a file of 1,073,741,825 bytes ((2**30)+1). Correctly reported reading/writing a file that was a 1,073,741,824 random byte stream, but did not pick up the extra byte when it was added to the file. ls -la correctly shows the size with the extra byte. Also, added 42 additional bytes which were not apparently read or written.
+* Check aimage ability to write a file of 1,073,741,825 bytes ((2**30)+1). Correctly reported reading/writing a file that was a 1,073,741,824 random byte stream, but did not pick up the extra byte when it was added to the file. ls -la correctly shows the size with the extra byte. Also, added 42 additional bytes which were not apparently read or written.  UPDATE - With 511 bytes added, still didn't read/write full file, however, adding 512 bytes did cause the whole file (1,073,742,336 bytes) to be read/written.
 == Medium Priority ==

← Older revision		Revision as of 16:55, 1 August 2007
Line 22:		Line 22:

	* Document that <tt>af_write</tt> may not be called without first setting the <tt>image_pagesize</tt> value inside of the <tt>AFFILE</tt> structure. Not doing so causes a divide by zero error. Perhaps we should 1. Check that <tt>image_pagesize</tt> is not zero and 2. Set <tt>image_pagesize</tt> to a known good default value when opening a new AFF file for writing.		* Document that <tt>af_write</tt> may not be called without first setting the <tt>image_pagesize</tt> value inside of the <tt>AFFILE</tt> structure. Not doing so causes a divide by zero error. Perhaps we should 1. Check that <tt>image_pagesize</tt> is not zero and 2. Set <tt>image_pagesize</tt> to a known good default value when opening a new AFF file for writing.
		+
		+	* Check aimage ability to write a file of 1,073,741,825 bytes ((2**30)+1). Correctly reported reading/writing a file that was a 1,073,741,824 random byte stream, but did not pick up the extra byte when it was added to the file. ls -la correctly shows the size with the extra byte. Also, added 42 additional bytes which were not apparently read or written.

	== Medium Priority ==		== Medium Priority ==

@@ Line 26: / Line 26: @@
 * How about renaming the library to libaff? That would allow developers to link with <tt>-laff</tt> instead of <tt>-lafflib</tt>. To my knowledge, there is no existing library named AFF already.
 * Is there a set of segment names that must be defined to have a ''valid'' AFF file?
@@ Line 33: / Line 34: @@
 * Does <tt>af_open</tt> refuse to open a file for writing if it already exists? If so, what kind of error does it return?
 * Document how to programmatically enumerate all segments and values in a file. That is, explain how to get the output of <tt>$ afinfo -a</tt>.
 == Low Priority ==

@@ Line 14: / Line 14: @@
   * [[afxml]]
   * [[afsegment]]
 * Create man pages and/or documentation for AFF library functions (e.g. ,<tt>af_open</tt>, <tt>af_get_imagesize</tt>)

← Older revision		Revision as of 18:35, 24 July 2007
Line 18:		Line 18:

	* Build library as a shared library using libtool. This will allow developers using the library to just link to the AFF. Without it, developers must link to the static library and the individual libraries necessary <em>on that machine</em>. There is no good way to determine those extra libraries.		* Build library as a shared library using libtool. This will allow developers using the library to just link to the AFF. Without it, developers must link to the static library and the individual libraries necessary <em>on that machine</em>. There is no good way to determine those extra libraries.
		+
		+	* Document that <tt>af_write</tt> may not be called without first setting the <tt>image_pagesize</tt> value inside of the <tt>AFFILE</tt> structure. Not doing so causes a divide by zero error. Perhaps we should 1. Check that <tt>image_pagesize</tt> is not zero and 2. Set <tt>image_pagesize</tt> to a known good default value when opening a new AFF file for writing.

	== Medium Priority ==		== Medium Priority ==

← Older revision		Revision as of 18:22, 24 July 2007
Line 22:		Line 22:

	* How about renaming the library to libaff? That would allow developers to link with <tt>-laff</tt> instead of <tt>-lafflib</tt>. To my knowledge, there is no existing library named AFF already.		* How about renaming the library to libaff? That would allow developers to link with <tt>-laff</tt> instead of <tt>-lafflib</tt>. To my knowledge, there is no existing library named AFF already.
		+
		+	* Is there a set of segment names that must be defined to have a ''valid'' AFF file?
		+
		+	* Document that <tt>af_open</tt> (when writing a file) does more than a standard <tt>fopen</tt> command. The command writes an AFF stub of some kind to the output file. Users should be cautioned not to use this function as a test, lest they overwrite data.
		+
		+	* Does <tt>af_open</tt> refuse to open a file for writing if it already exists? If so, what kind of error does it return?
		+
		+	* Document how to programmatically enumerate all segments and values in a file. That is, explain how to get the output of <tt>$ afinfo -a</tt>.

	== Low Priority ==		== Low Priority ==