Remove doc bundles from os-clr-on-clr and in their place add the base
bundle when it wasn't included before (since these were previously auto
included by the doc bundle).
bundles/os-clr-on-clr | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/bundles/os-clr-on-clr b/bundles/os-clr-on-clr
index 8e5d242..ea4be5a 100644
@@ -4,27 +4,27 @@
# [MAINTAINER]: William Douglas <william.douglas(a)intel.com>
-# needs autodoc first include(storage-utils-doc)
The latest release includes the potential for considerable performance boost for Python components in Clear Linux. It also adds several GNOME 3.22 components and continues to track the latest Linux kernel very closely.
Key component updates
Key new components
GNOME 3.22 components
Key Python components of the OS, like NumPy, SciPy, and scikit-learn, can now get a measurable performance gain on systems with an Intel(r) Advanced Vector Extensions 2 (Intel AVX2) capable processor. Some performance sensitive Python modules include compiled C code in the form of shared libraries. Typically, these shared libraries are compiled for the same CPU as the OS and do not use Intel AVX2 instructions. Python in Clear Linux now has two versions of these shared libraries pre-installed automatically, one without and one with the Intel AVX2 instructions enabled. At runtime, the Python interpreter picks the suitable version for the system's CPU.
The Clear Linux installer (Ister) now finds cloud-init configuration data during the install and uses micro config drive (ucf) to configure the host as directed by the cloud-init configuration file, allowing for customized and automated installation with the same configuration format for bare metal that is used for cloud provisioning.
Performance on Clear Linux maintains its advantage in several areas, including the latest tests from Phoronix showing our graphics performance advantage over Ubuntu, see the details here<http://www.phoronix.com/scan.php?page=article&item=clr-ubuntu-yak&num=1>.
Clear Linux recently updated systemd to 231 release. This update brings
some changes on how systemd-logind handle the remained process after a
user logs out (see CHANGES WITH 230).
To back to the previous behavior (do not kill tmux when exit), you can
configure logind.conf system-wide to not kill user process after
#. Create logind.conf directory
mkdir -p /etc/systemd/logind.conf.d
#. Set KilluserProcesses to no
echo -e "[Login]\nKillUserProcesses=no" >
#. Restart systemd-logind service
systemctl restart systemd-logind
Furthermore you can use a lists of usernames to override the
KillUserProcesses= settings, by using KillOnlyUsers=, KillExcludeUsers=
(see man logind.conf(5)).
An other workaround is explained in .
From systemd NEWS file:
CHANGES WITH 230:
* systemd-logind will now by default terminate user processes that are
part of the user session scope unit (session-XX.scope) when the user
logs out. This behavior is controlled by the KillUserProcesses=
setting in logind.conf, and the previous default of "no" is now
changed to "yes". This means that user sessions will be properly
cleaned up after, but additional steps are necessary to allow
intentionally long-running processes to survive logout.
CHANGES WITH 231:
* systemd will now log about all service processes it kills forcibly
(using SIGKILL) because they remained after the clean shutdown phase
of the service completed. This should help identifying services that
shut down uncleanly. Moreover if KillUserProcesses= is enabled in
systemd-logind's configuration a similar log message is generated for
processes killed at the end of each session due to this setting.
Miguel Bernal Marin Open Source Technology Center
https://clearlinux.org Intel Corporation
This is Manideep from Carnegie Mellon University. I am doing research on
container security from quite some time (results about which will be
published sometime mid-March or later). I came across clear containers
recently and started exploring more on that. Would need some confirmations
from your side so that I can proceed exploring more and include about your
work in my research. Please let me know if I get any of the below
1. When I use clear containers, there will be no necessity for namespaces
and cgroups anymore.
2. Clear containers will have their own kernel which is clear linux's
kernel. They get it as a part of clear containers installation. Though it
is solving the core security problem of shared kernel in containers
environment , the concept of space wastage (having multiple) kernels on the
same host is still in place.
3. Do the concept of KGT etc. comes in-built with Clear Linux?
Also, I am assuming that TPM/TCB for containers (where docker daemon is
also included in the process of boot verification process) is just an
extension to already existing TPM chip and has no relation to clear
linux project. TPM can be used to further enhance the security of Clear
4. It would be of great help if you can let me know what all packages does
Clear Linux comes up with? Does it trim most of the packages from Ubuntu or
else keeps all of them and then highly optimizes them? How does it work?