Richard Andrew x64 wrote:
How long did it take you to learn Linux well enough to become employed at working on it
About a month. The kernel is very similar to windows, PASSIVE is process, DISPATCH and DIRQ, soft and hard interrupt. DPCs are work items, spin locks are spinlocks and so on. The language is C and the protocols and HW interfacing are the same. The only difference is the API to the kernel and different tools; using test editors to edit code rather than VS, and having to use your own code profiling tools because browse info isn't built. Debugging is different too. Windbg is a great tool, and Linux has nothing like it, so the best that can be done is with kgdb, which isn't bad. Once annoyance, you cant build an entire kernel in debug (un optimized) mode, only per file using #pragma. You have to do that to have proper step through in the kernel. You also cant break into the OS at boot time and automatically drop into a debugger on exception, like in Windows. But it is so much easier to write code for, so many less hoops to jump through, that you can really focus on getting your work done rather than dicking around. Right now I am trying to run the MSFT HCK client on Vista, to fix a bug in a third party windows driver, and the HCK client isn't a valid win32 app apparently. This is typical MSFT. Absoloute shitty experience. Days and days and days I have wasted fucking around with this crap trying to get consistent results out of it and so far, zero. That's the Windows experience all over.