[EMAIL PROTECTED] wrote:
I'll respond in terms of U.S. law; if you want something else, please
mention it.
You might find a lot of useful information at
http://fairuse.stanford.edu/Copyright_and_Fair_Use_Overview/chapter9/index.html
http://www.usg.edu/admin/legal/copyright/#part3d3a
I'll respond in terms of U.S. law; if you want something else, please
mention it.
You might find a lot of useful information at
http://fairuse.stanford.edu/Copyright_and_Fair_Use_Overview/chapter9/index.html
http://www.usg.edu/admin/legal/copyright/#part3d3a
http://en.wikipedia.org/wiki/Fair_use
Charles Cazabon wrote:
Thomas Gleixner <[EMAIL PROTECTED]> wrote:
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
I am having some licensing questions. It would be
really great if you can clarify on them
1. For explaining the internals of a filesystem in
detail, I need to take their
Charles Cazabon wrote:
Thomas Gleixner [EMAIL PROTECTED] wrote:
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
I am having some licensing questions. It would be
really great if you can clarify on them
1. For explaining the internals of a filesystem in
detail, I need to take their
I'll respond in terms of U.S. law; if you want something else, please
mention it.
You might find a lot of useful information at
http://fairuse.stanford.edu/Copyright_and_Fair_Use_Overview/chapter9/index.html
http://www.usg.edu/admin/legal/copyright/#part3d3a
http://en.wikipedia.org/wiki/Fair_use
[EMAIL PROTECTED] wrote:
I'll respond in terms of U.S. law; if you want something else, please
mention it.
You might find a lot of useful information at
http://fairuse.stanford.edu/Copyright_and_Fair_Use_Overview/chapter9/index.html
http://www.usg.edu/admin/legal/copyright/#part3d3a
Followup to: <[EMAIL PROTECTED]>
By author:Charles Cazabon <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> I'm not sure that's the case. Inclusion of significant chunks of source code
> (not just a dozen lines or whatever) might bring the book into "derived work"
> territory, and
Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
> > I am having some licensing questions. It would be
> > really great if you can clarify on them
> >
> > 1. For explaining the internals of a filesystem in
> > detail, I need to take their code
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
> I am having some licensing questions. It would be
> really great if you can clarify on them
>
> 1. For explaining the internals of a filesystem in
> detail, I need to take their code from kernel sources
> 'as it is' in the book. Do I need to
On Wed, 2 Feb 2005, Frank klein wrote:
1. For explaining the internals of a filesystem in
detail, I need to take their code from kernel sources
'as it is' in the book. Do I need to take any
permissions from the owner/maintainer regarding this ?
Will it violate any license if reproduce the driver
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
> Hi,
> I have got an offer to write a book on Linux
> filesystems. In this I would like to cover existing
> filesystems like ext3, xfs etc. I would also cover
> embedded file systems such as jffs,ROMfs,cramsf etc.
>
> I am having some
Hi,
I have got an offer to write a book on Linux
filesystems. In this I would like to cover existing
filesystems like ext3, xfs etc. I would also cover
embedded file systems such as jffs,ROMfs,cramsf etc.
I am having some licensing questions. It would be
really great if you can clarify on them
Hi,
I have got an offer to write a book on Linux
filesystems. In this I would like to cover existing
filesystems like ext3, xfs etc. I would also cover
embedded file systems such as jffs,ROMfs,cramsf etc.
I am having some licensing questions. It would be
really great if you can clarify on them
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
Hi,
I have got an offer to write a book on Linux
filesystems. In this I would like to cover existing
filesystems like ext3, xfs etc. I would also cover
embedded file systems such as jffs,ROMfs,cramsf etc.
I am having some licensing
On Wed, 2 Feb 2005, Frank klein wrote:
1. For explaining the internals of a filesystem in
detail, I need to take their code from kernel sources
'as it is' in the book. Do I need to take any
permissions from the owner/maintainer regarding this ?
Will it violate any license if reproduce the driver
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
I am having some licensing questions. It would be
really great if you can clarify on them
1. For explaining the internals of a filesystem in
detail, I need to take their code from kernel sources
'as it is' in the book. Do I need to take
Thomas Gleixner [EMAIL PROTECTED] wrote:
On Wed, 2005-02-02 at 06:49 -0800, Frank klein wrote:
I am having some licensing questions. It would be
really great if you can clarify on them
1. For explaining the internals of a filesystem in
detail, I need to take their code from kernel
Followup to: [EMAIL PROTECTED]
By author:Charles Cazabon [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
I'm not sure that's the case. Inclusion of significant chunks of source code
(not just a dozen lines or whatever) might bring the book into derived work
territory, and your
18 matches
Mail list logo
