[54] in arla-drinkers
Re: arla 0.7.2 troubles on sparc netbsd 1.3.1
daemon@ATHENA.MIT.EDU (Derrick J Brashear)
Thu Jun 25 10:54:55 1998
From arla-drinkers-request@sundance.stacken.kth.se Thu Jun 25 14:54:54 1998
Return-Path: <arla-drinkers-request@sundance.stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 27170 invoked from network); 25 Jun 1998 14:54:54 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 25 Jun 1998 14:54:54 -0000
Received: from alycia.dementia.org (ALYCIA.DEMENTIA.ORG [128.2.35.149])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id QAA12841
for <arla-drinkers@stacken.kth.se>; Thu, 25 Jun 1998 16:49:48 +0200 (MET DST)
Received: from jooky.dementia.org (root@jooky.dementia.org [147.72.91.130]) by alycia.dementia.org (8.8.5/8.8.7) with SMTP id KAA24200; Thu, 25 Jun 1998 10:49:07 -0400 (EDT)
Date: Thu, 25 Jun 1998 10:49:09 -0400 (EDT)
From: Derrick J Brashear <shadow@dementia.org>
Sender: root@jooky.dementia.org
Reply-To: Derrick J Brashear <shadow@dementia.org>
Subject: Re: arla 0.7.2 troubles on sparc netbsd 1.3.1
To: arla-drinkers@stacken.kth.se
cc: Stoned Elipot <Stoned.Elipot@univ-evry.fr>
In-Reply-To: <lv11zsdu0tn.fsf@yakko.stacken.kth.se>
Message-ID: <ML-1.3.2.898786149.3978.root@jooky.dementia.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
> > I got some trouble with arla on sparc nbsd 1.3.1.
> > Some volumes mount point appear to be "not resolved". Here is an en
example:
> > :; ls -la
> > total 4
> > drwxr-xr-x 2 1028 20 2048 Jun 24 16:10 .
> > drwxrwxrwx 41 root wheel 2048 Jun 25 11:45 ..
> > lrw-r--r-- 1 1028 20 13 Jun 4 10:58 003 ->
#src.top.003#
>
> A mount point consists of a symbolic link that begins with a hash and
> ends with a dot. Since your symbolic link ends in a hash, arla does
> not recognize it as a mount point.
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)
-D
