Hello,

I built a custom linux monolithic kernel (RedHat 7.1 kernel 2.4). After
doing "make bzImage", I copied the newly created bzImage to
/boot/vmlinuz-2.4.2-2TONY and appended the following lines to
/etc/lilo.conf.

image=/boot/vmlinuz-2.4.2-2TONY
label=linux-TONY
read-only
root=/dev/hda5

However, on rebooting the PC, there is no change to the graphical user
interface of LILO ? Even if there's a problem with the kernel image, I
expected that at least a new line would've been created in boot options on
rebooting.

I was wondering what the problem could be becoz this procedure works with
"grub.conf" and Redhat 9.1.?

Thanks,
Tony

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Did you run lilo after you made the changes?

John Julian


-----Original Message-----
From: linux-admin-owner [at] vger.kernel.org
[mailto:linux-admin-owner [at] vger.kernel.org] On Behalf Of Tony Gogoi
Sent: Friday, April 02, 2004 12:09 PM
To: linux-admin [at] vger.kernel.org
Subject: /etc/lilo.conf



Hello,

I built a custom linux monolithic kernel (RedHat 7.1 kernel 2.4). After
doing "make bzImage", I copied the newly created bzImage to
/boot/vmlinuz-2.4.2-2TONY and appended the following lines to
/etc/lilo.conf.

image=/boot/vmlinuz-2.4.2-2TONY
label=linux-TONY
read-only
root=/dev/hda5

However, on rebooting the PC, there is no change to the graphical user
interface of LILO ? Even if there's a problem with the kernel image, I
expected that at least a new line would've been created in boot options
on
rebooting.

I was wondering what the problem could be becoz this procedure works
with
"grub.conf" and Redhat 9.1.?

Thanks,
Tony

-
To unsubscribe from this list: send the line "unsubscribe linux-admin"
in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

hi

if you have any questions first type 'man program_name' for
answers;) you should 'reinstall' lilo by using command ... 'lilo' :]
also you can use with option -v to make lilo more verbose.

Regards...
--
|Name.:.....................[Lukasz.Sztachanski]|
|WWW..:.......[http://rudy.mif.pg.gda.pl/~szati]|
|Mail.:............[szati<at>rudy.mif.pg.gda.pl]|

--5vNYLRcllDrimb99
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAbaDvAPX+CP2Pwf8RAuFQAJ9ZE+u6hSE/9+9g2xqClPjYTRTVcwCe Ppjf
z9PGR1r7ex7aIIKd/6vgdfs=
=ITLD
-----END PGP SIGNATURE-----

--5vNYLRcllDrimb99--
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

'label' line is meant to be before image isnt it? A bit like brackets in C
delimiting that description block...

On Sat, 03 Apr 2004 05:08, Tony Gogoi wrote:
| Hello,
|
| I built a custom linux monolithic kernel (RedHat 7.1 kernel 2.4). After
| doing "make bzImage", I copied the newly created bzImage to
| /boot/vmlinuz-2.4.2-2TONY and appended the following lines to
| /etc/lilo.conf.
|
| image=/boot/vmlinuz-2.4.2-2TONY
| label=linux-TONY
| read-only
| root=/dev/hda5
|
| However, on rebooting the PC, there is no change to the graphical user
| interface of LILO ? Even if there's a problem with the kernel image, I
| expected that at least a new line would've been created in boot options on
| rebooting.
|
| I was wondering what the problem could be becoz this procedure works with
| "grub.conf" and Redhat 9.1.?
|
| Thanks,
| Tony
|
| -
| To unsubscribe from this list: send the line "unsubscribe linux-admin" in
| the body of a message to majordomo [at] vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html

- --
2.4.24 on an i686 - Otherland

Logic is a little bird, sitting in a tree; that smells *_____awful*.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAbeGgKZRWL7vB/bERApiDAKCiVT7ZoP2OUM4A51Hdb+Q5QaRmGQCg 0c4Y
SYhF/JmlxAr34P0CYdX2+vE=
=2Qtj
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Glenn Enright wrote:

> 'label' line is meant to be before image isnt it? A bit like brackets in C
> delimiting that description block...

No. Each section starts with "image" or "other". "label" is an option;
if no label option is specified, the image's filename is used instead.

--
Glynn Clements <glynn.clements [at] virgin.net>
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 03 Apr 2004 10:44, Glynn Clements wrote:
| Glenn Enright wrote:
| > 'label' line is meant to be before image isnt it? A bit like brackets in
| > C delimiting that description block...
|
| No. Each section starts with "image" or "other". "label" is an option;
| if no label option is specified, the image's filename is used instead.

oops my bad :-p. dedicated grub user here...

- --
2.4.24 on an i686 - Otherland

"Jesus saves...but Gretzky gets the rebound!"
- -- Daniel Hinojosa (hinojosa [at] hp-sdd)


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAbjEdKZRWL7vB/bERAjMcAJwLhT+X/8No1QMdRuBYSDSFgCmNawCg riD9
T+OqCvBNsIVqRCLNxw6B9VI=
=ZZKQ
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html