Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262605AbUCRNJk (ORCPT ); Thu, 18 Mar 2004 08:09:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262606AbUCRNJk (ORCPT ); Thu, 18 Mar 2004 08:09:40 -0500 Received: from 81-2-122-30.bradfords.org.uk ([81.2.122.30]:6017 "EHLO 81-2-122-30.bradfords.org.uk") by vger.kernel.org with ESMTP id S262605AbUCRNJj (ORCPT ); Thu, 18 Mar 2004 08:09:39 -0500 Date: Thu, 18 Mar 2004 13:11:03 GMT From: John Bradford Message-Id: <200403181311.i2IDB3dE000721@81-2-122-30.bradfords.org.uk> To: Felix von Leitner , linux-kernel@vger.kernel.org In-Reply-To: <20040318130640.GA28923@codeblau.de> References: <20040318130640.GA28923@codeblau.de> Subject: Re: Remove kernel features (for embedded systems) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 580 Lines: 14 > 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? John, - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/