linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dmalek@jlc.net>
To: bsimon@ctam.com.au
Cc: linux-embedded <linux-embedded@waste.org>,
	linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: LinuxEmbedded: minimal network system packages.
Date: Thu, 11 Nov 1999 20:01:44 -0500	[thread overview]
Message-ID: <382B66F8.BFE03655@jlc.net> (raw)
In-Reply-To: 382B4396.57669F9B@ctam.com.au


Brendan Simon wrote:


> 
> Things I think I need are :
> * init

I don't run init, I just have the kernel start up with a
shell and runs /linuxrc to start whatever daemons I need.

> * mount (do I NEED this ?)

It's nice, because I at least mount /proc.

> * ifconfig (do I NEED this ?)

Depends how you start the embedded system.  If it is always part
of a network where a server can provide the necessary information
via BOOTP/DHCP, you don't need ifconfig.

> * inet

inetd....and associated network information files.


> Any pointers to documentation about getting a minimal embedded networked
> system up and running.

It's pretty straight forward.  Just think about what you need.  If
you have the "disk" space, you can go through the layers of rc.x and
sysconfig files, or just make a simple shell script to configure what
you need.  Do you want resolver library baggage or just use /etc/hosts?
Things like that.  It's a learning experience :-).


	-- Dan

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

  reply	other threads:[~1999-11-12  1:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-11 22:30 LinuxEmbedded: minimal network system packages Brendan Simon
1999-11-12  1:01 ` Dan Malek [this message]
1999-11-12  8:00 ` Sebastien HUET
1999-11-12  7:15   ` Brendan Simon
1999-11-12 18:14     ` Scott Wood
1999-11-12 13:35 ` Dave Weis

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=382B66F8.BFE03655@jlc.net \
    --to=dmalek@jlc.net \
    --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).