"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 [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Portable way to compare struct stat's? Kelly Yancey
- Re: Portable way to compare struct stat's? Wes Peters
- Re: Portable way to compare struct stat's? Robert Watson
- Re: Portable way to compare struct stat's? John Polstra
- Re: Portable way to compare struct stat... Garance A Drosihn
- Re: Portable way to compare struct... John Polstra
- Re: Portable way to compare st... Daniel C. Sobral
- Re: Portable way to compar... Wes Peters
- Re: Portable way to compar... Daniel C. Sobral
- Re: Portable way to compar... Daniel C. Sobral
- Re: Portable way to compar... Wes Peters
- Re: Portable way to compar... Robert Watson
- Re: Portable way to compar... Assar Westerlund
- Re: Portable way to compar... Wes Peters
- Re: Portable way to compar... Assar Westerlund
- Re: Portable way to compar... Garance A Drosihn
- Re: Portable way to compar... Assar Westerlund
- Re: Portable way to compar... Wes Peters
- Re: Portable way to compar... Assar Westerlund
- Re: Portable way to compare st... Garance A Drosihn
- Re: Portable way to compare struct stat's? Kelly Yancey