On 9 March 2011 19:15, Tom Gall tom.gall@linaro.org wrote:
Going deeper it's pretty easy to spot low hanging fruit: From fs - Do we need afs, jfs, code, minix, hpfs, xfs, hfs, hfsplus, gfs2, reiserfs... I'm thinking no. From drivers - net and media make about about 1/3rd of the 28 meg in use, I'm sure there's a number of drivers in here that can just be turned off. From sound - ac97, are there arm boards that use that? From net - x25, decnet, appletalk ?
So that said, what is the best way to proceed?
- Is there agreement that for all the kernels we supply that we
should change the policy for kernel configs to not default to everything on? (Maybe we should be using the upstream config with minimal modifications?)
Pro: everyone benefits from the diet Con: Our kernel would be build slightly different than ubuntu's others:
Can't we keep stuff configured as modules but move some of the modules out into other binary packages? That way everyone benefits from the diet, but it wouldn't stop anyone installing it if they had weird needs. I also don't think it would be a bad idea to propose making the same change to the Ubuntu kernels if you want to keep the differences down. I'd support turning the really obscure stuff off though,
- Linaro-media-create shouldn't install linux-firmware_1.47_all.deb ?
Do we have any any hardware that needs it? If so could there be a --nano option to not install it?
Aren't there a few boards with PCI which could take a whole variety of boards some of which will need firmware? It's surprising just how many things need it, and if it was your ethernet adapter it's really nasty to fix. But I think I agree in generally it could be off by default.
One thing that might help is to make it easy to specify on l-m-c that you want to add extra packages to the image; that way if you decide to take some packages out it's not that hard for someone to add them during the creation.
Dave