Date: Sat, 20 Nov 1999 20:21:40 -0700 From: Wes Peters <wes@softweyr.com> To: "Daniel C. Sobral" <dcs@newsguy.com> Cc: John Polstra <jdp@polstra.com>, Garance A Drosihn <drosih@rpi.edu>, hackers@FreeBSD.ORG Subject: Re: Portable way to compare struct stat's? Message-ID: <38376544.96B017E9@softweyr.com> References: <XFMail.991118185611.jdp@polstra.com> <3836DF98.9A84EC44@newsguy.com> <3836F873.D3B989FE@softweyr.com> <3836FF7C.2D8236AE@newsguy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Daniel C. Sobral" wrote:
>
> Wes Peters wrote:
> >
> > It's not broken in this case. 2^16 (st_dev) is certainly enough to uniquely
> > indentify all mounted filesystems, and 2^32 is (by definition) enough to
> > uniquely indentify each of the files on a filesystem. Discussions (with
> > strong, valid reasons) about expanding the size of ino_t should be carried
> > out on -arch.
>
> Just to expand a little bit more, some distributed filesystems *do
> not* have a unique identifier like the inode.
So then the FreeBSD client software should create one? Do they just assign
a random number as the st_ino when stat'ing the file?
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38376544.96B017E9>