tags 309256 + wontfix confirmed upstream
thanks

also sprach Enver ALTIN <[EMAIL PROTECTED]> [2005.05.16.0155 +0200]:
> It seems to me that somehow crucial parts of filewriter plugin
> has been #ifdef 0'ed, and it looks like on purpose.

Yes, this was done by upstream.

> I'd like to kindly ask, what was the reason behind that decision?
> 
> You know, my physical memory is larger than my available swap, and
> it's a bit weird to resize my filesystems and repartition just to
> be able to suspend when more physical memory is in use :)
> 
> I was just going to re-enable that again, but I thought I should
> ask before doing so.

The filewriter is relatively new and has not been stabilised.
Moreover, I have not had the time to incorporate it into Debian
properly. I am waiting for upstream to settle before doing so.

In the mean time, you can only use the swap writer.

If you want to accelerate the process, try enabling it yourself and
getting it to work nicely. Document your steps and send me your
documentation with comments and questions.

Thanks,

-- 
 .''`.     martin f. krafft <[EMAIL PROTECTED]>
: :'  :    proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
 
it is better to have loft and lost
than to never have loft at all.
                                                       -- groucho marx

Attachment: signature.asc
Description: Digital signature

Reply via email to