KDBUS, the new in-kernel IPC mechanism modeled after D-Bus, wasn’t accepted for Linux 4.1. Since the end of the Linux 4.1 merge window, the debate over KDBUS continued, but in the past two weeks the discussion settled down…
LLVM’s Clang Adds Support For ARM/AArch64 v8.1a
LLVM’s Clang compiler now has support for ARM’s v8.1a architecture revision of 64-bit ARM…
New Steam Client Lands with Better CPU and Memory usage
Valve has just released a new update for the Steam gaming client, and it’s a big one. Granted, it’s mostly filled with small fixes and improvements, but it’s important nonetheless.
A few weeks have passed since the previous major Steam update, so it’s time for another one, although it’s nothing too impressive. The developers from Valve seem to focus more on fixing problems and less on adding new features. Some of the updates made to Steam in 2014 were pretty important and a… (read more)
How to Become a Valued OpenStack Contributor

Adrian Otto is project team lead for OpenStack projects Magnum and Solum. Otto founded the OpenStack Containers team in 2014, and is a Principal Architect at Rackspace. He is a serial entrepeneur, with 20 years of experience in technology leadership roles, and gets excited about evolving new technology to shape the future of cloud computing.
How to full encrypt your system with lvm on luks from cli

Why lvm on luks?
Fist things first: destroy everything on your disk, filling it with random data
Filling a disk with random data can be very time consuming, especially on very large hard drives, but we can use a trick here: we will luks format the device first, and then fill it with 0s (much faster then random). Because of encryption the data will be written on the disk as random, so we’re actually using the luks device as a random data generator device. Then we will override just the header with random data.
Step 1 – create luks partition
cryptsetup luksFormat --hash=sha512 --key-size=512 --cipher=aes-xts-plain64 --verify-passphrase /dev/sda
You will be asked to enter a password for the encryption, it doesn't matter if it's not very secure this time, because we will only use this device as random data generator. Now we must open the device:
Step 2 – Open the encrypted device:
cryptsetup luksOpen /dev/sda sda_crypt
Step 3 – Fill the resulting device with 0s, using dd and /dev/zero as source:
dd if=/dev/zero of=/dev/mapper/sda_crypt bs=1M
Step 4 – Close the luks device and destroy the luks header overriding it with random data
Usually the header takes a few Megabytes, but to avoid calculations and be rude we will cover the first 10 Mb of the disk. We will use dd with /dev/urandom as random data source this time:
cryptsetup luksClose sda_crypt
dd if=/dev/urandom of=/dev/sda bs=512 count=20480
We have now the disk full of random data. Now for the serious stuff. Just repeat steps 1 and 2 but this time use a very secure passhrase, because it will be the key to unlock your disk
Step 5 – Now we’re going to use the device as phisical volume…
lvm pvcreate /dev/sda
Step 6 – … and create a volume group to contain it
vgcreate vg00 /dev/sda
Step 7 – Create the logical volumes
I usually use 4: one for root, one for the swap partition, one for /home and the other for a data partition, but this is obviously up to you.
lvcreate -n lv00_swap -L 4G vg00
lvcreate -n lv01_root -L 30G vg00
lvcreate -n lv02_home -L 10G vg00
lvcreate -n lv03_data -l +100%FREE vg00
Notice how on the last line i’ve used -l instead of -L. This modifies the command to use logical extends instead of size. The +100%FREE option tells the program to use all remaining space for the logical volume.
Now we must create the boot partition on a separate device, and when installing the system we should mark that device as bootloader device, in which to install grub. I will not cover this here, cause it’s a common operation.
Now format your logical volumes with the filesystem you like, install and enjoy your full encrypted system, but remember that encryption protects your computer only when it’s turned off, for example if someone steal your disk and tries to look for data inside it. Once your machine boots and the disk is decrypted, you will have no special defenses against any other sort of attack or danger.
Amazon Launches AWS Educate to Promote Cloud Learning
Amazon hopes to form the next generation of cloud specialists by bringing its services into the classroom.
Linux Foundation Updates SPDX Compliance Effort
Back in 2010, the Linux Foundation first launched its Software Package Data Exchange (SPDX) effort that helps to build out and identify software components in a standardized manner. Since then, use of SPDX has grown, and on May 12 the SPDX 2.0 specification was announced. The new specification aims to be even more comprehensive in helping organizations understand the open-source licenses that are used as part of an application deployment.Over the last several years, a number of large companies have adopted SPDX for internal tracking and sharing of licensing information, according to Jack Manbeck, SPDX Business Team co-chair.
Introduction to Samba – Share Files and Directories between Linux, Windows and Mac
Samba is the most popular and efficient way with which you can share your files and directories between Linux, Windows and Mac. You just have to create a Samba user, Decide which file/directory you wish to share and Set the permissions, in order to create a Samba share. Well, initially, this might seem to be difficult- especially for beginners, but when you understand all the configuration options, it will seem to be as simple as anything.
Read more at YourOwnLinux
How To: Install/Upgrade to Linux Kernel 4.0.3 in Ubuntu/Linux Mint Systems
The Linux Kernel 4.0.3 is now available for the users, announced Linus Torvalds. This Linux Kernel version comes with plenty of fixes and improvements. This article will guide you to install or upgrade to Linux Kernel 4.0.3 in your Ubuntu or Linux Mint system.
Read more at YourOwnLinux
Samsung Debuts Yocto-Based Linux IoT Boards

