Sixth round final proofreading

006/006 time.csv

@@ -67,3 +67,4 @@ Date,Topic,Minutes
 2026.02.22,,44
 2026.02.26,fifth round final proofreading,44
 2026.03.01,,32
+2026.03.15, sixth round final proofreading,30

006/chapters/basic_terminal_commands.tex

@@ -32,10 +32,10 @@ The point here is that a terminal is a physical object (either keyboard and prin
 
 In figure \ref{dec10}, we see a DEC terminal, which is similar to the terminal I used when I was in college the first time around. I wrote about this way back in the third issue of this zine, which seems like a lifetime ago, but was really only two and a half years ago. (Gosh, how times flies when you and the rest of the world are in the middle of an existential crisis.) It occurs to me that I am a member of an increasingly smaller and smaller group: people who used an actual terminal to do stuff. Of course, at the time ``doing stuff'' basically meant just typing up my notes from class. 
 
-By far, one of the most popular (not to mention the earliest) terminals in Linux is \textsf{Bash}—the Bourne Again SHell. The actual Bourne shell was developed by Stephen Bourne at Bell Labs in 1979 for use on Unix. Bash was created by Brian Fox for the GNU project in 1989 as a free software alternative to the Bourne shell—same functions, different code base.
-
 My background in computers was pretty much limited programming in BASIC, and I had no idea how to do much else. But I had terrible handwriting, and I wanted a decent copy of my class notes to refer to, so it was either check out a typewriter room on the first floor of the dorm or the second floor of the library\footnote{In those days, you could check out a study room either with or without a typewriter. What an eternity ago that seems like now.} or use the computer. Using the computer meant that I didn't have to bother with correction paper—I could just edit on the terminal. I would save my files, then send them to the printer in another room, then go stand in line to get my printouts. It was a different age, to be certain.
 
+By far, one of the most popular (not to mention the earliest) terminals in Linux is \textsf{Bash}—the Bourne Again SHell. The actual Bourne shell was developed by Stephen Bourne at Bell Labs in 1979 for use on Unix. Bash was created by Brian Fox for the GNU project in 1989 as a free software alternative to the Bourne shell—same functions, different code base. It's the one I use on a daily basis.
+
 \section{Basic Commands}
 
 Enough about me. Let's talk about some basic terminal commands you can start using right now. But first, we need to talk about information, and which way it flows…

006/chapters/coda.tex

@@ -26,7 +26,7 @@ The first line saves the \texttt{textsf} command under a new name (\texttt{oldte
 \begin{small}
 \paragraph{I cannot believe that this is where we are:}This is the sixth issue of this zine. I originally created this zine to learn \LaTeX{} and also to learn more about Linux (and get some practice with Git in the meantime). I thought I might get at most one or two issues and that would be the end of it. So when I started doing this, I pushed everything to my git repo at \kref{https://git.kjodle.net/kjodle/the-codex}{https://git.kjodle.net/kjodle/the\\-codex}. 
 
-It looks like this is a thing now, and a single repo just won't work. I'm at well over 300 commits in that repo, which doesn't really reveal much about the state of each issue. Going forward, I've decided to make this an organization on my git repo at \kref{https://git.kjodle.net/the-codex-zine}{https://git.kjodle.net/the-codex-\\zine}. That way, each issue can have its own repository and will eventually come to a logical end, instead of being never ending. I still need to move the wiki over from its current location at \kref{https://git.kjodle.net/kjodle/the-codex/wiki}{https://git.kjodle.net/kjodle/the\\-codex/wiki}. 
+It looks like this is a thing now, and a single repo just won't work. I'm at well over 300 commits in that repo, which doesn't really reveal much about the state of each issue. Going forward, I've decided to make this an organization on my git repo at \kref{https://git.kjodle.net/the-codex-zine}{https://git.kjodle.net/the-codex-\\zine}. That way, each issue can have its own repository and will eventually come to a logical end, instead of being never ending. 
 
 Believe it or not, I also have a forum for it at \kref{https://forums.kjodle.net/forumdisplay.php?fid=15}{https://forums.kjodle.net/\\forumdisplay.php?fid=15}, so if you want to join that forum and share your opinions and ideas, I encourage you to do so.
 

006/chapters/open_source.tex

@@ -4,7 +4,7 @@
 
 As a Linux user, I'm a big fan of open-source software. All the software I use in real life (i.e., when I'm not at work) is open source. (I finally did abandon VueScan for NAPS2, as I mentioned back in issue \#4.) I don't want Microsoft or Apple or Google in my personal life at all, if I can avoid it. I'm not worried about their stealing my identity or anything like that. For the most part, they already have it. What I want to avoid is their pernicious insistence on occupying a larger and larger role in my life. Alas, that takes a bit of work these days.
 
-Also, open-source is a difficult path to follow these days. There are always people looking to exploit this model for their own greed. As I mention in the next issue, it helps to examine a person's personal source code. 
+Also, open-source is a difficult path to follow these days. There are always people looking to exploit this model for their own greed. I'm not sure if greed and exploitation are a feature or a bug of the human species. 
 
 \subsection{GitHub}
 
@@ -20,7 +20,7 @@ Second, Microsoft included the option to just get a text message, but also indic
 
 This is problematic in so many ways. For one thing, once I have that app on my phone, Microsoft is now embedded in my life. It goes everywhere I go. If I have to choose between a Microsoft product or some other non-Microsoft product in the future, I am more likely to go with the Microsoft app because hey, I already have their authenticator app and so that's one less app I need to download and install, one less login I need to maintain. Microsoft is my friend, after all, looking out for me and making my life easier by providing this free app that makes 2FA so easy to manage. What a wonderful Big Brother it is!
 
-The worst thing about this is how deceitful it is. First, Microsoft creates an artificial barrier to doing what you want to do, and then it conveniently offers you a ``free'' solution to get around that barrier.\footnote{We would be wise here to remember Doctorow's Law: In a capitalist society, if somebody gives you something for free, you are not the customer, you are the product.} And of course, that solution means that Microsoft is going everywhere you go. It's a part of your life now. You can only get rid of it with a great deal of effort. 
+What bothers me most about this is how deceitful it is. First, Microsoft creates an artificial barrier to doing what you want to do, and then it conveniently offers you a ``free'' solution to get around that barrier.\footnote{We would be wise here to remember Doctorow's Law: In a capitalist society, if somebody gives you something for free, you are not the customer, you are the product.} And of course, that solution means that Microsoft is going everywhere you go. It's a part of your life now. You can only get rid of it with a great deal of effort. 
 
 As an aside, my company is heavily invested in Microsoft technology, and we have to use 2FA to log into our VPN. Fortunately, they gave us the option of either using the app or using these little credit-card sized authenticator cards (they call them tokens; I'm not sure if that's the official name). But there have been rumors that the tokens will soon go away and we'll be forced to install the Microsoft authenticator app on our phones and use that. For that reason (among others) I am looking to move on from this company. If they want me to use a digital device, then they need to provide it. Why should I have to spend my increasingly dwindling resources to help them make more profit?
 
@@ -30,7 +30,7 @@ So long, GitHub. It was good while it lasted, but nothing gold can stay.
 
 \subsection{WordPress}
 
-I started using WordPress when I created my second website at \kref{https://kjodle.net/}{https://kjodle.net/}. I was pretty excited about this blogging business, which was part of the what all the people in the education sphere called ``Web 2.0''.\footnote{See issue ``The Salad Days Are Over'' in issue \#5.}
+I started using WordPress when I created my second website. I was pretty excited about this blogging business, which was part of the what all the people in the education sphere called ``Web 2.0''.\footnote{See issue ``The Salad Days Are Over'' in issue \#5.}
 
 Back in the day, I absolutely \textit{loved} WordPress. The community was warm and welcoming and I made a lot of friends. Through developing themes, child themes, and plugins, I learned a lot about HTML, CSS, and PHP, as well as the basics of MySQL databases. Alas, that \textit{official} WordPress community was only warm and welcoming as long as you agreed with all the decisions The Powers That Be are making. Dissention (or disagreement or even just plain confusion) were not tolerated. You either toe the line or you protest what you view as unnecessary changes (i.e., solutions in search of a problem) and get the boot. 
 
@@ -56,7 +56,7 @@ I don't have too much issue with this (if that's the direction they want to go,
 
 The key difference between WordPress and all those other companies is that Matt Mullenweg holds the keys to \textit{both} wordpress.org \textit{and} wordpress.com. All the hundreds and thousands of people who have contributed hundreds of thousands, if not millions, of hours of their labor to wordpress.org—a non-profit open-source project—have also been forced to contribute those same hours to wordpress.com—a for-profit company. And because Mullenweg has control over both, he can direct all those volunteers to direct their work in a way that benefits not just the non-profit, open-source project, but also the for-profit company.
 
-This is a tremendous conflict of interest. Part of the purpose of the Gutenberg project was to make all those page-building plugins in the WordPress plugin repository unnecessary—and to impact the companies producing them with a financial hit, since most of them include both free (but limited) and paid (and thus, fully-featured) versions. If their customers no longer need those plugins because their capabilities are now part of WordPress core, those companies lose out on income, and possibly go out of business, meaning that wordpress.\textit{com} has fewer competitors.\footnote{Squashing your competitors is a feature, not a bug, of capitalism. If it weren't we wouldn't need anti-trust laws, would we?}
+This is a tremendous conflict of interest. Part of the purpose of the Gutenberg project was to make all those page-building plugins in the WordPress plugin repository unnecessary—which will impact the companies producing them with a financial hit, since most of them include both free (but limited) and paid (and thus, fully-featured) versions. If their customers no longer need those plugins because their capabilities are now part of WordPress core, those companies lose out on income, and possibly go out of business, meaning that wordpress.\textit{com} has fewer competitors.\footnote{Squashing your competitors is a feature, not a bug, of capitalism. If it weren't we wouldn't need anti-trust laws, would we?}
 
 And now that WordPress (.org? .com? I'm not sure which anymore.) has attacked WPEngine for not ``supporting'' the wordpress.org project, we see that this is not really about promoting open-source projects but about yet another oligarch (or in this case, a wannabe oligarch; Mullenweg is small peanuts compared to others) trying to consolidate his\footnote{It's interesting to note that all current oligarchs are male.} power, and drive all of its competitors out of their business either by hook or by crook, it seems. 
 
@@ -74,7 +74,7 @@ It's not always about money. I mean, it is \textit{partly} about money for now,
 \item Contribute to the documentation. A lot of open-source software projects have less than complete documentation. If you can help make it a bit more complete, please do. 
 \item Donate money. For better or for worse (mostly for worse) we live in a capitalist society where resources are allocated not on intrinsic value (i.e., how useful is this thing?) but on extrinsic value (i.e., how many people can we convince this thing is useful, even if it isn't?). Until the revolution comes\footnote{And it will someday, I'm sure—the only question is whether it will happen in time to save this planet.} we're going to have to depend on money.\par The good news is that you don't have to donate a lot of money. Capitalism is based on the Pareto Principle—80\% or more of the outputs are based on 20\% or less of the inputs. Alternatives to capitalism will advocate the Parity Principle, in which you give what you can, you take what you need, and you need what you take. If only 10\% of the users of any open-source project donated on an annual basis what they earn in an hour or even a half hour (after income taxes), then those software projects would probably experience anywhere between a 100 to a 1,000 times increase in their funding.
 \item Contribute to the core, if you can. Most of us can't, and that's okay. 
-\item You can always participate in the support forums, help other people out, and make suggestions for improvements.
+\item Participate in the support forums, help other people out, and make suggestions for improvements.
 \end{enumerate}
 
 \paragraph{About the title:} \textit{Support Your Local Sheriff} is a 1969 western/comedy starring James Garner. It was initially a box office bomb, and the movie studio wanted to pull it from theaters (because movie studios tend to be spineless, risk-averse creatures). Garner had confidence in it though, and challenged the studio to match a \$10,000 stake to keep it in the theaters. The studio accepted his challenge, word of mouth caught on, and the film became a minor classic. Kudos to Garner for putting his money where his mouth was. It's not the best film in the world, but it's worth a watch.