From: Indrek Kruusa <indrek.kruusa@tuleriit.ee>
To: linux-kernel@vger.kernel.org
Subject: Question: advancements in proven concepts
Date: Sun, 02 Jan 2005 14:07:11 +0200 [thread overview]
Message-ID: <41D7E3EF.8000700@tuleriit.ee> (raw)
Hi and HNY!
I have one question about the "existence of collected ideas".
It is obvious that by using only proven concepts and standards have led
the Linux on the top of the world. But it is hard to believe that you
guys are absolutely agree with every agreement or standard ever created.
Is there a place for linux kernel community where ideas about the needed
advancements in those proven concepts can be presented to the world in
nice, structured and easily readable way? Or is this the professional
property of the kernel programmer to not ask a question about the
"healtiness" of some POSIX thing or not to give a hint for better
hardware implementation? Well, this last question is a little nagging.
For example I found this message yesterday:
Re: ptrace single-stepping change breaks Wine
From: Linus Torvalds
Date: Sat Jan 01 2005 - 17:15:54 EST
...
<snip>
It would have been nice if Intel had added a
"single-step" bit to %db7, and then just or'ed in the values of TF and the
new flag when deciding to single-step.
<snip>
...
Maybe this idea have been said out just for fun (btw, I have one book
which have similar title :) ) but why not collect such things together?
For sure there are ideas about every tool, technology or standard which
is used for kernel development or with which the kernel have to cope
with. Is it possible to build up such a knowledge base or is there
similar already?
thanks,
Indrek
next reply other threads:[~2005-01-02 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 12:07 Indrek Kruusa [this message]
2005-01-02 13:03 ` Question: advancements in proven concepts bert hubert
2005-01-02 17:42 ` Indrek Kruusa
2005-01-02 13:13 ` Christoph Anton Mitterer
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=41D7E3EF.8000700@tuleriit.ee \
--to=indrek.kruusa@tuleriit.ee \
--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