Date: Wed, 16 Oct 2002 23:07:09 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: "Danny J. Zerkel" <dzerkel@columbus.rr.com> Cc: Robert Watson <rwatson@FreeBSD.ORG>, Maxim Sobolev <sobomax@FreeBSD.ORG>, "Vladimir B. Grebenschikov,Moscow,408-7227,123-4567,Some-info" <vova@express.ru>, freebsd-arch@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: short uid/gid Message-ID: <3DAE538D.848550B9@mindspring.com> References: <Pine.NEB.3.96L.1021016125106.24763B-100000@fledge.watson.org> <200210162344.22969.dzerkel@columbus.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Danny J. Zerkel" wrote: > To quote the POSIX standard: > > The ipc_perm structure shall contain the following members: > > uid_t uid Owner's user ID. > gid_t gid Owner's group ID. > uid_t cuid Creator's user ID. > gid_t cgid Creator's group ID. > mode_t mode Read/write permission. > > I don't think size is an issue. At least not within a given machine. > I think OpenBSD and NetBSD have already taken the correct path. > We just need to have a compatibility interface (automatic extra > flag: pretty cheap; or alternate syscalls: probably a waste). If our only goal were POSIX compliance, you are correct. Since we also want to maintain binary compatability with third party software, that's not enough. You also have to look at interfaces published in FreeBSD documentation, or by reference in FreeBSD or POSIX documentation. Such as the contents of the ipc_perm structure, as declared, rather than by way of an enumeration of required fields. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DAE538D.848550B9>