At Fri, 23 Jul 2004 16:28:56 +0200, Christoph Hellwig wrote: > On Fri, Jul 23, 2004 at 07:05:35PM +0900, GOTO Masanori wrote: > > I don't understand why you think it's bad idea. Until glibc included > > mqueue, it was existed as separated library. AFAIK, there is no > > application that use mqueue library in main. This means user links > > mqueue library with his application with his hand. > > glibc got mqueue support when the kernel got it. SLES9 and RHEL4 will > have it so applications will start to use it. But given glibc on sarge > is totally outdated anyway there will probably be little chance to run > recent 3rd-party binaries on sarge anyway.
POSIX message queue has been known since POSIX standardized them in 1996, but AFAIK there's no major 3rd-party binaries which use mqueue. If you know, please tell me, we enable mqueue at boot up time in default on 2.6 kernel after sarge. I agree with your argument about outdating glibc. Regarding both SLES9 and RHEL4, I think accelerating the release interval makes more sense. So I'm OK with Mattia's intension. Regards, -- gotom
