CentOS - Mar 2005 - [fixed] PXE boot Centos 4.0 problems

"MH" == Martin Hamant <mh@accelance.fr>

    MH> How did you named your kernel & vmlinuz ? :))) (ex: you
    MH> have to name it centos-4 , NOT centos-4.0 !! )

Wacky.  That doesn''t appear to be a problem with the Broadcom PXE
code on the Dells -- they still boot even with kernel and initrd
named like

   centos-3.3-initrd      centos-3.3-kernel
   centos-3.4-initrd      centos-3.4-kernel
   centos-4rc1-initrd     centos-4rc1-kernel
   centos-4.0-initrd      centos-4.0-kernel

I do have links with names like

   centos-3-initrd      centos-3-kernel
   centos-4-initrd      centos-4-kernel

that I reference in my PXE configuration files, but I tested one
machine with the dotted names, and it still works.

   Claire

--
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
  Claire Connelly                              cmc@math.hmc.edu
  Systems Administrator                          (909) 621-8754
  Department of Mathematics                 Harvey Mudd College
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url :
http://lists.caosity.org/pipermail/centos/attachments/20050314/065a36e5/attachment.bin

>    centos-3.3-initrd      centos-3.3-kernel
>    centos-3.4-initrd      centos-3.4-kernel
>    centos-4rc1-initrd     centos-4rc1-kernel
>    centos-4.0-initrd      centos-4.0-kernel
these will work fine.  the problem is with names like
     linux-kernel-2.6.0
     kernel-centos-4.0
where the .0 is take to be a file extension meaning a special type of
file... and the problem is only with the kernel image (which is booted by
pxe) not with the initrd (which although booted by pxe doesn''t require
extensions to determine it''s an initrd since it''s specified as
such in the
configuration file).

Cheers,
MaZe.

On Tue, 15 Mar 2005 02:05:58 +0100 (CET)
Maciej _enczykowski <maze@cela.pl> disait:

> where the .0 is take to be a file extension meaning a special type of
> file... and the problem is only with the kernel image (which is booted
> by  pxe) not with the initrd (which although booted by pxe doesn''t
> require  extensions to determine it''s an initrd since
it''s specified
> as such in the  configuration file).
Do you mean that you knew something about this issue ???? :)))))

--
Martin

> > where the .0 is take to be a file extension meaning a special type of
> > file... and the problem is only with the kernel image (which is booted
> > by  pxe) not with the initrd (which although booted by pxe
doesn''t
> > require  extensions to determine it''s an initrd since
it''s specified
> > as such in the  configuration file).
>
> Do you mean that you knew something about this issue ???? :)))))
It merely means that now that someone''s mentioned the .0 I can recall
having run afoul of it once before - nothing worked with FC2 and a custom
kernel simply because I''d named the kernel file kernel-2.4.26.0 or
something like that (I can''t actually remember what version of the
kernel and what filename I used, but it did end with a ".0") :)
This was of course at 3AM when setting up a farm of computers for a
programming contest starting up at 9AM :)

Cheers,
MaZe.