Hans Reiser wrote:

> Grant Miner wrote:
>
>> Someone mentioned earlier, and I like just the at sign: @ Think of it 
>> short for "attributes".
>>
>> file/@/uid
>>
>> The nice thing about @ is it shows up early lexicographically, it's 
>> short and unlikely to be used.  This name is important to pick well 
>> because it will likely set a long precedent.
>>
> It would be a problem for utilities like scp....
>
Hans, are you sure?  I tried some examples and had no troubles.  From my 
history:

      588  cd ~/tmp
      589  mkdir -p foo/@
      590  touch foo/@/uid
      591  scp -rp foo/@/uid stan:/tmp
      592  ssh stan 'mkdir -p /tmp/foo/@ ; touch /tmp/foo/@/uid'
      593  scp -rp stan:/tmp/foo/@ .

I'm not sure if @ is a good choice or not, but I don't think it would 
actually cause trouble syntactically, because everything expecting 
hostnames looks for a colon.

--

This message contains information which may be confidential and privileged. Unless you are the 
addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone 
the message or any information contained in the message. If you have received the message in error, 
please advise the sender and delete the message.  Thank you.