Bug#140579: Report: tftpboot install successfull
Le ven 03/01/2003 à 02:37, Chris Tillman a écrit :
> On Thu, Jan 02, 2003 at 10:33:36PM +0100, nb wrote:
> > Le jeu 02/01/2003 à 06:25, Chris Tillman a écrit :
> > > On Tue, Dec 31, 2002 at 03:50:56PM +0100, nb wrote:
> >
> > 192.168.1.255 would be better
>
> OK, got that.
>
> > In chapter 4.5.5 it is said that "the TFTP client will look for is
> > client-ip-in-hexclient-architecture". It is completely wrong.
> > In our case the "default" file is sufficient.
> > In fact it will try : C0A801 (192.168.1.200 in little endian as in x86)
> > then : 0A01010C8
> > then : 0A01010C
> > then : 0A01010
> > .
> > .
> > .
> > then : 0
> > and finally : default
>
> I take it that is wrong for PXE, but is it wrong for other methods
> of booting? Does it depend on the tftp server chosen or something?
It's also wrong for netboot which needs an image and a root fs added to
with mknbi. These are the two methods I practised.
--
nb <nb@dagami.org>
Reply to: