Waqas Posted March 15, 2004 Share Posted March 15, 2004 how linux handles the deadlocks? and how it differs from win 2000? Fiza 1 Share Link to comment Share on other sites More sharing options...
amoeba Posted March 15, 2004 Share Posted March 15, 2004 ... deadlocks? It freezes? Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted March 15, 2004 Veteran Share Posted March 15, 2004 If you are talking about GUI lockups, you can always CTRL+ALT+F2 (or any F1 through F6) to get a TTY terminal, and debug and terminate problem apps by PID. Link to comment Share on other sites More sharing options...
Waqas Posted March 15, 2004 Author Share Posted March 15, 2004 i need theoratical information and algorithms Link to comment Share on other sites More sharing options...
kemical Posted March 15, 2004 Share Posted March 15, 2004 google it Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted March 15, 2004 Veteran Share Posted March 15, 2004 Well, first we may have to make some assumptions, as Windows and GNU/Linux are two very different beasts. Linux is built as multi-user, and has seven built-in onboard user interfaces. Typically #7 is used for the GUI, leaving 1-6 available for textual interfaces (TTYs). This really doesn't exist in Windows yet... The Linux GUI interface is typically (but all optional), and X Windowing system to handle the basic graphical windowing functions. There is a Window Manager that is placed on top of this. And KDE & Gnome put a full Desktop Environment on top of the Window Manager. Linux applications tend to be text-based, or at least have their origins in the command line envionment. Many "GUI" apps are front-ends to the text commands (XCDRoast and nmap's front ends come to mind). There are also more and more GUI-only apps coming out, but basic tools are text based. A fault can occur on any of these levels, just as on Windows. However, in Windows, your only hope for recovery is the taskmanager (via CTRL+ALT+DEL). In the event on non-responsive GUIs (what your original question seems to be about), Windows requires a second CTRL+ALT+DEL to reboot the whole PC. Linux allows you to terminate the GUI environment (the X Window system) via CTRL+ALT+BACKSPACE. This will keep all services running (for example, a webserver, mailserver, printserver, etc.), but terminate X (and all tasks that are children of it). This is a Linux "disaster", as the offending task can be identified, and singly killed, instead of killing the whole GUI environment. You can also ssh into a Linux box and identify and kill the approriate task, though I have never had to do this. Rebooting on Linux is rare (hardware fault, or kernel upgrades for the most part). Reloading isn't necessary. There is no registry to get bloated and corrupted, as individual config files are text files associated with the programs that use them. In the end, Linux recoveries are better (more surgical and more powerful) and less-often needed due to the structure of the OS. But that is just my opinion. :cool: Link to comment Share on other sites More sharing options...
kongit Posted March 15, 2004 Share Posted March 15, 2004 ctrl+alt+backspace kills x. Although I have never had to do this... I have never had any deadlocks. Link to comment Share on other sites More sharing options...
hornett Posted March 16, 2004 Share Posted March 16, 2004 I think he means deadlocks as in two processess fighting for the same service thus getting trapped in a loop. Unfortunatley I do not remember how linux resolves these. Link to comment Share on other sites More sharing options...
markwolfe Veteran Posted March 16, 2004 Veteran Share Posted March 16, 2004 I think he means deadlocks as in two processess fighting for the same service thus getting trapped in a loop. Unfortunatley I do not remember how linux resolves these. Well, if in doubt, you can always go over the Linux source code. Which is more than Microsoft lets you do! (unless you enter a NDA and/or illegally download their leaked source) :pinch: Link to comment Share on other sites More sharing options...
kjordan2001 Posted March 16, 2004 Share Posted March 16, 2004 I think they use some sort of pre-emptability. Link to comment Share on other sites More sharing options...
kongit Posted March 16, 2004 Share Posted March 16, 2004 I have never had any deadlocks. This is no longer true. My computer deadlocked during the installation of Mandrake 10. Now it is all sorted. It is very nice by the way. I am going to use it as my xp replacement. :) I still will most likely use slackare 90% of the time, but I can print in mandrake, but not in slack. Damn Close-source drinvers by lexmark. Link to comment Share on other sites More sharing options...
MrA Posted March 16, 2004 Share Posted March 16, 2004 I think he means deadlocks as in two processess fighting for the same service thus getting trapped in a loop. Unfortunatley I do not remember how linux resolves these. If so, isn't this usually handled by semaphores? Link to comment Share on other sites More sharing options...
kjordan2001 Posted March 16, 2004 Share Posted March 16, 2004 If so, isn't this usually handled by semaphores? Yes, Linux uses semaphores. I also remember reading something about pre-emptability in the kernel. Link to comment Share on other sites More sharing options...
hornett Posted March 18, 2004 Share Posted March 18, 2004 ^^ Correct ... However I'm still looking for the notes from my lecture I had about it :/ Link to comment Share on other sites More sharing options...
Recommended Posts