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.
Ongoing quest for a dual boot rig. I've installed Red Hat 8.0 to a 2nd hard drive on my system (IDE, Primary Slave drive). I installed without a boot loader and created a boot floppy. Booting from the floppy works flawlessly.
However, I don't want to boot from the floppy, I want NT (W2K in this case) Boot Loader to present me with a list of available OS's, and choose from there. If you look all over the net for dual boot instructions, you find many variations of this procedure:
--Log in as root. Look at /etc/lilo.conf and make sure the default boot location is indeed where you installed. If not, you can change it and apply by running lilo.
(I tried to look at this file, it does not exist in this location)
(where HDxx equals the /boot partition of Linux, in my case, /hdb1, verifed by using the df command to check partitions)
This takes the first 512 bytes from the partition holding the boot record, and puts it into a file called bootsect.lnx. Replace /dev/hdc1 with the partition you used.
When I do this, I get a message that says:
1+0 records in
1+0 records out
The goddam documentation that's out there says NOTHING AT ALL about what that is supposed to mean!!!
-- mcopy that file to your _DOS_ floppy (don't forget to mount it first):
# mcopy bootsect.lnx /mnt/floppy
-- Restart your machine, no floppies. The W2k loader should show "normally" and get you right in to W2k.
-- Add an entry for W2k boot loader.
-- In a command shell, copy the file a:\bootsect.lnx into c:\.
-- Add a line to the end of boot.ini to read 'c:\bootsect.lnx="Linux"'
Well, I've done all that, many times, and when I try to boot to Linux, I get "Invalid boot partition" message.
I've got dual boot to work in the past, and when I did, the 1+0 message instead read 1+1 , not 1+0. I think it was back on an old version of Mandrake, using SCSI disks. However, now I am using IDE. In a word, why won't these supposedly simple procedures work for me???
(I tried to look at this file, it does not exist in this location)
Lilo and the Lilo configuration file need to exist on your hard drive -- you have them on your floppy, but not your hard drive. What you have copied to the bootsect.lnx file is just whatever random code exists in the boot sector of your Linux partition, which is probably no code at all. Thus, you get the "Invalid boot partition" message from Windoze.
You need to copy the lilo.conf file from your floppy to /etc/lilo.conf. Then edit it to refer to the correct hard drive partition locations and run /sbin/lilo -v. The "-v" option on the lilo command will show any errors on your screen. You want to make sure that lilo is targeted to the Linux partition where it can find the lilo.conf file and to where lilo wrote it's boot sector code.
I looked at my floppy under Linux, the only files on it are:
boot.msg, initrd.img, ldlinux.sys, syslinux.cfg, and vmlinuz. In case it matters, the syslinux.cfg file reads:
append initrd=initrd.img hdd=ide-scsi root=/dev/hdb2"
What's my next move? Thanks for posting...I think this is a step in the right direction.
The quoted part of the syslinux.cfg file does belong in your /etc/llilo.conf file. But you also need more info telling Lilo where to load the boot code -- such as a reference to the boot sector of your linux space ("hdb1", I believe).
You might want to read up on Lilo here at the mini-Howto.
Originally posted by billmaly I'm thinking about that...just don't want to hose up my existing W2K MBR like I did last time. Of course, I aborted install because I had a bad CD3. That probably didn't help!
Once again into the breach dear friends!!
There is no such thing as a W2K MBR. W2K does have boot code in the boot sector of its partition that ends up calling the W2K kernel (via ntldr). The MBR, in the instance when Windoze is the only OS and no other boot manager is present, contains nothing but partition addresses and about 490+/- bytes of very vanilla code that refers the BIOS and its bootstrap loader to the correct bootable partition.
Do not fear installing Lilo or Grub code to the MBR. The W2K ntldr will, of course, also work well enough but it does involve a higher level of complexity during the installation.
Reinstalled Red Hat, but this time, I installed LILO on /hda (where W2K resides), and set it up so that W2K is my primary OS (I'm not ready to make the leap, yet). I can't quote EVERY step I took, but I was cautious and made sure I understood every step before I took it (still, was nervous). Well, upon reboot, the ugly ass LILO screen comes up, giving me options for W2K and Red Hat. I can boot to both WITHOUT a boot floppy. Victory...moral of the story, let the installer do the work for you, especially if you are a Linux n00b.
since you dislike the lack of flashiness of LILO, you may consider using GRUB as a boot loader (GRand Unified Boat Loader). It's a little newer than LILO and might be easier to use. However, i see that you have it working so you may just want to leave well enough alone.
You'd think I'd leave it alone...I upgraded my NVidia drivers, then rebooted. Uh oh....where did X go? And what are those odd characters on my screen?? I did something bad....i'll reinstall and revisit tomorrow.
Also, during today's install, it was slow...I was afriad it had locked up, but I walked away and came back, and progress had occurd. Weird.
I read the instructions (at least some of them) off of NVidia's site, but I'll confess...I did not edit a file. Perhaps in my n00bish exuberence to play Tuxracer, I got ahead of myself and went to quickly. My very very bad. What (in a nutshell) needs to be editied?