4 ms·
When I was much younger I used to find this funny and entertaining, but nowadays I just find it boring. It always seems fashionable to hate on things, and I'm
by kelnos 3y ago
When I was much younger I used to find this funny and entertaining, but nowadays I just find it boring. It always seems fashionable to hate on things, and I'm just tired of the depressing, defeatist attitudes that support that fashion.
I do wonder, though, if this were (re)written today, how much of it would be the same, how much of it would be outdated, and how much new stuff the haters would come up with.
The chapter on file systems is mostly no longer relevant (some file systems do still suck, but the defaults are pretty solid now). NFS still sucks (IMO it sucks more than it used to), but far fewer people need to use it nowadays. C and C++ are still unfortunately prevalent, but there are at least quite a few systems programming alternatives, and they're gaining ground. Sendmail isn't the only game in town anymore, and I expect most outfits use something else these days, and USENET is a distant memory for most people, so there go another two chapters.
But then the terminal/TTY situation has barely changed, and how all that works is just as (if not more) divorced from the reality of daily usage. Security has improved, but most people still have a god-mode root account, and most of the security improvements have come out of necessity; the world of networked computing is much more "dangerous" today than it was in the early 90s. Documentation is still often poor, and many systems still seem designed more for programmers than less-technical users.
I wonder what they'd think of systemd and Wayland!
- lubutu 3y ago> NFS still sucks (IMO it sucks more than it used to) Any chance you could elaborate?
- kelnos 3y agoSeveral of the criticisms the book lists are still true today. File locking is unreliable, deletions are weird, security is either garbage (in that you set it up in a way where there's very little security) or trash (in that you have to set up Kerberos infrastructure to make it work, and no one wants to have to do that). Perhaps I was a bit hyperbolic about it sucking more nowadays. At least you can use TCP with it and not UDP, and you can configure it so you can actually interrupt file operations when the server unexpectedly goes away and doesn't come back, instead of having to reboot your machine to clear things out. But most of what the book says is still the NFS status quo today, 30 years later.
- chungy 3y agoEverything you listed was fixed in NFSv4. Don't use the ancient versions of NFS.
- yrro 3y agoWe're not there with authentication yet (although I've no problem with Kerberos myself).
- kiney 3y agoeasist way nowadays to get secure NFS is to just set up a wireguard tunnel
- yrro 3y agoNo because you still have to trust the client. With Kerberos a hacked client where user 1 has authenticated can't impersonate user 2 unless that user has also authenticated on the client. With sec=sys the client is simply trusted without any per-user authentication.
- kiney 3y agoin most cases you can just use more fine-grained exports. e.g. export /home/user1 to 10.0.0.1 and /home/user2 to 10.0.0.2 instead of /home to 10.0.0.0/24 etc.
- gnufx 3y agoHow are we not there? The only real issue I know is allegedly requiring host keys for gssd (e.g. "joining the domain"), but rpc.gssd(8) documents "anyname" principals.
- yrro 3y agoThe only per-user authentication option is Kerberos. Username/password based authentication is not possible.
- anthk 3y agoOn Unix and the rest of the comment: plan9/9front superseded it well: - 9p+encryption on top instead of NFS, much better. - C under plan9 it's far better and easier than POSIX. Also, we had Golang under Unix which almost made that better C philosophy into Unix with a better systems language. - Usenet/IRC works and you'll get far more trolls under the web. - The terminal makes things better in most cases than freezing UI's or Emacs, see my another post. But 9front doesn't use terminals, it's graphical from the start and composable. - On security, plan9/9front uses namespaces and factotum plus decoupled servers/devices for hardware, a much better design. - On documentation, the rest of the OSes have it far worse. But it was almost the same case with ITS and Macsyma/Maclisp, where you had a reference book and not starting guides to ease the learning of the language. GNU Texinfo made at least an Elisp intro a Maxima it's far better docummented wth on-line guides and examples. - SystemD it's a disaster, and Wayland destroys any scriptabilily/hacks with wmctrl/xdotool/custom WM/DE's or something simple like remapping keys on broken keyboards (I use the "<>" key as "\ |" as my physical one it's broken, and I already have < and > near 'm') and it works.
- jclulow 3y ago> 9p+encryption on top instead of NFS, much better NFS with IPsec for authentication and privacy seems similar in principle, with the added benefit that it's widely available.
- gnufx 3y agoNo, per https://news.ycombinator.com/item?id=40112697 https://news.ycombinator.com/item?id=40112697
- MisterTea 3y ago> NFS with IPsec for authentication and privacy seems similar in principle, But a total hack and duct taped together. > with the added benefit that it's widely available. On plan 9/ 9front 9p over TLS is out of the box. ipsec isnt.
- boxed 3y ago> The chapter on file systems is mostly no longer relevant (some file systems do still suck, but the defaults are pretty solid now) Really? Afaik filesystems still do `rm` immediately and with no recourse. GUIs on top like Finder and Explorer do something more sane though, but that doesn't save us terminal users. POSIX shell expansion is just as crazy as it has ever been too. Those are the two gigantic foot guns I can recall from memory from having read this 20 years ago.
- isametry 3y agoI know this is a discussion of Unix in general, but on your own Mac, you can get `trash` packages for the terminal [0] [1]. I use the former, I haven’t tried the latter. But afaict, they should be pretty much identical – they both supply `trash <path>` which could, for most intents and purposes, probably be aliased as `rm`. One thing to note is that none of these tools seem to support the “Put Back” feature of Finder. Trashed files don’t remember their original locations. But I’ll personally still choose that over being nervous before every `rm`. [0] – https://formulae.brew.sh/formula/trash https://formulae.brew.sh/formula/trash [1] – https://formulae.brew.sh/formula/macos-trash https://formulae.brew.sh/formula/macos-trash
- boxed 3y agoYea sure.. but again a big recurring theme of The Unix Haters Manual is "broken by default". That things can be fixed isn't the point, if the fix is local, ephemeral, easily forgotten, and the fix not being implemented is blamed on the user because "you can fix it". Broken by default is itself exactly the problem.
- skissane 3y agoI think some of its criticisms (see e.g. pages numbered 20-21, PDF pages 60-61) remain valid: (1) Unlike OpenVMS/TOPS-20/LispMachines/etc, mainstream POSIX file systems lack built-in versioning (there are a small number of POSIX systems which implemented it, e.g. SCO OpenServer's HTFS, but for whatever reason more mainstream systems like Linux or *BSD never did) (2) Directly related to (1), the fact that the unlink() system call is normally irreversible, and the rm command is (normally) a direct interface to unlink() (3) The simplicity of the interface between the shell and the commands it runs (just a list of strings, only slightly better than the DOS/Windows approach of a single string), and the potential issues induced by the fact that wildcards are implemented by the shell not the command itself. Regarding (3), OpenVMS DCL, IBM OS/400 and Microsoft PowerShell are all examples of systems where option parsing/etc happens in the shell, and the command is passed a parsed command line structure instead. However, although they are better in this regard, they have other disadvantages (the first two are super-proprietary; PowerShell is open source, but weighed down by the heaviness of .Net) I think a lot of historical issues with Unix are due to the fact that shared libraries didn't exist until much later, so seemingly obvious things like "put wildcard parsing in a shared library like getopt() is" weren't possible at the start. Also, Unix has never had any kind of standard structured data format (JSON would work, but it didn't exist for the first 30 years of Unix's existence), which is a problem for ideas like passing command arguments as structured data. > But then the terminal/TTY situation has barely changed, POSIX TTYs are a horrific pile of kludges, especially when one considers stuff like ECMA-48 (which isn't technically part of the POSIX TTY stack, but de facto is). Someone should just redo it as something more sensible, like exchanging null-terminated JSON packets. But getting everyone to agree on that is probably too hard.
- Bene592 3y agoFor (1) there's stuff like BTRFS snapshots, or you could use Git on top of the FS
- skissane 3y ago> For (1) there's stuff like BTRFS snapshots, From what I understand, BTRFS snapshots are time-based. Whereas, in classic versioned file systems, a "snapshot" is triggered by open/close operations – each time you open a file for writing, that creates a new snapshot. > or you could use Git on top of the FS Git requires your application to have explicit support for working with Git repos, it isn't seamless. And I know some people have built FUSE-on-Git implementations (there are a few around), but (I believe) they've all got various limitations and I don't believe (I could be wrong) that any of them is quite the same experience as a true versioned filesystem
- nurettin 3y ago> C and C++ are still unfortunately prevalent come now, they look nothing like they were 30 years ago.
- anthk 3y agoDon't confuse C and C++ because C99 covers a lot and it's 25 years old.
- rho4 3y agoWent through the same progression with Dilbert comics. Colleagues with a positive general attitude are priceless.
- msla 3y agoI can't get over the idea that this is a bunch of people who were angry their favorite proprietary systems got killed by open standards and, ultimately, open source. Compatibility and not being dependent on a single company are good things!