Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!agate!labrea!rutgers!bellcore!faline!thumper!ulysses!andante!alice!andrew
From: andrew@alice.UUCP (Andrew Hume)
Newsgroups: comp.unix.wizards
Subject: Portable Inode Descriptions
Summary: I want some outliers
Message-ID: <8773@alice.UUCP>
Date: 16 Jan 89 04:06:36 GMT
Organization: AT&T Bell Laboratories, Murray Hill NJ
Lines: 25



	I have (or more accurately want) a portable description
of an inode. assuming we have solved the byte-ordering problem,
the only question is how many bits do we need for each field?
I would like to cover all extent unix implementations but will
pragmatically decline really deviant cases. the fields(sizes in bits) are

dev(32), ino(32), mode(32), nlink(32), uid(32), gid(32),
size(64), [amc]time(64).

the questions are
	1) do you know of a unix where these sizes are insufficent?
	2) do you know of a unix where times are more than 32 bits
or where file sizes are bigger than 32 bits? cray unix is the only
one i know of for the latter case.

	i guess (near) future unixes also count; e.g. sun may
soon give 32 more bits of time resolution (say in usec units).

	e-mail responses preferred but everyone enjoys a giggle
at weird unixes.

research!andrew
andrew@research.att.com