Xref: utzoo comp.bugs.sys5:464 comp.unix.wizards:9282
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!agate!ig!uwmcsd1!marque!uunet!munnari!moncskermit!labtam!timr
From: timr@labtam.OZ (Tim Roper)
Newsgroups: comp.bugs.sys5,comp.unix.wizards
Subject: Re: File System Type (statfs, sysfs)
Summary: described in Rifkin et al but not in V.3 doc or SVID
Keywords: System V Release 3.1.1 Version 3 for AT&T 3B2
Message-ID: <691@labtam.OZ>
Date: 7 Jun 88 00:06:32 GMT
References: <479@uniq.UUCP> <681@labtam.OZ> <55038@sun.uucp>
Organization: Labtam Limited., Melbourne, Australia
Lines: 22

In article <55038@sun.uucp>, guy@gorodish.Sun.COM (Guy Harris) writes:
> > If you stat(2) a remote file you get the high order bit of st_dev
> > turned on so you can tell that it is remote if you want to.  Also the
> > major number tells which machine it resides on.  And the minor
> > number tells which filesystem on the remote machine the file
> > resides on.
> 
> Note that, as far as I know, none of this is documented anywhere; therefore, it
> should be considered a quirk of the implementation, *not* a documented part of
> the interface.  It happens to work under S5R3, but it may break someday.

It is described in

	%T RFS Architectural Overview
	%A Andrew P. Rifkin et al
	%J USENIX Conference Proceedings
	%C Atlanta, Georgia
	%D June 1986

But, stat(2) in System V.3 Programmer's Reference Manual and stat(ba_os) in
SVID Issue 2 Volume 1 say that st_dev has no significance other than as
input to ustat(2) and ustat(ba_os) respectively.
D