Re: Observation re third parties supporting Debian kernels
- To: debian-kernel@lists.debian.org
- Subject: Re: Observation re third parties supporting Debian kernels
- From: Sven Luther <sven.luther@wanadoo.fr>
- Date: Sat, 24 Sep 2005 12:58:39 +0200
- Message-id: <20050924105839.GA3880@localhost.localdomain>
- In-reply-to: <20050924090257.GA10444@daedalus.andrew.net.au>
- References: <20050924090257.GA10444@daedalus.andrew.net.au>
On Sat, Sep 24, 2005 at 07:02:57PM +1000, Andrew Pollock wrote:
> Hi,
>
> I attended a product briefing at Computer Associates on Thursday, and one of
> the products that was discussed more than demonstrated was something called
> eTrust Access Control[1], which, from my interpretation, sounds like it
> achieves something similar to what SE Linux probably does. That's not really
> the point of this email though.
>
> I asked one of the engineering types about their Linux support for this
> product during one of the breaks. It can enforce a policy on Windows, a few
> commercial Unix variants, and on "Linux". When I pressed the engineer on
> what Linux distros were supported, it was just RedHat Enterprise Linux.
>
> He did mention that they'd looked into supporting Debian, but slammed the
> lid back down on it after they had discovered (and I'm paraphrasing)
> "multiple kernels with the same version number".
Seems like uninformed non-sense, but then maybe due to the previous messy
situation. I think these guys are lying when speakign about linux support
anyway, and only mean linux/x86 anyway.
We provide the linux-headers apckage to make it as easy to build external
modules against those kernels as possible, so it should be no real problem.
I agree that the pre-2.6.12 situation was messy, but the new common
infrastructure should be no major problem for those guys.
Friendly,
Svne Luther
Reply to: