From: Edward Shishkin <edward@namesys.com>
To: John Gilmore <jgilmore@glycou.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiser4 documentation & specifically current status of repacker, compression, and semantics
Date: Mon, 24 Oct 2005 23:08:00 +0400 [thread overview]
Message-ID: <435D3110.8060204@namesys.com> (raw)
In-Reply-To: <200510241225.45686.jgilmore@glycou.com>
John Gilmore wrote:
>On Monday 24 October 2005 14:44, Edward Shishkin wrote:
>
>
>>John Gilmore wrote:
>>
>>
>>>There is a 'compress' directory in in my reiser4 source tree. So is the
>>>compression plugin done? Is my disk/files compressed?
>>>
>>>
>>not yet,
>>this is under construction..
>>
>>
>>
>>>And if it was/wasn't
>>>how would I know the difference, and change it?
>>>
>>>
>>I guess reiser4progs will be able to dump the attributes then
>>
>>Edward.
>>
>>
>I thought the ability to muck around with the plugins assigned to a
>particular file was implemented as file-as-directory? I've tried to re-enable
>that ability, but haven't been able to get it to work.
>
This code (pseudo plugin) has been removed as mainline folks required.
It will be supported as an optional patch a bit later
> How are plugin/file
>relationships handled without it?
>
>
>
For the first time there will be an option in mkfs to assign a file
plugin for regular files per superblock.
Then (if everything will be okay) we will granulate the relationship.
Edward.
next prev parent reply other threads:[~2005-10-24 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-23 18:50 Reiser4 documentation & specifically current status of repacker, compression, and semantics John Gilmore
2005-10-24 14:44 ` Edward Shishkin
2005-10-24 12:25 ` John Gilmore
2005-10-24 19:08 ` Edward Shishkin [this message]
2005-10-24 13:45 ` John Gilmore
2005-10-24 21:11 ` Hans Reiser
2005-10-25 19:06 ` Edward Shishkin
2005-10-25 22:12 ` Hans Reiser
2005-10-26 13:51 ` Edward Shishkin
2005-10-27 13:48 ` Edward Shishkin
2005-10-24 19:03 ` Hans Reiser
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=435D3110.8060204@namesys.com \
--to=edward@namesys.com \
--cc=jgilmore@glycou.com \
--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.