[338] in arla-drinkers
Re: @sys in /afs directory on arla-0.13 works ?
daemon@ATHENA.MIT.EDU (Brandon S. Allbery KF8NH)
Wed Oct 21 21:21:27 1998
From owner-arla-drinkers@stacken.kth.se Thu Oct 22 01:21:26 1998
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 13460 invoked from network); 22 Oct 1998 01:21:25 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 22 Oct 1998 01:21:25 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id DAA17565
for arla-drinkers-list; Thu, 22 Oct 1998 03:16:27 +0200 (MET DST)
Received: from hilfy.ece.cmu.edu (HILFY.ECE.CMU.EDU [128.2.253.106])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id DAA17560;
Thu, 22 Oct 1998 03:16:23 +0200 (MET DST)
Received: from rushlight.kf8nh.apk.net (allbery@ANNEX-9.SLIP.ECE.CMU.EDU [128.2.236.9])
by hilfy.ece.cmu.edu (8.8.8/8.8.8) with ESMTP id VAA03530;
Wed, 21 Oct 1998 21:16:19 -0400 (EDT)
Message-Id: <199810220116.VAA03530@hilfy.ece.cmu.edu>
X-Mailer: exmh version 2.0.2 2/24/98
To: Magnus Ahltorp <map@stacken.kth.se>
cc: arla-drinkers@stacken.kth.se
Subject: Re: @sys in /afs directory on arla-0.13 works ?
In-reply-to: Your message of "22 Oct 1998 02:02:01 +0200."
<lv13e8hjwg6.fsf@yakko.stacken.kth.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Oct 1998 21:16:22 -0300
From: "Brandon S. Allbery KF8NH" <allbery@kf8nh.apk.net>
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
In message <lv13e8hjwg6.fsf@yakko.stacken.kth.se>, Magnus Ahltorp writes:
+-----
| > In Transac AFS on linux, this @sys is interpreted as
| > i386_linux2 and works well, like as follows.
|
| In arla the sysnames are as follows on Linux i386:
|
| (i386_linux4 (libc4, not tested for))
| i386_linux5 (libc5)
| i386_linux6 (libc6)
|
| I think it's much more intuitive to number the sysnames after the libc
| version, and not the libc incarnation.
+--->8
It may make more sense, but it's not what the rest of the AFS world is using
so it's a problem when talking to existing AFS installations with existing
linux-afs clients.
FWIW we're using i386_linux2 for libc5, i386_linux2g currently for libc6,
but we're going to switch to i386_linux3 when the "official unofficial"
glibc linux-afs port comes out (it will use i386_linux3 for glibc2/libc6).
I'm not overly fond of it, but it's what I have to live with.
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university
