Path: utzoo!attcan!uunet!samsung!usc!rutgers!rochester!bbn.com!orc!inews!kseshadr@quasar.intel.com
From: kseshadr@quasar.intel.com (Kishore Seshadri)
Newsgroups: comp.unix.wizards
Subject: Re: getfh() systemcall
Keywords: getfh() NFS
Message-ID: <2499@inews.intel.com>
Date: 17 Jul 90 15:09:14 GMT
References: <1990Jul16.161053.4685@duc220.uni-duisburg.de>
Sender: news@inews.intel.com
Reply-To: kseshadr@quasar.intel.com (Kishore Seshadri)
Distribution: comp
Organization: Intel Corporation, Santa Clara, California
Lines: 27
In-reply-to: hz247bi@duc220.uni-duisburg.de (Bieniek)

In article <1990Jul16.161053.4685@duc220.uni-duisburg.de>, hz247bi@duc220 (Bieniek) writes:
>
>Hello,
>could someone be so nice and explain me the usage of the getfh
>systemcall which is available on machines running NFS-Kernels ?
>I know, it's a "read the funny source" Question, but I do not have
>access to BSD Kernel or Sun NFS sources.
>
On SunOS, the new getfh (4.x) takes a pathname:

int getfh(path, fh)
char *path;
fhandle_t *fh;

The old getfh took a file descriptor, so

getfh((char *)fd, fh)


works where fd is a file descriptor returned by open().


Kishore Seshadri
===============================================================================
Kishore Seshadri (Speaking only for myself) Intel Corp., Santa Clara, CA
CSNET: kseshadr@mipos3.intel.com ARPA: kseshadr%mipos3.intel.com@relay.cs.net
UUCP:{amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!kseshadr