Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
To open lilo.conf with vi, you would just type "vi lilo.conf" (no quotes). Enter insert mode (hit "i"), make your changes, and exit insert mode by hitting <esc>. Save your changes and quit by typing ZZ.
If it still yells at you about permissions, do "ls -l /etc/lilo.conf" and post the output.
Also, did you log in as root, or did you su to root? If su, try "su -" instead.
Seemed to work, but now only linux would boot.
I am set to /dev/hda5 and am trying to get system commander 2000 to allow me to boot to linux as an option....but it always says that the boot record is missing....(I had to restore the System commander MBR by the way)
So, I have system commander, which can boot winxp and win98se, and I can boot linux it I use the SuSE bootdisk.
that sucks though, (I just want to figure out how to do this anyways, without having to use the disk, or INSTALLING Linux first, then System commander, then windows)
like you said, but THAT boots me to linux and only linux, I have to
restore SC 2000 mbr to fix that.
Being that I am still getting my feet wet with SuSE...
(GREAT Look and feel by the way, I didn't know what I was missing with Linux) I don't know how to copy, rename, stuff like that.....
I will tell you EXACLTY how System Commander 2000 words it.
[All credit given to V-Com]
--------- "System Commander 2000 is fully compatible with Linux.
To Boot Properly into Linux, we recommend having LILO's Target location set to the root superblock. [ IS THAT THE SAME THING?]
This option is typically selected from within linux while installing linux, [DID IT DURING INSTALL, /dev/hda5 SAME ISSUE] For the fastest and easiest boot, we suggest having LILO boot linux, and no other OS.
To install LILO to the root superblock [IS THAT ROOT FOR SHORT?]
on an existing partition, modify the LILO configuration file, typically /etc/lilo.conf, so that the boot= line refers to your linux root partition, and not your first hard disk: ie boot=/dev/hda5 instead of boot=/dev/hda
After Editing the LILO.conf file, you must run the LILO program (typically /sbin/lilo)"
****Okay, I did try the above, and some of your suggestions (to you DMR) I put in "ls -l /etc/lilo.conf"
and I get this:
-rw------ 1 root root 613 Dec 1 01:30 /etc/lilo/conf
System commander also offers this option.... this is probably what I will have to do.....How do I copy and save from a terminal though? :
-----------"In very rare cases, an operating system fails to follow the pc architecture [Good one V-com, way to blame the SW]
standard and requires it's own master boot record...(MBR) to boot properly. The only two cases we've encountered are the pSOS operating system, and Linux's Optional LILO Mbr Intstall. Linux is normally installed with a partition boot (called the superblock in Linux terminology) and should not need this MBR File feature.
To setup the MBR Boot selection, you will need a binary file image of the MBR. If the OSes MBR was installed prior to System Commander 2000, we will have saved the MBR in the BOOT.DAT
Please copy this to your root directory."
What would I make of this....I don't know enough about linux to know where to start....
Last edited by tmnt_power; 12-02-2001 at 07:50 PM.