suse boot issues

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Ted Gould
Date:  
Subject: suse boot issues
--=-KFXDHazqCwbnQgo5lGfH
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2003-10-04 at 16:06, betty wrote:
> hi ted;
> i am running redhat 9.
> here is what came out when i pico etc/grub/config
>=20
> #NOTICE: You have a /boot partition. This means that all kernel and=20
> initrd paths are relative to /boot/, eg. root (hd0,0)
> kernel /vmlinuz-version ro root=3D/dev/hda2
> initrd /initrd-version.img
>=20
> boot=3D/dev/hda
> default=3D0
> timeout=3D10
> splashingimage=3D(hd0,0)/grub/splash.xpm.gz
> title Red Hat Linux (2.4.20-8)
> root (hd0,0)
> kernel /vmlinuz-2.4.20-8 ro root=3DLABEL=3D/ hdc=3Dide-scsi
> initrd /initrd-2.4.20-8.img
>=20
> does that make any sense or help?


Yeah, thanks Betty.

What this is saying is to use the initrd which is named
/boot/initrd-2.4.20-8.img. The initrd is the initial RAM disk that
Linux uses to boot up. These are the first utilities that are used, and
then the rest of the drives will be there later. Not all kernels
require this (I understand it will be more common under 2.6) but this is
how Redhat has chosen to do their boot.

So, I think the comand line option needed to boot under Suse would be
initrd=3D/boot/initrd-2.4.20-8.img.

        --Ted



--=-KFXDHazqCwbnQgo5lGfH
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

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

iD8DBQA/f6lDLE335pRPGp0RAv3hAKD5o3HvtPQQ6rL+s/TNKKRwQN3sCQCeITJK
N5UX5vtyumCRTaMuCXqaAVc=
=IYRl
-----END PGP SIGNATURE-----

--=-KFXDHazqCwbnQgo5lGfH--