<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Criu on Chris J Arges</title><link>https://chrisarges.net/tags/criu/</link><description>Recent content in Criu on Chris J Arges</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 25 Jun 2014 13:46:00 -0700</lastBuildDate><atom:link href="https://chrisarges.net/tags/criu/index.xml" rel="self" type="application/rss+xml"/><item><title>using CRIU to checkpoint a kernel build</title><link>https://chrisarges.net/posts/2014-06-25-using-criu-to-checkpoint-kernel-build/</link><pubDate>Wed, 25 Jun 2014 13:46:00 -0700</pubDate><guid>https://chrisarges.net/posts/2014-06-25-using-criu-to-checkpoint-kernel-build/</guid><description>&lt;p&gt;&lt;a href="http://criu.org/Main_Page"&gt;CRIU&lt;/a&gt; stands for Checkpoint/Restart in Userspace. As the criu package should&#10;be landing in Utopic soon, and I wanted to test drive it to see how it handles.&lt;/p&gt;&#10;&lt;p&gt;I thought of an interesting example of being in the middle of a linux kernel&#10;build and a security update needing to be installed and the machine rebooted.&#10;While most of us could probably just reboot and rebuild, why not checkpoint it&#10;and save the progress; then restore after the system update? I admit its not&#10;the most useful example; but it is pretty cool nonetheless.&lt;/p&gt;</description></item></channel></rss>