mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tony 'Nicoya' Mantler" <nicoya@apia.dhs.org>
To: Jamie Lokier <jamie@shareable.org>, linux-kernel@vger.kernel.org
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: Tue, 06 May 2003 20:17:56 -0500	[thread overview]
Message-ID: <nicoya-B9CA30.20175606052003@news.pp.shawcable.net> (raw)
In-Reply-To: <20030506220018$5b96@gated-at.bofh.it>

In article <20030506220018$5b96@gated-at.bofh.it>,
 Jamie Lokier <jamie@shareable.org> wrote:

: I do not see any practical alternative way to create a new kind of
: operating system kernel that is compatible with the wide range of PC
: hardware, other than:
: 
:   (a) read lots of open source code and then write drivers,
:       filesystems etc. from what is learned, or
:   (b) just use the available code with appropriate wrapping.
: 
: Both are lots of work.  But isn't (b) going to be less work?  I'm not
: sure.

If your interest is in creating a new and unique OS, you'll likely find that it 
becomes a great deal of work to try to glue the linux drivers into it.

I would imagine in the majority of cases you'd either have to change the driver 
code considerably to fit the subtleties of <newos>, or change the <newos> code 
considerably to fit the subtleties of linux.

When creating a new system, the last thing you want to have to do is carry 
around a bunch of extra baggage that you really don't need.

Anyways, this is 2003, aren't operating systems supposed to be boring by now? 
And where's my flying car damnit. ;)


To answer your question more directly, I think most developers would agree that 
the spirit of the GPL is "give as you take". If just releasing back the source 
to the modified drivers - completely useless without your new closed kernel - 
doesn't feel a whole lot like "giving", then you're probably not doing enough to 
keep people happy.


Cheers - Tony 'Nicoya' Mantler :)

-- 
Tony "Nicoya" Mantler - Renaissance Nerd Extraordinaire - nicoya@apia.dhs.org
Winnipeg, Manitoba, Canada           --           http://nicoya.feline.pp.se/

       reply	other threads:[~2003-05-07  1:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030506165014$3d57@gated-at.bofh.it>
     [not found] ` <20030506193019$0d29@gated-at.bofh.it>
     [not found]   ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07  1:17     ` Tony 'Nicoya' Mantler [this message]
2003-05-13  9:08 Dean McEwan
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09  1:23 Jean Tourrilhes
     [not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman
2003-05-06 16:42 Jamie Lokier
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54   ` Jamie Lokier
2003-05-06 19:28     ` Jean-Marc Lienher
2003-05-06 19:53     ` Alan Cox
2003-05-06 22:31       ` Jamie Lokier
2003-05-06 21:38         ` Alan Cox
2003-05-08 21:36     ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55   ` Jamie Lokier
2003-05-06 22:21     ` David Schwartz
2003-05-07  8:21     ` Eric W. Biederman
2003-05-07 14:25       ` Valdis.Kletnieks
2003-05-07 14:31         ` Jamie Lokier
2003-05-07 15:50           ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18   ` Jamie Lokier
2003-05-06 21:31     ` Alan Cox
2003-05-06 22:48       ` Jamie Lokier
2003-05-07 12:20         ` Alan Cox
2003-05-07 14:26           ` Jamie Lokier
2003-05-07 15:18             ` Pavel Machek
2003-05-08 11:11 ` Krzysztof Halasa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nicoya-B9CA30.20175606052003@news.pp.shawcable.net \
    --to=nicoya@apia.dhs.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®