From: "Måns Rullgård" <mru@inprovide.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Writing linux kernel specification
Date: Sat, 23 Oct 2004 16:01:05 +0200 [thread overview]
Message-ID: <yw1xu0slsfdq.fsf@inprovide.com> (raw)
In-Reply-To: 20041023133944.GA1204@beton.cybernet.src
Karel Kulhavy <clock@twibright.com> writes:
> Hello
>
> I am pondering on writing a Linux kernel specification, or rather
> compiling it from the various bits that are online.
>
> However I need to be sure that something like this is welcome at
> all:
>
> 1) Is Linux kernel meant to be a separate project or is it a subproject
> of GNU/Linux, Debian, Fedora, SuSE or whatever?
It seems pretty separate to me, although many kernel developers work
for redhat, suse or another distribution.
> 2) Is Linux kernel meant to be used by general public, or is it intended
> only for developpers of GNU/Linux, Debian, Fedora, SuSE etc.?
Read the GPL.
> 3) Is Linux kernel meant to have a specification and just a lack of time
> prevented it, or is Linux kernel meant to not have a specification?
POSIX?
> 4) If I produce a specification that is valid, correct and complete enough
> to be useful for general public, will it be included on the Linux kernel
> homepage http://www.kernel.org under a link "Linux kernel official
> specification" upon my request?
>
> Cl<
--
Måns Rullgård
mru@inprovide.com
next prev parent reply other threads:[~2004-10-23 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 13:39 Writing linux kernel specification Karel Kulhavy
2004-10-23 13:54 ` Lars Marowsky-Bree
2004-10-23 14:01 ` Måns Rullgård [this message]
2004-10-23 15:20 ` Rik van Riel
2004-10-23 23:10 ` Peter Williams
[not found] <Pine.LNX.4.44.0410231118570.25612-100000@chimarrao.boston.redhat.com.suse.lists.linux.kernel>
[not found] ` <417AE4EA.6070107@bigpond.net.au.suse.lists.linux.kernel>
2004-10-23 23:56 ` Andi Kleen
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=yw1xu0slsfdq.fsf@inprovide.com \
--to=mru@inprovide.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.