Domain: coriolis.com
Stories and comments across the archive that link to coriolis.com.
Comments · 5
-
Linux Core Kernel CommentaryI'd recommend Linux Core Kernel Commentary, whose first edition was favorably reviewed right here on Slashdot. It's unlike other kernel books in that it examines much of the core of the Linux kernel code line by line; it's a good way to pick up a lot of the code's idioms and to learn to think like a kernel programmer, but this approach necessarily narrows its coverage. Depending on your specific interests, this might be the perfect book for you, or it might serve well as a companion volume to a book with broader/different focus.
The publisher has a sample chapter online (though their HTML looks weird to me; I hope it looks better in your browser). Also, you can read a little more about the book, find links to online reviews, get errata listings, and so on, at its support site.
Oh, and I, er, happen to know the author.
:-) -
Book
I'd like to recommend Open Source Development with CVS
as a good starting point. -
This seems really coolNot only is he releasing a nice portion of the book for free electronically, but he encourages you to avoid amazon.com. From the site:
You can get it directly from the publisher at http://www.coriolis. com/bookstore/bookdetail.cfm?id=1576104907 (due to Amazon.com's recent abuse of the patent system, I am participating in a boycott of Amazon, and ask that you not purchase this book, nor any other, from them).
After looking at his site, this not only looks liek a great book, but an author I'd like to support. Besides, my CVS skills need the polish. -
I'd like to hear how well it works
I'd be very interested in hearing the experiences of both authors and publishers about how well open licenses work for books. There are now at least three publishers that I am aware of who have published books that are licensed in whole or in part under an open license: O'Reilly, Coriolis, and New Riders. I am not counting the various publishers who have printed the Linux HOWTOs, Guides, manpages, etc. because those were not new material at the time they were published in printed form. For the same reason, I have also omitted the Free Software Foundation, which has been publishing printed copies of its own manuals for years.
Obviously, from the point of view of the publishers, it works well enough to stick their financial necks out to print the copies. It would be interesting to hear the pros and cons from a financial viewpoint. But what I really want to know is whether anyone has found a way to blend an open license with a print book in such a way that the open source community feedback has continued to improve the text after print publication. There are a lot of worthwhile documentation projects that are too big for a single person working part time on them. A positive answer to this question could encourage them to happen. -
Re:6.0a upgrade fear
Anaconda kicks much tail.
Does anyone else notice a pattern here?
- Anaconda
- Asp and Asp 2
- Boa
- Bushmaster
- Caiman
- Cobra (Mk I and Mk III)
- Copperhead
- Coriolis
- Gecko
- Krait
- Mamba
- Python
- Sidewinder
- Viper 1 and 2
- Worm 1 and 2
Nominating companies or applications to match Hognose, Dodo, and Thargoid is left as an exercise to the reader.