On Wednesday 30 April 2008 14:11:49 David Woodhouse wrote: > > There are simply already far too many of them and they make the > > kernel harder and harder to change. > > I agree. And if we do want to pay attention to pure code size, there are > other approaches -- like --gc-sections and/or building with '--combine > -fwhole-program' which I was playing with for OLPC a while back. I must > dust that off now that the GCC fixes should mostly have made it into > current distributions. I like simplicity. I like _simple_. Half my attraction to embedded systems is that they're simpler than big desktop systems where you have to figure out how udev interacts with dbus to figure out why knetworkmanager convinced Konqueror that your network doesn't exist when you can wget from the command line just fine... I submitted a patch to remove the use of perl to build the linux kernel (which HPA added in 2.6.25) not because it affected the result, but because it unnecessarily complicates the build system. (And perl tends to metasticize. Nothing says "maintainability" like perl...) Yes, Perl was used for some debugging tools before, things like the check-patch script. But until 2.6.25 you never needed Perl to configure and build a kernel... Rob -- "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
