I don't understand the point of merely splitting the tarball. If you can't mix and match the "core" and "driver" parts (which you generally can't because Linux deliberately lacks stable kernel driver APIs), what good does it do to download them separately?
It would be a pain in the ass having separate tarballs. No thanks. I well remember the days of building separate modules (Atheros (madwifi) or Prism54, etc) and do not miss them. Having the kernel and drivers in one tree makes things much easier.
I'm not sure how you'd get useful granularity with multiple driver tarballs. It seems like no matter how you split it, you'd run into the problem of "80% of the users use 20% of the code, but it's never the same 20%".
Ah, the joy of statistics.
I don't care if the sources hit 1GB, to be quite honest. I'll take the increase in size to mean that they've been busy fixing the various shortcomings the kernel has had over the years, and adding support for even more oddball architectures I'll never use.
The size of a compiled and packaged kernel still tends to be between 1MB and 100MB depending on what you've included. Come and alarm me when a compiled kernel hits 100GB and I no longer have the hard drive space to install it.
From the busybox about page:
From the serial console on my router, I see that the kernel boots and then BusyBox loads later in the boot sequence. I don't quite understand how the kernel can boot if it doesn't support MIPS.To create a working system, just add some device nodes in /dev, a few configuration files in /etc, and a Linux kernel.
Last edited by chenxiaolong; 11-13-2011 at 12:09 AM.