> 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
