I’m really curious how the embedded systems folks took this latest 
“improvement”. 

By this argument, Intel and ARM systems running from EPROM are no longer 
viable, or at least will require a forklift upgrade - are they expecting to 
always copy the entire kernel into RAM and allow it to modify itself? There’s 
an awful lot of avionics and industrial controls/IoT hardware deployed out 
there that will stop getting updates because it flat out doesn’t have enough 
onboard RAM to support this approach, and that’s the last thing we need: more 
systems we can’t fix when some other dumb error happens. It also opens up an 
entirely new class of exploits possible by interfering with the running kernel 
image or the transfer of the image to RAM. 

This whole approach seems poorly thought out at best, but I guess that is the 
norm for Linux these days. A little Linus vitriol of old seems in order, IMHO. 


 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to