It was only a passing wonder, because in my specific case the original fifo is on an NFS mount and I needed it to be accessible elsewhere. So hardlink wouldn't have worked anyway.
@jesse_b oh it's not the worst I've seen by far, it's just an immediate warning that the person who wrote the script didn't understand what command substitution actually does and there will probably be much worse things also.
By the time Windows 7 came out I was jaded enough to know that anything that could only run on Windows 7, would probably not run on any system in 30 years.
Of course it helps that this is a virtualbox VM and I never shut it down, I "save state" and close it, so I don't actually go through the Windows login process again. If/when I have done that I seem to recall that I did sometimes run into trouble with the trial period expiring after all.
Although, as I recall I had trouble using the license key last time I tried. I think I ended up finding a wikihow article that directed on how to modify the registry entry so the thirty day trial would become like a 30000 day trial or something like that.
Searching (without quotes) "Stallman content terminology" found it in one shot on Google (just found the top level "words to avoid" page) but nothing related on DDG. Interesting example of the difference.
I'm trying to hunt down an article I saw years ago, I think from Richard Stallman, about why he thinks the generic word "content" is demeaning to art and artists. Anyone know what I'm talking about or where I could find it?
Apropos of nothing, I was amused to come across this old answer from Jeff Atwood in 2011. My how the times have changed. unix.meta.stackexchange.com/a/595/135943
And I think the other was more focused on the idea that technical people love interesting problems but hate stupidity, or something along those lines, and you need to convince them e.g. in your email title that it's not a total waste of their time to read it.
Search engines are turning up some random "wikihow" articles for how to post on Stack Overflow, which is NOT what I'm looking for. There were a few I remember reading. One was from one specific person who was apparently well-known (though not to me), which covered a lot of useful debugging advice as well as how to write the question.
There's one that talks about reproducing the problem, doing your homework, etc., etc. Advice that's equally applicable to posting on an email list as it is to posting on S.O.
@bmike thanks, hadn't heard of that. It's kind of the opposite of my use case, though, because it's about input, not output. Nothing secret gets typed into the terminal in my scenario, so keystroke loggers (or whatever) wouldn't be able to catch anything important.
@verbose Thanks, I think I will ask it on the site then for posterity. I'll link back to chat as well since there are so many useful tips already given. (Will ask in several hours, after work.)
And I'm wondering if there's some way to put it online. I don't necessarily want to go through the work of scanning it myself, but maybe there is a project whereby I could give it to someone to do so?
