Quote:
I would recommend that if you are a programmer to go for the device driver training. That is really the nuts and bolts to getting things to run with Linux.
|
I'm certainly interested in the "nuts and bolts" of Linux but don't necessarily want to write device drivers every day of the week, although I have written drivers in the past in RTL/2 to speak to PLC's, flow meters and the like. It's the outer edges and the fundamentals of the course that interests me.
My main worry is that by skipping the essentials course my memory will be a little rusty in certain areas such as semaphores, makefiles and IPC's. However, a quick on-the-fly root in a book or man page would get my brain re-oiled - it really depends on how complicated they want to get!
Quote:
The question is : Are you really familiar with Linux? As a workstation? As a server? If you have no plans for Linux Sys Admin then I wouldn't try to become an expert at that.
|
I can find my way around the kernel and the environment, but from the server/sys admin point I'd be floundering a bit. Mind you, that's what the man pages and various Linux books are for. I'm more than happy to dive in at the deep end without a life guard. (Fortunately, I can play with (and break!) a Linux server without causing problems to others)
Quote:
How many Linux "Gurus" actually write drivers for hardware? If you can write code to a level that hardware gets what you're saying then I think you're one of the "elite."
|
I'd hardly call that being "elite" as you're only using all that nasty stuff those devilishly clever "guru" types wrote.