Re: Download process for a "split kernel" (was: obsolete code must die)

From: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
To: <linux-kernel@vger.kernel.org>
Cc: "Jaswinder Singh" <jaswinder.singh@3disystems.com>
Subject: Re: Download process for a "split kernel" (was: obsolete code must die)
Date: Wed, 13 Jun 2001 19:30:52 -0700	[thread overview]
Message-ID: <016c01c0f47a$08807e40$4fa6b3d0@Toshiba> (raw)
In-Reply-To: <NEBBJBCAFMMNIHGDLFKGCEFCEEAA.rmager@vgkk.com>  <200106140200.f5E20NL3012987@typhaon.pacific.net.au>

>
> Or as a simpler design, something like;
>
>   * a copy of the kernel maintained in a CVS tree
>   * kernel download would pull down:
>         * the build script
>         * a file containing the list of filenames depended on by
>           each config option
>   * build script builds the config and then cvs updates the file list
>     and the files for each config option in question to the version as
>     tagged in the build script
>
> Someone could relatively easily maintain this separate to all the kernel
> developers, and it would mean only ever having to download files you were
> actually using.

OR

50 % of kernel size is from /linux/drivers
25 % of kernel size is from machine dependent /linux/arch/XXXX and
/linux/include/XXXX

If  we are able to divide Linux tree in such a way that everyone can
download it from from their personnal modems and enjoy linux.

may be i am wrong .

But i love downloading whole kernel and i usually refer different
architectures.

Thank you,

Best Regards,

Jaswinder.
--
These are my opinions not 3Di.