Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
-Experimental PC: of course it is experimental, just like Red Hat experiments with Fedora on its users (from what you claim RH is doing through Fedora), users experiment with this system to see if it is worthwhile after so much Linux advocacy.
-Conveying the feeling: but these are hard facts, no need of conveying feelings , giving comfort or anything similar. Due to hardware failure the system that you reffered to as global experiment couldn't boot up. Hardware that worked well under the OS that Linux advocates reffer to as "legacy system" was fried after several installations of the advanced OS. And if you intend to do anything more serious on your Linux box, at some point you would have to touch around the kernel. But the kernel has a typo... in the final release...
-The great work of proactive people that created this can only be appreciated through the use of their creation. And you can only use it if it works.
I hope you followed my point so far. I have solved my GRUB problem by replacing damaged hardware with new one. Although the OS was free, the damaged hardware was not. Neither was the time spent in trying to make it work.
I dont want to be an advocate for linux it itself does not need any. The os is free(please check it out what does it mean by free you may find it on gnu.org and also read the GPL) and that free spirit has made me Love it.
One more thing, how can any software (except for X) can damage hardware?
If you do not have a good experience in something, you should try to get it with an open mind.
I think I have already hurt you in more than one ways.
Obviously imageneers7 is not following my point (or maybe didn't try to with the same open mind he is suggesting). I am still talking hard facts, imageneers7 advocates ("not a linux advocate" but "visit gnu.org and see what does it meen free"?!).
Typo in a final release of ANY software is unprofessional. Period.
Damaged hardware out, new hardware in. Problem solved. As to the reason why the problem occured, facts again: countless CD's went through the old CD-ROM without a hitch. But after several installs of certain OS, it burned.
This is where reasonable discussion stops and advocacy takes over...
Software doesn't damage hardware directly. No linux/unix/microsoft offering does mysterious bad things to your CDRom that causes it not to work. How about the possibility that the CDRom was going which caused you to need to reburn the same thing several times?
As to the kernel typo, since it is open source, at least the error was found and corrected. Since you seem so concerned about it and the professionalism involved, why don't you comb through the entire kernel source and detect all the typos for the kernel team? I'm sure they'd appreciate the help! Seriously though, yes a typo sucks for all involved parties, but you have guys working on the kernel with little to no official compensation. So they missed something. AT least it was found and corrected, in a short manner of time. Googleing kernel typo shows that this wasn't the first and probably won't be the last.
This is seeming more and more like flamebait, so I'll lay off and return later.
If you're that upset and blaming the OS for hardware issues, then go ahead and use something else. Not a problem.