Skip to contentSkip to conversation

Updating LDD3

DISCUSSION Liam Ryan 4 participants 9 messages Oct 24, 2017 – Oct 25, 2017

lore
Share & tools
lore

Liam Ryan

author
#0 lore raw

I'm currently working through the Linux Device Drivers 3rd edition
(https://lwn.net/Kernel/LDD3/) and much of the code is outdated.

Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x

I'm wondering about the Creative Commons license on the LDD3 book. I believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?

Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.

Thanks,
Liam

#1 lore raw

Hello Ryan,

24.10.2017, 13:58, "Liam Ryan" <[email protected]>:

Quoted 7 lines

I'm currently working through the Linux Device Drivers 3rd edition
(https://lwn.net/Kernel/LDD3/) and much of the code is outdated.

Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x

I'm wondering about the Creative Commons license on the LDD3 book. I believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?

I think you can update and re-publish the example code and don't break the original comment lines. At least I think this.

Quoted 6 lines

Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.

Thanks,
Liam

Regards

Ozgur

#2 lore raw

There is a repo at github with all the samples don't?

Quoted 26 lines · Ozgur

Hello Ryan,

24.10.2017, 13:58, "Liam Ryan" <[email protected]>:

Quoted 7 lines

I'm currently working through the Linux Device Drivers 3rd edition
(https://lwn.net/Kernel/LDD3/) and much of the code is outdated.

Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x

I'm wondering about the Creative Commons license on the LDD3 book. I

believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?

I think you can update and re-publish the example code and don't break the original comment lines.
At least I think this.

Quoted 6 lines

Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.

Thanks,
Liam

Quoted 9 lines

Regards

Ozgur

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171024/2f4bd8c3/attachment.html

#4 lore raw

Here it is https://github.com/martinezjavier/ldd3

Regards

Quoted 41 lines · Ozgur

Hello Daniel,

24.10.2017, 14:50, "Daniel." <[email protected]>:

There is a repo at github with all the samples don't?

I think that no, I not seen before on github.

Regards

Ozgur

On Oct 24, 2017 9:06 AM, "Ozgur" <[email protected]> wrote:

Hello Ryan,

24.10.2017, 13:58, "Liam Ryan" <[email protected]>:

Quoted 7 lines

I'm currently working through the Linux Device Drivers 3rd edition
(https://lwn.net/Kernel/LDD3/) and much of the code is outdated.

Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x

I'm wondering about the Creative Commons license on the LDD3 book. I

believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?

I think you can update and re-publish the example code and don't break the original comment lines.
At least I think this.

Quoted 4 lines

Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.

Quoted 8 lines
Quoted 2 lines

Thanks,
Liam

Regards

Ozgur

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171024/3a5ae8da/attachment.html

#6 lore raw

You're welcome!

Quoted 60 lines · Ozgur

Hello,

24.10.2017, 15:31, "Daniel." <[email protected]>:

Here it is https://github.com/martinezjavier/ldd3

Regards

oh, it's very good, nice.
Thank you

Ozgur

On Oct 24, 2017 9:58 AM, "Ozgur" <[email protected]> wrote:

Hello Daniel,

24.10.2017, 14:50, "Daniel." <[email protected]>:

There is a repo at github with all the samples don't?

I think that no, I not seen before on github.

Regards

Ozgur

On Oct 24, 2017 9:06 AM, "Ozgur" <[email protected]> wrote:

Hello Ryan,

24.10.2017, 13:58, "Liam Ryan" <[email protected]>:

Quoted 7 lines

I'm currently working through the Linux Device Drivers 3rd edition
(https://lwn.net/Kernel/LDD3/) and much of the code is outdated.

Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x

I'm wondering about the Creative Commons license on the LDD3 book. I

believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?

I think you can update and re-publish the example code and don't break the original comment lines.
At least I think this.

Quoted 4 lines

Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.

Quoted 8 lines
Quoted 2 lines

Thanks,
Liam

Regards

Ozgur

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20171024/d24bd48d/attachment.html

author
#7 lore raw
Quoted 10 lines · Daniel.

You're welcome!

Quoted 6 lines · Ozgur

Hello,

24.10.2017, 15:31, "Daniel." <[email protected]>:

Here it is https://github.com/martinezjavier/ldd3

Thanks I had found this repo which is a great reference for when I get
stuck in my own attempt to update the old code, however I believe this repo is also outdated. For instance it calls aio_complete on line 405 of main.c of scullc which I found has since been removed ( or I made a huge error :) ).

Leaving that aside I'm referring to updating the book itself rather than the code as the text makes reference to the code as written in 2005.

I'll ask the question on the debian-legal list as recommended, I think the threads diverged at some point.

Regards,
Liam

Quoted 67 lines
Quoted 54 lines

Regards

oh, it's very good, nice.
Thank you

Ozgur

On Oct 24, 2017 9:58 AM, "Ozgur" <[email protected]> wrote:

Hello Daniel,

24.10.2017, 14:50, "Daniel." <[email protected]>:

There is a repo at github with all the samples don't?

I think that no, I not seen before on github.

Regards

Ozgur

On Oct 24, 2017 9:06 AM, "Ozgur" <[email protected]> wrote:

Hello Ryan,

24.10.2017, 13:58, "Liam Ryan" <[email protected]>:

Quoted 7 lines

I'm currently working through the Linux Device Drivers 3rd edition
(https://lwn.net/Kernel/LDD3/) and much of the code is outdated.

Right now I'm going through chapter 3 and rewriting the scull.c sample code so that it will compile with 4.14.x

I'm wondering about the Creative Commons license on the LDD3 book. I

believe I would be able to annotate or alter the pdf files and re-publish them once I respect the license, however I'm wondering if this would be considered bad form? I assume there's a reason somebody else has not done this to date?

I think you can update and re-publish the example code and don't break the original comment lines.
At least I think this.

Quoted 4 lines

Obviously as a kernel newbie I'm not best positioned to do this work but I'm happy to make a start and publish to a wiki or similar in a few months once I've gone through everything.

Quoted 8 lines
Quoted 2 lines

Thanks,
Liam

Regards

Ozgur

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

#8 lore raw
Quoted 6 lines · Liam Ryan
Quoted 5 lines · Daniel.

You're welcome!

Quoted 1 line · Ozgur
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines

Hello,

24.10.2017, 15:31, "Daniel." <[email protected]>:

Here it is https://github.com/martinezjavier/ldd3

Thanks I had found this repo which is a great reference for when I get
stuck in my own attempt to update the old code, however I believe this repo is also outdated. For instance it calls aio_complete on line 405 of main.c of scullc which I found has since been removed ( or I made a huge error :) ).

This is the repo I worked off of

https://github.com/duxing2007/ldd3-examples-3.x

Quoted 1 line

Leaving that aside I'm referring to updating the book itself rather than the code as the text makes reference to the code as written in 2005.

Isn't that the same thing? You need updated code to update the book. Not to throw water on your enthusiasm but that book is amazingly well written, there are [throw away] comments in that book that have taught me loads about subtle concepts of kernel development.

I would be very hesitant removing any text from that book if one is not _very_ experienced. There is a wealth of knowledge in it and the few functions that are out of date do little to reduce it's educational value IMO.

Sure, it would be nice to have a few of the newer kernel features included but again this is not a job for just anyone. Those guys that wrote that book are seriously experienced.

Hope this helps,
Tobin.