Date: Wed, 07 Dec 2005 15:12:30 -0700 From: Scott Long <scottl@samsco.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, Doug Ambrisko <ambrisko@ambrisko.com>, David Xu <davidxu@FreeBSD.org>, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys signal.h Message-ID: <43975E4E.4060103@samsco.org> In-Reply-To: <200512071703.09422.jhb@freebsd.org> References: <200512072116.jB7LGtFG075170@ambrisko.com> <200512071703.09422.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Wednesday 07 December 2005 04:16 pm, Doug Ambrisko wrote: > >>David Xu writes: >>| David Xu wrote: >>| > davidxu 2005-12-06 06:02:35 UTC >>| > >>| > FreeBSD src repository >>| > >>| > Modified files: >>| > sys/sys signal.h >>| > Log: >>| > o Add some pad fields into struct sigevent for future extension. >>| > (suggested by alfred@) >>| > o Reuse si_band field in struct __siginfo, add a mqd member which >>| > will be used by mqueue. >>| > o Add code SI_KERNEL to indicate a signal is queued by kernel. >>| > >>| > Revision Changes Path >>| > 1.54 +14 -2 src/sys/sys/signal.h >>| >>| You have to rebuild world and your program if you are using aio, >>| signal queue, timer, or mqueue which are new to many FreeBSD >>| people. ;-) >> >>Does this include people running FreeBSD 4.X compiled programs on -current? > > > Even 6.x programs that use aio would be affected if 4.x ones were affected. I > think aio is the only thing 6.x and earlier could be using though. > So will there be some sort of compatibility shims? I bet that there will still be a lot of 4.x binaries being run on 7.0 systems in the future, just like 2.2.8 binaries were being run for years after 3.x and 4.x came out. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43975E4E.4060103>