From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Notes on static configuration of an eCos network interface
Date: Thu, 20 Jul 2000 07:00:00 -0000 [thread overview]
Message-ID: <pt3dl4di4y.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <25482.963837944@raven.ravenbrook.com>
Hi Nick; I've finally made time to have a read at that. I'll probably put
in some of your requests/recommendations, thanks, all good stuff.
One specific comment springs to mind:
> 5.1. Config tool
>
> Assuming the simple situation, with a default router and without
> multiple static routes. Then the config tool should be set up to
> allow the specification of:
> ....
> and _not_ "server", which is a meaningless idea in the absence of BOOTP.
Indeed it is meaningless BUT several of our test programs use the server
address as "someone to talk to" so it's worth IMHO having it settable in
static configurations. Eg. ftp test, tftp test, ping tests and the like
expect the "server" to be a nice freindly chap.
So I'm definitely leaving it in, but with more comment to that effect...
- Huge
next prev parent reply other threads:[~2000-07-20 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 5:45 Nick Barnes
2000-07-17 6:59 ` Bart Veer
2000-07-17 7:07 ` [ECOS] Notes on static configuration of an eCos network inte Gary Thomas
2000-07-18 5:52 ` [ECOS] Notes on static configuration of an eCos network interface Nick Barnes
2000-07-18 8:03 ` Grant Edwards
2000-07-17 8:52 ` Grant Edwards
2000-07-17 9:03 ` [ECOS] Notes on static configuration of an eCos network inte Gary Thomas
2000-07-17 9:28 ` Andrew Lunn
2000-07-17 9:40 ` Grant Edwards
2000-07-17 9:47 ` Andrew Lunn
2000-07-17 9:29 ` Grant Edwards
2000-07-17 9:45 ` Gary Thomas
2000-07-17 10:01 ` Grant Edwards
2000-07-17 9:45 ` [ECOS] Notes on static configuration of an eCos network interface Hugo 'NOx' Tyson
2000-07-20 7:00 ` Hugo 'NOx' Tyson [this message]
2000-07-20 9:57 ` Bart Veer
2000-07-20 11:00 ` Hugo 'NOx' Tyson
2000-07-20 11:19 ` Bart Veer
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=pt3dl4di4y.fsf@masala.cygnus.co.uk \
--to=hmt@cygnus.co.ukx \
--cc=ecos-discuss@sourceware.cygnus.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).