Originally posted by siride
View Post
Announcement
Collapse
No announcement yet.
The Increasing Size Of The Linux Kernel
Collapse
X
-
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.
Comment
-
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.
Comment
-
Originally posted by chenxiaolong View PostAlso, if the kernel developers go for amd64 only, then we'll be back in the internet-less world, since Linux won't support that MIPS processor in your modem and router anymore.
Comment
-
Originally posted by Ex-Cyber View PostI'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%".
Comment
-
Originally posted by yogi_berra View PostLinux doesn't have to support MIPS, busybox has to. There is no reason, beyond sheer laziness or incompetence, that the busybox people can't role their own code for MIPS.
From the busybox about page:
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; 13 November 2011, 02:09 AM.
Comment
-
I can't really see the problem with the size. It's 100MB, anytime you see an HD movie online you download at least 400MB.
You don't usually compile the kernel everyday, and if you do, it's more useful to just clone a git repo and pull everyday, and that way the download doesn't take that long.
And about the hard disk space, with a 1TB drive (which is not that unusual right now) I can't see how 1 or 2GB of uncompressed kernel could be a problem.
Cutting features and dropping drivers to get more advanced capabilities is one thing, and I support it in mesa even considering I use an Unichrome IGP in one of my boxes, but cutting it just because 100MB sounds big, is another thing.
I think it's a pretty bad idea.
Comment
Comment