From owner-freebsd-current Mon Nov 8 11:25:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 78F7514F58 for ; Mon, 8 Nov 1999 11:25:43 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11kuQd-000KyQ-00; Mon, 8 Nov 1999 19:26:11 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id UAA11970; Mon, 8 Nov 1999 20:25:33 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <382723AD.DCD6719A@scc.nl> Date: Mon, 08 Nov 1999 20:25:33 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Steve Price Cc: freebsd-current@freebsd.org Subject: Re: new sigaction struct References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Price wrote: > Just curious as to what the motivation for re-ordering the > sa_flags and sa_mask members in sigaction were? The manpage > still describes the old order BTW. If sigset_t is to be changed again, then having it the last field in the structure leaves us some room to avoid introducing new syscalls all over again and handle the change with the current structure and syscalls. > My Alpha box has been limping through a package build and I've > noticed a number of ports that seem to be falling over for > signal-related changes. This should not be caused be the ordering of the fields in struct sigaction. > One in particular would be the rawio > port which expects sa_mask to be before sa_flags in struct > sigaction. Silly... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message