DebianThis forum is for the discussion of Debian Linux.
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.
When Etch becomes Stable you have a fairly modern system, so no need (yet) for Testing. Running Testing just for the sake of being able to say you run Testing is the wrong reason. You should only use Testing when it contains a package you require. Keep in mind that unlike distro's like Suse, Fedora and Ubuntu the emphasis with Debian is stability. The forenamed distro's focus more on 'cutting edge' and thus accept failing combinations of packages, sometimes even breakage and causing useless systems. So if you're after the latest packages, Debian might not be the distro for you.
I think most "hobbyist" Debian users run Testing. It is really quite stable, and you keep fairly cutting edge software. Use your own judgment, but unless you are running a production system of some sort, Testing will probably be more suitable.There will be an influx of new programs to Testing when Etch goes stable, but they will have had extra time in Sid to get the bugs worked out. I foresee no problems with that transition. A harder transition may be moving from Sarge to Etch because of Xserver issues.
A harder transition may be moving from Sarge to Etch because of Xserver issues.
That's the one I'm fearing and the reason I've been reluctant to move to testing! I'm kind of hoping the Deb developers have managed to iron out the problems before Etch goes stable or there are going to be some disgruntled Debian stable users. Personally, I'm fed up of getting a distro just how I like it with everything working and then borking it up.
I just switched from sarge to etch a couple of days ago. There were warnings in the installation about gdm becoming unstable, so I stopped the install at that point and switched to a non-X login to finish. Of course it then complained all the way through that it was falling back to the console interface. LOL If I remember correctly, xorg didn't get completely installed, so I had to do that manually. Not a real biggy. The nvidia installer complained about something (can't remember what), but it pointed out what to do to fix it.
The installation really went pretty well, actually. The biggest aggravation was that my mouse side buttons broke, and xf86config is no longer available. I used xev to figure out that my mouse was now sending buttons 8 and 9 for the side buttons. Setting up xmodmap fixed that.
The one thing tha above has that you might want to change is using the name etch instead of testing in your sources.list that way you stay with etch when it becomes stable.
Also it is a good idea to not have X/kde/gnome running when you dist-upgrade. Do it from a console boot. That's one of the nice things about Kanotix/Sidux init 3 goes to console and kills X/kdm/gdm, that way there is little chance of messing with running processes.
dist-upgrade" is Ctrl+Alt+F1 ; logon as root, type init 3 ; apt-get update ; apt-get dist-upgrade ;run fix-fonts ; run update-scripts-sidux.sh ; run fglrx or nvidia script if xorg updated [DO NOT DIST-UPGRADE [or UPGRADE] with adept or synaptic, or while in KDE/Gnome/X]