[lkml]   [2001]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Download process for a "split kernel" (was: obsolete code must die)
> 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

Thank you,

Best Regards,

These are my opinions not 3Di.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:55    [W:0.343 / U:18.856 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site