UNIX and Linux Handbook, 5e

The book is solid for Linux knowlege, the printing is pretty good and probably close to the US printing, and at this price point it's a bargain.

Great resource for linux administration

- Best quality- Best delivery- Best Price- Overall awesomeJust go for it without a second thought.

Book covers a lot about linux and additionally helpful fpr other topics like networking, security etc. Hence, an overall package for SA,

Good

The media could not be loaded.  You can start linux with this book ....great

Excellent book for anyone working in linux environment

Suitable for people who want an in-depth understanding of linux os

I have bought this book 3 month ago and I can say it is a total diapointment.I was mislead by amazon "bestseller" and the amount of 5 stars reviews.This is in no way shape or form , in fact is not even a decent book, it is toxic, and what i mean by that is lets say you are a noob that want to learn about linux . The amount of bad content that this book has makes you think after you go trough some chapters believe that linux is a unreachable skill to acomplish and you move on. Well is not, it is only written by some guys that maybe they are gurus in linux , which i seriously doubt, but they are most defenatelly , lets just say only this. If they pursue this career path , that is teaching, they are in the wrong place at the wrong time.My arguments for putting this book on my shelf and be 1 second away to throw it to garbage is this.1. I paid for it2.the book has many lets say uncommon words, that for someone who is not native in english is kind of hard to understand without google translate. not even that but from what i read i got the impression that the authors rather prefered that they look smart instead of making it easy to understand.3. the book lack consistency, that is you get some references , not all ,of something like "read page 123" and you go there and it is a total different animal.4. most of the chapters are bad , in a way that is not written well, for example, in the 2,3,4 chapter or whatever they start by explaining "sudo". that is great. well if you believe they give you a fairlly complex example of the sudoers file and then after you wrap arround your mind about what is what , then they give you the blueprint about the sintax of the file about which is what , what fields go where and so on. in my opinion they should have started with the layout of the file then giving some examples. anyway...5.the references are extremlly bad , and what i mean by that is for a 1000+ pages book you get a lot (underlined) of references to the man pages. well if i want to learn about dhcp for examples i have 2 options right? i ether could look for man pages which from experience is not that well explained or i could buy a book which presumelly is better explained. well for a book to send you back to the man pages and btw they are not explaining 80% of the topic and then they send you to man pages , no they give you a blueprint (read down) that is maybe 10% (and i am beeing generous) and then they say "go read the man pages" which is hilarious. remeber this book has 1000+ pages.and as a side note at the end of the chapters that i did read you get references to book that are 20years old :) i kid you not.6. the blueprint for understanding is like this : lets say you want to learn chinese grammar and you dont know the alphabet that has 100 caracters. they explain in such manner that is the following: they start with a fairlly complex example of the chinese grammar(i am guessing they want to look smart or whatever) , they throw in some 7-8 characters of the alphabet and then they say "go read the man mages" :) this is exactlly their blueprint in explaining the topics of the book they are supose to cover. and btw this review is written after reading some chapters of the book many times. i mean first i said , maybe i didnt understand it at begining. anyway...7.there are a lot of off topic content. for example , they explain in great detail networking , adressing , cidr, adn so on, which for a linux book.... anyway the information is welcomed right? lets move on to the rest of the chapter which i am guessing that it will have as well a wealth of info like the networking they started with and i end up next at dhcp . great !!! dhcp configuring is somewhat of interest am i looking forward to learn. well :)))) and this is from the book, actually i challenge anyone who read the book to prove me wrong and prove that i am lieing even by 1% and i will delete the review. anyway, they get into dhcp. again :)))))) , they give you a laughable configuration example of dhcpd.conf which will not work in a seroius , decent enviroment! anyway is only the first page , i am sure it is a lot more info on the next page , you turn the page and they start saying some more advanced topics and i quote "you should configure your dhcp to work with dns, because is good practice and so on" well that is great i am going to learn about that . going to the next paragraph and they change topic :) to a whole diferent subject! wait / what?you give as i said a lot of info on network addressing in a linux book and almost 2 pages for a linux important component? again as i said 10% covering of the subject i am beeing generous. again.8. the chapters (most of them , not all of them ) are a disaster. what do i mean by that? lets take dhcp as we are on dhcp. they say and i qoute about the config file "you should find the config file somewere underneath the var directory" bare in mind they started with giving examples for 2-3 distros which is what in the begining of the book, i mean for redhat do this , for bsd do this and so on, and i guess they got bored and wrote that. well that is all good and fine trent or whatever yourname is who wrote this chapter but the var subdirectory has many more files do you expect me to go trough each and every one? i kid you not the qoutes are from the book. reading on , they do say (after maybe you paused and look for each and every one of the file which is the lease files :) ) that the man ( again :) ) dhcpd.conf shoud tell you where the lease file is located. whell i am thinking , is better the nothing right? and i start man dhcpd.conf , forward slah and i am looking for leases instances :) if you can believe that :| and after going to about 60 instances of leases i find out that there is no such thing as telling the location of the lease files. what a waste of time!9. and btw the dhcp is one example. there are many topics written in a laughable manner. for example when you buy a 1000 pages book about linux you expect to learn about samba right which is in my opinion an important component that is sharing files between linux and windows in the internet age. well again :)))) they give you a 3 pages (is defenetely less but i cant remember exact no of pages ) discussion about samba and again references to the man pages. i am laughing as i type this.10. regarding to this ... i mean ... networking chapter 100+ pages with 8pt font and a lot of words typed on it you'd expect and beeing resonable, to give you at least a starting point from where you can go on your journey to learning , i mean again i dont buy a book to get referenced to the man pages because i want to learn from someone who understands it and explains it in a manner that is easy for one to understand ( this is for me at least the reason i buy a book and not reading the man pages). nevertheless is no trouble if they give you references to the man pages. the problem i have with this book is that , you as an author, can reference the man pages , but my friends , after you give a starting poing , that is explaining at least 40% of the subject . not giving a laughable configuration example , not referencing to something that does not exist (man dhcpd.conf - lease file) not saying something like "you shoud do that" and then move to a different subjet and defenatelly not writing a chapter about networking and explaining offtopics subjects (like networking in a linux book) in great detail and only explain in a few words an inportant component for networking like dhcp11. to be fair not all the chapters are a disaster . for example dns chapter is well writen . they start with a blueprint , giving you the layout of the config file , the definition , and so on , and they they get to the practical examples , which is not covered in full but at least they give you a config example that will work on most dns servers. aplause for that.12. one may ask if the content of the relevant topic is scarce what are the 1000+ pages for ? well :)))) againis a little bit of everything. reference to the blueprint as i said before. a little bit of this and that a lot of reference to the man pages. there are a lot of things explained and no continuity, for example spf is covered in the book only to say some words about it and again no practical examples of any kind. you get a lot of off topic content which is fun if you think of it a book about linux which is not focused on linux :) i mean... you do get in a linux book the terms and definition for installing / configuring / and whatever ( i stopped reading at that point ) for google cloud and amazon aws :) which again the information is welcomed. but in my opinion a book about linux shoud focus on linux not on 30 pages of networking and only 2 or less on samba for example13. if you have some experience you realise that there are people in the world that they do not share any info. in this line of work i have met people that they like to "show how smart they are by solving a rather simple problem" , arogant and whatever and do not share any info. this is the feeling i am getting for some of the writers of the book. again as i said they throw in a rather complex example of something (i am guessing to show how smart they are) and they continue by sayin something advanced like "you should get you dhcp server to work with dns" and then they stop :) well , this is only valid if we met in a bar and have a discussion about linux , but from the moment i bought the book , and i paid you for something you shoud have provided and going trough this chapters only to realise that this was only a mere waste of time , then i can only give this review in hoping that a reader , a potential reader understands exactlly the kind of value you are bringing to the table14. again i chalenge anyone who wrote the book , anyone who actually read it to prove me wrong. to prove me that after you read the dhcp paragraphs you can say that you understand how dhcp configuration works , anyone that has read that samba laughable example that can say that it has a starting point and if so if that is what he expected 2 pages on a linux important component on a 1000+ pages book.15. one more and i finish up . i had to mention this . another laughable example is mail . they say in the book that sendmail is obsolete and of course they not only dedicate 30 pages or so to covering something that is no longer in use but they start with that too :) . not only that after reading about postfix i can say without any doubt that this is indeed a waste of time, not giving practical examples, not having cntinuity not giving commands , the most used options , is somewhat (the chapter) a discussion between 2 guys that are having a drink and discuss somewhat advanced manner. the point is you dont understand anything if you are getting started with that, that is administering mail. they give you some definitions ,some of this and that, but nothing that you can build from.16. i have tryed my best to give an honest review. maybe to help a potential buyer to understand what is buying and with this the promise that i will never buy any of the book those so called authors wrote. this has been a complete waste of time. the worst book i have ever bought. and a very bad investment.17. a shoutout if you can call that goes to the technical reviewers that they shoud point out the amount of missing info that this book has. and the lack of consistency in going trough each step of explaining things.18. i still dont understand why people give 5 stars to this book. i a m guessing that maybe because amazon sends review request by mail in the 30 day from when i buy the book and one does not have time to read it.