LinuxQuestions.org Member Success StoriesJust spent four hours configuring your favorite program? Just figured out a Linux problem that has been stumping you for months?
Post your Linux Success Stories here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The coolest thing I've done so far...I stumbled on "xinerama" this afternoon and four hours later I had dual displays set up with my radeon 7000 and my onboard intel. Windoze wouldn't do that. My monitors are different too, the ati running a Compaq FS740 and the intel running a relic korean 13" svga (circa '94).
That was last night. It wasn't so cool this morning when the old 13" started squeeling and gave up. Next time I try xinerama it'll be with matching cards and monitors. Oh well, I learned a bunch about X, and learning something new is always cool.
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
xinerama, i've heard of it and am drooling at the prospect, but i have yet to sucessfully understand how. are there any gui frontends or is it going to be all command line based grit? either way sounds fun, but i would hope to have a gui 'safety net' in case i screw up.
install knoppix on an old machine at my parents place....remove all the unnecessary software and then compile my own kernel 2.4.23 and coming out of all this alive and well....oh and removing the terminally slow XP install on the same machine.
The coolest thing ON linux is wine, the coolest things i do are with wine
while it is nothing great when just stated, getting games like warcraft 3: RoC and FT, red alert, simciy 3000 and 4 to run in linux is just jaw-dropping, not to mention they work with near perfect quality and in a definitely more clean and more manageable environment (simcity was always slow because windows doesn't know how to handle memory or cache, but in linux, good grief is the speed amazing!)
so ya, gaming on linux, coolest thing ever, especially when your peers shun linux because they say that gaming will never be possible on it.... hahaha!
Distribution: Home: Fedora Core 1, Mepis RC4, Red Hat 6.2. Work: Fedora Core 1&2, Mandrake 9.0.
I get lightening pings as a Linux client playing Team Fortress Classic, which was never as fast under Windows on the exact same box! I now regularly ping around 25 to 75, whareas before in Windows, pings were 75-150 average at best.
And THAT is also one of the coolest things I ever did with Linux!
I think the slickest thing I ever did in linux was writting a module that pre-empted the kernel. It was of course, extremely dangerous, but what I did was manually write the interrupt table in a kernel module and when my super short ISR was complete I cleared my interrupt and jump to the standard interrupt service routine for linux so it would clean up the mess I created. I ended up having to compile the code with no optimizations and I had to put in assembler statements at the being and end of my function to save registers and restore them so I didn't distrub anyones data and cause the system to be unstable or a kernel panic. It was ugly ugly code, and Linus would probably shit a brick if he saw it, but it is out there in a commercial product they use in printing presses to ensure that multiple colors are aligned correctly on the fly. Unfortunetly I don't have a copy of it anymore, and I don't remember the name of the company that actually sold it (I was working for a client that was working for another company... one of those situations) so I can't go to there web page and download it (since they best have it up or it is a GPL violation). It was the only programming project I have ever done that caused me to pull out the old spec. book on Intel x86 processers so I could figure out how to over-write the interrupt translation table and check and reset the interrupt registers manually.
All because I couldn't get the desired performance from rt-linux. Of course I later found out the guy that told me how fast I had to be able to service the interrupts had done a math error and rt-linux would have easily accomidated our problem, but that is besides the point.
Getting lm_sensor installed and running on 2.6.1-mm2. This after upgrading my motherboard which took a total of 10 minutes after I put the old harddrive in the computer. 2.6.x is totally awsome. I have been working with 2.6.x since 2.5.75 and all of the anomolies.