9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] FS to skip/put-together duplicate files
Date: Tue, 14 Aug 2007 08:02:23 -0700	[thread overview]
Message-ID: <3e1162e60708140802i2dbaab18y146544f08554dbd1@mail.gmail.com> (raw)
In-Reply-To: <397930e51c2a9a4f604cfcf75e5155ad@coraid.com>

[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]

Anyone run Venti on flash or eeprom before?  It might be more suitable there
than on giant disks.
Dave

On 8/14/07, erik quanstrom <quanstro@coraid.com> wrote:
>
> > > does anyone have an example of a case where compression and uniquing
> are required?
> >
> > the compression is nice to have of course but the uniqing is very
> > neat. I have always though of it as plan9's answer to CSV et al.
> >
> > When you do a release of a software package you copy the files to
> > a new directory with the name of the release (the equivilent of
> > tagging your release in CVS) - and continue working. this tne takes
> > up the space for the directory entries and all releases are always
> > available. branching is trivial (dircp) only a pretty merge tool
> > is missing - I have diff3 from edition7 in my contrib area
> > but some sort of interactive differencting GUI tool would be very
> > hand somtimes.
> >
> > have I drifted off topic I wonder...
>
> seems on topic to me.
>
> the extra disk space used for a copy of source should be tiny.
> if you have a 500GB disk (< $150 at newegg), making a several of extra
> copies of /sys/src would cost you 1/1000th of your disk space if not
> uniqued.
>
> the old way to do versioning is to remember the date of the release
> and use history.  this also doesn't use any disk space, except for the
> deltas.
>
> - erik
>

[-- Attachment #2: Type: text/html, Size: 1796 bytes --]

  reply	other threads:[~2007-08-14 15:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 11:39 Enrico Weigelt
2007-08-10 11:51 ` Gabriel Diaz
2007-08-10 12:26 ` erik quanstrom
2007-08-13  3:32   ` YAMANASHI Takeshi
2007-08-13 12:01     ` erik quanstrom
2007-08-13 13:43       ` Francisco J Ballesteros
2007-08-13 13:52         ` erik quanstrom
2007-08-13 14:40           ` Francisco J Ballesteros
2007-08-14 13:16     ` erik quanstrom
2007-08-14 13:57       ` Steve Simon
2007-08-14 14:13         ` erik quanstrom
2007-08-14 15:02           ` David Leimbach [this message]
2007-08-14 16:18       ` Uriel
2007-08-14 16:25         ` erik quanstrom
2007-08-15  0:27           ` Uriel
2007-08-15  0:42 YAMANASHI Takeshi
2007-08-15  0:47 ` erik quanstrom
2007-08-15  0:49 YAMANASHI Takeshi

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=3e1162e60708140802i2dbaab18y146544f08554dbd1@mail.gmail.com \
    --to=leimy2k@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).