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"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: LinuxEmbedded: minimal network system packages.
Date: Fri, 12 Nov 1999 10:14:05 -0800	[thread overview]
Message-ID: <382C58ED.C782DCBB@broadlink.com> (raw)
In-Reply-To: 382BBE88.12C92D9C@ctam.com.au


> 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.
> 

There is a utility in the Linux Router Project
(http://www.linuxrouter.org/)
called 'busybox' which contains many useful utilities and it's about 80k
(430k statically linked).  busybox can 'mount' but it just silently failed
on my MPC850 board, so I'm using 'mount' from util-linux-2.9.  If you're
using
a RedHat-based distribution, you can use 'rpm -qf </path/to/filename>' 
to find the name of the package that <filename> belongs to.  


> Thanks,
> Brendan Simon.

-- 
+---------------------+----------------------+
|     Scott Wood      |   Systems  Engineer  |
|=====================+======================|
|           BroadLink Communications         |
+--------------------------------------------+

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

  reply	other threads:[~1999-11-12 18:14 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
1999-11-12 18:14     ` Scott Wood [this message]
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=382C58ED.C782DCBB@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).