From: spam@streefland.xs4all.nl (Dick Streefland)
To: linux-kernel@vger.kernel.org
Subject: Re: List of SCO files
Date: Sun, 16 Nov 2003 16:03:34 -0000 [thread overview]
Message-ID: <4f6a.3fb79fd6.49695@altium.nl> (raw)
In-Reply-To: 1068679942.3082.131.camel@mentor.gurulabs.com
Dax Kelson <dax@gurulabs.com> wrote:
| http://www.groklaw.net/article.php?story=2003111203544653
|
| "I used it for comparison to file listings of different kernel versions,
| and my conclusion is that this list is either based on 2.5.68 (released
| April 20, 2003) or on 2.5.69 (released May 5, 2003). Those are the only
| two versions that contain all of the listed files." -- Groklaw reader
| "Lev"
I think they used 2.5.69. Their list includes net/bridge/br_if.c, and
patch 2.5.69 adds code containing the word "rcu", which is probably
one of the keywords they searched for. The following script generates
a list very close to SCOs list:
#!/bin/sh
# to be run in the linux-2.5.69 kernel tree
(
find * -name '*.[ch]' |
egrep -v '^(drivers|sound)|(arch/|include/asm-)(sparc|alpha|parisc)' |
xargs egrep -iwl '(smp|numa|rcu)'
ls fs/jfs/*.[ch]
) |
sort -u
The only files not on SCOs list are:
arch/um/drivers/harddog_kern.c
arch/um/drivers/harddog_user.c
arch/um/drivers/mconsole_kern.c
include/asm-h8300/smplock.h
--
Dick Streefland //// De Bilt
dick.streefland@xs4all.nl (@ @) The Netherlands
------------------------------oOO--(_)--OOo------------------
prev parent reply other threads:[~2003-11-16 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 23:32 List of SCO files Dax Kelson
2003-11-13 2:49 ` Benjamin Herrenschmidt
2003-11-13 4:50 ` Steven Cole
2003-11-14 9:35 ` Jon Evans
2003-11-13 9:36 ` Geert Uytterhoeven
2003-11-13 15:19 ` Jes Sorensen
2003-11-13 15:26 ` Richard B. Johnson
2003-11-13 12:57 ` Rik van Riel
2003-11-16 16:03 ` Dick Streefland [this message]
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=4f6a.3fb79fd6.49695@altium.nl \
--to=spam@streefland.xs4all.nl \
--cc=dick.streefland@xs4all.nl \
--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