Update webpage "About" from version "7.0.0" to "8.0.0"
This commit is contained in:
parent
89933ac856
commit
3335d1d7b2
SSH Key Fingerprint:
SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
180
about.xhtml
180
about.xhtml
@ -1,7 +1,7 @@
|
|||||||
<!DOCTYPE html>
|
<!DOCTYPE html>
|
||||||
|
|
||||||
<!-- Inferencium - Website - About -->
|
<!-- Inferencium - Website - About -->
|
||||||
<!-- Version: 7.0.0 -->
|
<!-- Version: 8.0.0 -->
|
||||||
|
|
||||||
<!-- Copyright 2022 Jake Winters -->
|
<!-- Copyright 2022 Jake Winters -->
|
||||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||||
@ -16,25 +16,22 @@
|
|||||||
</head>
|
</head>
|
||||||
<body>
|
<body>
|
||||||
<nav class="navbar">
|
<nav class="navbar">
|
||||||
<div><a href="index.xhtml"><img src="asset/img/logo-inferencium-no_text.png" width="110px" height="110px"/></a></div>
|
<div><a href="index.xhtml"><img src="asset/img/logo-inferencium-no_text.png" width="110" height="110" alt="Inferencium logo"/></a></div>
|
||||||
<div><a href="index.xhtml" class="title">Inferencium</a></div>
|
<div><a href="index.xhtml" class="title">Inferencium</a></div>
|
||||||
<div><a href="about.xhtml">About</a></div>
|
<div><a href="about.xhtml">About</a></div>
|
||||||
<div><a href="contact.xhtml">Contact</a></div>
|
|
||||||
<div><a href="blog.xhtml">Blog</a></div>
|
|
||||||
<div><a href="documentation.xhtml">Documentation</a></div>
|
<div><a href="documentation.xhtml">Documentation</a></div>
|
||||||
<div><a href="source.xhtml">Source</a></div>
|
<div><a href="source.xhtml">Source</a></div>
|
||||||
<div><a href="key.xhtml">Key</a></div>
|
|
||||||
<div><a href="changelog.xhtml">Changelog</a></div>
|
<div><a href="changelog.xhtml">Changelog</a></div>
|
||||||
|
<div><a href="blog.xhtml">Blog</a></div>
|
||||||
|
<div><a href="contact.xhtml">Contact</a></div>
|
||||||
<div><a href="directory.xhtml">Directory</a></div>
|
<div><a href="directory.xhtml">Directory</a></div>
|
||||||
|
<div><a href="key.xhtml">Key</a></div>
|
||||||
</nav>
|
</nav>
|
||||||
<h1>About</h1>
|
<h1>About</h1>
|
||||||
<nav id="toc">
|
<nav id="toc">
|
||||||
<h2 id="toc"><a href="#toc">Table of Contents</a></h2>
|
<h2><a href="#toc">Table of Contents</a></h2>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="#about_me">About Me</a></li>
|
<li><a href="#about_me">About Me</a></li>
|
||||||
<ul>
|
|
||||||
<li><a href="#about_me-gnulinux_or_linux">Is it GNU/Linux or Just Linux?</a></li>
|
|
||||||
</ul>
|
|
||||||
<li><a href="#date_time">Date and Time</a></li>
|
<li><a href="#date_time">Date and Time</a></li>
|
||||||
<li><a href="#licensing">Licensing</a></li>
|
<li><a href="#licensing">Licensing</a></li>
|
||||||
<ul>
|
<ul>
|
||||||
@ -49,6 +46,11 @@
|
|||||||
</ul>
|
</ul>
|
||||||
<li><a href="#licensing-open_source_vs_free_software">Do I Distinguish Between Open-source and Free Software?</a></li>
|
<li><a href="#licensing-open_source_vs_free_software">Do I Distinguish Between Open-source and Free Software?</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
<li><a href="#versioning">Versioning</a></li>
|
||||||
|
<ul>
|
||||||
|
<li><a href="#versioning-numbering_scheme">What is the Numbering Scheme?</a></li>
|
||||||
|
<li><a href="#versioning-phases">What Are the Phases?</a></li>
|
||||||
|
</ul>
|
||||||
<li><a href="#services">Services</a></li>
|
<li><a href="#services">Services</a></li>
|
||||||
<ul>
|
<ul>
|
||||||
<li><a href="#services-websites">Websites</a></li>
|
<li><a href="#services-websites">Websites</a></li>
|
||||||
@ -66,10 +68,11 @@
|
|||||||
</ul>
|
</ul>
|
||||||
<li><a href="#recommendations-music">Music</a></li>
|
<li><a href="#recommendations-music">Music</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
<li><a href="#gnulinux_or_linux">Is it GNU/Linux or Just Linux?</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
</nav>
|
</nav>
|
||||||
<section id="about_me">
|
<section id="about_me">
|
||||||
<h2 id="about_me"><a href="#about_me">About Me</a></h2>
|
<h2><a href="#about_me">About Me</a></h2>
|
||||||
<p>I am Jake Winters, also known by my pseudonym "Inference", a security
|
<p>I am Jake Winters, also known by my pseudonym "Inference", a security
|
||||||
researcher based in United Kingdom.<br/>
|
researcher based in United Kingdom.<br/>
|
||||||
I am the founder, lead developer, and administrator, of Inferencium.<br/>
|
I am the founder, lead developer, and administrator, of Inferencium.<br/>
|
||||||
@ -92,21 +95,9 @@
|
|||||||
webpage.</p>
|
webpage.</p>
|
||||||
<p>If you wish to contact me for any reason, you can use my
|
<p>If you wish to contact me for any reason, you can use my
|
||||||
<a href="https://inferencium.net/contact.xhtml">contact methods</a>.</p>
|
<a href="https://inferencium.net/contact.xhtml">contact methods</a>.</p>
|
||||||
<h3 id="about_me-gnulinux_or_linux"><a href="#about_me-gnulinux_or_linux">Is it GNU/Linux or Just Linux?</a></h3>
|
|
||||||
<p>It's just Linux. GNU is unrelated to Linux, which is a kernel
|
|
||||||
developed by Linus Torvalds. Linux can be used entirely without GNU
|
|
||||||
software in userspace, and the kernel can be compiled without the use of
|
|
||||||
GNU tools. Just because GNU tools were used to initally develop and
|
|
||||||
compile the kernel, and were initially the only available tools for
|
|
||||||
userspace, does not make this true today, and it never made GNU a part
|
|
||||||
of Linux itself at any point of time.</p>
|
|
||||||
<p>Where are all of the other forward-slashes for every other piece of
|
|
||||||
software on a Linux-based system which makes it just as usable? If a
|
|
||||||
system is running "GNU/Linux", it should be using more than a single
|
|
||||||
forward-slash when there is more to the system than only GNU.</p>
|
|
||||||
</section>
|
</section>
|
||||||
<section id="date_time">
|
<section id="date_time">
|
||||||
<h2 id="date_time"><a href="#date_time">Date and Time</a></h2>
|
<h2><a href="#date_time">Date and Time</a></h2>
|
||||||
<p>All dates and times across my services are
|
<p>All dates and times across my services are
|
||||||
<a href="https://wikipedia.org/wiki/ISO_8601">ISO 8601</a>-compliant. The
|
<a href="https://wikipedia.org/wiki/ISO_8601">ISO 8601</a>-compliant. The
|
||||||
short-form format <code>YYYY-MM-DD</code> is used for dates, and
|
short-form format <code>YYYY-MM-DD</code> is used for dates, and
|
||||||
@ -117,7 +108,7 @@
|
|||||||
<code>YYYYMMDDThhmmss-hhmm</code> (with negative offset).</p>
|
<code>YYYYMMDDThhmmss-hhmm</code> (with negative offset).</p>
|
||||||
</section>
|
</section>
|
||||||
<section id="licensing">
|
<section id="licensing">
|
||||||
<h2 id="licensing"><a href="#licensing">Licensing</a></h2>
|
<h2><a href="#licensing">Licensing</a></h2>
|
||||||
<p>I care about upstreaming and sharing code, strongly preferring licenses which
|
<p>I care about upstreaming and sharing code, strongly preferring licenses which
|
||||||
have high license compatibility in order to permit sharing code with as many
|
have high license compatibility in order to permit sharing code with as many
|
||||||
other projects as possible; for this reason, permissive licenses are my
|
other projects as possible; for this reason, permissive licenses are my
|
||||||
@ -193,8 +184,97 @@
|
|||||||
push an ideology by a specific group of people. If software
|
push an ideology by a specific group of people. If software
|
||||||
isn't "free", it's not open-source, either.</p>
|
isn't "free", it's not open-source, either.</p>
|
||||||
</section>
|
</section>
|
||||||
|
<section id="versioning">
|
||||||
|
<h2><a href="#versioning">Versioning</a></h2>
|
||||||
|
<section id="versioning-numbering_scheme">
|
||||||
|
<h3><a href="#versioning-numbering_scheme">What is the Numbering Scheme?</a></h3>
|
||||||
|
<p>All code uses
|
||||||
|
<a href="https://semver.org">Semantic Versioning</a>.
|
||||||
|
The numbering scheme divided into 3 blocks (herein referred to
|
||||||
|
as Block 0, Block 1, and Block 2, in left-to-right order); the
|
||||||
|
version blocks are separated by periods. When a version number
|
||||||
|
block is incremented, all blocks to the right of it are reset to
|
||||||
|
0. The legacy versioning scheme was a similar numerical
|
||||||
|
versioning scheme which lacked standardisation.</p>
|
||||||
|
<p>Block 0 contains the <code><var>MAJOR</var></code> version;
|
||||||
|
this number is incremented whenever an API-incompatible change
|
||||||
|
is made to the code.</p>
|
||||||
|
<p>Block 1 contains the <code><var>MINOR</var></code> version;
|
||||||
|
this number is incremented whenever an API-compatible,
|
||||||
|
substantial change is made to the code, such as adding a
|
||||||
|
feature.</p>
|
||||||
|
<p>Block 2 contains the <code><var>PATCH</var></code> version;
|
||||||
|
this number is incremented whenever an API-compatible,
|
||||||
|
unsubstantial change is made to the code, such as fixing or
|
||||||
|
optimising the code.</p>
|
||||||
|
<p>Development and pre-release versions are suffixed with
|
||||||
|
a hyphen, followed by their phase, a period, then the version of
|
||||||
|
that phase; for example, <code>-alpha.<var>n</var></code> for an
|
||||||
|
alpha version, <code>-beta.<var>n</var></code> for a beta
|
||||||
|
version, and <code>-rc.<var>n</var></code> for a release
|
||||||
|
candidate version, with <code><var>n</var></code> being a
|
||||||
|
non-negative integer. Stable versions have no suffix.</p>
|
||||||
|
</section>
|
||||||
|
<section id="versioning-phases">
|
||||||
|
<h3><a href="#versioning-phases">What Are the Phases?</a></h3>
|
||||||
|
<p>There are 4 phases of development. Each phase typically has
|
||||||
|
its own branch in each source code repository. The phases are as
|
||||||
|
follows:
|
||||||
|
<ol>
|
||||||
|
<li>Alpha: Pre-alpha development and alpha
|
||||||
|
testing occurs in this phase. Features are
|
||||||
|
added, modified, and/or removed. Fixes and
|
||||||
|
optimisations may also occur if they are caught
|
||||||
|
during this phase. This is where the majority of
|
||||||
|
changes occur and where the fine-grained commits
|
||||||
|
can be found. Breakage is highly likely within
|
||||||
|
this phase as it makes no attempt to be stable
|
||||||
|
or usable due to being where the most rapid
|
||||||
|
development occurs. Code is tested internally in
|
||||||
|
a fine-grained manner and is moved to the next
|
||||||
|
phase only when it is deemed feature-complete
|
||||||
|
and reasonably stable for broader public
|
||||||
|
testing. If you would like to assist in testing
|
||||||
|
code in this phase, you must use the code and/or
|
||||||
|
tags from the source code repositories due to it
|
||||||
|
not being available publicly outside of
|
||||||
|
them.</li>
|
||||||
|
<li>Beta: Feature-complete testing occurs in
|
||||||
|
this phase. Only bug fixes and optimisations
|
||||||
|
occur in this phase, such as stability and
|
||||||
|
security fixes. This phase is classified as
|
||||||
|
stable enough for broad public testing and is
|
||||||
|
made available publicly in many cases without
|
||||||
|
having to use the source code repositories.
|
||||||
|
Since this phase contains only feature-complete
|
||||||
|
code, no features will be added, modified, or
|
||||||
|
removed in this phase.</li>
|
||||||
|
<li>Release candidate (RC): Feature-complete
|
||||||
|
testing occurs in this phase. Code in the RC
|
||||||
|
phase is often stable enough for production
|
||||||
|
usage, but is not yet completely acceptable to
|
||||||
|
be classified as stable by my standards. This
|
||||||
|
phase is often skipped due to most bugs being
|
||||||
|
caught in the beta phase, but will be used
|
||||||
|
should the need arise for finer-grained testing
|
||||||
|
beyond what the beta phase can provide. Like the
|
||||||
|
beta phase, code in this phase is available
|
||||||
|
publicly without requiring usage of the source
|
||||||
|
code repositories.</li>
|
||||||
|
<li>Stable: Feature-complete and well-tested
|
||||||
|
code is moved to this phase. Code in this phase
|
||||||
|
is deemed to be stable enough for production
|
||||||
|
usage and full support is provided.</li>
|
||||||
|
</ol>
|
||||||
|
</p>
|
||||||
|
<p>When development of a new version has begun, the code within
|
||||||
|
the alpha phase is rebased onto the most recent code from the
|
||||||
|
stable phase before work commences. This cycle continues for the
|
||||||
|
lifetime of the code.</p>
|
||||||
|
</section>
|
||||||
|
</section>
|
||||||
<section id="services">
|
<section id="services">
|
||||||
<h2 id="services"><a href="#services">Services</a></h2>
|
<h2><a href="#services">Services</a></h2>
|
||||||
<p>This list contains the policies and practices of my services.</p>
|
<p>This list contains the policies and practices of my services.</p>
|
||||||
<p>My policies and practices are heavily security- and privacy-focused, with
|
<p>My policies and practices are heavily security- and privacy-focused, with
|
||||||
improvements made on an ongoing basis as new technologies, protocols, and
|
improvements made on an ongoing basis as new technologies, protocols, and
|
||||||
@ -214,14 +294,14 @@
|
|||||||
<a href="https://wikipedia.org/wiki/Forward_secrecy">forward secrecy</a></li>
|
<a href="https://wikipedia.org/wiki/Forward_secrecy">forward secrecy</a></li>
|
||||||
<li>All connections made via high-security AEAD ciphers,
|
<li>All connections made via high-security AEAD ciphers,
|
||||||
preferring AES-256-GCM for devices with AES
|
preferring AES-256-GCM for devices with AES
|
||||||
hardware-acceleration, and ChaCha20-Poly1305 for devices without
|
hardware acceleration, and ChaCha20-Poly1305 for devices without
|
||||||
AES hardware-acceleration, with AES-128-GCM as a fallback
|
AES hardware acceleration, with AES-128-GCM as a fallback
|
||||||
(AES-128-GCM is mandated for TLS 1.3 by
|
(AES-128-GCM is mandated for TLS 1.3 by
|
||||||
<a href="https://datatracker.ietf.org/doc/rfc8446#section-9.1">IETF RFC8446 section 9.1</a>)</li>
|
<a href="https://datatracker.ietf.org/doc/rfc8446#section-9.1">IETF RFC8446 section 9.1</a>)</li>
|
||||||
<li>All connections are made via high-security key exchange
|
<li>All connections are made via high-security key exchange
|
||||||
protocols, preferring X25519, with secp256r1 as a fallback
|
protocols, preferring X25519, with secp256r1 as a fallback
|
||||||
(secp256r1 is mandated for TLS 1.3 by
|
(secp256r1 is mandated for TLS 1.3 by IETF RFC8446 section
|
||||||
<a href="https://datatracker.ietf.org/doc/rfc8446#section-9.1">IETF RFC8446 section 9.1</a>)</li>
|
9.1)</li>
|
||||||
<li><a href="https://wikipedia.org/wiki/Domain_Name_System_Security_Extensions">Domain Name System Security Extensions (DNSSEC)</a>
|
<li><a href="https://wikipedia.org/wiki/Domain_Name_System_Security_Extensions">Domain Name System Security Extensions (DNSSEC)</a>
|
||||||
enabled to provide a root-of-trust for encryption and
|
enabled to provide a root-of-trust for encryption and
|
||||||
authentication for domain and server configuration</li>
|
authentication for domain and server configuration</li>
|
||||||
@ -246,7 +326,7 @@
|
|||||||
</ul>
|
</ul>
|
||||||
</section>
|
</section>
|
||||||
<section id="recommendations">
|
<section id="recommendations">
|
||||||
<h2 id="recommendations"><a href="#recommendations">Recommendations</a></h2>
|
<h2><a href="#recommendations">Recommendations</a></h2>
|
||||||
<h3 id="recommendations-hardware"><a href="#recommendations-hardware">Hardware</a></h3>
|
<h3 id="recommendations-hardware"><a href="#recommendations-hardware">Hardware</a></h3>
|
||||||
<h4 id="recommendations-hardware-smartphone"><a href="#recommendations-hardware-smartphone">Smartphone</a></h4>
|
<h4 id="recommendations-hardware-smartphone"><a href="#recommendations-hardware-smartphone">Smartphone</a></h4>
|
||||||
<div style="overflow-x:auto;">
|
<div style="overflow-x:auto;">
|
||||||
@ -261,7 +341,7 @@
|
|||||||
<tr>
|
<tr>
|
||||||
<th id="hardware-smartphone-smartphone">Smartphone</th>
|
<th id="hardware-smartphone-smartphone">Smartphone</th>
|
||||||
<th id ="google-pixel" headers="hardware hardware-smartphone-smartphone">
|
<th id ="google-pixel" headers="hardware hardware-smartphone-smartphone">
|
||||||
<img src="asset/img/google-pixel_8_pro.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/google-pixel_8_pro.png" width="100" height="100" alt="Front and rear view of a Google Pixel 8 Pro in Obsidian colour"/><br/>
|
||||||
Google Pixel
|
Google Pixel
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="hardware-description google-pixel">
|
<td class="desc" headers="hardware-description google-pixel">
|
||||||
@ -340,18 +420,13 @@
|
|||||||
by eliminating up to 95% of all security
|
by eliminating up to 95% of all security
|
||||||
issues caused by memory-unsafety.</p>
|
issues caused by memory-unsafety.</p>
|
||||||
<h5>Support</h5>
|
<h5>Support</h5>
|
||||||
<p>Pixel 4a (5G), Pixel 5, and Pixel 5a, are
|
<p>Pixel 5a is supported for a
|
||||||
supported for a
|
|
||||||
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-a-g-pixel-pixel-a-g-pixel-a-pixel-xl-pixel">minimum of 3 years from launch</a>.</p>
|
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-a-g-pixel-pixel-a-g-pixel-a-pixel-xl-pixel">minimum of 3 years from launch</a>.</p>
|
||||||
<p>Pixel 6-series, Pixel 7-series, Pixel
|
<p>Pixel 6-series, Pixel 7-series, Pixel
|
||||||
Fold, and Pixel Tablet, are supported for a
|
Fold, and Pixel Tablet are supported for a
|
||||||
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-a-pixel-pixel-pro-pixel-a-pixel-pixel-pro-pixel-fold">minimum of 5 years from launch</a>.</p>
|
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-a-pixel-pixel-pro-pixel-a-pixel-pixel-pro-pixel-fold">minimum of 5 years from launch</a>.</p>
|
||||||
<p>Pixel 8-series is supported for a
|
<p>Pixel 8-series is supported for a
|
||||||
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-pro">minimum of 7 years from launch</a>,
|
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-pro">minimum of 7 years from launch</a>.</p>
|
||||||
putting it on the same support level as
|
|
||||||
Apple; Google have even surpassed Apple in
|
|
||||||
this regard, as Apple does not commit to a
|
|
||||||
support timeframe for their devices.</p>
|
|
||||||
</td>
|
</td>
|
||||||
<td headers="hardware-smartphone-source_model google-pixel">
|
<td headers="hardware-smartphone-source_model google-pixel">
|
||||||
</td>
|
</td>
|
||||||
@ -372,7 +447,7 @@
|
|||||||
<tr>
|
<tr>
|
||||||
<th id="software-desktop-os">Operating system</th>
|
<th id="software-desktop-os">Operating system</th>
|
||||||
<th id="gentoo_linux" headers="software-desktop software-desktop-os">
|
<th id="gentoo_linux" headers="software-desktop software-desktop-os">
|
||||||
<img src="asset/img/logo-gentoo_linux.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/logo-gentoo_linux.png" width="100" height="100" alt="Gentoo Linux logo"/><br/>
|
||||||
Gentoo Linux
|
Gentoo Linux
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-description gentoo_linux">
|
<td class="desc" headers="software-description gentoo_linux">
|
||||||
@ -406,7 +481,7 @@
|
|||||||
<tr>
|
<tr>
|
||||||
<th id="software-web_browser">Web browser</th>
|
<th id="software-web_browser">Web browser</th>
|
||||||
<th id="chromium" headers="software-desktop software-web_browser">
|
<th id="chromium" headers="software-desktop software-web_browser">
|
||||||
<img src="asset/img/logo-chromium.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/logo-chromium.png" width="100" height="100" alt="Chromium logo"/><br/>
|
||||||
Chromium
|
Chromium
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-description chromium">
|
<td class="desc" headers="software-description chromium">
|
||||||
@ -442,7 +517,7 @@
|
|||||||
<tr>
|
<tr>
|
||||||
<th id="software-smartphone-os">Operating system</th>
|
<th id="software-smartphone-os">Operating system</th>
|
||||||
<th id="grapheneos" headers="software-smartphone software-smartphone-os">
|
<th id="grapheneos" headers="software-smartphone software-smartphone-os">
|
||||||
<img src="asset/img/logo-grapheneos.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/logo-grapheneos.png" width="100" height="100" alt="GrapheneOS logo"/><br/>
|
||||||
GrapheneOS
|
GrapheneOS
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-smartphone-description grapheneos">
|
<td class="desc" headers="software-smartphone-description grapheneos">
|
||||||
@ -487,7 +562,7 @@
|
|||||||
<tr>
|
<tr>
|
||||||
<th id="software-smartphone-web_browser">Web browser</th>
|
<th id="software-smartphone-web_browser">Web browser</th>
|
||||||
<th id="vanadium" headers="software-smartphone software-smartphone-web_browser">
|
<th id="vanadium" headers="software-smartphone software-smartphone-web_browser">
|
||||||
<img src="asset/img/logo-vanadium.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/logo-vanadium.png" width="100" height="100" alt="Vanadium logo"/><br/>
|
||||||
Vanadium
|
Vanadium
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-smartphone-description vanadium">
|
<td class="desc" headers="software-smartphone-description vanadium">
|
||||||
@ -512,7 +587,7 @@
|
|||||||
<tr>
|
<tr>
|
||||||
<th rowspan="2" id="software-smartphone-messenger">Messenger</th>
|
<th rowspan="2" id="software-smartphone-messenger">Messenger</th>
|
||||||
<th id="molly" headers="software-smartphone software-smartphone-messenger">
|
<th id="molly" headers="software-smartphone software-smartphone-messenger">
|
||||||
<img src="asset/img/logo-molly.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/logo-molly.png" width="100" height="100" alt="Molly logo"/><br/>
|
||||||
Molly
|
Molly
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-smartphone-description molly">
|
<td class="desc" headers="software-smartphone-description molly">
|
||||||
@ -546,7 +621,7 @@
|
|||||||
</tr>
|
</tr>
|
||||||
<tr>
|
<tr>
|
||||||
<th id="conversations" headers="software-smartphone software-smartphone-messenger">
|
<th id="conversations" headers="software-smartphone software-smartphone-messenger">
|
||||||
<img src="asset/img/logo-conversations.png" width="100px" height="100px"/><br/>
|
<img src="asset/img/logo-conversations.png" width="100" height="100" alt="Conversations logo"/><br/>
|
||||||
Conversations
|
Conversations
|
||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-smartphone-description conversations">
|
<td class="desc" headers="software-smartphone-description conversations">
|
||||||
@ -565,9 +640,22 @@
|
|||||||
</div>
|
</div>
|
||||||
</section>
|
</section>
|
||||||
<section id="recommendations-music">
|
<section id="recommendations-music">
|
||||||
<h3 id="recommendations-music"><a href="#recommendations-music">Music</a></h3>
|
<h3><a href="#recommendations-music">Music</a></h3>
|
||||||
<p>For a curated list of music I enjoy, visit my
|
<p>For a curated list of music I enjoy, visit my
|
||||||
<a href="music.xhtml">music page</a>.</p>
|
<a href="music.xhtml">music page</a>.</p>
|
||||||
</section>
|
</section>
|
||||||
|
<section id="gnulinux_or_linux">
|
||||||
|
<h2><a href="#gnulinux_or_linux">Is it GNU/Linux or Just Linux?</a></h2>
|
||||||
|
<p>It's just Linux. GNU is unrelated to Linux, which is a kernel developed by
|
||||||
|
Linus Torvalds. Linux can be used entirely without GNU software in userspace,
|
||||||
|
and the kernel can be compiled without the use of GNU tools. Just because GNU
|
||||||
|
tools were used to initally develop and compile the kernel, and were initially
|
||||||
|
the only available tools for userspace, does not make this true today, and it
|
||||||
|
never made GNU a part of Linux itself at any point of time.</p>
|
||||||
|
<p>Where are all of the other forward-slashes for every other piece of software
|
||||||
|
on a Linux-based system which makes it just as usable? If a system is running
|
||||||
|
"GNU/Linux", it should be using more than a single forward-slash when there is
|
||||||
|
more to the system than only GNU.</p>
|
||||||
|
</section>
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user