Cliquer sur une vignette pour aller sur Google Books.
Chargement... The Design and Implementation of the 4.3 BSD Operating System (1989)par Samuel J. Leffler, Michael J. Karels (Auteur), Samuel J. Leffler, Marshall Kirk McKusick, John S. Quarterman
Aucun Chargement...
Inscrivez-vous à LibraryThing pour découvrir si vous aimerez ce livre Actuellement, il n'y a pas de discussions au sujet de ce livre. aucune critique | ajouter une critique
The first authoritative description of Berkeley UNIX, its design and implementation. Book covers the internal structure of the 4.3 BSD systems and the concepts, data structures and algorithms used in implementing the system facilities. Chapter on TCP/IP. Annotation copyright Book News, Inc. Portland Aucune description trouvée dans une bibliothèque |
Discussion en coursAucun
Google Books — Chargement... GenresClassification décimale de Melvil (CDD)005.43Information Computing and Information Computer programming, programs, data, security Systems programming and programs Systems programsClassification de la Bibliothèque du CongrèsÉvaluationMoyenne:
Est-ce vous ?Devenez un(e) auteur LibraryThing. |
I am not a tremendously smart person, I understand something about programming, but not a great deal, and I'm pretty good at following a sequence of logical steps, and most of all, I'm curious about things like how UNIX fits together. Having read this book, I won't say that I understand UNIX, but I certainly have a much better overview of what pieces are required to make something like this work, and how they get put together in this case. I suspect that if I take this knowledge off into the world and return to this book in a year or two, I'll be in a position to get a bit further into the overview; it seems like a book that rewards readers at many levels of initial understanding.
The writing is not prose to savor, but it is certainly effective. The authors do not try to impress with their style, and they don't, but the explanations are clear and lucid and the overall structure is sound and well-motivated, developing from the kernel outward through process and memory management to filesystems and I/O, and finally out to the network before wrapping up with the startup procedure. There is a logical flow from one section to the next, and the structure as a whole has a coherence that technical writing often lacks. ( )