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 am a relative n00b to Linux, but I'll tried virtually all the major distros and many offshoots. I would like to spend more time in Linux at home and at work, but I have two last hurdles to overcome. Namely, I need to figure out if there is a specific distro or package which will allow me to restore quickly if I break something during an upgrade. I use Mepis and other Debian-based distros, and I am about to try PCLinuxOS, but I am afraid that I will continue to break things as I do now, because it takes too long to recover. If I try to take Mepis from KDE 3.2 to 3.4, for example, I risk hosing my system (I know some have done it, but this is just an example).
Is there a system that helps protect against "failed" upgrades? I mean, something beyond apt's dependency-checking?
As a sidenote, my other hurdle would be to find a gui-based snapshot capability like rsync which would allow me to backup a PC and create incrementals which could be selected for quick restore later.
in my experience, the system has always been restorable(maybe with a rm -fr / it might not be) . You would just use the boot disk to repair,copy, etc. I deleted the kernel a long time ago by accident...lol...but i just used the one off of the orig cd to boot up the system.
Upgrading kde shouldn't hose the computer regardless.
I know this doesn't answer ur question, but people are only too ready to reinstall when you don't have to.
I also think quite a few distros have rollbacks available after upgrades. Take a look here.
If you break the system you get to keep all the pieces.
No, there isn't really an idiot proof Linux, but the more times you break your system the more you learn from it. Backup, backup, and backup.
Upgrades are always a tad risky, but the more you do it the easier it becomes and you'll learm how to avoid the "dumb" mistakes that break the system.
Did I mention backups?
I've never cared for distros that automatically make config changes as those changes are the biggest source of problems during upgrades. When doing any upgrade, be vary stingy about allowing any changes to your config files.
These are all great solutions, thanks. They definitely help out in the backup/image department, and the transactional rollback looks like it is close to what I need. I hope they've improved the process and auto deleted the rollback packages after a rollback, though. I must admit, the "System Restore" feature in XP is very handy when you install/uninstall as much as I do!