|
L i n u x H e l p
: :
: :
: :
: :
|
How to Dual Boot Linux and Windows with LiLo
Well, if you're here, it's because you're not sure how to get your new linux box to cohabitate with windows. Actually, it's pretty simple, so read on and I'll take you through the basics.
The first thing that you need to understand is how linux looks at disk partitions. I assume that since you've gotten this far, you have a bit of an idea how partitions work so let's run with it.
/dev/hda is the first hard disk (Primary IDE Master). The first partition on this disk is /dev/hda1 the second is /dev/hda2 and so on.
/dev/hdb is the second hard disk (Primary IDE Slave). This disk is partitioned the same as hda was, /dev/hdb1 /dev/hdb2 etc...
Your secondary master and slave are /dev/hdc and /dev/hdd, respectively. This is just for your information, as you probably won't be booting from these devices. /dev/hdc will normally be your CDROM drive.
So lets assume (I like to do that) that we have a system with one hard disk, and linux is installed on the first partition ( /dev/hda1 ) and windows is installed on the second partition ( /dev/hda2 ). This is a rather simplistic way of doing it, you may have more than one linux partition, but we're going to keep it simple.
Here is a sample /etc/lilo.conf that goes along with the assumption that we made in the previous line:
#/etc/lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
# Linux Partition
image=/boot/vmlinuz-2.2.12-20
label=linux
initrd=/boot/initrd-2.2.12-20.img
root=/dev/hda1
read-only
# Windows Partition
other=/dev/hda2
label=win
table=/dev/hda
Once you have edited lilo.conf to suit you, you need to run '/sbin/lilo' and it looks like this:
[root@panic krnl]# /sbin/lilo
Added linux *
Added win
The asterisk indicates that the linux label is the default boot image and that after the timeout expires, your machine will automatically boot into linux.
That's about it! I hope you have found this helpful. If you have any other questions, I can be found on Undernet in #linux or #linuxhelp.
-KrnlPanic
|
|
|
|
|
L i n u x W o r l d N e w s
: :
: :
: :
: :
|
|
|
What in the hell is a KrnlPanic? Well, a KrnlPanic is me! Actually, let's start with "What is a kernel?". The
kernel is the core of your operating system (OS), whether your OS is Linux, Unix or windows. The kernel takes
care of all process management (what program runs and when), memory management (which parts of memory get used for what) and
also, the kernel takes care of interfacing the OS with your computer's hardware (disk drives, sound card, modem, network card, etc).
Now...since the kernel is doing all of these extremely important jobs, it stands to reason
that if it has an error, it will be a Bad Thing(tm).
If you use windows, you know a kernel panic as a "BSOD" or Blue Screen of Death. Or how about "Invalid Page
Fault in KERNEL32.DLL". I'm sure you've probably seen both of those. In Linux, a Kernel Panic is normally plainly stated
so. At boot time is when you will see most linux panics. I have yet to see a linux kernel panic while the system is running.
You may have seen "Kernel Panic: init not found" or "Kernel Panic: VFS unable to mount root fs on 2:00". All of these previously
listed errors are because of something that happened to the kernel that it couldn't handle, whether it was an access to an
invalid memory location or the inability to find the initialization files it requires.
I hope that sufficiently explains things. Oh yeah...KrnlPanic is also my name ;-)
- Rick
|
|
|
|
|
|
S l a s h d o t / F r e s h m e a t
: :
: :
: :
: :
|
Slashdot and Freshmeat Headlines at 1219201315
(Unixtime)
|
|
|
|
