Doubt on boot process

msrpower · 09-27-2008, 11:49 AM

Hi,
my lilo.conf doesn`t have a path to initrd, besides i don`t have the file initrd.gz in /boot.
That means the the RAM Disk is not loaded by the lilo ?

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb1
  label = Linux
  read-only
# Linux bootable partition config ends

Thanks in advance.

jailbait · 09-27-2008, 04:49 PM

You don't need an initrd if the kernel was compiled specifically for your hardware configuration. What happens when you try to boot /dev/sdb1?

------------------
Steve Stites

msrpower · 09-27-2008, 06:15 PM

Quote:

Originally Posted by jailbait

You don't need an initrd if the kernel was compiled specifically for your hardware configuration. What happens when you try to boot /dev/sdb1?

------------------
Steve Stites

Hi, i`ve succesfully installed Slackware 12.1 on a external USB hard drive. It is located at /dev/sdb1. But when I try to boot it cannot find the correct partition.

Code:

VFS : Cannot open root device "811" or unknown block(8,17)
Please append a correct "root=" boot otion : here are the available partitions:
0300	4194302	   hda driver : ide-cdrom
0800	117220824  sda driver : sd
0801    117218304  sda1
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(8,17)

brianL · 09-28-2008, 06:46 AM

Quote:

Originally Posted by msrpower

Hi,
my lilo.conf doesn`t have a path to initrd, besides i don`t have the file initrd.gz in /boot.
That means the the RAM Disk is not loaded by the lilo ?

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb1
  label = Linux
  read-only
# Linux bootable partition config ends

Thanks in advance.

You only need an initrd if you change from using the default huge kernel to the generic kernel.

sundialsvcs · 09-28-2008, 10:04 PM

"initrd" is rather a bit of a hack...

Quote:

"A hack" is rather like 'a particularly elegant archway over the front entrance to a supermarket.'
It perfectly-satisfies the particular need that it was designed for, but you might prefer not to admit to having been the person who actually designed it...

The problem that the designers of Linux (distributions...) had to face is, "how can we manage for our operating-system to successfully boot itself ... one way or the other ... on 'any old-or-new piece of computer-junk on this planet?'"

You see, every "piece of computer-junk" (yours and mine...) consists of a peculiar set of hardware-devices, each one of which requires its own peculiar set of software-drivers. Therefore, in order to "not only 'work,' but 'work gracefully'," Linux needs to have some way to identify the hardware and load the proper set of drivers "on the fly!"

Once Linux has accomplished that, it can proceed to "boot normally."

In short, "that's what initrd does." And, yeah, "it's magic." Serious voodoo....

(This is also what gives you that nice, reassuring, graphic logon-screen that presents a nice splash-image and a progress bar that all but screams to you, "pay no attention to the little man behind the curtain...")

So... "I'm sorry to have spoiled 'the trick.' But, this is how 'the magic' is actually done." Now you know. Windows does it, OS/X does it, and Linux does it...