SUSE / openSUSEThis Forum is for the discussion of Suse 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.
I was installting suse linux but suddenly it stopped working. I abort the installation, and check the cds, it said checksum failed, cd is broken. So now I'm re-downloading the iso files. But the problem is there is no checksum info available along with iso. Is there any way to check if the cd/iso is broken, before burning to a disk?
Just taking a stab at this...
I had the same problems when I tried to install on an older system. More specifically I had mixed and matched RAM on the motherboard. The checksum would appear when I was installing bigger packages. I believe that the problem would be when it had to use both sticks of RAM. Run a memtest86 on them and make sure that the RAM are compatable with each other.
Once again, just a stab, I am a complete n00b at Linux.
Well, u r right. There r two RAM on my PC. Can u tell me:
1. How can I run a memtest86?
2. Both RAM works perfect on Windows so can it be a problem with Linux?
3. Will it work if I remove one of the two RAM while installation and put it back after?
4. Will it work if I connect the hard drive to my new pc, install suse and connect it back to the old one?
1. ) To run memtest86 I use a great tool called Universal Boot CD (UBCD). Download, burn the CD, reboot your system with the CD in the optical drive still, and run memtest86 (I believe) under the Memory page. It will run until you tell it to stop. I usually let it have about 20 passes before I reboot.
2.) No clue.
3.) As far as removing one, I believe that I tried that and it worked for me just fine until I found out that I bigger problems.
4.) From working on computers extensively with Windows, trying to put the hard drive in another system and installing then putting back in the original system has never fully worked for me. There has always been some sort of hardware conflicts. New to Linux so this may not be the case. Ask around.
the forum moderators don't want us to post download links in our posts since all of the currently available suse 9.3 downloads, even mine, are officially unofficial.
0. download suse 9.2 directly from novell.
1. wait several weeks, maybe months, until novell makes all of 9.3 available on their ftp. (parts of it are on their ftp now but not enough to do an install.)
2. keep looking around for 9.3.
Last edited by knetknight; 04-23-2005 at 05:48 AM.
DL the bittorent . burned the 5 iso,s md5 checksums are ok, but when i installed have problems with the unarchiving checksums.
Have not been able to complete an install on two different machines.