lilo

lilo

[Tom Beer]

Hi,

I just compiled a new kernel. Now I have
the vmlinux file in /usr/scr/linux-2.4.18/linux/arch/i386/boot/vmlinux
If I copy the file to boot and edit the /etc/lilo.conf
and run a lilo -t -v  it says file too big.
If I cp bzImage to /boot/ as vmlinux it issues 
vmlinux-2.4.18-initrd.img not found.
Could anyone explain to me how to
get the right files in the /boot directory and run lilo on it.
I read the Kernel howto, but either something is missing
or I don't understand it (I favor the last alternative :-)
and I don't want to make an error.

Thanks in advance Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: lilo

[Steven Smith]

[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]

> I just compiled a new kernel. Now I have
> the vmlinux file in /usr/scr/linux-2.4.18/linux/arch/i386/boot/vmlinux
I would ignore this, to be honest. bzImage is usually a better bet.

> If I cp bzImage to /boot/ as vmlinux it issues 
> vmlinux-2.4.18-initrd.img not found.
> Could anyone explain to me how to
> get the right files in the /boot directory and run lilo on it.
The only file you usually need in /boot is the bzImage, and that can
just be cp'd in:

cp arch/i386/boot/bzImage /boot/bzImage.2.4.18

(or use some sensible destination name). System.map is also occasionally
useful, but not very often.

You then need to add an entry to lilo.conf. If you're not doing
anything clever (like an initial ram disk), the entry usually goes:

image=/boot/bzImage.2.4.18
	label=test
	read-only

I've never needed to add anything more than that, once the rest of
lilo.conf is set up.

The big exception is initrd. This is a disk image loaded by LILO,
and is used by some recent distributions to store modules needed to
access the real root filesystem. For custom built kernels, you almost
never need this, as you can just compile the essential modules in.
You might want to check in the lilo.conf that you're not trying to
load a non-existent initrd, and, if you are, stop. Make sure you don't
change the old image's initrd, though, or it won't work.

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: lilo

[Tom Beer]

Two follow ups, if I may.

I can't locate the relevant initrd. 
Where can I find it, just to get everything
correct.
The second is under /usr/src
is, as normally, a symbolic link to
my old kernel. Should I change this to the
new one, if this is the primary, or is this
not relevant?

Thanks Tom

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: lilo

[Tom Beer]

I'm using Redhat 7.0 and there
should be a way to get it running.
It fits on a disk. I think that I
can't get the lilo process in my head 
(and I hope so). I compiled many things
as modules and the kernel 2542462 big.
But isn't there a way to install the bzImage?

Greets Tom




-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: lilo

[Steven Smith]

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

> It fits on a disk.
Have you tried running the kernel off of a floppy? That would at
least confirm it's working.

> I compiled many things as modules and the kernel 2542462 big.
That's a big kernel. Do you mean vmlinux (which could be that large)
or bzImage (which shouldn't be)?

> But isn't there a way to install the bzImage?
Usually, you go:

cp arch/i386/boot/bzImage /boot/bzImage.2.4.18

and add a section to lilo.conf:

image = /boot/bzImage.2.4.18
	label = some_label
	read-only

before rerunning lilo:

/sbin/lilo -v

If that doesn't work, then please post the output and the contents of
your lilo.conf to the list.

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: lilo

[Jos Lemmerling]

On Sat, 27 Apr 2002, Tom Beer wrote:

> I'm using Redhat 7.0 and there
> should be a way to get it running.
> It fits on a disk. I think that I
> can't get the lilo process in my head 
> (and I hope so). I compiled many things
> as modules and the kernel 2542462 big.

just to make sure: you did use "make bzImage" while compiling? _Normally_ 
a kernel-image isn't much bigger than 1 MB.

> But isn't there a way to install the bzImage?

if it's really called bzImage, it should be compressed (at least on my
system...) and there shouldn't have to be a problem with his size.


HTH

--
Jos Lemmerling on Debian GNU/Linux			jos(@)lemmerling(.net)

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: lilo

[Ray Olszewski]

Tom -- Your description of your problem is a bit too elliptic to get good
answers. (I think the range of responses from others who have posted
illustrates how unclear your questions are ... people are trying hard to
guess your meaning.)

At 06:56 PM 4/27/02 +0200, Tom Beer wrote:
>I'm using Redhat 7.0 and there
>should be a way to get it running.

There certainly should. Many ways, usually.

>It fits on a disk. 

What is "it" and what do you mean by "a disk" (a floppy, a hard disk
partition, or a CD)? 

>I think that I
>can't get the lilo process in my head 
>(and I hope so). 

Huh?

>I compiled many things
>as modules and the kernel 2542462 big.

What do you mean by "the" kernel? That's a chubby kernel even *after* it is
uncompressed to run. More to the point ... how large is the actual bzImage
file you created?

>But isn't there a way to install the bzImage?

Install it on what?

On a floppy? Sure. You can just dd it to the floppy for a crude boot.

On a hard disk partition? Well, not really; here you do require a bootloader
like LILO or GRUB. The usual way to do it is to cp the bzImage file to a
suitable place (/boot is the custom), edit /etc/lilo.conf so it identifies
the new image as the one to boot from, and run lilo.

Some kernel Makefiles have a "make install" option that puts the bzImage or
zImage where it needs to be; I don't know if whatever kernel RH 7.0 used did
this.


--
------------------------------------"Never tell me the odds!"---
Ray Olszewski                                        -- Han Solo
Palo Alto, CA           	 	         ray@comarre.com        
----------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs