Re: Download process for a "split kernel" (was: obsolete code must die)
Jaswinder Singh (firstname.lastname@example.org)
Wed, 13 Jun 2001 19:30:52 -0700
> 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.
50 % of kernel size is from /linux/drivers
25 % of kernel size is from machine dependent /linux/arch/XXXX and
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
These are my opinions not 3Di.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/