public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Gonzalo Servat <gonzalo@linuxaus.com>
To: Linux MTD mailing list <linux-mtd@lists.infradead.org>
Subject: OpenSSH/OpenSSL is too big... any alternatives?
Date: 26 Jun 2002 00:09:58 +1000	[thread overview]
Message-ID: <1025014199.2220.3.camel@beamer.servat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 345 bytes --]

Hi All

I have a 2MiB DiskOnChip. After installing the kernel, BusyBox, iptables
and a couple of libs from uClibc I only have 400k left of space.
OpenSSH needs to link to OpenSSL and OpenSSL is well over 1MB on it's
own. Is there any alternatives to OpenSSL/OpenSSH that will fit on 400k?

Thanks in advance!

Regards,

Gonzalo.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-06-25 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-25 14:09 Gonzalo Servat [this message]
2002-06-25 14:43 ` OpenSSH/OpenSSL is too big... any alternatives? cfowler
2002-06-25 14:50   ` Paul Jimenez
2002-06-25 15:04     ` Gonzalo Servat
2002-06-25 17:21       ` Robert Schwebel
2002-06-25 17:19 ` Russ Dill

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=1025014199.2220.3.camel@beamer.servat.com \
    --to=gonzalo@linuxaus.com \
    --cc=linux-mtd@lists.infradead.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