<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>cyborgworkshop.org &#187; kernel</title>
	<atom:link href="http://cyborgworkshop.org/tag/kernel/feed/" rel="self" type="application/rss+xml" />
	<link>http://cyborgworkshop.org</link>
	<description>Blurring the line</description>
	<lastBuildDate>Wed, 18 May 2011 13:57:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Get quick log messages from the kernel</title>
		<link>http://cyborgworkshop.org/2008/04/07/get-quick-log-messages-from-the-kernel/</link>
		<comments>http://cyborgworkshop.org/2008/04/07/get-quick-log-messages-from-the-kernel/#comments</comments>
		<pubDate>Mon, 07 Apr 2008 21:00:41 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Solaris]]></category>
		<category><![CDATA[dmesg]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[syslog]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=24</guid>
		<description><![CDATA[The kernel has a log message ring buffer that messages are stored in before they go to syslog. When you just want to get a quick look at what the kernel has to say, you can view that buffer by running dmesg. dmesg]]></description>
			<content:encoded><![CDATA[<p>The kernel has a log message ring buffer that messages are stored in before they go to syslog.  When you just want to get a quick look at what the kernel has to say, you can view that buffer by running dmesg.</p>
<blockquote><p>dmesg</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/04/07/get-quick-log-messages-from-the-kernel/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgrade a Linux kernel remotely with a backout plan</title>
		<link>http://cyborgworkshop.org/2008/03/20/upgrade-a-linux-kernel-remotely-with-a-backout-plan/</link>
		<comments>http://cyborgworkshop.org/2008/03/20/upgrade-a-linux-kernel-remotely-with-a-backout-plan/#comments</comments>
		<pubDate>Thu, 20 Mar 2008 10:29:05 +0000</pubDate>
		<dc:creator>jason</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[backout]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[panic]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://cyborgworkshop.org/?p=8</guid>
		<description><![CDATA[This was borrowed from Sebastien Wains website and then paraphrased. To upgrade a linux kernel when you don&#8217;t have physical access to the machine, it&#8217;s important to give yourself a backout plan. Should the box panic and die, it&#8217;ll just sit there and wait for a user to come and start pressing buttons by default. [...]]]></description>
			<content:encoded><![CDATA[<p>This was borrowed from <a href="http://www.wains.be/" target="_blank">Sebastien Wains</a> website and then paraphrased.</p>
<p>To upgrade a linux kernel when you don&#8217;t have physical access to the machine, it&#8217;s important to give yourself a backout plan. Should the box panic and die, it&#8217;ll just sit there and wait for a user to come and start pressing buttons by default. Kinda sucks.  So here is a way to upgrade to that new kernel and revert automatically to old faithful should the box puke.  Keep in mind, if you do something brain dead like forgetting to compile in your NIC drivers into the new kernel, this method isn&#8217;t going to help you out. This will only protect you in the event of a hard panic.</p>
<p>First thing to go under the knife is the grub menu.lst file</p>
<blockquote><p> default         saved<br />
timeout         5<br />
# new kernel, not tested<br />
title           Untested Kernel<br />
root            (hd0,0)<br />
kernel          /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro panic=5<br />
initrd          /boot/initrd.img-2.6.18-6-686<br />
savedefault 1</p>
<p># tested and working kernel<br />
title           Old Faithful<br />
root            (hd0,0)<br />
kernel          /boot/vmlinuz-2.6.18-5-686 root=/dev/sda1 ro<br />
initrd          /boot/initrd.img-2.6.18-5-686<br />
savedefault</p></blockquote>
<p>Now tell grub to use the new kernel on the next boot, but not subsequent boots. e.g., boot the new kernel now, but not next time.</p>
<blockquote><p> grub-set-default 0</p></blockquote>
<p>Boot away!   We&#8217;ve really done two things here. The first is telling grub to boot a different kernel then the configured default and the second is telling Linux to reboot if it should kernel panic instead of just sitting there.  Neat trick and props to Sebastien Wains.</p>
]]></content:encoded>
			<wfw:commentRss>http://cyborgworkshop.org/2008/03/20/upgrade-a-linux-kernel-remotely-with-a-backout-plan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

