inodes on remote disks (was: running out of inodes?)

[David C Lawrence]

In article <17641 at mimsy.UUCP> chris at mimsy.UUCP (Chris Torek) writes:
Chris> On modern systems, simply run `df -i'.

This is on a tangent, but here is something that has been noticed on
our SunOS 4.0.1 system:

Filesystem             iused   ifree  %iused  Mounted on
/dev/xy0a                620    1428    30%   /
life.pawl.rpi.edu:/usr
                           0      -1    -0%   /usr
/dev/xy1h              10047   18625    35%   /appl/imagine2
/dev/xy1e              43257   32519    57%   /home
/dev/xy0h              24785   28463    47%   /appl/imagine1
/dev/xy0e                194    1854     9%   /var
/dev/xy1a                602    1446    29%   /var/spool/mail
/dev/xy0d               5970   43182    12%   /export
rpi.edu:/usenet            0      -1    -0%   /usenet
hope.its.rpi.edu:/itss_b
                           0      -1    -0%   /itss_b
hope.its.rpi.edu:/itss_c
                           0      -1    -0%   /itss_c
life.pawl.rpi.edu:/appl/life1
                           0      -1    -0%   /appl/life1
life.pawl.rpi.edu:/usr/local
                           0      -1    -0%   /usr/local

The thing that puzzles us in the curious data for any remote
filesystem; my first wild guess was that the information from the
remote disk couldn't be found by the local df.  The problem with that
wild guess, from my perspective, is that it used to work fine under
SunOS 3.5.  Now are users get absolutely no useful information
regarding inodes when they are on the diskless Suns; in the case of
/usenet, at least, the information can sometimes be useful to people
who don't really have any control over the disks.

Can someone please tell me why this is like this?

Dave
--
 (setq mail '("tale at pawl.rpi.edu" "tale at itsgw.rpi.edu" "tale at rpitsmts.bitnet"))
 (error "UUCP not spoken here.  Long bang paths unlikely to get mail replies.")