From: Harri Haataja <realblades@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a question of file and the history of magic
Date: Mon, 7 Jul 2008 11:58:47 +0300 [thread overview]
Message-ID: <1215421127.8591.3.camel@Nokia-N810-22-8> (raw)
----- Original message -----
> There are a lot of things like that. Do we still need to
> compress man pages on 1TB disk driver? :)
I actually happened to be reading this on a small device that has a compressed system fs. Compressing data here on the "app" side with uninformed algorithms is discouraged to avoid double compression and other assorted losses. I believe you hit the same things with compression on some network protocols.
Touching GB range, this isn't that tiny but well below TB. :)
next reply other threads:[~2008-07-07 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 8:58 Harri Haataja [this message]
2008-07-11 16:21 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2008-07-06 23:45 geoff
2008-07-06 21:20 erik quanstrom
2008-07-06 21:59 ` Brantley Coile
2008-07-06 22:31 ` Bakul Shah
2008-07-06 22:44 ` Charles Forsyth
2008-07-06 19:30 erik quanstrom
2008-07-06 21:00 ` Jeff Sickel
2008-07-06 18:16 Jeff Sickel
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=1215421127.8591.3.camel@Nokia-N810-22-8 \
--to=realblades@gmail.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).