fsid_t

[Dag-Erling Smorgrav]

fsid_t is currently defined as a struct containing an array of two
32-bit ints:

typedef struct fsid { int32_t val[2]; } fsid_t; /* filesystem id type */

which is ridiculous as the only place where this is actually useful is
when it is initialized (val[0] is set to the udev_t and val[1] to the
vfs type number) and this can easily be handled by a macro.  The other
significant use of fsid is to compare the fsids of two files to
determine whether they are on the same fs; that would be far easier to
do if fsid_t was defined as uint64_t.

Are there any objections to making fsid_t a uint64_t?

DES
-- 
Dag-Erling Smorgrav - des at ofug.org