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.
Thanks, both of you. I have screened through virtually all the logs, thousands of lines that I am not competent to understand fully, but they don't seem unusual except for in user.log, a lot of lines with "debian ......... tests: debug:........" and "debian .........debug: parsing:......." which seem to have to do with checking or locating disk partition devices rather than anything to do with the screen freezing.
I have not booted with a DVD but booting with Debian 6 "squeeze" which is also on the box, the cursor moves normally. Therefor the problem is only in "wheezy" and specifically
in corruption of a setting affecting the cursor and display.
My hope is to find out how to locate and correct that.
Wheezy might not be the best choice in this moment in time. It's been frozen pending the release of Jessie (the next version which I believe is Debian 8). In any event you might want to try a Debian Live Install CD and see if the problem persists.
Thank you jdk for taking an interest in my freeze-up problem.
I don't see what is to be gained by running a live CD, inasmuch as Debian 6 functions on the same machine without freezing and Debian 7 "wheezy" has always also, until this current glitch.
As to Debian 8 "jessie", I plan to upgrade to it when stable (as in essence it probably is now), as I have done in the past from "etch", "lenny", and "squeeze". But I want to use my "wheezy" until then because it is configured as needed for my regular work.
Do you think running apt-get upgrade from failback might replace whatever element is misbehaving with a properly functioning one?
Last edited by hilltownboy; 12-11-2014 at 04:57 PM.
jdk, with business and personal programs, and records both current and going back many years, Debian stable seems to be the choice for reliability and dependability. I use Arch for learning linux and for using the latest packages of interest, and PCLinux as a fallback and sometimes for cues on how to set somethings up. Right now my Arch is broken by a mistake I made and the Debian stable is blocked by the freeze at the login screen. I really need it back.
with business and personal programs, and records both current and going back many years,
Describes my own system to a "T". I back up regularly and have been using Testing for many many years. Never had a problem and I prefer running a system that's reasonably up to date. My mental image of Debian Stable is a server for an office filled with 367 machines all running accounting software. For home use as you have described it, I'd suggest Testing (and I'm considered conservative by Sid users). But chacun à son goût.