From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: bartv@redhat.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Which packages are needed for networking?
Date: Fri, 16 Feb 2001 11:19:00 -0000 [thread overview]
Message-ID: <3A8D7CE9.8A8067C2@larwe.com> (raw)
In-Reply-To: <200102161801.f1GI1do07795@sheesh.cambridge.redhat.com>
Hi Bart,
> And quoting from the TCP/IP documentation at
> http://sources.redhat.com/ecos/docs-latest/tcpip/tcpip.3.html#pgfId=1133601
>
> "In general, using the networking code may require definition of two
> symbols: _KERNEL and __ECOS. _KERNEL is not normally required; __ECOS
Ouf. And I thought I had read the introductory portions of the documentation
carefully. Sorry about that, and thanks for the analysis :)
> Usage: ecosconfig [ qualifier ... ] [ command ]
> commands are:
> list : list repository contents
> <snip>
If you imagine the packages as being in a tree (like the tree control in the
graphical configtool) then ecosconfig list gives a "trunk" without dependency
descriptions or sub-options.
I guess what I'm really looking for boils down to "the graphical configuration
tool". I think I will run the graphical tool on my Windows desktop system here so I
can refer to things and know how to drive my Linux dev box. It gives me a better
idea of the relationship of the various packages.
> packages and targets in the current system. Alternatively you can look
> at the ecos.db file in any text editor, since that is where the
> information comes from.
Right, that is where I look now. I then need to go down into the sub-files in order
to extract some of the "implicitly adds xxx..." type info though.
-- Lewin A.R.W. Edwards (Embedded Engineer) * Linux system
Work: http://www.digi-frame.com/
Personal: http://www.larwe.com/ and http://www.zws.com/
next prev parent reply other threads:[~2001-02-16 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 9:09 Lewin A.R.W. Edwards
2001-02-16 10:01 ` Bart Veer
2001-02-16 11:19 ` Lewin A.R.W. Edwards [this message]
2001-02-16 11:55 ` [ECOS] Still having problems getting networking up Lewin A.R.W. Edwards
2001-02-16 12:30 ` Gary Thomas
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=3A8D7CE9.8A8067C2@larwe.com \
--to=larwe@larwe.com \
--cc=bartv@redhat.com \
--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).