Hi Martin; Am 18.02.2012 18:33, schrieb Martin Hejl: > Hi kp, > >> It does cost about 300kb. Agreed that is a lot, but there is still room >> for improvements in other areas (AFAIK iptables and ip6tables has been >> merged, shorewall may shrink with the future versions) and finally speed >> and size will improved if we carefully cleanup initrd for i486 images. >> >> Although a LEAF device usually runs for a long without reboot, booting >> as quick as possible is a nice-to-have. > I tend to agree. While I've always been one to try to avoid bloat and > keep things small, I would, in this case, trade speed for size. > > Speaking for the boxes I maintain, they hardly ever go down - but if > they do (for whatever reason - hardware failure, system upgrade, power > outage longer than the UPS can handle, typing "reboot" in the wrong > terminal), I'd like the box to be up again as quickly as possible, since > it provides internet connectivity to public services I have to keep up > and running (email, VPN, public bugzilla, internet access for my > employees and so on). So, if the difference is "only" 300k, I'd go for > it (even though I'm not affected by this change, since I no longer use > lower end CPUs). > > Rather than a fork - maybe an additional kernel/initrd can be provided, > so the users can make the choice themselves? Those that are running on > limited storage, can use the one that boots slower, but uses less > storage, and those who have space to spare can use the one that boots > faster. Providing several setups for the same kind of hardware might > cause some confusion for users, but if the documentation clearly states > which image/kernel/initrd to use for which purpose, it shouldn't be too bad. > > Just an idea
This was my first thought also, but I think it's not worth the effort. While it seems tempting to add an additional kernel, it is a lot of work in the long run: Maintaining another kernel version (config patch), longer build time, probably providing special images or a *very* detailed documentation how to replace kernel/initrd on your IDE/CD/WHATEVER boot media and so on - you'll get the idea :) And this only affects i486 users - if don't choose to go that way with every image we provide. And if everything else fails - going back to gzip the kernel is also a viable option. Let's see, if there a complaints from users about Andrews decision, before we invest work on this issue. To save 300kb we may better have a look into initrd-i486 or improve a script Erich posted some time ago, that adapts initrd to the modules really needed, which will be an one-time-effort - and serves all images. kp ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
