From: Felix von Leitner <felix-kernel@fefe.de>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Remove kernel features (for embedded systems)
Date: Thu, 18 Mar 2004 14:29:37 +0100 [thread overview]
Message-ID: <20040318132937.GB29111@codeblau.de> (raw)
In-Reply-To: <200403181311.i2IDB3dE000721@81-2-122-30.bradfords.org.uk>
Thus spake John Bradford (john@grabjohn.com):
> > And if it is at all possible, I would like to be able to remove parts of
> > the IP stack, e.g. routing. In particular, I would like to be able to
> > remove policy routing, if it is at all worth it from the code size point
> > of view.
> Why not just write your own IP stack in userspace, if you're doing a
> heavily embedded system?
People use Linux _because_ of the IP stack.
They just normally don't need all of it.
And I propose to let them remove the parts they don't need.
Felix
next prev parent reply other threads:[~2004-03-18 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 13:06 Remove kernel features (for embedded systems) Felix von Leitner
2004-03-18 13:11 ` John Bradford
2004-03-18 13:29 ` Felix von Leitner [this message]
2004-03-18 13:39 ` Christoph Hellwig
2004-03-19 19:11 ` Matt Mackall
[not found] <369036857@toto.iv>
2004-03-18 22:15 ` Peter Chubb
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=20040318132937.GB29111@codeblau.de \
--to=felix-kernel@fefe.de \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.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.