On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many applications including KDE use
''+' to encode paths (replacing blanks
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many applications including KDE use
''+' to encode paths (replacing blanks
On 6/20/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many
Holger Berger wrote:
On 6/19/06, Eric Schrock [EMAIL PROTECTED] wrote:
Simply because we erred on the side of caution. The fewer metachacters,
the better. It's easy to change if there's enough interest.
You may want to change that since many applications including KDE use
''+' to encode
I accidentally tried to create a ZFS file system called lost+found[1]
and zfs(1) told me that + was an invalid char for a filesystem name.
Why is that ?
[1] cd /export/projects (where that is a ufs file system)
for i in * ; do
zfs create cube/projects/$i
done
--
Darren J
