* Rob Landley <[email protected]> [05.04.2013 09:00]: > What exactly is the _problem_? The existing ifconfig works fine. This
and that is the dangerous thing about it: it's working "enough", so ip will be always missing (because there is so little Leidensdruck: 'psychological strain') > But this "Oh no, the code is old! Code RUSTS!" I don't get it. Linux the argument was: the code/idea/implementation is old AND incomplete AND inconsistent. only old is not a problem but all 3 together. > 2.4 doesn't support modern hardware, containers, tickless operation, > sucks at threading and SMP. But if it had decent arm support I expect > android would have been based on it because it ran in a quarter the > memory the current one needs. adventurous hypothesis. for a modern network device you want a modern network stack which has 2.4 not. for a modern device with multitasking you want a modern scheduler and a modern VM which has 2.4 not. for a modern device with many interfaces (HDMI, USB, wifi) you want support for the attachable devices which 2.4 has not. in fact it does not matter if you have 1 gig or 1.008 gig of memory... lets stop the discussion here, it's only timeconsuming and the opinions are deadlocked somehow. lets see how it performs and maybe in autumn i will jump in for 'ip'. bye, bastian _______________________________________________ Toybox mailing list [email protected] http://lists.landley.net/listinfo.cgi/toybox-landley.net
