So I must satiate my thirst to know MORE about computers.

It really does help to have some spare cash on hand so you can assemble a test system. I found that my knowledge skyrocketed when I finally had a computer that was not only non-critical, but also more or less up to snuff in the hardware department so I could experiment on it without everything taking forever.

If you want to learn about hardware, there's really no better way than building a computer yourself. You won't learn about all the tiny nuances of firmware/chipsets/drivers/etc. that way, but you'll get a very good idea of how things go together (literally and figuratively) and you'll also get a feel for what's currently on the market.

If you want to learn shitloads about your hardware (and I do mean SHITLOADS), try a build of Linux From Scratch or maybe a Stage-1 Gentoo installation. Mind you, these builds are not for the faint of heart and I would not recommend them to a Linux newcomer, but if you've got the intestinal fortitude and the TIME, then it's an experience you won't soon forget. At least not until your hair grows back.

Otherwise, if you're looking to learn a particular software package, the best way is to jump in and do it. Fuck up a lot. Hell, fuck up on purpose. The more you learn by trial-and-error and dumb luck, the better you'll be. It's what I did with Final Cut Pro, Reason 3, and Photoshop (still haven't gotten together the guts to do Cinema4D yet). A book will help, but use it as a reference as opposed to reading it cover-to-cover. I find that I get bored and set it aside halfway through the "History of...[$FIELD_OF_PROGRAM]" chapter that every goddamn tech author feels the sick, twisted compulsion to write. Java has garbage collection. I don't care that other programming languages from the 1970s don't: I'm learning Java and it does, so tell me that, tell me why it's good, and move the fuck on. Have a book on hand if you want to so you can reference specific chapters on what you're trying to do.

Finally, there are some things that seem harder to get into than others. For example, learning Linux was a pisser of a bitch for me as my computers were a Mac and a laptop that, until recently, did NOT play well with Linux at all (eMachines M6805, for those interested). It was tough learning where to start because even getting the system up and running was difficult.

Similarly, enterprise database or server systems like Oracle are difficult not only because of their resource-intensive nature and astronomical license fees, but also because HOW THE HOLY FUCK DO YOU PRACTICE DATABASES ANYWAY? You'll find that for some things, you need to come up with projects or sample scenarios with which to learn and experiment.

The best way to learn is to find something you think is cool on the internet. Stumble across a wallpaper image or music video that you like? Find yourself noticing details or techniques used therein? Might be an indication to take up Photoshop or Final Cut/Avid. Marvel at the well-laid-out design and/or functionality of your favourite website? Maybe scripting and web design are for you. There's nothing worse than trying to chew through lessons in a technology you consider boring, so don't bother unless you're getting course credit or can otherwise benefit VERY directly and VERY significantly from it.

Bottom line is pick something you're interested in, jump in and get your hands dirty, and above all don't lose heart. It's impossible to know everything about computers, so don't try. You're guaranteed to drive yourself insane, or at the very least get a first-class ticket to hair loss and ulcers. I consider myself a decent video editor and network/security guy, but I know shit about circuit board design. I can assemble a computer from parts and make it work well, but I'm fucked if you sit me in front of AutoCAD. Point is, I don't care because they don't interest me.

Go with your gut and have some guts, and you'll excel. Oh, yeah, that's another thing I don't know and don't want to. Excel. Fuck that app.

Jam it back in, in the dark.