[45] in arla-drinkers
Re: fs does not work?
daemon@ATHENA.MIT.EDU (Love)
Wed Jun 24 18:14:27 1998
From arla-drinkers-request@sundance.stacken.kth.se Wed Jun 24 22:14:26 1998
Return-Path: <arla-drinkers-request@sundance.stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 15727 invoked from network); 24 Jun 1998 22:14:23 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 24 Jun 1998 22:14:23 -0000
Received: from elixir.e.kth.se (sendmail@elixir.e.kth.se [130.237.48.5])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id AAA06718;
Thu, 25 Jun 1998 00:08:52 +0200 (MET DST)
Received: from zafir.e.kth.se (zafir.e.kth.se [130.237.48.6])
by elixir.e.kth.se (8.8.7/8.8.7) with ESMTP id AAA22606;
Thu, 25 Jun 1998 00:08:44 +0200 (MET DST)
Received: (e96_lho@localhost) by zafir.e.kth.se (8.8.7/8.6.6) id AAA31970; Thu, 25 Jun 1998 00:08:42 +0200 (MET DST)
Sender: e96_lho@elixir.e.kth.se
From: Love <lha@stacken.kth.se>
To: Naomaru Itoi <itoi@eecs.umich.edu>
Cc: shadow@dementia.org, lha@stacken.kth.se, arla-drinkers@stacken.kth.se
Subject: Re: fs does not work?
References: <199806242032.QAA26610@soso.eecs.umich.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Date: 25 Jun 1998 00:08:42 +0200
In-Reply-To: Naomaru Itoi's message of Wed, 24 Jun 1998 16:32:05 -0400
Message-ID: <yxb2d8bylafp.fsf@zafir.e.kth.se>
Lines: 26
X-Mailer: Gnus v5.3/Emacs 19.34
Naomaru Itoi <itoi@eecs.umich.edu> writes:
> Love, if your question is "does the syscall in 'fs' reach xfs?", my
> answer is I guess not. Several debug messages should be printed by
> xfs/bsd/xfs_syscall.c if a syscall is received by xfs, but I have seen
> none of them. (Yes, I have flipped all the debug flags on.) In fact,
> I believe no syscall is called from "fs" command because it fails at
> k_hasafs().
Ok, but k_hasafs() does a syscall i libkafs to probe if arla is there,
so you should at least see one probe in xfs.
If you look k_hasafs() in ${kth-krb}/lib/kafs/afssys.c you'll
see the syscall.
Make sure that its 210 that is the AFSSYSCALL. Run the
preprocessor on afssys.c and see what it really send to that syscall
in k_hasafs() Like:
cd ${kth-krb-objdir}/lib/kafs && rm afssys.o && \
make -n afssys.o | sed 's/-c/-E/' | sh | less
Good luck,
Love
