![Linux TCP/IP: Networking for Embedded Systems [With CDROM]](http://ecx.images-amazon.com/images/I/51AVYyGZjfL._SL75_.jpg)
- Paperback: 600 pages
- Publisher: Charles River Media; 1 edition (April 15 2004)
- Language: English
- ISBN-10: 1584502843
- ISBN-13: 978-1584502845
- Product Dimensions: 22.9 x 18.5 x 3.6 cm
- Shipping Weight: 1 Kg
- Average Customer Review: 3.0 out of 5 stars See all reviews (1 customer review)
-
Amazon Bestsellers Rank:
#119,297 in Books (See Top 100 in Books)
- #8 in Books > Computers & Internet > Networking > Networks, Protocols & APIs > TCP-IP
- #12 in Books > Computers & Internet > Hardware > Microprocessors & System Design > Embedded Systems
- #19 in Books > Computers & Internet > Operating Systems > Linux > Networking & System Administration
- See Complete Table of Contents
|
||||||||||||||||||
|
||||||||||||||||||
|
||||||||||||||||||
|
There is a newer edition of this item:
|
Product Details |
Product Description
Book Description
The Linux TCP/IP Stack: Networking for Embedded Systems provides an in-depth guide to implementing and using the Linux TCP/IP stack in embedded systems projects. It begins with a general overview of TCP/IP networking, with background information on applicable networking standards. From there, it details the TCP/IP implementation in Linux 2.6 by following a packet of data as it flows through the stack from the sending system, out the wire, and back through the input side of the stack in the receiving machine. This unique approach gives programmers an “inside” look at the entire process.
Throughout the text, topics of particular interest to engineers implementing embedded systems are discussed, such as sockets, network interfaces, application layer protocols, and practical considerations. This is a great resource for embedded systems programmers and engineers, as well as networking professionals interested in learning more about the implementation of Linux TCP/IP in the 2.6 kernel.
KEY FEATURES * Discusses key topics for embedded systems such as real-time requirements, the Linux IPv6 implementation, and how Linux TCP/IP is interfaced to diverse drivers and protocols * Provides embedded systems engineers, protocol writers, network device driver writers, and others interested in Linux networking with an in-depth guide to how TCP/IP works * Answers detailed networking questions by focusing on the internal operations and structure of the Linux TCP/IP stack—not just applications programming
About the Author
Thomas F. Herbert (Richmond, VA) is Vice President of Technology and Managing Partner of Infosecure Systems and Solutions, LLC. Infosecure Systems and Solutions is a company specializing in open source solutions for IT and embedded technology throughout the Americas. He has over 15 years of experience as an embedded engineer and has worked on many aspects of both open and embedded systems. He has written for Embedded Systems Programming and given numerous presentations at the Embedded Systems Conference.
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Customer Reviews
Most helpful customer reviews
disappointing
Dec 9 2004
Format:Paperback
I like to support people writting Linux books which are
based on the kernel and in particular on the network code.
This book is disappointing. It essentially is a copy
of the code with mostly comments from the code. Sad.
This would be the last hungry author i support. I think
Linux has grown mature enough we dont need just about anybody
writting books. This author is definetely not well qualified.
Seems like he can read code in a hurry - but does he even understand it? Why didnt the publisher have someone
knowledgeable review it? As of now i am no longer going to support any linux author for the sake of support.
If you know a little bit about the code - this book is useless;
dont waste your money like i did. I found a few errors in the
one section i paid attention to - the net device. Buy the
oreilly device driver book instead.
OTOH, If you have spare $50 to spend and you have never
bothered looked at the code before - it may be worth buying it.
Its almost equivalent to printing code. If you are serious
about learning - spend about a week on it and shelf it.
based on the kernel and in particular on the network code.
This book is disappointing. It essentially is a copy
of the code with mostly comments from the code. Sad.
This would be the last hungry author i support. I think
Linux has grown mature enough we dont need just about anybody
writting books. This author is definetely not well qualified.
Seems like he can read code in a hurry - but does he even understand it? Why didnt the publisher have someone
knowledgeable review it? As of now i am no longer going to support any linux author for the sake of support.
If you know a little bit about the code - this book is useless;
dont waste your money like i did. I found a few errors in the
one section i paid attention to - the net device. Buy the
oreilly device driver book instead.
OTOH, If you have spare $50 to spend and you have never
bothered looked at the code before - it may be worth buying it.
Its almost equivalent to printing code. If you are serious
about learning - spend about a week on it and shelf it.
Generally, a dissapointing book and to be fair to the author
not unlike any other book that has been written on the network
stack so far. The things that bothers me is Why cant we have people who really know this stuff write
books? dammit, why do these books keep popping up?
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
7 reviews
11 of 11 people found the following review helpful
very detailed under the hood type of book
July 26 2004
Format:Paperback
Mr. Herbert has disected the LINUX TCP/IP stack using the source code. In this book he presents what he has discovered. The book goes through a lot of the source code and has good explanations of what it does. It is better than a lot of LINUX books where only the source code is listed with few explanations. The book also discusses the RFC's and how they are implemented in the stack. The source code for the LINUX TCP/IP stack is fairly large. The book does not cover all of it, but it does cover the main paths packets take through the stack. Having read the book, I found it easier to read the LINUX TCP/IP source code myself.
14 of 16 people found the following review helpful
detailed but not easy to read and follow
Oct 11 2004
Format:Paperback|Amazon Verified Purchase
I have not finished reading the whole book yet so the review is based on the first a hundred pages I read.
The author apparently has plenty of knowledge about networking and Linux and his description about networking code in Linux (like device drivers in first part of the book) is generally very detailed. It covers almost all Linux tcp/ip related design and implementation so the book is good enough to give you an overall picture of what the book claims to do: tcp/ip stack and how it is implemented in Linux.
But the main issue with the book is that it is not easy to read and follow. When the author throw out some new concept/variable/function/usage/etc., he not necessary gives enough explanation on them. Sometimes there is no explanation at all. This makes you have more questions when you read on. Eventually these more questions overwhelm you and make you stop and start thinking how/why all these things work. I really like the writing style of two other books in Linux: Robert Love's Linux Kernel Development and Rubini/Corbet's Linux Device Drivers. Any new topic/concept/variable is accompanied with notes/explanations/usage on how/why such is such. This difference makes this one a 4-star, instead of 5-star.
By all means, read the above two books (and maybe other books on Linux kernels) before reading this one. Read this one when you feel you are comfortable with device driver, kernel development
and tcp/ip protocol. Otherwise you make feel disappointed or confused.
The author apparently has plenty of knowledge about networking and Linux and his description about networking code in Linux (like device drivers in first part of the book) is generally very detailed. It covers almost all Linux tcp/ip related design and implementation so the book is good enough to give you an overall picture of what the book claims to do: tcp/ip stack and how it is implemented in Linux.
But the main issue with the book is that it is not easy to read and follow. When the author throw out some new concept/variable/function/usage/etc., he not necessary gives enough explanation on them. Sometimes there is no explanation at all. This makes you have more questions when you read on. Eventually these more questions overwhelm you and make you stop and start thinking how/why all these things work. I really like the writing style of two other books in Linux: Robert Love's Linux Kernel Development and Rubini/Corbet's Linux Device Drivers. Any new topic/concept/variable is accompanied with notes/explanations/usage on how/why such is such. This difference makes this one a 4-star, instead of 5-star.
By all means, read the above two books (and maybe other books on Linux kernels) before reading this one. Read this one when you feel you are comfortable with device driver, kernel development
and tcp/ip protocol. Otherwise you make feel disappointed or confused.
6 of 6 people found the following review helpful
An Excellent book and covers the 2.6 kernel
Jun 13 2005
Format:Paperback
This is an excellent book which explains everything related to the TCP/IP Linux implementation in the 2.6 kernel. There are other excellent Linux networking books, but this is the best one in terms of the details for the TCP/IP implementation.
It explains in detail Network devices, drivers, UDP, TCP, IP and IPv6. And it shows in detail all the steps a packet goes through when moving from the application layer to the socket layer, then through the transport layer (TCP or UDP), Network Layer (IP) and Data Link Layer and finally to the physical layer. Then it shows the details of the flow of the packet at the receiving side.
It explains in detail Network devices, drivers, UDP, TCP, IP and IPv6. And it shows in detail all the steps a packet goes through when moving from the application layer to the socket layer, then through the transport layer (TCP or UDP), Network Layer (IP) and Data Link Layer and finally to the physical layer. Then it shows the details of the flow of the packet at the receiving side.
Listmania!
Look for similar items by category
- Books > Computers & Internet > Certification Central
- Books > Computers & Internet > Hardware > Microprocessors & System Design > Embedded Systems
- Books > Computers & Internet > Networking > Networks, Protocols & APIs > TCP-IP
- Books > Computers & Internet > Operating Systems > Linux > Networking & System Administration
- Books > Computers & Internet > Operating Systems > Linux > Programming
- Books > Computers & Internet > Operating Systems > Unix
- Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Software Development
- Books > Engineering > Electrical & Electronics > Electronics
- Books > New & Used Textbooks > Computer Science & Information Systems > Networking
- Books > New & Used Textbooks > Computer Science & Information Systems > Operating Systems
- Books > New & Used Textbooks > Computer Science & Information Systems > Software Design & Engineering
- Books > New & Used Textbooks > Engineering > Electrical & Electronic Engineering
- Books > Professional & Technical > Engineering > Electrical & Electronics > Electronics
Look for similar items by subject
Feedback
Would you like to update product info or give feedback on images?
|
