From: Stephane Eranian <eranian@frankl.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] PXE Boot
Date: Wed, 16 Jan 2002 19:21:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805855@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805846@msgid-missing>
On Wed, Jan 16, 2002 at 11:15:57AM -0800, Michael Madore wrote:
> Stephane Eranian wrote:
> >
> > Mike,
> >
> > The problem is that the client side needs to know the size of the file
> > to allocate memory for it. By default, the TFTP protocol has no
> > command to ask for the size of the file. To work around the problem,
> > the client can load the file a few bytes at a time just to calculate
> > the size. Once the size is known, the allocation is done and the
> > file can be downloaded for real.
>
> I noticed that the tftp server logged two requests for elilo.efi. Does
> this look like a problem on the client or the server?
That is normal with a normal tftpd. Note that you don't see this for the
kernel because elilo.efi uses an internal cache to avoid asking for the
file again.
>
> > The ATFTP adds the support to ask for the file size, therefore you save
> > one download of the file. Note that elilo has the same thing when it
> > downloads any file from the network.
>
> Is aftpd required?
No I don't run it and I netboot everyday. I use the tftpd shipped with RH7.2.
--
-Stephane
next prev parent reply other threads:[~2002-01-16 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 18:21 [Linux-ia64] PXE Boot Luck, Tony
2002-01-16 18:23 ` Stephane Eranian
2002-01-16 18:24 ` Michael Madore
2002-01-16 18:49 ` Stephane Eranian
2002-01-16 18:56 ` Michael Madore
2002-01-16 18:57 ` Michael Madore
2002-01-16 18:59 ` Egan Ford
2002-01-16 19:13 ` Michael Madore
2002-01-16 19:15 ` Michael Madore
2002-01-16 19:21 ` Stephane Eranian [this message]
2002-01-16 19:29 ` Tolentino, Matthew E
2002-01-16 19:36 ` Dick Brown
2002-01-16 19:58 ` Michael Madore
2002-01-16 20:01 ` Michael Madore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805855@msgid-missing \
--to=eranian@frankl.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.