concerns-with-linux.html 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  2. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  4. <head>
  5. <title>Concerns with Linux - Kevin "The Nuclear" Bloom's Personal Website</title>
  6. <link rel="shortcut icon" type="image/png" href="/img/guy-in-space.png"/>
  7. <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
  8. <meta name="generator" content="Org mode" />
  9. <meta name="author" content="Kevin &quot;The Nuclear&quot; Bloom" />
  10. <meta http-equiv="cache-control" content="no-cache, must-revalidate, post-check=0, pre-check=0" />
  11. <meta http-equiv="cache-control" content="max-age=0" />
  12. <meta http-equiv="expires" content="0" />
  13. <meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
  14. <meta http-equiv="pragma" content="no-cache" />
  15. <link rel='stylesheet' href='/styles/main.2.css' />
  16. </head>
  17. <body>
  18. <div id="preamble" class="status">
  19. <div id="banner">
  20. <h1><a href="/home.html">Kevin "The Nuclear" Bloom</a></h1>
  21. <hr />
  22. <div id="navit">
  23. <a href="/contact.html">Contact</a>
  24. &nbsp;
  25. <a href="/blog.html">Blog</a>
  26. &nbsp;
  27. <a href="/projects.html">Projects</a>
  28. &nbsp;
  29. <a href="/about-me.html">About Me</a>
  30. </div>
  31. </div>
  32. </div>
  33. <div id="content">
  34. <div id="outline-container-org1f2e80f" class="outline-2">
  35. <h2 id="org1f2e80f">Concerns with Linux</h2>
  36. <div class="outline-text-2" id="text-org1f2e80f">
  37. <div class="PREVIEW">
  38. <p>
  39. A few months ago I was poking around on a Debian system just for fun and wanted
  40. to install <a href="https://gnu.org/s/emacs">GNU Emacs</a>. On the core install <a href="https://www.gtk.org/">GTK</a> isn't installed by default, so I
  41. fired up <code>apt</code> to pull down the program and it's <i>insane</i> amount of
  42. dependencies. When I saw the number of dependencies, I was shocked! I've built
  43. Emacs like a hundred times now and never needed all that. I was curious and
  44. began to look through the depends to see what's up. To my surprise, I found tons
  45. and tons of <i>unneeded</i> programs and libraries, especially <a href="https://webkitgtk.org/">webkitGTK</a>, which I
  46. have <i>never</i> needed for Emacs.<sup><a id="fnr.1" class="footref" href="#fn.1">1</a></sup> Especially because Emacs is an editor not a web
  47. browser. "Interesting," I said, "there could be hundreds of programs installed
  48. and no one would ever know&#x2026;" This thought made me take a deep look at the
  49. current state of GNU/Linux and here's what I've found.
  50. </p>
  51. </div>
  52. <p>
  53. While looking into my concerns on what I'm calling <i>dependency hell</i>, I ran into
  54. an interesting article entitled
  55. <a href="https://unixsheikh.com/articles/why-you-should-migrate-everything-from-linux-to-bsd.html">Why You Should Migrate Everything from Linux to BSD</a>.<sup><a id="fnr.2" class="footref" href="#fn.2">2</a></sup> While I'm not totally
  56. advocating that, it brought up some very interesting points and valid concerns
  57. with <a href="https://en.wikipedia.org/wiki/GNU_General_Public_License">GPL</a>'d software. From my own findings in tandem with the information from
  58. the article, I have come up with 4 concerns that I have with GNU/Linux:
  59. malicious influence, dependency hell, proprietary influence, and lack of care.
  60. </p>
  61. </div>
  62. <div id="outline-container-org18744db" class="outline-3">
  63. <h3 id="org18744db">Malicious Influence</h3>
  64. <div class="outline-text-3" id="text-org18744db">
  65. <p>
  66. If you read the article mentioned above, you'll see how <a href="https://systemd.io/">systemd</a>, Firefox, Linux
  67. (I don't think he explicitly mentioned Microsoft's influence in that article)
  68. have been influenced by companies in a potentially malicious way. I won't repeat
  69. what he wrote about but I will say that this should be a rather large concern
  70. for us. With core programs like systemd and Linux being hijacked can we really
  71. say if a GNU/Linux system (running systemd) is safe? Probably not. At this
  72. point, I wouldn't recommend anyone run a distro that using systemd. This knocks
  73. out many distros including but not limited to: Debian, Arch, and anything based
  74. on those 2 (besides Devuan).
  75. </p>
  76. <p>
  77. "But that's just one program, why does it matter?" Yes, it is one program,
  78. however, on the mentioned distros above, it is very difficult to run them
  79. without using systemd. Also, systemd has become a program of programs. It
  80. encompasses nearly every aspect of your system. It can even integrate with some
  81. programs such as Emacs.<sup><a id="fnr.3" class="footref" href="#fn.3">3</a></sup> In theory, systemd could be used as a gateway to
  82. nearly every part of your system. If that isn't concerning, I don't know what
  83. is! Check out <a href="https://unixsheikh.com/articles/systemd-isnt-safe-to-run-anywhere.html">this</a> article too!
  84. </p>
  85. </div>
  86. </div>
  87. <div id="outline-container-orgd7fd584" class="outline-3">
  88. <h3 id="orgd7fd584">Dependency Hell</h3>
  89. <div class="outline-text-3" id="text-orgd7fd584">
  90. <p>
  91. I have always complained about dependencies. I've been annoyed with them since
  92. like 2010! This is on of the many reasons I started using Dragora. It doesn't
  93. suffer from the same dependency struggles that you get when you have a
  94. dependency tree such as in <code>apt</code>, <code>pacman</code>, or <code>portage</code>. Why is this a concern
  95. for me? Well, the biggest issue that I see is that there is a potential for
  96. something unknown being put on your system. For example, say you never want to
  97. see webkitGTK again due to some security bug or something. Then you go to
  98. download Emacs and just like that you got webkitGTK back. A normal person
  99. wouldn't think Emacs would depend on something like that since it's an editor,
  100. not a web browser. This is not only annoying but potentially dangerous if that
  101. security bug hadn't been fixed in webkitGTK yet (only if you found yourself
  102. using it by accident).
  103. </p>
  104. <p>
  105. Another reason I dislike massive amounts of dependencies is that it complicates
  106. your system. You already are running a very complicated computer with a
  107. complicated OS with a complicated kernel etc, etc. Why add another complication
  108. to the party? Have hundreds and hundreds (potentially thousands) of dependencies
  109. is just a great way to break your system. You install an update, something
  110. breaks. Totally normal on a Arch system! Well, what broke? I don't know, go
  111. check the 100 packages that got updated in the last update. Good luck. That
  112. situation is truly stupid, in my opinion. The fewer dependencies the better, the
  113. simpler the system the better! There are only a few distros nowadays that don't
  114. suffer from this issue (that I know of): Dragora, Slackware, [potentially] Void,
  115. [potentially] Guix System (although this has other complicating factors), and
  116. CRUX.
  117. </p>
  118. </div>
  119. </div>
  120. <div id="outline-container-org1e701e5" class="outline-3">
  121. <h3 id="org1e701e5">Proprietary Influence</h3>
  122. <div class="outline-text-3" id="text-org1e701e5">
  123. <p>
  124. Why doesn't it seem to bother anyone except for free/libre-tards, such as
  125. myself, that there are so many damn proprietary modules in Linux? Also, why the
  126. hell does no one care that Linux is starting to be more like the Windows kernel
  127. with it's ~28 million lines of code and hundreds, potentially thousands, of
  128. proprietary drivers/modules? Heck, at this rate Linux <i>will</i> be the new
  129. Windows!! Well, I believe that part of the reason for this odd behavior is that
  130. Microsoft (MS) is "hijacking" Linux (the kernel). I don't have any real proof of this
  131. except that MS going from hating Linux to loving them and now they're donating
  132. tons of money to The Linux Foundation&#x2026; Yeah, seems sketchy to me! If I was
  133. getting millions of dollars to do something, I'd probably listen to the guy
  134. giving it to me.
  135. </p>
  136. <p>
  137. At the rate this is going, I wouldn't be surprised if we would start to see
  138. potentially malicious code being put into Linux and it becoming difficult or
  139. impossible to turn off. This would be a major concern to projects like
  140. <a href="https://www.fsfla.org/ikiwiki/selibre/linux-libre/">Linux-libre</a> whom just take the code and run it through a de-blobbing program. If
  141. something like that were to happen, I doubt that the folks at Linux-libre would
  142. have the manpower to fork Linux and keep it going. It would be interesting to
  143. see what would happen that's for sure.
  144. </p>
  145. </div>
  146. </div>
  147. <div id="outline-container-org018908f" class="outline-3">
  148. <h3 id="org018908f">Lack of Care</h3>
  149. <div class="outline-text-3" id="text-org018908f">
  150. <p>
  151. As mentioned in the previous section, no one seems to care about what's going on
  152. here! There are some folks in the "Free Software-side" of the GNU/Linux
  153. community that do but the majority don't. I believe that this may be the worst
  154. factor of them all. If the community just lets all this stuff happen <b>it will
  155. happen</b> and it won't get better. Unless we actively refuse these concerning
  156. items, they'll just keep going. Sadly, I don't think that the community will do
  157. this. I believe that in due time we will see Linux push malicious changes and
  158. other programs following suit (such as systemd).
  159. </p>
  160. <hr />
  161. <p>
  162. So, what are we to do? Well, let's lay out the options: <a href="https://www.gnu.org/software/hurd/">GNU Hurd</a>, *BSD, keep
  163. using linux-libre until the dark times and then decide, nothing. The most ideal
  164. situations would be to get Hurd working well or remove Linux and use a BSD
  165. kernel. The two best would be <a href="https://www.openbsd.org/">OpenBSD</a><sup><a id="fnr.4" class="footref" href="#fn.4">4</a></sup> or <a href="https://netbsd.org/">NetBSD</a>, as they don't load
  166. proprietary modules by default. You could do as the article says and migrate
  167. over to a BSD.<sup><a id="fnr.5" class="footref" href="#fn.5">5</a></sup> They don't really have the same issues due to their
  168. specialized communities (more to come on this topic. The most practical as of
  169. now is to just use Linux-libre and see what happens. I, personally, think
  170. migrating to BSD is the best for advanced users but normal folks should probably
  171. stay were they are for now (if not on linux-libre, migrate to that).
  172. </p>
  173. <p>
  174. All-and-all, I'm not sure what's going to happen here in the GNU/Linux world. I
  175. hope for the best but plan for the worst. We will see what happens!
  176. </p>
  177. </div>
  178. </div>
  179. </div>
  180. <div id="footnotes">
  181. <h2 class="footnotes">Footnotes: </h2>
  182. <div id="text-footnotes">
  183. <div class="footdef"><sup><a id="fn.1" class="footnum" href="#fnr.1">1</a></sup> <div class="footpara"><p class="footpara">
  184. I later found out that webkitGTK can be used with xwidgets, something
  185. that I have never ever wanted to do. I understand that the Debian package
  186. maintainers what to include everything possible in their standard Emacs package
  187. but this fact doesn't change my mind about my concerns with dependency hell.
  188. </p></div></div>
  189. <div class="footdef"><sup><a id="fn.2" class="footnum" href="#fnr.2">2</a></sup> <div class="footpara"><p class="footpara">
  190. Check out his <a href="https://unixsheikh.com/articles/why-you-should-migrate-everything-from-linux-to-bsd-part-2.html">sequel</a> too.
  191. </p></div></div>
  192. <div class="footdef"><sup><a id="fn.3" class="footnum" href="#fnr.3">3</a></sup> <div class="footpara"><p class="footpara">
  193. I fundamentally disagree with the Emacs team's decision to do this.
  194. </p></div></div>
  195. <div class="footdef"><sup><a id="fn.4" class="footnum" href="#fnr.4">4</a></sup> <div class="footpara"><p class="footpara">
  196. <a href="https://www.hyperbola.info/">Hyperbola GNU/Linux</a> is currently doing this with OpenBSD's kernel. See <a href="https://www.hyperbola.info/news/announcing-hyperbolabsd-roadmap/">here</a>.
  197. </p></div></div>
  198. <div class="footdef"><sup><a id="fn.5" class="footnum" href="#fnr.5">5</a></sup> <div class="footpara"><p class="footpara">
  199. This is something I am planning on doing. Article to come!
  200. </p></div></div>
  201. </div>
  202. </div></div>
  203. <div id="postamble" class="status">
  204. <p class="author">Author: Kevin "The Nuclear" Bloom</p>
  205. </div>
  206. <div id="footer">
  207. <hr />
  208. <p>
  209. <a href="https://anybrowser.org/campaign/">
  210. <img src="/img/any-browser.png" alt="Viewable with any browser! No JS, no cookies, no bullshit!"/></a>
  211. &nbsp;
  212. <a href="http://validator.w3.org/check?uri=nuclearkev.org"><img
  213. src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0 Strict" height="31" width="88" /></a>
  214. &nbsp;
  215. <a href="http://NetBSD.org/"><img
  216. src="https://www.netbsd.org/images/powered-by-NetBSD.png" alt="NetBSD" width="88" /></a>
  217. </p>
  218. <p>
  219. Copyright © 2017-2022 Kevin "The Nuclear" Bloom
  220. </p>
  221. </div>
  222. </body>
  223. </html>