6 ms·
Learning modern Linux: A handbook for the cloud native practitioner
- leetrout 5y agoI am so sick of the word practitioner. I don't have a better alternative but something about practitioner just feels so forced and stuffy. On the flip side I do like viewing operation of technical tooling in support of businesses as a practice to be continually improved. Most businesses don't really embrace that in my experience. If they did, even with it being a cost center, they would spend more time making sound decisions around tech being used (which would hopefully reduce the k8s mania).
- orangepurple 5y agoI have a similar reaction when people are called consumers. They should just cut to the chase and call them what they really want to call them: useless eaters.
- kk6mrp 5y agoSo is this a book mostly on Linux or Linux with systemd?
- wrycoder 5y agoThe latter
- znpy 5y agoEverything looks okay except for the section regarding other “friendly” shells: that’s really the part where we as an industry don’t need more fragmentation.
- sophacles 5y agoRight, how dare people use tools that they find comfortable and enjoy using? What if they choose a tool that goes against your preferences, or worse (bad word coming, consider yourself warned) makes you have to learn something?
- _vdpp 5y agoAs a fish user myself, I’ll admit there is something to be said for standardization. It’s easy to poke fun at somebody for being afraid to learn something new - but with the explosion of different tools it’s becoming impossible to stay abreast of all the changes and feel proficient in anything anymore.
- BirAdam 5y agoStandardization builds industries and economies of scale. Having competing standards is great for technologists, but makes the current problem particularly painful: in job descriptions, employers now specify not just general technologies used but also particular frameworks, ci/cd tools, and on and on. So many tools that a person must be competent with using, that only a handful of people might know all of them on day one, which makes hiring much more expensive. You either pay over market rate for the perfect person, or hire someone decent and pay for them to learn the job. Ultimately, I think we’re in a better place than we were without modern tooling, but it makes it hard to hire…
- jeroenhd 5y agoI don't see the problem. I like zsh and I can live with bash. I've tried fish, but it just didn't click with me. Others swear by fish and how it revolutionised their terminal. Hell,I've seen people fall in love with Powershell of all shells because of its interactivity and cross platform scripting language that doesn't rely on Unix tools being present in $PATH. I don't get it, but that's okay; they can have their preferences and I can have mine. You've got to find what works for you. Nano, emacs, .*vim, vi, using a magnetic needle to manually flip bits on a spinning platter, it doesn't matter, whatever keeps you happy and/or productive. The vast majority of Linux users seem to use bash. Zsh has been picked up more and more by Apple for licensing and the "threat" of open source. I don't think shells like fish are a threat to the ecosystem as long as they keep the most basic form of compatibility with bash (not sh). You need bash installed anyway, otherwise you can't curl2bash to install "modern" Linux software!
- hedora 5y agoThe problem comes in when you need to manage 100's of machines, and there isn't a single shell that is in everyone on the team's muscle memory.
- mixmastamyk 5y agoYou don’t use a shell for that, directly. Ansible, puppet, docker, etc.
- theamk 5y agoThat's what sh or bash is for, a least common denominator present on every machine. Sure, it is not the same as your home machine - but even with the right shell, you customized config files woukd still be missing. So it is easier to get used to defaukt setup on defaut shell when managing many machines. (This is the reason I had to learn vi back in the day: sure, my machine has lovingly customized emacs.. But that old Sun one needs to debug? Vi only.)
- fragmede 5y agoand not even vim, but vi.
- plandis 5y agoDisagree. In my experience it’s way easier to use something like fish out of the box rather than spending hours configuring bash to your liking assuming you don’t have your dot files made to your liking yet. If someone is just starting out I’d absolutely recommend something like fish or zsh over bash or csh.
- aulin 5y agoIt's almost twenty years that I use Linux daily and the only thing I ever changed in .bashrc is the history size. What kind of customizations are we talking about? maybe I'm missing out using stock bash configuration and I should start customizing it to my liking it (serious, no sarcasm)
- barefeg 5y agoAutocomplete from history is something I really enjoy from my config. I can live without the nice colors and data. Though having the execution time of the previous command has been very handy a few times
- fragmede 5y agofzf for command history searching custom PATH for your own programs options to programs like LESS
- p5a0u9l 5y agoHistory-based auto completion is a productivity game changer. But, You can get fish-like niceties with trivial effort in zsh. The deal breaker for be with fish is abandoning decades of bash syntax. With zsh, I can have my fancy, productive prompt and still write bash-compatible sheets scripts.
- rmbyrro 5y agoAnd who is gonna decide which shells stay or go?
- _vdpp 5y agoI could probably use this. My muscle memory still reaches for “ifconfig”.
- tra3 5y agoMe too. I just, yet again, rediscovered the ip command. This and moving to systemd from init are two things that always trip me up.
- mindcrime 5y agoA couple of days ago I needed to set up a scheduled job for something. I typed "crontab -e" and got "no such command or filename" and remembered "Oh yeah, this distro doesn't even install cron by default anymore." I could have done a quick "dnf -y install cronie", but I decided "F it, might as well go ahead and learn to write SystemD timer definitions". It wasn't bad, but I feel like I've turned to the dark side or something.
- jhgb 5y agoGood news - a new version of Slackware was released just for you! ;) (And me as well, actually)
- GekkePrutser 5y agoAnd the command line options for netstat, route etc.. But usually I just install net-tools :) I know it's outdated but my main driver is FreeBSD where these tools are still the normal toolchain.
- marcosdumay 5y agoBut then, a book won't fix your muscle memory. I'm also one of the many people suffering for the loss of the old tools. Maybe we should create a support group? Anyway, I would keep them installed, but the new ones interfaces just make a lot more sense, so even though it's hard to write the correct command (they could be better documented), it is much easier to decide if a command is correct or not after it's written.
- 5y ago
- blub 5y agoI’ve read some chapters from the linked book to complement “How Linux Works” from No Starch Press and while the information was useful and seemed correct, in the end I decided to stick with HLW, since it was both broader and deeper at ~460 vs 250 pages.
- amelius 5y agoWhat is the best book on the design/architecture of the Linux kernel?
- nickmcc 5y agoOne very in-depth book I have is: The Linux Programming Interface: A Linux and UNIX System Programming Handbook
- fitnessrunner 5y agoHave you read it? I recently purchased a copy, and the exercises look fun/useful.
- jb3689 5y agoAs someone who does not write C regularly and doesn’t not need to read stacks docs regularly, I’ve found it immensely useful. I have not gotten very far yet but have already found real world use for flag combinations for avoiding race conditions
- nbaksalyar 5y agoAlthough it's not a book, the Linux documentation [1] is actually very good and does the job of explaining design and architecture of the kernel. I'd also suggest reading "Unix Internals" by Uresh Vahalia. While this book is from 1995 and it doesn't cover Linux specifically, it's an exceptional resource for understanding how *nix kernels work in general. [1] https://docs.kernel.org/ https://docs.kernel.org/
- valbaca 5y ago"A Heavily Commented Linux Kernel Source Code" by Zhao Jiong and "The Linux Programming Interface" by Michael Kerrisk are the best I'm aware of.
- alfiedotwtf 5y agoAlso Maxwell's "Linux Core Kernel Commentary" which also annotates the kernel. It's old so is based on 2.2, but its a gold mine
- readingnews 5y agoI have been using linux since 1992, Solaris and UNIX (dec, etc) before then... I run Gentoo now on my box, compile my own kernels, etc. I admin 100s of linux boxes at work.. but there is verbiage that different people see totally differently: What does "Learn critical components such as the Linux kernel" mean to the author? I have not read this book, but do they mean we are going kernel hacking or I will show you how to compile a kernel for cloud native applications (whatever that would mean, really)?
- hoppyhoppy2 5y agoThe book's table of contents is viewable at the link, if that helps at all.
- mellosouls 5y agoWe're doing book adverts now?
- leetrout 5y agoYes with quite a lot of defense for some reason.
- rmbyrro 5y agoThe author [1] appears to have some substantial hands on experience [1] https://mhausenblas.info/ https://mhausenblas.info/
- jb3689 5y agoI skimmed this book the other day while looking for OReilly books. It was alright. It doesn’t offer enough over other similar books like How Linux Works, the ship book, or TLPI. Maybe one advantage is the detail of the networking chapter which is more substantial than the ship book or HLW. Still however it is not enough for understanding modern cloud infra