On Mon, 12 Apr 2010 16:24:25 +0200 "W. Martin Borgert" <debacle@debian.org> wrote: > Quoting Wookey <wookey@wookware.org>: > > Any in the works, perhaps? > > My company will use Debian, but not Emdebian, for an embedded > device in the field of wind and solar energy. We started with > Emdebian originally, but found no advantage over standard > Debian for us. Lower RAM usage would be nice, but smaller > package size is not relevant in our case. Other aspects of > Emdebian are still interesting for us, such as the focus on > cross-compiling, e.g. i386 -> armel. I've kept this kind of requirement in mind - what I hope multistrap will achieve is the ability to only select packages that have lower resource expectations and remove packages that are memory hogs from the installation. Emdebian cannot really take on providing new upstream code that is optimised to low resource environments but we can ensure that where such code is packaged for Debian, users of Emdebian have easy access to those packages without having to put up with bloat from the rest of Debian. If there is anything extra we can do to make it easier to select a package set that is optimised for low resource devices, let me know. Which standard Debian packages are at fault for hogging RAM in your situation? Are there simple compile-time options that can be provided to such packages (or unobtrusive patches) that can dramatically reduce the memory footprint and which we can introduce as a new foo-crush package? Presumably you're looking for lower power consumption, not just lower RAM usage, so packages that do fewer complex calculations or are just less complex and so take up fewer clock cycles etc. Are there situations where you'd like to use one package but Debian gets in the way and puts a more bloated alternative in instead? -- Neil Williams ============= http://www.data-freedom.org/ http://www.linux.codehelp.co.uk/ http://e-mail.is-not-s.ms/
Attachment:
pgpv2fga3VulJ.pgp
Description: PGP signature