Re: fsck.reiser4 can't fix 1 fixable corruption

[Hans Reiser <reiser@namesys.com>]

Vitaly Fertman wrote:

>On Thursday 22 April 2004 15:44, Domenico Andreoli wrote:
>  
>
>>On Thu, Apr 22, 2004 at 02:46:21PM +0400, Vitaly Fertman wrote:
>>    
>>
>>>with --enable-stand-alone you get another 'stand alone' library that
>>>includes the minimum of the code needed for programs like grub --
>>>no librepair, no tree balancing code, no modification code, etc. The
>>>code is minimised to be used with grub stage1_5. Libaal in stand-alone
>>>includes simple memory menagement methods (malloc, free) to avoid
>>>linking to libc -- as it links to no other libraries it is called
>>>stand-alone.
>>>      
>>>
>>thanks, now it's much more clear :)
>>    
>>
how about calling it --minimal-footprint and fixing the documentation to 
include some of the words above?

Please work on reviewing your documentation and options naming for 
greater clarity for a day.

>>    
>>
>>>>what does really change in the libraries? is something related to
>>>>reiser4 or to libtool & co?
>>>>
>>>>is it legal for debian to distribute libaal and libreiser4 packages
>>>>compiled with this option?
>>>>        
>>>>
>>>yes. Although new changes are tested not in the stand-alone mode
>>>first, and the stand-alone support may be delayed sometimes.
>>>      
>>>
>>this is not a problem, more people is able to use it, more will test
>>it for bugs :) this is the main reason i'm doing this packaging stuff ;)
>>
>>ok, i'm trying to build packages (always targeted to debian experimental)
>>with these stand alone libraries. i'm also reading in configure help
>>message about "--enable-memory-manager". is anything a distribution
>>could need [to test]?
>>    
>>
>
>yes, I forgot to tell the memory manager I mentioned above is enabled
>with --enable-stand-alone and with --enable-memory-manager. Without
>--enable-stand-alone you use libc methods, with --enable-stand-alone
>only you can use you own memory methods implementation.
>
>  
>