From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Q: moving directories? hard links?
Date: Sat, 16 Apr 2011 13:51:18 -0400 [thread overview]
Message-ID: <a371befd960a8971817c72434164e9b9@ladd.quanstro.net> (raw)
In-Reply-To: <86d3km6qz0.fsf@cmarib.ramside>
> It's not that obvious to me. A hard link is another name for a file,
> uniquely identified by <type,device,qid>.
how do you specify the device? you can't without giving up
on per-process-group namespaces. i don't think there's any
way to uniquely identify a device except through a namespace,
and there's no global namespace.
> I don't understand why 9P doesn't allow transporting bind operations
> from machine to machine like this.
this is done all the time. every time you cpu, you are exporting
your whole namespace to the target machine.
> It's similar for moving directories. If you have a 10 GiB directory,
please explan why a bind is not appropriate here?
> At $local_big_networking_corp, I got chewed out for copying a 650MB ISO
> across a single router.
did the router get tired?
- erik
next prev parent reply other threads:[~2011-04-16 17:51 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 [this message]
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
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=a371befd960a8971817c72434164e9b9@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).