From: "Charles P. Wright" <cpwright@cpwright.com>
To: porte64@free.fr
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: built-in rotating and compressed files: rotfs and zfs
Date: Thu, 22 Jan 2004 10:59:37 -0500 [thread overview]
Message-ID: <1074787177.12904.4.camel@arcticfox.foo> (raw)
In-Reply-To: <1074785688.400fed980f994@imp1-l.free.fr>
Look at FiST, which is available from http://www.filesystems.org. The
FiST package includes gzipfs, a stackable file system that compresses
and decompresses data on the fly.
Charles
On Thu, 2004-01-22 at 10:34, porte64@free.fr wrote:
> Many applications make heavy usage of compressed files
> and some need rotating files.
>
> Though compression methods are almost stabilized as standards,
> one still does need special tools like zcat to read from them.
> But many applications are not aware of zcat, zcat cannot read
> byte ranges within binary files ...
>
> Hence a proposal: how about implementing a file compression
> and a file rotation within the kernel ?
> - This would make system calls like read() and write() transparent
> ... so it would brought transparency to all applications
> - e.g. syslog messages would be compressed on-the-fly, backup
> utilities would not have to delay job queues due to compression
> overcost.
> - Humans would not have to bother about disk usage and machine
> power when uncompressing files.
>
> So many advantages !
> Now, one open question: is it better to implement this at file
> level (one extra attribute) or at file system level
> (designing zfs and rotfs) ?
>
> Regards
> Phil
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2004-01-22 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 15:34 built-in rotating and compressed files: rotfs and zfs porte64
2004-01-22 15:59 ` Charles P. Wright [this message]
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=1074787177.12904.4.camel@arcticfox.foo \
--to=cpwright@cpwright.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=porte64@free.fr \
/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.