From: Robert Schwebel <robert@schwebel.de>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Configtool
Date: Wed, 06 Mar 2002 03:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0203061225380.13819-100000@callisto.local> (raw)
In-Reply-To: <20020306090512.G37@biferten.ma.tech.ascom.ch>
On Wed, 6 Mar 2002, Andrew Lunn wrote:
> Yes, ecosconfig. Its part of the host tools.
ecosconfig seems to be command line oriented only - is there no menu
driven text mode utility? It's rather difficult to find out how things are
meant to be, and the online documentation doesn't really help for all the
details...
Robert
--
+--------------------------------------------------------+
| Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de |
| Pengutronix - Linux Solutions for Science and Industry |
| Braunschweiger Str. 79, 31134 Hildesheim, Germany |
| Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 |
+--------------------------------------------------------+
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-03-06 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 0:03 Robert Schwebel
2002-03-06 1:02 ` Andrew Lunn
2002-03-06 3:28 ` Robert Schwebel [this message]
2002-03-06 3:44 ` Julian Smart
-- strict thread matches above, loose matches on Subject: below --
2006-11-17 4:22 [ECOS] configtool Larry Phillips
2005-11-03 15:04 Wang, Liu (Liu)
2005-07-22 17:14 Matt Sartori
2005-07-22 17:35 ` Andrew Lunn
2004-06-25 10:30 [ECOS] Fw: " David Lewin
2004-06-25 15:13 ` David Lewin
2004-06-25 8:09 [ECOS] One question anton yakovlev
2004-06-25 10:13 ` [ECOS] configtool David Lewin
2004-05-04 17:23 paape
2002-06-06 4:07 [ECOS] Configtool Chandra Sekhar, G
2001-11-22 1:19 [ECOS] ConfigTool Omar Khan
2001-11-22 3:46 ` Jesper Skov
2001-11-29 6:42 ` Jesper Skov
2001-11-29 6:26 ` Omar Khan
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=Pine.LNX.4.33.0203061225380.13819-100000@callisto.local \
--to=robert@schwebel.de \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-discuss@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).