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.
Ok so I wrote reboot (I suppose that's what you meant), a few lines appeared and it restarted.
Not that it matters for the main problem, but I've always wondered : where are the lines that appear on start up/shut down logged ? (I'm sure they're logged somewhere otherwise it's useless, as you don't have time to read them).
Anyway, now I'm back to the login window. It seems it's ok.
So how can I delete what I did in the first place ?
First of all, check if you can log in to your system and tryout a couple of things. Also check if you can use su or sudo in a terminal. Main issue is to have full access to your system, otherwise you will not be able to complete the necessary steps I think.
So basically, you've got your system up and running again? That's good news. Regarding the package you installed, I've never installed it myself that way. Since it doesn't have an uninstall option (like you checked with repo) it's going to be a lot harder I think to do it correctly and completely, and more important without breaking anything again.
First of all I had a look at the site where you got the download from. May I ask why you downloaded version 0.77 and not the latest? Is there any particular reason for that?
You could delete the files that are created and the links to them. Files are described here.
Do you have a log file in the directory from where you ran the install? If you do, then check that log file to find out what was installed and where, such as links as per your first post.
If there's no log file then we'll have to go through the scripts to find out what's done in order to undo it.
Yes it seems to be running again.
No there's no reason I installed the 0.77, I just didn't know it wasn't the latest.
I didn't find any file called exactly "log", but there's quite a lot of files including the word "log", as i found out during a quick search :
changelog, config.log, faillog.h,pam_lastlog.c, pam_nologin.c,...
(do you want me to list all of them?)
In the meantime, may I offer you a small advice? Actually two?
1. If you want to install things and don't want to run the risk of breaking your system, stick to the package manager (also stated by repo) instead of installing from source until you know what the installation will do. To find out what it will do, read what's in the package, the README, INSTALL and other files are there for a reason. And don't install old versions of software unless you really need them/want them.
2. If you want to experiment and install from source, you'll have to take into account that you might break your system. So be prepared that you might have to reinstall everything (if the break cannot be fixed). So; the golden rule: BACKUP, BACKUP, BACKUP.
Yeah I know. But I was quite in a hurry to try this, and I don't think it is in the package manager.
the config.log file is quite big.
there are some c-like lines. gcc is mentionned some times as well.
the first two lines are :
this file contains any messages produced by the compilers while running configure, to aid debugging if configure makes a mistake.
Would you like me to mail you the whole file ? (312 lines)