linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: bsimon@ctam.com.au
Cc: linux-embedded <linux-embedded@waste.org>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linux-embedded: which shell, termcap or ncurses ?
Date: Tue, 21 Dec 1999 12:44:59 -0500	[thread overview]
Message-ID: <385FBC9B.E80D568@netx4.com> (raw)
In-Reply-To: 385EE46B.1D97C2D2@ctam.com.au


Brendan Simon wrote:


> ... I now need to get a shell running so I can call shell scripts to
> setup the IP addresses etc via ifconfig (is there any other way ?).


Why don't you just use the binaries from a standard distribution?
I try to use as much of this as I can, and it seems to make the
job easier for me.



	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-12-21 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-21  2:22 linux-embedded: which shell, termcap or ncurses ? Brendan Simon
1999-12-21 17:44 ` Dan Malek [this message]
1999-12-22  0:21   ` Brendan Simon
1999-12-21 21:33 ` Scott Wood

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=385FBC9B.E80D568@netx4.com \
    --to=dan@netx4.com \
    --cc=bsimon@ctam.com.au \
    --cc=linux-embedded@waste.org \
    --cc=linuxppc-embedded@lists.linuxppc.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 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 NNTP newsgroup(s).