From owner-freebsd-arch Wed Feb 7 10:33:19 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id DBF3B37B491; Wed, 7 Feb 2001 10:32:59 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f17IX5H02713; Wed, 7 Feb 2001 19:33:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Brian F. Feldman" Cc: arch@FreeBSD.ORG Subject: Re: xucred introduction In-Reply-To: Your message of "Wed, 07 Feb 2001 13:28:21 EST." <200102071828.f17ISLr17637@green.dyndns.org> Date: Wed, 07 Feb 2001 19:33:05 +0100 Message-ID: <2711.981570785@critter> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102071828.f17ISLr17637@green.dyndns.org>, "Brian F. Feldman" wri tes: >The only question is whether or not to add some spare fields to >xucred now in case we /do/ want to expand it in the future, and also whether >it's appropriate to make some of the field type changes (for example, >sockaddr length type -> u_char, since that _IS_ what is defined by the >sockaddr interface). Have you already put a version number in it ? Otherwise please do so. That is the best way to ensure that we don't get too many problems in the future. I think in general all structures shared between the kernel and userland should be equipped with a version number as the first element. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message