linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scott@broadlink.com>
To: bsimon@ctam.com.au
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux-embedded: which shell, termcap or ncurses ?
Date: Tue, 21 Dec 1999 21:33:27 +0000	[thread overview]
Message-ID: <385FF227.DEBE0159@broadlink.com> (raw)
In-Reply-To: 385EE46B.1D97C2D2@ctam.com.au


Brendan Simon wrote:

> I am trying to get a powerpc embedded system up and running.  I have
> compiled the kernel and can mount a root filesystem using initrd or
> nfs.  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 ?).
> 
> I got the latest version of bash(2.0.3) and ncurses(5.0).  Bash requires
> termcap but apparently termcap is obsolete and is replaced by ncurses.
> 

You can still use an earlier 1.x version of bash which is linked to
libtermcap.
It will be much smaller and you probably don't need much functionality in
your 
shell if you're just setting up networking and running simple scripts.

> Has anyone cross-compiled a recent version of bash and ncurses ?  Are
> they huge ?  Will they fit on a 4MB initrd image ?

My bash, from the yellowdog distro, stripped, is about 400k.
If you're worried about space, strip all your binaries and libraries, 
and look at possibly using a more minimal shell like ash.

> 
> Thanks,
> Brendan Simon.

-- 
Scott Wood

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

      parent reply	other threads:[~1999-12-21 21:33 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
1999-12-22  0:21   ` Brendan Simon
1999-12-21 21:33 ` Scott Wood [this message]

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=385FF227.DEBE0159@broadlink.com \
    --to=scott@broadlink.com \
    --cc=bsimon@ctam.com.au \
    --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).