Index: general.ent
===================================================================
--- general.ent	(revision 6a609bd7ce4cc9d1a690f84fdb1067a0068afa16)
+++ general.ent	(revision bdfc85498958c0eb662880ce8975c0860dbc3e48)
@@ -1,5 +1,5 @@
 <!-- $LastChangedBy$ $Date$ -->
 
-<!ENTITY day          "19">                   <!-- Always 2 digits -->
+<!ENTITY day          "21">                   <!-- Always 2 digits -->
 <!ENTITY month        "03">                   <!-- Always 2 digits -->
 <!ENTITY year         "2020">
@@ -7,5 +7,5 @@
 <!ENTITY copyholder   "The BLFS Development Team">
 <!ENTITY version      "&year;-&month;-&day;">
-<!ENTITY releasedate  "March 19th, &year;">
+<!ENTITY releasedate  "March 21st, &year;">
 <!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
 <!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->
Index: general/prog/gcc.xml
===================================================================
--- general/prog/gcc.xml	(revision 6a609bd7ce4cc9d1a690f84fdb1067a0068afa16)
+++ general/prog/gcc.xml	(revision bdfc85498958c0eb662880ce8975c0860dbc3e48)
@@ -7,8 +7,8 @@
   <!ENTITY gcc-download-http  "&gnu-http;/gcc/gcc-&gcc-version;/gcc-&gcc-version;.tar.xz">
   <!ENTITY gcc-download-ftp   "&gnu-ftp;/gcc/gcc-&gcc-version;/gcc-&gcc-version;.tar.xz">
-  <!ENTITY gcc-md5sum         "3818ad8600447f05349098232c2ddc78">
+  <!ENTITY gcc-md5sum         "d00a144b771ddeb021b61aa205b7e345">
   <!ENTITY gcc-size           "67 MB">
-  <!ENTITY gcc-buildsize      "9.9 GB (2.4 GB installed with all listed languages; add 930 MB for tests)">
-  <!ENTITY gcc-time           "25 SBU (with parallelism=4, add 62 SBU for tests with parallelism=4)">
+  <!ENTITY gcc-buildsize      "9.9 GB (2.5 GB installed with all listed languages; add 1.0 GB for tests)">
+  <!ENTITY gcc-time           "24 SBU (with parallelism=4, add 48 SBU for tests with parallelism=4)">
 ]>
 
@@ -188,7 +188,4 @@
 esac
 
-sed -e '1161 s|^|//|' \
-    -i libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
-
 mkdir build                                            &amp;&amp;
 cd    build                                            &amp;&amp;
Index: general/sysutils/systemd.xml
===================================================================
--- general/sysutils/systemd.xml	(revision 6a609bd7ce4cc9d1a690f84fdb1067a0068afa16)
+++ general/sysutils/systemd.xml	(revision bdfc85498958c0eb662880ce8975c0860dbc3e48)
@@ -105,4 +105,5 @@
     <bridgehead renderas="sect4">Optional</bridgehead>
     <para role="optional">
+      <xref linkend="btrfs-progs"/> <!-- homed may support it, see the C.E.-->
       <xref linkend="curl"/>,
       <xref linkend="cryptsetup"/>,
@@ -200,7 +201,10 @@
       -Drpmmacrosdir=no     \
       -Db_lto=false         \
+      -Dhomed=false         \
+      -Duserdb=false        \
       ..                    &amp;&amp;
 
 ninja</userinput></screen>
+<!-- Regarding homed and userdb, see the note below in Command Explanations-->
 
     <note>
@@ -248,4 +252,57 @@
   </sect2>
 
+  <sect2 role="commands">
+    <title>Command Explanations</title>
+
+    <para>
+      <parameter>-Duserdb=false</parameter>: Removes a daemon that does not
+      offer any use under a BLFS configuration. If you wish to enable the
+      <application>userdbd</application> daemon, replace "false" with "true"
+      in the above meson command.
+    </para>
+
+    <para>
+      <parameter>-Dhomed=false</parameter>: Remove a daemon that does not offer
+      any use under a traditional BLFS configuration, especially using accounts
+      created with useradd. To enable systemd-homed, first ensure that you have
+      <xref linkend="cryptsetup"/> and <xref linkend="libpwquality"/>, and then
+      change "false" to "true" in the above meson command.
+    </para>
+
+    <!-- EDITORS NOTE: Explanation on removing userdbd and homed:
+    In BLFS, we do not fully support disk encryption. We offer instructions for
+    building 'cryptsetup' as a dependency, but we do not offer instructions for
+    actually configuring it. In addition, we generally do not include
+    functionality that could potentially conflict with other packages, or that
+    is not of any use to us (in an enterprise configuration using Thin Clients
+    or laptops with LUKS encryption, it could make sense though, but that isn't
+    the configuration that we natively support).
+
+    A few of the complications of systemd-homed include:
+      - SSH Logins
+      - Disk Space Assignments
+      - UID Assignments (chown() on login)
+      (See https://cfp.all-systems-go.io/media/homed-asg2019.pdf)
+
+    In an article I read when systemd-homed was originally unveiled, I remember
+    reading about systemd-homed causing problems with OpenSSH Private Key Auth
+    because the user would have to login at the console in order to unlock
+    their home directory, thus allowing the private key to be unlocked and
+    processed by OpenSSH. Since BLFS does not fully support encrypted disks,
+    and because systemd-homed is incompatible with our usage of useradd /
+    traditional UNIX users and groups, I advise that we take the following
+    approach to avoid any confusion:
+
+    - Leave the added Short Descriptions for homectl and userdbctl
+    - Add the above command explanations and restore the previous behavior
+
+    Should we decide to enable homed by default anytime in the future, 
+    let's move cryptsetup to recommended or required.
+
+    I would be open to discussing this after the next systemd version when
+    systemd-homed has matured a bit more. -renodr -->
+
+  </sect2>
+
   <sect2 role="configuration">
     <title>Configuring systemd</title>
@@ -331,5 +388,5 @@
           <!-- maybe userdbd/userdbctl can go in LFS, try at next time -->
           homectl (if <xref linkend="cryptsetup"/> is installed)
-          and userdbctl
+          and userdbctl (optionally)
         </seg>
         <seg>
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision 6a609bd7ce4cc9d1a690f84fdb1067a0068afa16)
+++ introduction/welcome/changelog.xml	(revision bdfc85498958c0eb662880ce8975c0860dbc3e48)
@@ -41,5 +41,15 @@
       </itemizedlist>
     </listitem>
-       -->
+    -->
+    <listitem>
+      <para>March 21st, 2020</para>
+      <itemizedlist>
+        <listitem>
+          <para>[renodr] - Update to gcc-9.3.0. Fixes
+          <ulink url="&blfs-ticket-root;13260">#13260</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>March 19th, 2020</para>
Index: packages.ent
===================================================================
--- packages.ent	(revision 6a609bd7ce4cc9d1a690f84fdb1067a0068afa16)
+++ packages.ent	(revision bdfc85498958c0eb662880ce8975c0860dbc3e48)
@@ -322,5 +322,5 @@
 <!ENTITY elfutils-version             "0.170">
 <!ENTITY expect-version               "5.45.4">
-<!ENTITY gcc-version                  "9.2.0">
+<!ENTITY gcc-version                  "9.3.0">
 <!ENTITY gc-version                   "8.0.4">
 <!ENTITY gdb-version                  "9.1">
