'Linux IP Stacks Commentary' Book Tries Free Online Updates (satchell.net) 13
Recently the authors of Elements of Publishing shared an update. "After ten years in print, our publisher decided against further printings and has reverted the rights to us. We are publishing Elements of Programming in two forms: a free PDF and a no-markup paperback."
And that's not the only old book that's getting a new life on the web...
22 years ago, long-time Slashdot reader Stephen T. Satchell (satch89450) co-authored Linux IP Stacks Commentary, a book commenting the TCP/IP code in Linux kernel 2.0.34. ("Old-timers will remember the Lion's Unix Commentary, the book published by University xerographic copies on the sly. Same sort of thing.") But the print edition struggled to update as frequently as the Linux kernel itself, and Satchell wrote a Slashdot post exploring ways to fund a possible update.
At the time Slashdot's editors noted that "One of the largest complaints about Linux is that there is a lack of high-profile documentation. It would be sad if this publication were not made simply because of the lack of funds (which some people would see as a lack of interest) necessary to complete it." But that's how things seemed to end up — until Satchell suddenly reappeared to share this update from 2022: When I was released from my last job, I tried retirement. Wasn't for me. I started going crazy with nothing significant to do. So, going through old hard drives (that's another story), I found the original manuscript files, plus the page proof files, for that two-decade-old book. Aha! Maybe it's time for an update. But how to keep it fresh, as Torvalds continues to release new updates of the Linux kernel?
Publish it on the Web. Carefully.
After four months (and three job interviews) I have the beginnings of the second edition up and available for reading. At the moment it's an updated, corrected, and expanded version of the "gray matter", the exposition portions of the first edition....
The URL for the alpha-beta version of this Web book is satchell.net/ipstacks for your reading pleasure. The companion e-mail address is up and running for you to provide feedback. There is no paywall.
But there's also an ingenious solution to the problem of updating the text as the code of the kernel keeps changing: Thanks to the work of Professor Donald Knuth (thank you!) on his WEB and CWEB programming languages, I have made modifications, to devise a method for integrating code from the GIT repository of the Linux kernel without making any modifications (let alone submissions) to said kernel code. The proposed method is described in the About section of the Web book. I have scaffolded the process and it works. But that's not the hard part.
The hard part is to write the commentary itself, and crib some kind of Markup language to make the commentary publishing quality. The programs I write will integrate the kernel code with the commentary verbiage into a set of Web pages. Or two slightly different sets of web pages, if I want to support a mobile-friendly version of the commentary.
Another reason for making it a web book is that I can write it and publish it as it comes out of my virtual typewriter. No hard deadlines. No waiting for the printers. And while this can save trees, that's not my intent. The back-of-the-napkin schedule calls for me to to finish the expository text in September, start the Python coding for generating commentary pages at the same time, and start the writing the commentary on the Internet Control Message Protocol in October. By then, Linus should have version 6.0.0 of the Linux kernel released.
I really, really, really don't want to charge readers to view the web book. Especially as it's still in the virtual typewriter. There isn't any commentary (yet). One thing I have done is to make it as mobile-friendly as I can, because I suspect the target audience will want to read this on a smartphone or tablet, and not be forced to resort to a large-screen laptop or desktop. Also, the graphics are lightweight to minimize the cost for people who pay by the kilopacket. (Does anywhere in the world still do this? Inquiring minds want to know.)
I host this web site on a Protectli appliance in my apartment, so I don't have that continuing expense. The power draw is around 20 watts. My network connection is AT&T fiber — and if it becomes popular I can always upgrade the upstream speed.
The thing is, the cat needs his kibble. I still want to know if there is a source of funding available.
Also, is it worthwhile to make the pages available in a zip file? Then a reader could download a snapshot of the book, and read it off-line.
And that's not the only old book that's getting a new life on the web...
22 years ago, long-time Slashdot reader Stephen T. Satchell (satch89450) co-authored Linux IP Stacks Commentary, a book commenting the TCP/IP code in Linux kernel 2.0.34. ("Old-timers will remember the Lion's Unix Commentary, the book published by University xerographic copies on the sly. Same sort of thing.") But the print edition struggled to update as frequently as the Linux kernel itself, and Satchell wrote a Slashdot post exploring ways to fund a possible update.
At the time Slashdot's editors noted that "One of the largest complaints about Linux is that there is a lack of high-profile documentation. It would be sad if this publication were not made simply because of the lack of funds (which some people would see as a lack of interest) necessary to complete it." But that's how things seemed to end up — until Satchell suddenly reappeared to share this update from 2022: When I was released from my last job, I tried retirement. Wasn't for me. I started going crazy with nothing significant to do. So, going through old hard drives (that's another story), I found the original manuscript files, plus the page proof files, for that two-decade-old book. Aha! Maybe it's time for an update. But how to keep it fresh, as Torvalds continues to release new updates of the Linux kernel?
Publish it on the Web. Carefully.
After four months (and three job interviews) I have the beginnings of the second edition up and available for reading. At the moment it's an updated, corrected, and expanded version of the "gray matter", the exposition portions of the first edition....
The URL for the alpha-beta version of this Web book is satchell.net/ipstacks for your reading pleasure. The companion e-mail address is up and running for you to provide feedback. There is no paywall.
But there's also an ingenious solution to the problem of updating the text as the code of the kernel keeps changing: Thanks to the work of Professor Donald Knuth (thank you!) on his WEB and CWEB programming languages, I have made modifications, to devise a method for integrating code from the GIT repository of the Linux kernel without making any modifications (let alone submissions) to said kernel code. The proposed method is described in the About section of the Web book. I have scaffolded the process and it works. But that's not the hard part.
The hard part is to write the commentary itself, and crib some kind of Markup language to make the commentary publishing quality. The programs I write will integrate the kernel code with the commentary verbiage into a set of Web pages. Or two slightly different sets of web pages, if I want to support a mobile-friendly version of the commentary.
Another reason for making it a web book is that I can write it and publish it as it comes out of my virtual typewriter. No hard deadlines. No waiting for the printers. And while this can save trees, that's not my intent. The back-of-the-napkin schedule calls for me to to finish the expository text in September, start the Python coding for generating commentary pages at the same time, and start the writing the commentary on the Internet Control Message Protocol in October. By then, Linus should have version 6.0.0 of the Linux kernel released.
I really, really, really don't want to charge readers to view the web book. Especially as it's still in the virtual typewriter. There isn't any commentary (yet). One thing I have done is to make it as mobile-friendly as I can, because I suspect the target audience will want to read this on a smartphone or tablet, and not be forced to resort to a large-screen laptop or desktop. Also, the graphics are lightweight to minimize the cost for people who pay by the kilopacket. (Does anywhere in the world still do this? Inquiring minds want to know.)
I host this web site on a Protectli appliance in my apartment, so I don't have that continuing expense. The power draw is around 20 watts. My network connection is AT&T fiber — and if it becomes popular I can always upgrade the upstream speed.
The thing is, the cat needs his kibble. I still want to know if there is a source of funding available.
Also, is it worthwhile to make the pages available in a zip file? Then a reader could download a snapshot of the book, and read it off-line.
Re: (Score:2)
if people can get something free, they will, and then they will value it less.
Haven't seen how many people brag about stealing music, movies, or video games, have you?
Re: (Score:3)
I both "pirate" and buy a lot of CDs (Score:1)
I was a tape trader. We used to dub stuff to each other, sometimes multiple generations from the source. It helps to be able to try before you buy. But after that? If the music is good, it deserves support, period. Many of the CDs I bought years ago have paid for themselves many times over by providing hundreds of hours of enjoyable listening. You know, the Beethoven nine symphonies, early Kraftwerk, and first couple Sepultura EPs. Stuff like that.
At this point, the type of "piracy" I engage in is 100% lega
Re:How does the author get paid? (Score:5, Interesting)
No, I'm living off of freelance writing, Social Security (at least, I will be in six months), the severance from my last job, and money I have in the bank. Right now, writing the Second Edition is more of a hobby than a money-making enterprise, to help me keep sharp and busy between writing assignments. Or alternating with writing assignments, as if/when the market bulds up for me.
There is another aspect. Back when I talked about this in 2000, there were a number of comments that I should "publish" as an open-source project. To me, that means "free for everyone." I don't have a problem with that. "Open source" means I can update whenever I want without having to schedule a press run. Moreover, I may be able to accept section (chapter) contributions wholesale, as well as critiques and errata notices retail. In short, I want to fulfill the promise in the original edition of "continuous update."
As for publishing in paper, the design of the Web book is such that transferring the content to the printed page should be pretty simple, if tedious. The sections in both the articles and commentary correspond to chapters in a book. The downside is that publishing on paper means the content is frozen in time. If you look at Linus' Git repository for the kernel, it's by no means frozen. Indeed, the velocity of releases is increasing, particularly as the IETF RFC document numbers are about to break into five digits.
The audience for my book is very much into mobile devices: phones, tablets, and other neat gadgets with small screens. Also, we may see something like Google Glass make an appearance. (Wonder how my book would render in eye-phones?) A very small number may elect to kill trees retail, so why should I kill trees wholesale? (No, I'm not a tree-hugger: saving paper is not in my list of goals for the second edition.)
Repeat: this is not a money-making project for me. I want to give back to the community that has supported me so well over the decades.
And that's the tooth. (<Bronx cheer>)
Free as in beer (Score:1)
Having given away a fair amount of writing over the years, I can respect this. Give things away and have people use them; this is the model that FOSS and early g-philes worked on. However, at this point, I find that people respect things more if they have paid for them. It is a weird psychology on one level, but makes sense entirely on another: that which has cost them something, they have fought for in some way, therefore is an achievement and worth defending.
What I find interesting as a long-term question
Is this a useful book? (Score:2)
Re: (Score:3)
Link us to the wiki that has the current documentation instead of advertising the book.
Where is this wiki you are talking about? The only "current documentation" is in the Git repository in the form of source code.
But you make an interesting suggestion: provide links to the current documentation about the protocols. That would be the RFCs that the IETF have released. That's the original source material. All I do in the gray matter sections is combine the information from some number of RFCs into a single whole.
Reference links for each section. That's the ticket.
Wrong book name in first sentence (Score:2)
"Recently the authors of Elements of Publishing..."
Typo in 6th word of article!
Re: Wrong book name in first sentence (Score:1)
How do you handle "Bandwidth Exceeded" (Score:4, Informative)
Answer: I host it on my own Web server, not a Web host. (That could change sometime, but not soon.) The server sits on a 100/20 AT&T fiber link. If traffic increases to fill that 20 megabits, then I'll upgrade to a 100/100 circuit. If the book ever gets that popular. Judging from the royalty reports on the first edition, I don't expect this to be a problem. But I do Have A Plan(tm) if it does.
Which reminds me, I need to install MRTG somewhere sometime to monitor the traffic. Be a good little sysadmin.
zip file (Score:1)
> Also, is it worthwhile to make the pages available in a zip file? Then a reader could download a snapshot of the book, and read it off-line.
A zip file containing web pages, with a few additional formalities, intended for offline reading, is called an EPUB book.
In the fine tradition of A Commentary (Score:2)
In the fine tradition of A Commentary on the UNIX Operating System. [wikipedia.org] .