Norman,
There's nothing wrong with a short name symlink to your cell's fully qualified
path per se, but it's incredibly difficult to keep it from creeping into places
is shouldn't be: hard-coded paths in package builds, scripts, documentation and
services that might eventually be available to
Jeffrey Hutzelman wrote:
[...] Don't use them in [...] email messages [...].
Otherwise you _will_ regret it later.
Yup. I sure do regret putting one in the email to this list that lit the
fuse on this discussion. My mozilla's delete button is 'bout wore out.
--
Excuse me for being dense, (and I was in one of those Transarc training
classes back in the day), but what's the harm in that symbolic link?
-norm
On Wed, 2004-10-27 at 11:34, Mitch Collinsworth wrote:
On Wed, 27 Oct 2004, Jim Rees wrote:
'/afs/isis' is a symbolic link, leading to a
* Derek Atkins [2004-10-28 00:18:36 -0400]:
tab requires stat'ing the directory which has always been a no-no
in /afs... With dynroot it's a bit better, but it's still an issue
if you're not using dynroot.
I think you meant to write fakestat instead of dynroot.
On Wednesday, October 27, 2004 12:37:52 -0400 Derrick J Brashear
[EMAIL PROTECTED] wrote:
On Wed, 27 Oct 2004, Derek Atkins wrote:
Jim Rees [EMAIL PROTECTED] writes:
3. (Optional) Create a symbolic link to a shortened cell name, to
reduce the length of pathnames for users in the local cell.
Jim Rees wrote:
Mount points is worse. At least with a symlink you can pwd and get a
correct global name. But if you are going through a local mount point, that
won't work.
Ken Hornstein and I checked the Unix dynamic roots mode. It supports a
static symlink like functionality through the
Joshua Johnson wrote:
So, at the risk of starting something here, I am going to ask what
other
peoples experiences are with placing /usr/local in AFS and sharing among
machines of same @sys type (much like the AdminGuide suggests).
I think it depends on how much administrative control you
'/afs/isis' is a symbolic link, leading to a mount point for
volume 'root.cell'.
So you broke one of the most important features of afs, the global name
space. Why?
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
Jim Rees wrote:
'/afs/isis' is a symbolic link, leading to a mount point for
volume 'root.cell'.
So you broke one of the most important features of afs, the global name
space. Why?
'Cause we're stupid? 'Cause I didn't want to make an already too long
message even longer?
Actually, we
Todd M. Lewis wrote:
Joshua Johnson wrote:
So, at the risk of starting something here, I am going to ask what other
peoples experiences are with placing /usr/local in AFS and sharing
among machines of same @sys type (much like the AdminGuide suggests).
Rather then /usr/local we have a
Todd M. Lewis wrote:
Jim Rees wrote:
'/afs/isis' is a symbolic link, leading to a mount point for
volume 'root.cell'.
So you broke one of the most important features of afs, the global name
space. Why?
'Cause we're stupid? 'Cause I didn't want to make an already too long
message even
3. (Optional) Create a symbolic link to a shortened cell name, to reduce
the length of pathnames for users in the local cell. For example, in the
abc.com cell, /afs/abc is a link to /afs/abc.com.
That really needs to be removed from the documentation.
On Wed, 27 Oct 2004, Jim Rees wrote:
'/afs/isis' is a symbolic link, leading to a mount point for
volume 'root.cell'.
So you broke one of the most important features of afs, the global name
space. Why?
Huh? Transarc trainers specifically taught to do exactly this 15
years ago. The
That really needs to be removed from the documentation.
I don't agree at all. It's listed as optional and has been there for
ages. It perhaps needs additional wording about the ramifications,
but should not be deleted IMO.
Not a single cell in our internal network will ever participate in
the
Jim Rees [EMAIL PROTECTED] writes:
3. (Optional) Create a symbolic link to a shortened cell name, to reduce
the length of pathnames for users in the local cell. For example, in the
abc.com cell, /afs/abc is a link to /afs/abc.com.
That really needs to be removed from the
Derek Atkins wrote:
Jim Rees [EMAIL PROTECTED] writes:
3. (Optional) Create a symbolic link to a shortened cell name, to reduce
the length of pathnames for users in the local cell. For example, in the
abc.com cell, /afs/abc is a link to /afs/abc.com.
That really needs to be removed from the
Mount points is worse. At least with a symlink you can pwd and get a
correct global name. But if you are going through a local mount point, that
won't work.
___
OpenAFS-info mailing list
[EMAIL PROTECTED]
On Oct 27, 2004, at 5:34 AM, Todd M. Lewis wrote:
Joshua Johnson wrote:
So, at the risk of starting something here, I am going to ask what
other
peoples experiences are with placing /usr/local in AFS and sharing
among machines of same @sys type (much like the AdminGuide suggests).
I think it
On Wed, 27 Oct 2004, Derek Atkins wrote:
Jim Rees [EMAIL PROTECTED] writes:
3. (Optional) Create a symbolic link to a shortened cell name, to reduce
the length of pathnames for users in the local cell. For example, in the
abc.com cell, /afs/abc is a link to /afs/abc.com.
That really needs to
Something that has come up with respect to the use of dynamic roots is
that the dynamic roots support mountpoints but not symlinks.
Organizations which have symlinks in their root.afs find using dynamic
roots on laptops to be extremely difficult if not impossible.
There is (at least on Unix
Derrick J Brashear [EMAIL PROTECTED] writes:
Which cell is /afs/cs?
That's local policy. But that's fine. Real references should
use the full path. The shorthand is for user convenience.
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student
Todd M. Lewis [EMAIL PROTECTED] writes:
It's convenient not to type .unc.edu a couple hundred times a
day. Whether it's worth it is an open question. (BTW,
'/afs/isis.unc.edu' is also a mount point for volume 'root.cell'.)
And I thought that was what the TAB key was for.
--
/Ian D
[EMAIL
Ian Delahorne [EMAIL PROTECTED] writes:
Todd M. Lewis [EMAIL PROTECTED] writes:
It's convenient not to type .unc.edu a couple hundred times a
day. Whether it's worth it is an open question. (BTW,
'/afs/isis.unc.edu' is also a mount point for volume 'root.cell'.)
And I thought that was what
So, at the risk of starting something here, I am going to ask what other
peoples experiences are with placing /usr/local in AFS and sharing among
machines of same @sys type (much like the AdminGuide suggests).
We've always run that way. The biggest problem, at least on OpenBSD, is
that
24 matches
Mail list logo
