From: smiley@zenzebra.mv.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Q: moving directories? hard links?
Date: Thu, 21 Apr 2011 15:44:32 +0000 [thread overview]
Message-ID: <864o5r623j.fsf@cmarib.ramside> (raw)
In-Reply-To: <20110416182213.8E1D5B849@mail.bitblocks.com> (Bakul Shah's message of "Sat, 16 Apr 2011 11:22:13 -0700")
Bakul Shah <bakul@bitblocks.com> writes:
> Ask yourself *why* do you need it. Is it just convenience
> (what you are used to) or is there something you do that
> absolutely requires hard links? Next compare the benefit
> of hardlinks to their cost. It is worth it?
I'm trying to create a data structure in the form of a directed acyclic
graph (DAG). A file system would be an ideal way to represent the data,
except that P9 exposes no transaction to give a node more than one name.
I could store the data in a P9 file system tree and maintain a set of
links in, say $home/lib/bindrc.d/myDAG. But, every time I
copy/relocate/distribute the tree, I would have to include the myDAG
bindings. It would be much nicer if the structure of the data embodied
in the data itself.
ATM, I'm thinking about creating a DAGfs backed by pq. That way,
standard file utilities could still be used be used to manipulate the
data. However, that solution strikes me as being suspiciously similar
to creating a new disk file system. (How many do we have, already?)
--
+---------------------------------------------------------------+
|E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+
next prev parent reply other threads:[~2011-04-21 15:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 2:36 smiley
2011-04-16 2:40 ` Jacob Todd
2011-04-16 4:22 ` ron minnich
2011-04-16 16:53 ` erik quanstrom
2011-04-16 17:33 ` smiley
2011-04-16 17:51 ` erik quanstrom
2011-04-21 15:32 ` smiley
2011-04-21 15:43 ` ron minnich
2011-04-16 18:22 ` Bakul Shah
2011-04-21 15:44 ` smiley [this message]
2011-04-21 15:49 ` ron minnich
2011-04-21 16:54 ` Bakul Shah
2011-04-21 20:17 ` Richard Miller
2011-04-21 21:10 ` Bakul Shah
2011-04-21 22:41 ` erik quanstrom
2011-04-21 23:17 ` ron minnich
2011-04-21 23:54 ` Bakul Shah
2011-04-21 23:55 ` erik quanstrom
2011-04-22 0:01 ` ron minnich
2011-04-22 0:04 ` erik quanstrom
2011-04-22 8:03 ` Bakul Shah
2011-04-22 8:27 ` dexen deVries
2011-04-22 13:05 ` erik quanstrom
2011-04-22 17:47 ` Bakul Shah
2011-04-24 18:58 ` erik quanstrom
2011-04-16 18:03 ` Richard Miller
2011-04-16 18:17 ` Skip Tavakkolian
2011-04-16 18:56 ` Rob Pike
2011-04-18 9:08 ` Aharon Robbins
2011-04-18 12:41 ` erik quanstrom
2011-04-18 12:59 ` Lucio De Re
2011-04-18 13:00 ` erik quanstrom
2011-04-18 13:11 ` Lucio De Re
2011-04-23 3:48 ` Ethan Grammatikidis
2011-04-21 9:22 ` Balwinder S Dheeman
2011-04-16 16:58 ` erik quanstrom
2011-04-19 15:36 ` Charles Forsyth
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=864o5r623j.fsf@cmarib.ramside \
--to=smiley@zenzebra.mv.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).