From: Jamie Lokier <jamie@shareable.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Bryan Henderson <hbryan@us.ibm.com>, Greg KH <greg@kroah.com>,
Jan Hudec <bulb@ucw.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: buffer cache
Date: Tue, 16 Sep 2003 11:18:13 +0100 [thread overview]
Message-ID: <20030916101813.GA26576@mail.jlokier.co.uk> (raw)
In-Reply-To: <1063689231.788.63.camel@imladris.demon.co.uk>
David Woodhouse wrote:
> I accept the idea. I also accept the idea that said module writer can
> also write all his own include files _too_, and avoid even having to
> have a kernel tree around at all.
I don't think you can entertain that idea, because...
> I think he'd have to be on crack, but I do accept that he _can_ do that.
...to write his own files which allow modules to work with the kernel
would require duplicating the existing include files in great detail -
perhaps enough to count as a derived work.
In other words, it's widely believed that he _can't_ do that.
Fwiw I don't have any problem with this.
-- Jamie
ps. It may be possible, after all people have written binary modules
for other operating systems purely by reverse engineering the
operating system, starting with no source. Perhaps that's what
you're advocating ;)
next prev parent reply other threads:[~2003-09-16 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 8:51 buffer cache vadiraj c s
2003-09-13 10:27 ` Jan Hudec
2003-09-13 13:14 ` Matthew Wilcox
2003-09-13 17:25 ` Bryan Henderson
2003-09-13 17:28 ` Jan Hudec
2003-09-14 9:32 ` David Woodhouse
2003-09-14 10:03 ` Jan Hudec
2003-09-14 10:37 ` David Woodhouse
2003-09-14 11:19 ` Jan Hudec
2003-09-15 16:18 ` Bryan Henderson
2003-09-15 16:35 ` Greg KH
2003-09-15 22:41 ` Bryan Henderson
2003-09-16 5:13 ` David Woodhouse
2003-09-16 10:18 ` Jamie Lokier [this message]
2003-09-16 12:16 ` David Woodhouse
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=20030916101813.GA26576@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=bulb@ucw.cz \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@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