All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Simon <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: Fri, 12 Nov 1999 18:15:21 +1100	[thread overview]
Message-ID: <382BBE88.12C92D9C@ctam.com.au> (raw)
In-Reply-To: 382BC934.EB69AB6D@linuxembedded.com


Sebastien HUET wrote:

> Brendan Simon wrote:
>
> > Things I think I need are :
> > * init
> > * mount (do I NEED this ?)
> > * ifconfig (do I NEED this ?)
> > * inet
> > * ftp, http, snmp and telnet software.
>
> Hi,
>
> the bootdisk howto is a good way to learn how a linux config starts.
> http://linuxdoc.org/HOWTO/Bootdisk-HOWTO.html

I've got a basic understanding of how things startup.  Use of init or
/linuxrc and shell scripts, etc.  I don't have the binaries and want to
be able to compile the binaries from the sources.

I need to know what packages I NEED and where to find the sources for
them.  RedHat and Debian supply all the sources for the releases.  I
have been to the LinuxPPC mirror and also found RPM sources.  I am
currently looking at these these packages are put together by the
vendors and they must get the sources from somewhere else.  eg. where is
the orignal site for "mount" ?  I prefer to use a tarball than some
proprietry distribution package.

Thanks,
Brendan Simon.


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

  reply	other threads:[~1999-11-12  7:15 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
1999-11-12  8:00 ` Sebastien HUET
1999-11-12  7:15   ` Brendan Simon [this message]
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=382BBE88.12C92D9C@ctam.com.au \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.