[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Newbie compat_linux question
- To: <firstname.lastname@example.org>
- Subject: Re: Newbie compat_linux question
- From: Peter Fairbrother <email@example.com>
- Date: Wed, 12 Jun 2002 07:04:16 +0100
- User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630)
> Ted U wrote:
> binary compat for kernel is about the last feature likely to be added to
> openbsd. the benefit/effort ratio is very low, and it's not likely anyone
> who could do such a thing would want to. so i think the answer is no.
I wasn't asking, but if anyone cares to... I just wondered if anyone could
think of a solution to the wider problem before I rewrite a year's work in
an unfamiliar OS.
> also, many of the binary drivers for linux aren't freely distributable to
> my knowledge, so you can't do that anyway. just something to think about.
> besides, in a trusted OS like you're planning, relying on other vendors'
> unaudited code is a bad idea.
I haven't come across any redistribution problems yet, and I'd probably
ignore them anyway - this is the UK, the relevant laws are different, eg for
compatibility purposes like writing a driver you can decompile driver code
and no-one and no clause in a contract can stop you from doing so. You can
use the ideas behind it to write your own driver, no software patents, "fair
use" under UK copyright law. I don't think you could charge for it, but
m-o-o-t will be free, "gratuit" as well as as "libre" as I can get it.
As far as a trusted OS goes, I can do red/black separation between the
OpenBSD and (hypothetical) Linux bits. Wouldn't matter that much even if the
Linux binaries were trojaned, and they're also unlikely to be trojaned in a
useful way anyway. Besides, only a minority of the available drivers have
-- Peter Fairbrother