From: Wolfgang Denk <wd@denx.de>
To: "SangTae Ha" <stha@postech.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Do you have your minimum ramdisk image which can provide basic network services ?
Date: Mon, 29 May 2000 09:56:13 +0200 [thread overview]
Message-ID: <200005290756.JAA27458@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 29 May 2000 16:27:37 +0900." <020e01bfc93f$5dc075c0$db52df8d@helsinki>
In message <020e01bfc93f$5dc075c0$db52df8d@helsinki> you wrote:
>
> I want to make my ramdisk image which can provide basic network services such as "ping","traceroute","telnet" and "ftp". I want to reduce my file size within (1or2)M bytes. I already downloaded full image file at ftp://ftp.ppc.kernel.org/pub/linuxppc/em
> bedded/mbxroot.full.tgz
This is most probably not the best approach.
You should not start with a full installation of everything, but
instead start with an empty system and design what you need to have
it it.
/bin/ping, /usr/sbin/traceroute, /usr/bin/ftp, and /usr/bin/telnet
together need (compressed) well below 100 kB, so if you don't need
glibc2 for any reasons you can easily fit this within your limits
(hell, in 1 MB you can have a compressed image with a full web server
including >560 kB of web pages *plus* the Linux kernel).
> This file is so big including all of things. I am currently pruning various directories and files in it. I hope that it doesn't take too much time.
> I have two choices.
> 1) compile the LRP(Linux Router Project) package and make it into root file system image
> 2) reducing file size from full image file and make final small size image
What's wrong with using one of the existing embedded releases, and
building your system from buttom up? Both the Montavista HHL release
or our CD-ROM should get you started easily (see
http://www.denx.de/solutions-en.html for a start).
> How do you think about above solutions?
I think you are on a wrong track.
> I just want to use TCP/IP networking facilities. I will really be happy if you already got that image..
What is the purpose of your embedded system?
What do you want to have FTP for, when you don't have any files to
send, or any commands to process files you "get"? It's difficult to
make recommendations (especially for embedded systems) when you hold
back essential information...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Nothing ever becomes real until it is experienced. - John Keats
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-29 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-29 7:27 Do you have your minimum ramdisk image which can provide basic network services ? SangTae Ha
2000-05-29 7:56 ` Wolfgang Denk [this message]
2000-05-30 18:29 ` Tom Roberts
2000-05-30 18:39 ` Daris Nevil
2000-05-31 13:45 ` Tom Roberts
2000-05-31 15:35 ` Daris Nevil
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=200005290756.JAA27458@denx.local.net \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stha@postech.edu \
/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).