This week Samsung debuted three new system-on-chips on several Yocto-based Linux “Artik” computer-on-modules aimed at the Internet of Things market. Last week, a hugely successful Kickstarter campaign by Next Thing Co. launched a tiny, IoT focused “Chip” single board computer starting at $9 that will debut a new, small footprint Allwinner R8 SoC. And in February, the Raspberry Pi Foundation launched a wildly successful Raspberry Pi 2 Model B that features a quad-core Broadcom BCM2836 SoC that was custom made for the SBC.
While most new SoCs still debut on smartphones, tablets, or PCs, there’s an increasing trend toward embedded boards getting some of the opening day glory. And like the three examples above, they increasingly run Linux on SBCs or modules targeting the IoT market.
In olden times, it was the PC that drove new processor launches, and consumers still wait for new chips like the 14nm Broadwell version of Intel’s Core chips, for example, instead of settling for a Haswell version. Qualcomm’s Snapdragons and Nvidia’s Tegras have traditionally debuted on high-end Android smartphones, tablets, and game players, and Intel Atoms have appeared first in versions optimized for mobile devices, followed by much lower-key launches for the embedded version.
As developer-oriented products, SBCs — and especially COMs — are not likely to dominate processor product launches the way mobile devices do. Yet, the fact that embedded boards are beginning to not only debut new SoCs, but affect their design shows how far IoT has come. The trend actually may have started when Intel announced its IoT-focused Intel Edison module in conjunction with its new Quark chip, although the Edison eventually shipped with the Atom processor while the Quark is still disabled. The Quark instead will appear on a tiny Curie module later this year, but it won’t apparently run Linux.
One reason vendors are customizing their SoCs for IoT is that the size, weight, power, and price constraints in IoT, combined with the need for built-in wireless features, are requiring a rethink of processor design, Here’s a quick look at Samsung’s Artik, and the new Chip SBC, each of which could have a significant impact on the course of embedded Linux in the years to come.
Samsung Artik
Samsung’s Artik is unusual on several levels. First, there was the high-profile launch at IOT World this week, combined with ambitious plans to expand Artik throughout Samsung’s mobile and consumer electronic device offerings in the years to come. The devices all support a common SmartThings Open Cloud platform from the SmartThings home automation company Samsung acquired last year.
Second, the modules are highly compact, given their relative power. For example, at 29 x 25mm, the dual-core, Cortex-A7 based Artik 5 is even smaller than Intel’s tiny Edison, with which it directly competes. The Artik 10, which boasts an octa-core, Cortex-A15 and -A7 SoC, is not much larger at 39 x 29mm.
The products are also notable for the tight integration between SoC and module, blurring the line between them. The Artik name refers both to the modules and the SoCs that drive them, and there are no current plans to spin the processors off from their modules.
Like most IoT modules and SBCs, the Artik chips have built-in WiFi and Bluetooth. Yet, they also feature ZigBee, and soon will support Google’s 6loWPAN-based Thread protocol. In addition, they support a common hardware encryption technology for greater security.
The device also ships with a unified IoT stack. Despite Samsung’s recent move to re-spin the smartphone-oriented Tizen OS at wearables and other IoT devices, the Artik 5 and 10 modules instead run Yocto-based Linux, which like Tizen is a collaborative project hosted by the Linux Foundation. The third module — the tiny (12 x 12mm), MIPS-based Artik 1 — runs Nucleus OS. There was no mention of Tizen in the Artik announcement.
Although there were no claims for full open source compliance, Artik is billed as an “open” platform. At the very least, the Yocto build is open source, and Samsung has broken with its own past practices by already posting extensive documentation, despite the fact that the modules have only begun sampling, and the firmware is still in alpha stage.
$9 Chip Wags the Allwinner dog
Last week’s debut of the Next Thing Co.’s Chip SBC rocked the technosphere, and that was before the Kickstarter campaign jumped past the $1.1 million mark. The Debian Linux-based, open source Chip will likely have less of an impact than Artik, due in part to the fact that Next Thing is a small Oakland, Calif. startup rather than a global CE and mobile device giant. Yet, like the recent RPi 2, the Chip will apply pressure for SBC vendors to cut prices even further.
The breakthrough $9 price, which is still available on Kickstarter for another few weeks, is not quite as impressive as it seems at first glance, but it’s still a breakthrough. First, the processor is a relatively slow 1GHz Cortex-A8. Second, the boards won’t ship until December, and fully configured versions won’t arrive until May 2016.
In addition, devices with real-world VGA or HDMI ports, which are added via adapters, run to $19 and $24 respectively. Otherwise you’re limited to the base I/O of a USB port, micro-USB port, audio jack, and composite video jack. Next Thing is also selling a version baked into a “PocketCHIP” clamshell handheld with a 4.3-inch touchscreen, QWERTY keyboard, battery, and GPIO breakout, selling for $49 to $64.
Even when you take all that into account, and add in shipping, the Chip still offers an impressive price/performance ratio. It’s not quite on par with the quad-core RPi 2, which has had the advantage of guarantees for huge sales, but it should offer stiff competition for a host of under $40 modules and SBCs that runs OpenWRT Linux on MIPS-based Atheros AR9331 SoCs. Like these boards, and unlike the RPi, the Chip offers onboard WiFi and Bluetooth, reducing aftermarket costs.
Like the RPi 2, the Chip was able to keep things lean thanks to a customized, lightweight SoC designed to support it. Instead of going to Broadcom, as the Pi Foundation did, Next Thing tapped Allwinner, whose A20, A31, and A80 processors are dominant on low- and mid-range Android tablets, not to mention a growing number of open-spec SBCs.
Next Thing worked closely with Allwinner through the Shenzhen-based “HAXLR8R” accelerator to strip down its earlier Cortex-A8 based A13 processor into a new, IoT-focused R8 SoC. Few details are available yet on the R8, but it’s said to be smaller and more affordable than the A13.
Allwinner boards are fairly popular among open source hackers due to the processors’ low cost and relatively open Mali-400 GPU. However, those same hackers complain about the lack of polished, timely Linux code available by Allwinner for its predominantly Android-focused SoCs.
Next Thing says that Allwinner is planning to release “all the necessary documentation and source code” for the R8 processor and the Chip’s power management chips. Together with Samsung’s “open platform” claims for the Artik, it gives hope that as Linux-based IoT grows in importance, some of its openness may rub off on chip manufacturers as well.