Should BusyBox and uClibc also make a "flag version" likeEmbedded Linux?

Mikhail Gusarov dottedmag at dottedmag.net
Sat Nov 6 09:30:40 UTC 2010


Twas brillig at 16:06:50 05.11.2010 UTC-07 when jcathey at ciena.com did gyre and gimble:

 CJ> It's when BB can be blamed for burnt toast that the
 CJ> 'lid comes off the box', and then one may reasonably
 CJ> consider updating.  But if BB v20 is notably bigger
 CJ> than BB v2, as configured, that could be a problem.
 CJ> Especially if the toaster were quite resource-constrained.
 CJ> And spending more ROM bytes on infrastructure like BB is
 CJ> usually much less attractive than spending them on direct
 CJ> features.

 CJ> 'Stale' software is a fact of life in embedded world.
 CJ> We prefer to pronounce it 'stable', however!

Especially if toaster is not connected to network, and hence attacker
can't burn all user's toasts due to security vulnerability in BB.

-- 
  http://fossarchy.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/uclibc/attachments/20101106/6b9415d4/attachment.pgp>


More information about the uClibc mailing list