<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=3638&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Some ISO image insights and bugs]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=3638</link>
		<description><![CDATA[The most recent posts in Some ISO image insights and bugs.]]></description>
		<lastBuildDate>Fri, 26 Jun 2020 21:34:35 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Some ISO image insights and bugs]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=23035#p23035</link>
			<description><![CDATA[<p>Thanks. I&#039;ll have to play with this when I have time. Extra modules were added when I was testing on my uefi toshiba laptop and much of the boot messages were not being displayed.</p><p>The empty isolinux.cfg is a know characteristic. If you use refracta2usb to make a multiboot live-usb that uefi capable, it will actually put an empty isolinux.cfg on the usb so grub can find it. All the other isolinux files get renamed as syslinux in that case.</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Fri, 26 Jun 2020 21:34:35 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=23035#p23035</guid>
		</item>
		<item>
			<title><![CDATA[Some ISO image insights and bugs]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=23020#p23020</link>
			<description><![CDATA[<p>After my experiences <a href="https://dev1galaxy.org/viewtopic.php?id=3635" rel="nofollow">here</a> I created an as small as possible minimal-live ISO image with adjustments in grub&#039;s menu and a persistence partition for the /home directory.</p><p>While doing so I found some bugs in the desktop-live ISO image.</p><p>In <span class="bbc">boot/grub/x86_64-efi/grub.cfg</span> there are both incorrect entries (insmod with *.mod) and non-existent entries (insmod ieee1275_fb, insmod vbe, insmod vga), which generate error messages during boot. Actually, all insmod entries are unnecessary and should be removed (i.e. only <span class="bbc">source /boot/grub/grub.cfg</span> should remain) once the error in <span class="bbc">boot/grub/grub.cfg</span> is fixed.</p><p>In <span class="bbc">boot/grub/grub.cfg</span> the first line must read <span class="bbc">if loadfont <strong>/boot/grub</strong>/font.pf2 ; then</span> in order for the following statements to be executed!</p><p>By the way, the directory <span class="bbc">efi</span> seems to be unnecessary, because its content is already in <span class="bbc">boot/grub/efiboot.img</span>. Furthermore, <span class="bbc">grub/x86_64-efi/{config.h,kernel.img}</span> seem to be unnecessary.</p><p>For a UEFI boot only USB stick, a virtually empty directory <span class="bbc">isolinux</span> is sufficient, containing only an empty <span class="bbc">isolinux.cfg</span>.</p><p>I did all this for my ISO image and after xorriso-ing an edited <span class="bbc">boot</span>, an &quot;empty&quot; <span class="bbc">isolinux</span> and a copied <span class="bbc">live</span> the USB stick boots perfectly.</p>]]></description>
			<author><![CDATA[dummy@example.com (jdev)]]></author>
			<pubDate>Fri, 26 Jun 2020 12:19:36 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=23020#p23020</guid>
		</item>
	</channel>
</rss>
