<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=3405&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED]How do I unpack our intrd.img]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=3405</link>
		<description><![CDATA[The most recent posts in [SOLVED]How do I unpack our intrd.img.]]></description>
		<lastBuildDate>Wed, 22 Apr 2020 01:41:34 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED]How do I unpack our intrd.img]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=21208#p21208</link>
			<description><![CDATA[<p>Thanks will check out later</p>]]></description>
			<author><![CDATA[dummy@example.com (aus9)]]></author>
			<pubDate>Wed, 22 Apr 2020 01:41:34 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=21208#p21208</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED]How do I unpack our intrd.img]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=21203#p21203</link>
			<description><![CDATA[<p>Almost easier is to use the programs found in the package &quot;initramfs-tools-core&quot;. In particular lsinitramfs and unmkinitramfs work really well for me. I build a custom kernel and initramfs to have a router system that runs completely within memory once booted, no disk or usb stick<br />access.</p>]]></description>
			<author><![CDATA[dummy@example.com (dgrif)]]></author>
			<pubDate>Tue, 21 Apr 2020 17:59:49 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=21203#p21203</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED]How do I unpack our intrd.img]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=20812#p20812</link>
			<description><![CDATA[<p>Hi</p><p>I want to do some exploring of our initrd.img</p><p>I found a simple command that appeared to work but it only unpacks microcode</p><p>eg&#160; all commands done as root</p><div class="codebox"><pre><code>cp /boot/initrd.img-4.19.0-8-amd64 /tmp
cd /tmp
cpio -i -F initrd.img*
ls -al (culling older timestamps) 
kernel </code></pre></div><p>and the kernel has sub dirs to lead to your amd or intel or both microcodes.</p><p>I am aware that we have a file as follows</p><div class="codebox"><pre><code>file initrd.img-4.19.0-8-amd64 
initrd.img-4.19.0-8-amd64: ASCII cpio archive (SVR4 with no CRC)</code></pre></div><p>I found a hit after changing my search to ask why I could only see a kernel&#160; got this<br /><a href="https://unix.stackexchange.com/questions/163346/why-is-it-that-my-initrd-only-has-one-directory-namely-kernel" rel="nofollow">https://unix.stackexchange.com/question … ely-kernel</a></p><p>new root commands</p><div class="codebox"><pre><code>mkdir /tmp/unpack
cp /boot/initrd.img-4.19.0-8-amd64 /tmp/unpack
cd /tmp/unpack
(cpio -id; zcat | cpio -id) &lt; initrd.img-4.19.0-8-amd64

ls
bin  conf  cryptroot  etc  init  initrd.img-4.19.0-8-amd64  kernel  lib  lib64	run  sbin  scripts  usr</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (aus9)]]></author>
			<pubDate>Mon, 30 Mar 2020 03:21:43 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=20812#p20812</guid>
		</item>
	</channel>
</rss>
