From: Maciej Soltysiak <maciej@soltysiak.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: Check for ccreg40
Date: Tue, 13 May 2008 08:36:38 +0200 [thread overview]
Message-ID: <482936F6.1020009@soltysiak.com> (raw)
In-Reply-To: <5ac301dfeac0d00ba1e2b281d90be66d@free.fr>
Hi,
I haven't looked at r4 development for a while now and I have a few
questions.
> Default profile:
> create: "reg40" (id:0x0 type:0x0) [Regular file plugin for creat(2)]
> key: "key_large" (id:0x1 type:0xb) [Key plugin]
> compress: "lzo1" (id:0x0 type:0xc) [Compression plugin]
> compressMode: "conv" (id:0x4 type:0xd) [Compression Mode plugin]
> [...]
>
> I am confused, does reg40 means no compression, or does the compress lzo1 being there means compression?
>
Is it possible to create a regular r4 partition and choose which files
keep compressed (how?)
or do I have to create a all-compressed partition?
To play with compression can I just use the standard patch from
http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
?
Does this patch include also file-as-directory stuff?
BTW it might be good to change the *Reiser4 is released!* message on
http://reiser4.erudified.com/install_v4.html
to at least point to
http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/
instead of giving a 404.
Best regards,
Maciej
next prev parent reply other threads:[~2008-05-13 6:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 23:01 Check for ccreg40 Mat
2008-05-12 23:16 ` Edward Shishkin
2008-05-13 0:41 ` John
2008-05-13 9:51 ` Matthew
2008-05-13 13:10 ` Edward Shishkin
2008-05-13 0:04 ` John
2008-05-13 6:36 ` Maciej Soltysiak [this message]
2008-05-13 8:53 ` Edward Shishkin
2008-05-13 7:53 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2008-05-12 21:53 John
2008-05-12 23:05 ` Edward Shishkin
2008-05-13 0:32 ` John
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=482936F6.1020009@soltysiak.com \
--to=maciej@soltysiak.com \
--cc=reiserfs-devel@vger.kernel.org \
/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.