News for hackers. Stuff that matters.
Re:Linux containers in 500 lines of code (2016) by oblio on Thursday November 02, 2017 @07:06AM (#15609304)
True, because most of them either add a million diagrams or a million copy-pasted source code snippets. And this happens because people "respect" a thick book when they are looking for a technical book. It's quite silly, actually :)
Re:Linux containers in 500 lines of code (2016) by mcny on Thursday November 02, 2017 @07:11AM (#15609332)
Somewhat tangentially related, I would like to know how the parent poster or for that matter printed the document.

somewhat unrelated, I don't use emacs but is there a way to break lines such as

#+caption: [[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux....]

in the org mode source? https://blog.lizzie.io/linux-containers-in-500-loc.org

Re:Linux containers in 500 lines of code (2016) by kurlberg on Sunday November 05, 2017 @04:02AM (#15628751)
You can export from org to pdf (type C-c C-e l p in emacs). For some fine tuning you can export to tex and then use pdflatex.
Re:Linux containers in 500 lines of code (2016) by vidarh on Thursday November 02, 2017 @12:40PM (#15611981)
It's kind of strange, considering that most of the non-fiction books I remember most fondly, are fairly thin. The big tomes tend to largely be forgettable (there are of course exceptions) - I guess often because they go into too much detail that date rather than concisely describing concepts.
Re:Linux containers in 500 lines of code (2016) by pjmlp on Thursday November 02, 2017 @08:38AM (#15609809)
Because many of us needed to thrust our work to thick books on the days before ubiquitous Internet. :)