<link rel="stylesheet" href="style.css">
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
In US, 49% handsets sold were Android, 31% iPhone
Cockroaches outnumber humans by a rather incredible margin. Which do you think is superior?
Depends on the human.
Suddenly even Myspace sounds like a real option for the first time since puberty,
Two weeks ago.
Oh, you also just turned 33?
Umm... most distributions of Linux and FreeBSD do in fact make it easy to download other browsers. You won't hear me condoning Apple business practices wrt bundling Safari, but since they are not a convicted monopolist they probably will not need to worry about this.
Legal definition != dictionary definition. See Sherman anti-trust laws.
Well, in a case when you need to know the length, you have to use strict evaluation (sort of- I'm simplifying), in which case Haskell is reducing to what "normal languages" do. In the case where you do not need the length, you get the benefits of laziness.
Prentice Hall's Embedded Linux Primer by Christopher Hallinan was published September 18th, 2006 as part of their Open Source Software Development Series. Very much like a textbook, Embedded Linux Primer is very informative and an excellent source of information for an engineer looking to enter or move to the embedded Linux field. The text is a decent size, with 537 pages spanning 17 chapters and 6 appendices; it retails for around $45 USD.
I had some reservations on reviewing a detailed technical book since most of the ones I have are dry and have a very segmented structure. However after taking a look at the sample chapter, chapter 7 "Bootloaders", available on the Prentice Hall website along with the table of contents for the text I figured I would give it a look and I am very glad I did.
Many technical books focus on a specific demographic in the technology world, mostly beginners or professionals expanding their knowledge base. I was quite pleased to see this text is written for both professional developers and emerging embedded engineers.
Professional engineers will find the text informative on the Linux operating system and how flexible it is to implement on even the most custom hardware. The author understands that a large number of embedded system engineers work with proprietary systems and explains items that might be new and different than these systems. For example Chapters 4-6 detail the Linux boot sequence and describe common pitfalls engineers new to the embedded Linux methodology might make. Chapters 8-11 dive further into the operating system and explain device driver creation, the important file system and how Linux handles volatile and non-volatile memory systems using the MTD subsystem.
Engineers starting in the field of embedded systems will find information on what an embedded system is in Chapter 1, processor and board comparisons in Chapter 2 and setting up an embedded environment for development in Chapter 12.
It is quite obvious throughout the text the author has an extensive in depth understanding of embedded systems and the inner workings of the Linux operating system. With such a deep understanding of the material an author many times explains items in such detail it clouds the mind of the reader. The first line in Chapter 2 says (paraphrasing) that the best way understand something is to understand the 'big picture' . This is exactly the approach the author takes through out the text, first explaining the theory and high level aspect of the system, then diving into the detail of how it is done on the low level. Also, rather than get sidetracked in chapters by explaining every processor attribute or software package, the author suggests external sources mid-text and in the "Suggestions for Additional Reading" at the end of each chapter.
For the first edition of a book, Embedded Linux Primer is rather complete, with the only exception being chapter 8, Device Driver Basics, which is...well, rather basic. I started the chapter expecting to finish with a detailed understanding of how the Linux kernel processes driver requests and a look into some common drivers. This is not the case; for a second edition of this text I would suggest beefing up this chapter to provide more of an insight into kernel-driver interaction.
Overall Embedded Linux Primer is an excellent source of information for both the seasoned professional and aspiring embedded engineer. I know that when I dive fully into the world of embedded Linux this book will have a permanent place on the bench right next to the spec sheets.
For those interested in this text, the Prentice Hall book page can be found here: http://www.phptr.com/bookstore/product.asp?isbn=0
Sample Chapter "Bootloaders": http://www.phptr.com/articles/article.asp?p=67469
Geeksinside.com review link: http://geeksinside.com/review.php?r=3
*s1axter is the main poster for Geeksinside.com.
*Geeksinside.com is a DIY, hardware hacking, technology blog that showcases projects, reviews and technical links"
Link to Original Source
Perhaps Slashdotters would like to hear what we've been getting wrong for the past era."
Our goal is simple: we want to collect community donations to enter a Linux sponsored car in the 2007 Indianapolis 500. We need your help! If less than 1% of the Linux community donates $1, this will happen... will you do your part? http://tux500.com/"