arla 0.7.2 troubles on sparc netbsd 1.3.1

[Magnus Ahltorp]

> Ah, but (Transarc) AFS does recognize these. We have the same problem;
> Presumably EMT is mis-creating mount points. On the other hand "real" AFS
> source doesn't seem to care what the mount points end with. The code seems to
> check exactly never (but I haven't looked hard either)

sundance:~$ ln -s "#home.map" testfoo1
sundance:~$ ln -s "#home.map." testfoo2
sundance:~$ ln -s "#home.map#" testfoo3
sundance:~$ ln -s "#home.map;" testfoo4
sundance:~$ ls -ld testfoo1
ls: testfoo1: No such device
sundance:~$ ls -ld testfoo2
drwxr-xr-x 40 root        22528 Jun 25 17:04 testfoo2
sundance:~$ ls -ld testfoo3
drwxr-xr-x 40 root        22528 Jun 25 17:04 testfoo3
sundance:~$ ls -ld testfoo4
drwxr-xr-x 40 root        22528 Jun 25 17:04 testfoo4
sundance:~$ fs lsm testfoo1
'testfoo1' is a mount point for volume '#home.ma'
sundance:~$ fs lsm testfoo2
'testfoo2' is a mount point for volume '#home.map'
sundance:~$ fs lsm testfoo3
'testfoo3' is a mount point for volume '#home.map'
sundance:~$ fs lsm testfoo4
'testfoo4' is a mount point for volume '#home.map'
sundance:~$ 

Obviously, transarc does not care what that last character is, even if
it is a letter.

/Magnus
map at stacken.kth.se