From: retu <retu834@yahoo.com>
To: Valdis.Kletnieks@vt.edu
Cc: Jamie Lokier <jamie@shareable.org>, Kenn Humborg <kenn@linux.ie>,
linux-kernel@vger.kernel.org
Subject: Re: 2.7 thoughts: common well-architected object model
Date: Sun, 12 Oct 2003 09:51:19 -0700 (PDT) [thread overview]
Message-ID: <20031012165119.17264.qmail@web13004.mail.yahoo.com> (raw)
In-Reply-To: <200310121644.h9CGiUeb011798@turing-police.cc.vt.edu>
nobody says that it belongs into the kernel rather
designed by core=kernel folks core-up, that is e.g.
not being a derivative of a set of all-encompassing
classes developed for an application.
I think the issue is serious and brushing it aside as
being non-kernel at first will come back biting.
What's going on could be described as being cornered.
--- Valdis.Kletnieks@vt.edu wrote:
> On Sun, 12 Oct 2003 09:04:19 PDT, retu said:
>
> > What's the solution out of this - a clean, open
> object
> > model designed by the core folks, extensible and
> free
> > of licensing issues - and that in the next months.
>
>
> The point that seems to be continually missed is
> that although
> it may be a *fine* concept for userspace, it doesn't
> belong in the
> kernel. There's a syscall barrier for multiple
> reasons, some technical
> and some political/legal.
>
> If anything, we collectively DON'T want to go there
> because a clever lawyer
> could argue that doing a "all the way from kernel to
> userspace" object-oriented
> scheme would make essentially all userspace code a
> derived work, since it would
> be so tightly entwined with the kernel
> implementation (basically, you'd be
> subjecting all of userspace to the same "derived
> work" limbo that closed-source
> kernel modules currently live in). This could
> render totally irrelevant this
> text from /usr/src/linux/COPYING:
>
> NOTE! This copyright does *not* cover user
> programs that use kernel
> services by normal system calls - this is merely
> considered normal use
> of the kernel, and does *not* fall under the
> heading of "derived work".
> Also note that the GPL below is copyrighted by the
> Free Software
> Foundation, but the instance of code that it refers
> to (the Linux
> kernel) is copyrighted by me and others who
> actually wrote it.
>
> Yes, this would mean that userspace would be GPL'ed
> as well, and
> you'll never see Oracle on a Linux box again for a
> VERY long time....
>
> ATTACHMENT part 2 application/pgp-signature
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
next prev parent reply other threads:[~2003-10-12 16:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 4:45 asdfd esadd
2003-10-11 14:30 ` Valdis.Kletnieks
2003-10-11 16:06 ` asdfd esadd
2003-10-11 16:48 ` Valdis.Kletnieks
2003-10-11 17:13 ` asdfd esadd
2003-10-11 17:38 ` Valdis.Kletnieks
2003-10-11 17:56 ` asdfd esadd
2003-10-11 18:20 ` Mark Hahn
2003-10-11 18:13 ` Zwane Mwaikambo
2003-10-11 23:33 ` J.A. Magallon
2003-10-11 17:00 ` Scott Robert Ladd
2003-10-11 17:57 ` Kenn Humborg
2003-10-11 18:34 ` asdfd esadd
2003-10-11 18:46 ` Valdis.Kletnieks
2003-10-11 19:01 ` Kenn Humborg
2003-10-11 19:11 ` retu
2003-10-11 19:25 ` viro
2003-10-12 11:59 ` Jamie Lokier
2003-10-12 16:04 ` retu
2003-10-12 16:44 ` Valdis.Kletnieks
2003-10-12 16:51 ` retu [this message]
2003-10-12 17:50 ` viro
2003-10-12 21:52 ` Jamie Lokier
2003-10-12 20:21 ` Rik van Riel
2003-10-13 20:21 ` James Antill
2003-10-14 5:01 ` retu
2003-10-14 6:00 ` Nick Piggin
2003-10-14 5:31 ` retu
2003-10-14 6:05 ` Tim Hockin
2003-10-14 6:46 ` viro
[not found] <Ft4B.3ML.3@gated-at.bofh.it>
[not found] ` <FutO.5TB.29@gated-at.bofh.it>
2003-10-11 17:03 ` Ihar 'Philips' Filipau
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=20031012165119.17264.qmail@web13004.mail.yahoo.com \
--to=retu834@yahoo.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jamie@shareable.org \
--cc=kenn@linux.ie \
--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®