Slashdot Mirror
Inside the Linux kernel debugger
An anonymous reader writes "Here's a good article that shows you how to install and set up the kernel debugger (KDB) to trace Linux kernel execution and examine memory and data structures. The best part is, you don't need a separate machine for debugging."
I'm not basing my hatred of Windows on kernel debugging. There's so much wrong with Windows, I just cannot think where to start. Everything about Windows is "dumbing down" the experience from the user and in doing so removing power from them. A UNIX system is an incredibly rich and flexible (and extensible) tool. It's very empowering. WIndows is all smoke and mirrors, trade secrets, treating the user as a moron etc. As someone who uses computers every day to do work, I just can't imagine how I'd get 1/10th the work done on a Windows box, without substantial expensive 3rd-party add-ons (mainly software). The last time I used Windows at work was NT4 in 2000. I found it so primitive, buggy, unstable and restrictive compared to Linux and Solaris. I know Windows has improved some what, however it's still an expensive toy compared to Linux and Solaris. On a UNIX machine, everything's there, it's documented and it just works. Most of the software is Open Source or Free. Everything conforms to standards. If you don't like one system, you can move over to another e.g. fed up with Linux? Try Free BSD. Want an enterprise server with a support contract? Move up to Solaris. Need a real-time embedded POSIX kernel? Get QNX. Want to run on a small ARM machine? Get Net BSD. ... and KEEP YOUR EXISTING SOFTWARE.... and we haven't mentioned 64-bits yet, have we? There have been 64-bit UNIXes for over 10 years now. They're mature. Where is Windows? What about porting your applications? Which processor? Do you have a choice other than itanic? Good luck.
Stick Men