Hi!
The Minix file system uses 16 bit UIDs, which creates an obvious problem
for us. Linux handles this by using a special "overflow UID":
#define fs_high2lowuid(uid) ((uid) > 65535 ? (uid16_t)fs_overflowuid : \
(uid16_t)(uid))
This overflow UID can be set with sysctl(8) and defaults to the value
65534 (not 65535, as one might expect). It seems to be good enough for
Linux, but I'm not sure if it is good enough for us, so how should we
handle this situation? Storing the UID `(ushort) ~0' in the i_uid field
of the inode and using some trick (which shouldn't break anything, of
course) to store the real UID elsewhere?
Cheers,
GNU/Wolfgang
--
Wolfgang Jährling <[EMAIL PROTECTED]> \\ http://stdio.cjb.net/
Debian GNU/Hurd user && Debian GNU/Linux user \\ http://www.gnu.org/
The Hurd Hacking Guide: http://www.gnu.org/software/hurd/hacking-guide/
["We're way ahead of you here. The Hurd has always been on the ]
[ cutting edge of not being good for anything." -- Roland McGrath ]
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
