GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
PLEASE NOTE: All LQ Rules apply to the General forum. Flame wars, personal attacks, hostility, insults and behavior of that nature will not be tolerated. Differing opinions are one of the things that make this site great, but to benefit from differing opinions the discourse must happen respectfully and thoughtfully... without insult and personal attack. Members who are unable or unwilling to participate in General under those parameters will not be permitted to do so. If you see behavior of this nature please report it.
I just started using XP (for my gaming system) and I havent got the BSOD or illegal program operations crap yet I keep getting this new nice error message saying something like, Windows/Explorer has encountered an internal error and needs to shut down please save any information and restart, blah blah blah. Why the F*** cant they stop the dam errors? Its so dam frustrating when these dialog boxes pop up. Why not have some kind of debugging program run in the background that fixes the problem or detects what the problem is or something, im not a programmer but it seems like something can be done to fix this crap.
the other irritation is the necessity to have antivirus software that decides to scan or send popup messages to you just when you're doing something else
and the persistent update messages from windows
and those stupid balloons
and the way even though it has booted up, some kind of hard disc activity makes you have to wait another 5 minutes before you can get down to work
Don't get me started! There's been enough Winblows bashing! One of my main goals right now is to get Slackware to the point where I can format c:/q Winblows right out of my computers! And, I'm getting fairly close!
begin rant - take a break *nix and open source
But I must say that I run W2K and never have any of those type of errors, and everything "just works well." Of course, that is at great expense!
Windblows has a place - it's for those who don't have the time, or desire, to read and learn about something better and/or different. If you only want to point and click, use Windblows.
Originally posted by Chinaman You seem to have stumbled upon one of the 69,345,899,319,802 reasons I'm personally migrating away from the demon possessed Mirco$loth Winblows operating systems to Slackware Linux.
Originally posted by Whitehat I don't have any problems with my Windows XP box. It just runs and runs and runs and runs ..........and runs and runs and runs
I leave it up for days and weeks and months at a time I only reboot when I have to for security updates or installs or whatever.
Every now and then it just locks up hard or programs with memory leaks take up too much RAM and force a reboot. Heck even Linux (well...I should say KDE) locks up every now and then .....but not much!
I just never understand the problems that people have with Windows XP because I don't ever have them.
I never had problems with NT/2000/XP. Now.....9x/ME is another story.
Ditto to all that! If you know how to properly install Windblows, it will function well for you. Of course, you will have to pay some bucks for the software that you could mostly get for free (downloaded) in *nix.
I build and install computers, and the only time my customers call me is when they either (a) try to install something and mess it up, or (b) get a virus or worm and can't clean up. They give me so much trouble with that, that my policy now is to ghost their hard drive and just restore it to where I gave it to them. They can reinstall their other programs and learn to backup from experience.
Originally posted by johnleemk The only time XP itself crashed was when I screwed with my hard drive in my BIOS. Other than that, the only unreliable apps on it are MozillaFirebird, Opera and Mozilla. Must be sabotage.
Last time I used Firebird on Doze it had more bugs than almost anything I've ever used. And Opera I tried years ago. IMO it's a joke. Now I've got Mozilla running on Doze, also, and it's great! Tabbed browsing, pop-up blocking, and much more make it a pleasure to use. It's much better than IE to me.
I hate to admit it, but windows 2000 has been absolutley BULLETPROOF for me. I have had it up for about a month at a time, only rebooting when I wanted to, not beacuse it locked up. Granted, I run it with very few addon programs other than the adobe and macromedia suite, but i cannot complain too much.
Windows 98/Me howver, nehaved like and eigth grade computers class project. Actually, I have seen some eigth graders write better stuff than that. I think I saw more blue than anything else....
Most people you say they never had problems with winXP are most likely using it on a HOME network.
At work, I have a network with about 50 workstation running either winXP or win2000 (and 5 or so still on win98... I really have to format those computers... ).
Anyways, those annoying networking problems seem to be still present in winXP (at least to some extent).
The Network Neighbourhood locks-up on occasion. And if you try to close it, a nice window pops-up and says "This program is no longer responding... blah blah blah..." ... and Explorer -- which is an intergrated part of windows -- crashes and all programs close...
At least I no longer have to Reboot, I guess that's an improvement.
All the servers and 4 workstations run Linux, I rarely have any networking problem.
If you build a good image and you have good hardware, Windows XP will run flawlessly.
Don't get me started on hardware... we purchased new computers with Asus P4S800 motherboards and the driver for the built-in NIC overrides the MAC address with a pre-defined one.
This means that the 8 new computers had the same MAC address.
The mistake here was to let the computer store do the installation and upgrades. Next time, I do everything myself.
Most people who have problems with Windows XP are novices!
In a way, you are right. Prior to starting this new job, I had not touched windows in over 6 months and never fully used windowsXP.
Guess what buddy. I run a network with 60+ servers and 1200+ workstations. Most of those workstations are Windows XP. They run freakin' flawlessly.
This LAN is not very big, but it is a total mess... and I have to clean it up.
Luckily for me, the WAN is well structured.
One other thing I have to say. When it comes to PC's in a corporate environment....you're always better off going with Compaq/HP or Dell or IBM corporate PC's like the Deskpro or the Optiplex. They don't have problems like you're talking about because they have such huge R&D departments.
Plus it helps to standardize on one thing and only one thing.