From: Andrew Lunn <andrew@lunn.ch>
To: David Vrabel <dvrabel@arcom.com>
Cc: "Doyle, Patrick" <Patrick_Doyle@dtccom.com>,
'Andrew Lunn' <andrew@lunn.ch>,
"'ecos-devel@sources.redhat.com'"
<ecos-devel@sources.redhat.com>,
'Andrew Dyer' <adyer@righthandtech.com>
Subject: Re: RedBoot patches regarding redboot_getc_terminate
Date: Thu, 18 May 2006 15:14:00 -0000 [thread overview]
Message-ID: <20060518151236.GE11223@lunn.ch> (raw)
In-Reply-To: <446C8BE9.10503@arcom.com>
> I'm not entirely happy with the fix. It terminates the download when all
> the relevant bits of the ELF have been transferred. The causes the
> sender to think that the file transfer has failed which causes some
> customer confusion.
It is possible to include a text string in the error message.
http://www.faqs.org/rfcs/rfc1350.html, figure 5-4.
So maybe a message like "Remaining file contents not required" would
prevent confusion. This assumes the lame tftp servers actually display
the message to the user.
> I think a better solution would be for the downloader to continue to
> transfer the remaining portions of the ELF image and just throw them away."
This can be a lot of data, eg the complete debug symbol table if the
image has been compiled -g. I would not really be in favor of that.
Andrew
next prev parent reply other threads:[~2006-05-18 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 13:40 Doyle, Patrick
2006-05-18 13:54 ` Andrew Lunn
2006-05-18 15:00 ` David Vrabel
2006-05-18 15:14 ` Andrew Lunn [this message]
2006-05-18 15:59 ` David Vrabel
-- strict thread matches above, loose matches on Subject: below --
2006-05-20 0:08 Andrew Dyer
2006-05-18 16:59 Doyle, Patrick
2006-05-18 13:32 Doyle, Patrick
2006-05-18 13:18 Doyle, Patrick
2006-05-18 13:26 ` Andrew Lunn
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=20060518151236.GE11223@lunn.ch \
--to=andrew@lunn.ch \
--cc=Patrick_Doyle@dtccom.com \
--cc=adyer@righthandtech.com \
--cc=dvrabel@arcom.com \
--cc=ecos-devel@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).