From mboxrd@z Thu Jan 1 00:00:00 1970 From: smiley@zenzebra.mv.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <8662qej52i.fsf@cmarib.ramside> <86d3km6qz0.fsf@cmarib.ramside> Date: Thu, 21 Apr 2011 15:32:29 +0000 In-Reply-To: (erik quanstrom's message of "Sat, 16 Apr 2011 13:51:18 -0400") Message-ID: <868vv362nm.fsf@cmarib.ramside> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [9fans] Q: moving directories? hard links? Topicbox-Message-UUID: d1d06212-ead6-11e9-9d60-3106f5b1d025 erik quanstrom writes: >> It's not that obvious to me. A hard link is another name for a file, >> uniquely identified by . > > 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 got the impression, from what I read, that the kernel driver chooses the device number. >> 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. Then what's all that about in paragraphs 2-3 on p. 21 of /sys/doc/9.ps? >> It's similar for moving directories. If you have a 10 GiB directory, > > please explan why a bind is not appropriate here? The old directory will still be visible in its old location, even if it's bound to a new name. I had thought about sticking all my files under $home/files/ and binding them where I wanted them. But then, I'd just be reinventing all the i-node stuff of *nix. I might as well just call the directory $home/inodes/. :) >> At $local_big_networking_corp, I got chewed out for copying a 650MB ISO >> across a single router. > > did the router get tired? Yeah, I didn't understand their reaction, either. -- +---------------------------------------------------------------+ |E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B| |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B| +---------------------------------------------------------------+