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.
I thought that linux didnīt crash, but I can consistantly get it to crash just by loading xawtv and moving the xawtv window. I could understand it if just crashed xawtv... but it completly freezes my system and I have to reboot.
Any ideas? I would be happy even if there was some way of isolating xawtv so that it doesnīt completely lock up my system.
Umm I donīt think so donīt have the best system but a Celeron 1700 512mb ddr333 ram 40gb 5200 rpm hdd Radeon 9100 128mbddr ....I donīt think it should be a problem???
Is it ctr alt backspace??? Not ctr alt del???
I hope thats not too stupid a question but Linux really seems to crash properly (but ONLY when I load xawtv and move the window)... I think it could be some sort of an IRQ problem but I have no Idea how to sort that sort of thing out cant even find my manual that is supposed to tell you which slots share IRQs
It does sound like a problem with the display (only after moving the window), so I guess it's just X dying. Have you also tried Ctrl+Atl+F1 to get a login console? Ctrl+Alt+F7 is normally to get back to the X screen if it's working.
I've had to push the reset button probably a dozen times on my red hat 8.0 box in my short history with linux and thru several reinstalls. Sometimes it just locks up and there's no going to a new terminal, no escaping, no ctrl-c'ing, no ctrl-alt-bs, nothing.
Hasn't happened lately tho.
Originally posted by ufgeek And linux doesn't crash, people crash linux.
I doubt that anyone who has done any programming at all would make a claim like that
Operating systems are very complex things, especially when you consider the amount and variety of large, complicated, and potentially flawed software that is running at any given time on a modern PC, which contains any number of complex and potentially uncooperative pieces of hardware. OSes do crash once in a while. Some people use Windows XP for a year with no crashes, some use Linux for a day and have a hard freeze.
If the crash is consistent, there may be a way to localize the problem to keep it from happening. Try running GKrellm or another monitoring application and then seeing if it's possible to duplicate the crash; run 'top' in a terminal window and see if some process is hogging all the CPU right before it freezes. Check the logs, or use tail -f on one of your system logs (/var/log/messages, etc.) to see if anything useful is printed there. Find out if there is a known bug with that software, and see if there's a patch or upgrade that might fix it; use a utility like memtest-86 to test yor RAM and make sure it's okay. There are lots of things to try!
Originally posted by jhansman Hmmm, can I use that logic with Windows too? I ask because in all the time I've been using XP (including the beta) it has never once produced a BSOD for me. Must be luck, huh?
Nope, never. But then, I built my system, installed the OS, took the time to learn it and configure it, don't overclock and maintain things regularly. Have I had apps freeze and need to be terminated? Sure. There's no shortage of crappy software out there written by half-assed programmers. But not BSOD here. Not even from games. Go figure.
Yes, I too am impressed and pleased with how stable Linux is. I just wish it was a tad easier to get things done in. Still, I've managed to install what needs installing, update the updatable, and eventually find the configurators I need. Now I just wish I could connect to our Win2K Exchange server at work without having to buy a 3rd party utility like Crossover. Sigh....