Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 have installed Redhat Linux and Windows 2003 Server on my machine and both are on seperate hard drives and it is setup to dual boot and it does this just fine. However... When you select to boot up Linux it just sits there with GRUB on the screen obviously waiting for the boot disk (and when you put the boot disk in it boots just fine). I am wondering why in the hell I even need a boot disk to boot linux. I mean this isn't practical. I don't want to have to boot Linux with a boot disk at all. I want it to boot up without any disk. I am wondering if anyone can help me in telling me how I can make it so I DO NOT need a boot disk. Maybe I am missing something but needless to say can anyone help me?
Last edited by EVO VIII Chris; 01-17-2004 at 10:18 PM.
Also, here is the contents of my grub.conf file so that you all may help me better...
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda6
# initrd /initrd-version.img
title Red Hat Linux (2.4.18-14)
kernel /vmlinuz-2.4.18-14 ro root=LABEL=/
I will try and explain this as best I can very simply as well. I start up the computer and after the BIOS loads and everything it just sits there with the word GRUB blinking on the screen. Now on the other hand if you start the computer with the GRUB boot disk I created during the installation of Redhat it will boot up Linux just fine! So basically when you don't have the boot disk to boot Linux it just sits there with GRUB on the screen. Also can you tell me if all Linux systems by default are meant to boot with a boot disk? And if so why? Im really new to Linux.
Last edited by EVO VIII Chris; 01-17-2004 at 10:16 PM.
Hmm, I never liked Grub, it always gave me troubles. Is it flashing in a pattern or anything? Or does it repeat anything other than just flashing GRUB? Have you looked through RH's forums? I'd imagine this problem would be fairly easy to look up over there.... Does Grub load at all? Is it how you choose whether to use Windows or RedHat? If it doesn't load at all, I think you made a mistake in where you installed it. I have to always install my bootloaders on my MBR.
grub does have some nice features though r_jensen... cause if you screw up your config file you can still boot it with manual commands in the grub command line.... and it actually understands how to read the filesystems. So if you try and boot a kernel that just plain ain't there it'll let you look through the file system and find where it really is.
Originally posted by jtshaw grub does have some nice features though r_jensen... cause if you screw up your config file you can still boot it with manual commands in the grub command line.... and it actually understands how to read the filesystems. So if you try and boot a kernel that just plain ain't there it'll let you look through the file system and find where it really is.
Uhh, I'd feel hesitant if my bootloader tried to boot a random kernel if it didn't find the one I had it pointing to. Maybe that's just me, though. I do like the option to use command-line booting, but if you know how to set up Lilo properly, you shouldn't have any problems. And just in case you do, there's always a bootdisk so you can fix lilo.