All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Rik van Riel <riel@redhat.com>
Cc: Karel Kulhavy <clock@twibright.com>, linux-kernel@vger.kernel.org
Subject: Re: Writing linux kernel specification
Date: Sun, 24 Oct 2004 09:10:34 +1000	[thread overview]
Message-ID: <417AE4EA.6070107@bigpond.net.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0410231118570.25612-100000@chimarrao.boston.redhat.com>

Rik van Riel wrote:
> On Sat, 23 Oct 2004, Karel Kulhavy wrote:
> 
> 
>>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?
>>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?
> 
> 
> You can write a specification, but I can guarantee you that
> it will be out of date the moment you run your spell checker
> on it.
> 
> Linux kernel development continues at a very high speed, and
> things inside the kernel change all the time.  The only thing
> that's stable is the user space ABI (the system calls), since
> the behaviour of those (mostly) follows POSIX and the Single
> Unix Standard (SUS).

Maybe that (the mostly bit) is what needs to be documented/specified 
i.e. any differences between the Linux user space ABI and those two 
standards.  Surely that difference is reasonably stable and having it 
documented in a single place would be useful.

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

  reply	other threads:[~2004-10-23 23: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
2004-10-23 15:20 ` Rik van Riel
2004-10-23 23:10   ` Peter Williams [this message]
     [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=417AE4EA.6070107@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=clock@twibright.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    /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.