All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Edward Shishkin <edward@namesys.com>
Cc: Fred Schaettgen <namesys.Sch@ttgen.net>, reiserfs-list@namesys.com
Subject: Re: Will I need to re-format my partition for using the compression plugin?
Date: Thu, 22 Sep 2005 15:11:59 -0500	[thread overview]
Message-ID: <4333100F.6080307@slaphack.com> (raw)
In-Reply-To: <43330E14.9050209@namesys.com>

Edward Shishkin wrote:
> Fred Schaettgen wrote:
> 
>> On Thursday, 22. September 2005 18:41, Edward Shishkin wrote:
>>  
>>
>>> Grzegorz Jaśkiewicz wrote:


>> Or is there another reason why you packed both things into one plugin?
>>
> 
> Because sometimes it is useful to compress data before encryption since 
> compression
> destroys vulnerable regular structure of some special files (like *.html)

Although I'd imagine some algorithms are fairly resistant against that 
(RSA, maybe?), the main reason is simple -- encryption tends to 
introduce randomness.  If the crypto is any good at all, you won't be 
able to compress very well after you've encrypted.

Anyway, can't you stack plugins?  Or at least create one new plugin out 
of two existing ones?

>> If most new file features have to be implemented as part of one single 
>> plugin,
>>
> 
> Then this plugin will look like a monster ;)
> Not necessarily. On the oher hand, creating a separate file plugin for 
> each feature
> imho is not a good idea.

How about some other examples of things to group together and things to 
not group together?

I wonder if it would make sense to try to optimize for a huge number of 
plugins?  It'd be harder than optimizing for a huge number of files per 
directory, but would it be possible?

  reply	other threads:[~2005-09-22 20:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 13:31 Will I need to re-format my partition for using the compression plugin? Clemens Eisserer
2005-09-20 13:58 ` Edward Shishkin
2005-09-20 15:49 ` Vladimir V. Saveliev
2005-09-20 16:12   ` Edward Shishkin
2005-09-20 19:19     ` Clemens Eisserer
2005-09-20 19:38       ` Tomasz Chmielewski
2005-09-20 19:43         ` Edward Shishkin
2005-09-22 15:24           ` Grzegorz Jaśkiewicz
2005-09-22 16:41             ` Edward Shishkin
2005-09-22 17:51               ` Fred Schaettgen
2005-09-22 20:03                 ` Edward Shishkin
2005-09-22 20:11                   ` David Masover [this message]
2005-09-22 20:49                     ` Valdis.Kletnieks
2005-09-22 20:54                       ` michael chang
2005-09-22 21:05                         ` Valdis.Kletnieks
2005-09-23  9:00                         ` Edward Shishkin
2005-09-22 22:13                       ` Gregory Maxwell
2005-09-23  6:08                         ` Valdis.Kletnieks
2005-09-22 20:38                   ` Valdis.Kletnieks
2005-09-22 20:54                   ` Gregory Maxwell
2005-09-22 21:33                   ` PFC
2005-09-22 21:38                   ` Fred Schaettgen
2005-09-23 11:12                     ` Edward Shishkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4333100F.6080307@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=edward@namesys.com \
    --cc=namesys.Sch@ttgen.net \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.