[0] http://en.wikipedia.org/wiki/Source_lines_of_code#Example
On a typical computer more than half of the drivers loaded are made by Microsoft, you can check easily with sysinternals' autoruns.
- code that compiles to the single executable file that runs the OS (this can be limited to a mechanism for booting the system, a thread scheduler, basic memory allocator, but this may also contain some device drivers, file systems, etc)
- any code that compiles to anything that will run in kernel mode (many file systems and device drivers)
- the code that someone (say the people distributing what they call "the Linux kernel") call the kernel.
This count is about the third. I do not think it contains a kitchen sink, but it is close :-)
I'm not a programmer but I know you can cram certain methods, functions onto one line instead of arranging it on separate lines for easier comprehension by other programmers. As well comments and blank lines would add a lot depending on the style of the programmers doing it and if a blank line is considered a line.
Logical SLOC and physical SLOC make sense.