3 ms·
Your first paragraph is spot on. A quick look at the ToC made me think it's a "how to reproduce every r/unixporn screenshot ever" rather than teaching something
by koito17 3y ago
Your first paragraph is spot on. A quick look at the ToC made me think it's a "how to reproduce every r/unixporn screenshot ever" rather than teaching something interesting about Linux for people well-versed in administering or using other Unix-like systems (e.g. Mac OS, FreeBSD, ...).
This may be oddly specific to myself, but I hate having to memorize internal IPs and like to address my computers with their hostnames. This article makes no attempt to tell me anything about hostnames, mDNS, DNS-SD, etc. on Linux. Is mDNS configured OOTB on most Linux distros like it is on Mac OS? If not, which implementations should I consider using? So on, so forth.
I also find it a bit amusing NeoVim is automatically chosen for the reader. I'll stick with Emacs, and I know many others will stick with VS Code or just plain old Vim. :)
- candiddevmike 3y agomDNS does work out of the box mostly with systemd-resolve (and the right firewall rules if you only allow certain inbound traffic). You can add something like avahi and have Linux do more interesting things like reflection between interfaces/networks--critical for segregating your Chromecasts and other IoT devices.
- sbuk 3y agoI get that some people want to switch from macOS to Linux, but why would they want to change from *BSD? In all likelihood, one uses a BSD precisely because it's not GNU.