Embedded Linux: Semantics and Reality
Subject:   Coments on book
Date:   2003-05-14 07:27:43
From:   anonymous2
If the "Embedded Linux vendor" is unable to contribute the code changes back to the originating Open Source project, that should be a warning signal, either they are too incompetent (not necessarily technically but communication wise) or client's best interests are not in their best interests.

About the book, I think it's very nice overview of all the embedded stuff upto command line level. It might have had some small sections on real-time alternatives (real-time linux kernel, linux on top of real-time kernel, linux and real-time kernel side by side, either on top of interrupt scheduler or separate CPUs) and internationalization (C-library locale data can be huge, how to add locales, handling gettext and message catalogs).

Some more mentions of what could be done on host machine would have been nice too, e.g. tell about using valgrind to find memory errors and leaks before going to target.

Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • Coments on book
    2003-05-15 09:45:13  Karim Yaghmour | O'Reilly Author [View]

    Indeed, a vendor's lack of cooperation with the open source and free software community should be seen as a warning signal.

    Thanks for the comments on the book. I know real-time is one item some readers will miss. I made a decision not to discuss the subject in the book based on my own involvement in the real-time in Linux community. I've detailed the rational for this choice in an article available on the book's web site if you're interested (

    I've noted the other items you mentioned and will take them into consideration for future versions.


    Karim Yaghmour