Index: general.ent
===================================================================
--- general.ent	(revision c8216c3d00bad8ceca526cfb20f5a22a21857342)
+++ general.ent	(revision 088e7e0664d569f79597bc01c1060c5fc583033b)
@@ -1,5 +1,5 @@
 <!-- $LastChangedBy$ $Date$ -->
 
-<!ENTITY day          "15">                   <!-- Always 2 digits -->
+<!ENTITY day          "16">                   <!-- Always 2 digits -->
 <!ENTITY month        "02">                   <!-- Always 2 digits -->
 <!ENTITY year         "2018">
@@ -7,5 +7,5 @@
 <!ENTITY copyholder   "The BLFS Development Team">
 <!ENTITY version      "&year;-&month;-&day;">
-<!ENTITY releasedate  "February 15th, &year;">
+<!ENTITY releasedate  "February 16th, &year;">
 <!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
 <!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->
Index: introduction/welcome/changelog.xml
===================================================================
--- introduction/welcome/changelog.xml	(revision c8216c3d00bad8ceca526cfb20f5a22a21857342)
+++ introduction/welcome/changelog.xml	(revision 088e7e0664d569f79597bc01c1060c5fc583033b)
@@ -42,4 +42,15 @@
     </listitem>
 -->
+    <listitem>
+      <para>February 16th, 2018</para>
+      <itemizedlist>
+        <listitem>
+          <para>[ken] - Update to qt-5.10.1 (bug fixes) and
+          qtwebengine-5.10.1 (includes security fixes). Fixes
+          <ulink url="&blfs-ticket-root;10385">#10385</ulink>.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>February 15th, 2018</para>
Index: packages.ent
===================================================================
--- packages.ent	(revision c8216c3d00bad8ceca526cfb20f5a22a21857342)
+++ packages.ent	(revision 088e7e0664d569f79597bc01c1060c5fc583033b)
@@ -577,6 +577,6 @@
 <!ENTITY pango-version                "1.40.14">
 <!ENTITY pangomm-version              "2.40.1">
-<!ENTITY qt5-version                  "5.10.0">
-<!ENTITY qtwebengine-version          "5.10.0">
+<!ENTITY qt5-version                  "5.10.1">
+<!ENTITY qtwebengine-version          "5.10.1">
 <!ENTITY qtwebkit-version             "5.9.0">
 <!ENTITY qscintilla-version           "2.10.2">
Index: x/lib/qt5.xml
===================================================================
--- x/lib/qt5.xml	(revision c8216c3d00bad8ceca526cfb20f5a22a21857342)
+++ x/lib/qt5.xml	(revision 088e7e0664d569f79597bc01c1060c5fc583033b)
@@ -10,8 +10,8 @@
   <!ENTITY qt5-download-http "&qt5-url;/qt-everywhere-src-&qt5-version;.tar.xz">
   <!ENTITY qt5-download-ftp  " ">
-  <!ENTITY qt5-md5sum        "c5e275ab0ed7ee61d0f4b82cd471770d">
-  <!ENTITY qt5-size          "289 MB">
-  <!ENTITY qt5-buildsize     "9.6 GB (225 MB installed)">
-  <!ENTITY qt5-time          "29.8 SBU (using parallelism=4)">
+  <!ENTITY qt5-md5sum        "7e167b9617e7bd64012daaacb85477af">
+  <!ENTITY qt5-size          "391 MB">
+  <!ENTITY qt5-buildsize     "10.1 GB (238 MB installed)">
+  <!ENTITY qt5-time          "30 SBU (using parallelism=4)">
 ]>
 
Index: x/lib/qtwebengine.xml
===================================================================
--- x/lib/qtwebengine.xml	(revision c8216c3d00bad8ceca526cfb20f5a22a21857342)
+++ x/lib/qtwebengine.xml	(revision 088e7e0664d569f79597bc01c1060c5fc583033b)
@@ -8,16 +8,8 @@
   <!ENTITY qtwebengine-download-http "https://download.qt.io/archive/qt/&qtwebengine-major;/&qtwebengine-version;/submodules/qtwebengine-everywhere-src-&qtwebengine-version;.tar.xz">
   <!ENTITY qtwebengine-download-ftp  " ">
-  <!ENTITY qtwebengine-md5sum        "0ea0b32e97911cf80d32b31cf10a6d8b">
-  <!ENTITY qtwebengine-size          "208 MB">
-  <!ENTITY qtwebengine-buildsize     "3.3 GB (144 MB installed)">
-  <!ENTITY qtwebengine-time          "95 SBU (using 4 cores)">
-
-  <!--   Both qmake and ninja will use all available cores, in fact ninja runs n+2
-     jobs at a time.  Most of our readers do not have more than 4 cores.
-     To reduce the number of available cores for measuring the build time:
-     # echo 0 > /sys/devices/system/cpu/cpu4/online
-     and repeat for each subsequent cpu.  Never do this for cpu0.
-     You can cat /sys/devices/system/cpu/{online,offline} to check.
-     To reinstate the cores after measuring, echo 1 to the same files. -->
+  <!ENTITY qtwebengine-md5sum        "77374c184f2ff5005d1c61a32ea38491">
+  <!ENTITY qtwebengine-size          "201 MB">
+  <!ENTITY qtwebengine-buildsize     "3.2 GB (137 MB installed)">
+  <!ENTITY qtwebengine-time          "43 SBU (using 4 cores)">
 ]>
 
@@ -49,8 +41,9 @@
 
     &lfs81_checked;
-  
-    <note><para>Both qmake and ninja will use all available cores when
-    building.  There is no conveninet way to control the number of cores 
-    used during the build.</para></note>
+
+    <note><para>By default, ninja will use all online CPUs +2 (if at least
+    4 exist), even if they are not available to the current task because the
+    build terminal has been restricted with 'taskset'.  To work around this,
+    see the Command Explanations below.</para></note>
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -178,6 +171,19 @@
       <command>qmake</command>: This will build the included copy of
       <application>ninja</application> if it is not already installed
-      and use it to configure the build.  That and the subsequent 
-      <command>make</command> command will use all available CPU cores.
+      and use it to configure the build.
+    </para>
+
+    <para>
+      <option>NINJAJOBS=4 make</option>: If you patched system ninja in LFS to
+      recognize the NINJAJOBS environment variable, this command will run system
+      ninja with the specified number of jobs (i.e. 4). Among the reasons why
+      you might want to do this are: building on a subset of CPUs, either to
+      measure the build time for that number of processors or to run other
+      CPU-intensive tasks on other cores, or to improve the build speed on a
+      less-well endowed 4-core machine. On a machine with a powerful CPU and
+      plenty of RAM, running N+2 jobs (the ninja default for 4+ cores) for the
+      large working sets of the C++ compiles in this package is typically only
+      marginally slower than running 4 jobs at a time.  But for a machine with
+      less memory it might be much slower.
     </para>
 
