SlackwareThis Forum is for the discussion of Slackware 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.
fyi - I have searched the forum on this variation of dual boot woes with no luck....
I have been unsuccessful in tracking down the solution to my dual boot problems. I have an IBM(NTFS) drive with a booting win2k install on it (old server). I have a WD(EXT3) drive completely devoted to slack 8.1 (new server). I have reasons for wanting win2k to hang around; so, I'm trying to get them to play nice together. Here are my actions so far in the land of linux:
- partitioned the WD drive into separate /boot (50MB), / (3GB), /usr(7.5GB), /home(25GB), /tmp(1GB), and /var(1GB) partitions to control access and log growth.
- got slack 8.1 + video/sound/eth drivers working and booting on WD drive installed as /dev/hda (IBM drive unplugged, using mainboard IDE channel) -- thanks to this forum
- lilo was installed and working on MBR of WD drive
- since MB only has ATA33 I pop in my Promise U66 controller and plug both drives in - IBM(Win2k) as PriMast and WD(Linux) as SecMast -- I did this because I read that Win2k boot loader complained when not on PriMast
- the drives are now IBM (/dev/hde) and WD (/dev/hdg)
- rerun lilo to install to super block of /boot (/dev/hdg1)
- I can boot to Win2k fine and have tried multiple times to copy the first 512b of my /boot partition to a floppy and then onto c:\ of /dev/hde (IBM) for the win2k boot loader to use
- I have managed to successfully get L 01 01 etc (and L 80 80 etc once) oh, about 10 times now trying different locations of the root= , map=, and install= in my lilo.conf
- I can boot linux via the slack8.1 iso and pass "bare.i root=/dev/hdg3" at the boot prompt to get to my WD drive and linux install.
- yes I do run lilo after I change lilo.conf and I do recopy the appropriate 512b of boot partition to floppy (as bootsect.lnx)
I've lost quite a bit of sleep on this one as i'm stubborn and a sucker for a challenge (ie linux fan). But I'm querying the forum now as I really just want this server back up...in linux...
Any of you gurus have an example lilo.conf for something like this? or maybe something new to try?
How exactly are you booting into windows? Your using the Windows boot loader? Yet you want to still use LILO to boot into Linux? ummm, didn't the OLD lilo only do that...eg: you had to hit tab to boot into linux, otherwise if its left it boots into windows...or is this the sort of setup you have/want?
What i do is just let lilo be my main, and only, bootloader. I install lilo into the MBR of the first HDD, and select either Windows or Linux from the menu...
Copy the file /bootsect.lnx to the same directory as your ntldr. There will be a boot.ini (hidden) in the same directory. Add this line to it. C:\bootsect.lnx="Linux" If you comment out the lines as in my lilo.conf it will cycle through lilo and load the kernel.
1) linuxcool - I have an updated fstab to reflect the hda->hdg change...guess i should have listed that above
2) grim - I am using the ntldr to load the system and would like to use it to boot into linux as it is working at the moment. I was under the impression I still needed to use lilo to set the first 512b of the boot partition (the part I copy to a file and reference in my boot.ini file)
3) Allen614 - I have tried the dd command before. And I get the L 10 or L 80 messages. In your lilo.conf, why is your vmlinuz in / rather than /boot ?
What it comes down to I guess is when I copy the 512b of the boot partition (bootsect.lnx) does that come from /boot or /. As I have seperate partitions for those I'm thinking that may be my problem. Ideas?
Right now using lilo, the main settings I have in lilo.conf are:
My "vmlinuz" was placed in the on the original kernel install.(Slackware} My /boot is not a partition but a directory. Those error messages indicate that lilo is not installed in the first 512 but that they're not set. IMHO making /boot a partition just complicates the process. Is your /boot partition the first partition? Try "fdisk -l hdg" and see what it returns.
Here's a thought. You're trying to copy bootsect.lnx to a NTFS partition. I believe the ntldr creates the MBR as FAT to be compatible with dual booting FAT32. Unless you've a FAT32 partition to copy the bootsect.lnx on you may be forced to use Lilo. All my Windows OSs as FAT32.