On Mon, May 12, 2003 at 12:13:46PM -0700, Seth Arnold wrote: > On Mon, May 12, 2003 at 02:29:48AM -0400, Ed L Cashin wrote: > > Does anyone else have any good ways to print the kernel sources? > > I rather like a2ps's output. I've also used vgrind and lgrind. vgrind works great. I wrote two ruby scripts that together allow me to create a postscript file that has all the code in a given list of files, together with code from all the headers that the files use. http://noserose.net/e/code/index.php#kern-ps For example, to get a postscript file with pretty- printed code from fork.c and all the headers it uses, I'd do this: cd ~/kernel kern-ps /tmp/ps-output 2.5.70-mm4/include 2.5.70-mm4/kernel/fork.c kern-ps-merge /tmp/ps-output > /tmp/fork.c-all.ps gv /tmp/fork.c-all.ps If you don't already know, that's a lot of reading. You have to create the asm-{arch} asm symlink yourself if the sources are fresh. These are very simple scripts without much error checking or fancy features. No warranties; YMMV, but they work for me so far. -- --Ed L Cashin | PGP public key: ecashin@uga.edu | http://noserose.net/e/pgp/ -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
