Suse/NovellThis 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.
And the third one has 1 primary ntfs then under and extended partition has a mandrake linux partition and a swap partition.
But now when I lock in, I can even get to X...
It stops halfway through saying that fsck failed.
Scanning for LVM volume groups
Reading all physical volumes
No physical volumes found
Activating LVM volume groups
No volume groups found
Checking File Systems
fsck 1.34 (25-July-2003)
fsck.ext3 No such device or address while trying to open /dev/hdg5 (or hdc5)
Possibly non extistant or swap device?
fsck.ext3 /dev/hdg5 (or hdc5) failed (status 0x8). Run Manually!
blogd: no message logging because /var file system is not accessible
Then it says some other crazy jibberish about USB (which i havent got enabled anyway)
fsck failed. Please repair manually and reboot. The root
files system is currently mounted read only. To remount it
read write do:
bash# mount -n -o remount,rw /
So I do exactly as it says and it does the same thing next reboot.
I also tried changing the disk names in fstab... like put them all to the letters they should be. i.e hdg5 to hdc5 but to no avail. It just did the same thing.
I'm going to go search the forum and suse portal for this problem now, but incase I dont find anything I wrote it here for anyone whos had the same problem or if anyone already knows a link.
But one more thing: you do not need to edit the grub.conf or menu.lst in order to pass those parameters to the kernel. In suse, you can type them into the boot menu directly (just type as soon as the menu appears).
Originally posted by aus9 or I have misunderstood the SECRETS of suse? heh heh
No, you did not ;-)
I just mentioned this possibility for testing the parameters. It makes the whole thing much easier when you do not know if the parameter will show the desired effect. Changing config each time you want to try something new is a pain in the ass, especially if the system does not boot with the new parameters. Once you know it will work, you make the changes permanent by adding them to the config.