erik quanstrom <quans...@quanstro.net> writes:

>> 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 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: smi...@zenzebra.mv.com             PGP key ID: BC549F8B|
|Fingerprint: 9329 DB4A 30F5 6EDA D2BA  3489 DAB7 555A BC54 9F8B|
+---------------------------------------------------------------+

Reply via email to