Re: modules, firmware, kernel size (was Re: systemd requires HTTP server and serves QR codes)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Oct 17, 2012 at 5:46 PM, Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx> wrote:
> On Wed, Oct 17, 2012 at 05:38:55PM +0200, drago01 wrote:
>> > Basically: it's hard,
>> it is a mess.
>> > but the only way we're going to get to a
>> > reasonably-small minimal image,
>> not true.
>
> Given that the kernel is currently a full quarter of the current image, I
> think it has to be.

No you could also use a different kernel image; build your own kernel;
use a compressed filesystem, don't use a kernel at all and some
container based approach instead of full virt for your cloud instances
(you could even base them on a btrfs subvolume and save more space
that way).

Outside of the cloud use case the disk space added by modules and
firmware does not matter a bit (so I am ignoring this cases).

So there are lots of other ways to achieve what you want without
splitting the kernel into hundreds of sub packages.  So while it is a
way it is not "the only way".
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux