[Arm-dev] Enterprise distros and the two faces of 'reliability'

[Robert Moskowitz]

On 10/26/18 12:19 PM, Fred Gleason wrote:
> Howdy Folks:
>
>
> All of this to pose the question: is an ‘enterprise’ distro (in the 
> specific sense meant here) an appropriate long-term choice for an 
> ‘embedded’ project? Given the stated intention of the Upstream 
> Provider to support only ARM systems that integrate APCI and comply 
> with SBSA  [Server Base System Architecture] standards in future major 
> releases (see 
> https://lists.centos.org/pipermail/arm-dev/2017-October/003120.html), 
> is such a distro an appropriate long-term choice for an ‘embedded’ 
> project?

There are a number of issues around embedded systems.

They have to work for 10 - 20 years.

They have to be 'safe' for as long as they are working.

At development time, often the most current components are needed (e.g. 
openSSL 1.1.1, TLS 1.3)
     This is because, often only patches are done and things still need 
to work in 10 years.

I still deal with embedded systems that are 8bit processors with 32KB 
memory/storage.  Those need not apply to this discussion.

I have dealt with vendors that say they now charge extra for only 1GB 
memory, as their current design is 2GB.  And they call this an IoT board....

There are many classes of embedded systems.  You look at what is being 
embedded in home control gateways, they either are cloud service based 
(great for captive customers and monetizing) or self-sufficient for lots 
of reasons (privacy for one).

So I am here, because I believe in enterprise code for these systems.