Add zarb MLs html archivesHEADmaster

2 files changed, 52 insertions, 0 deletions

diff --git a/zarb-ml/mageia-dev/attachments/20130104/a3bcfb67/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20130104/a3bcfb67/attachment-0001.html
new file mode 100644
index 000000000..b29367b85
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130104/a3bcfb67/attachment-0001.html
@@ -0,0 +1,26 @@
+Hi Thomas,<br><br><div class="gmail_quote">On 4 January 2013 04:41, Thomas Backlund <span dir="ltr">&lt;<a href="mailto:tmb@mageia.org" target="_blank">tmb@mageia.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+Glen Ogilvie skrev 3.1.2013 13:10:<br>
+<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+Hi,<br>
+<br>
+Has anyone got Mageia 2 or Mageia 3 beta running on Amazon EC2?<br>
+<br>
+I have been having a go, but not quite got there yet, so thought I&#39;d ask<br>
+if anyone has already done it?<br>
+</blockquote>
+<br>
+There was someone on irc testing it and had some progress...<br>
+I don&#39;t know if he finished his tests.<br>
+<br>
+One thing... you need kernel-server-3.4.24-1 from 2/updates_testing<br>
+to get it to boot (kernel image gz kompressed)<br></blockquote><div><br>Thank you fro the tip about using  kernel-server-3.4.24-1.<br>After switching to this kernel, and rebuilding initrd, with the command:<br>mkinitrd-mkinitrd --with=xen-blkfront --with=xennet --with=xen-netfront initrd-3.4.24-server-2.mga2.img 3.4.24-server-2.mga2<br>
+<br>It worked on Amazon EC2 and I have a nice Amanzon EC2 Mageia2 box.  I&#39;ll create a clean AMI for others to use in the next few weeks!  I released a Mandriva 2011 public AMI about a year ago.<br><br>It went much better than my attempt with 3.3.8-server-2.mga2, which complained about the compression format.<br>
+I see in the change log, you have switched it back to gzip.  <br><br>Searching for the gzip signature, using<br> od -A d -t x1 vmlinuz-3.3.8-server-2.mga2 | grep &#39;1f 8b 08 00&#39;  does not find it, for 3.3.8, but searching for the xz sig, using<br>
+od -A d -t x1 vmlinuz-3.3.8-server-2.mga2 | grep -i &#39;fd 37 7a 58 5a 00&#39;, return a match.  <br><br>I found what is a little bit of a trap for people...  funny now I think about it. <br><br>the output from running file vmlinuz*<br>
+<br>vmlinuz-3.4.24-server-2.mga2:
+ Linux kernel x86 boot executable bzImage, version 3.4.24-server-2.mga2 
+(<a href="mailto:iurt@ecosse.mageia.org">iurt@ecosse.mageia.org</a>) #1 SMP Tue Dec 18, RO-rootFS, swap_dev 0x3, 
+Normal VGA<br>vmlinuz-3.3.8-server-2.mga2:  Linux kernel x86 boot 
+executable bzImage, version 3.3.8-server-2.mga2 (<a href="mailto:iurt@jonund.mageia.org">iurt@jonund.mageia.org</a>)
+ #1 SMP Mon Jul 30 , RO-rootFS, swap_dev 0x2, Normal VGA<br><br>It is easy to assume that bzImage mean&#39;s bzip.. but it does not.. it means big zimage.  the actual compression type is not displayed using the file command.<br>
+<br>I wonder if a patch to the file command to also output the compression type for kernel images, might be a good idea?<br><br>Regards<br>Glen Ogilvie<br></div></div>
diff --git a/zarb-ml/mageia-dev/attachments/20130104/a3bcfb67/attachment.html b/zarb-ml/mageia-dev/attachments/20130104/a3bcfb67/attachment.html
new file mode 100644
index 000000000..b29367b85
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130104/a3bcfb67/attachment.html
@@ -0,0 +1,26 @@
+Hi Thomas,<br><br><div class="gmail_quote">On 4 January 2013 04:41, Thomas Backlund <span dir="ltr">&lt;<a href="mailto:tmb@mageia.org" target="_blank">tmb@mageia.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+Glen Ogilvie skrev 3.1.2013 13:10:<br>
+<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+Hi,<br>
+<br>
+Has anyone got Mageia 2 or Mageia 3 beta running on Amazon EC2?<br>
+<br>
+I have been having a go, but not quite got there yet, so thought I&#39;d ask<br>
+if anyone has already done it?<br>
+</blockquote>
+<br>
+There was someone on irc testing it and had some progress...<br>
+I don&#39;t know if he finished his tests.<br>
+<br>
+One thing... you need kernel-server-3.4.24-1 from 2/updates_testing<br>
+to get it to boot (kernel image gz kompressed)<br></blockquote><div><br>Thank you fro the tip about using  kernel-server-3.4.24-1.<br>After switching to this kernel, and rebuilding initrd, with the command:<br>mkinitrd-mkinitrd --with=xen-blkfront --with=xennet --with=xen-netfront initrd-3.4.24-server-2.mga2.img 3.4.24-server-2.mga2<br>
+<br>It worked on Amazon EC2 and I have a nice Amanzon EC2 Mageia2 box.  I&#39;ll create a clean AMI for others to use in the next few weeks!  I released a Mandriva 2011 public AMI about a year ago.<br><br>It went much better than my attempt with 3.3.8-server-2.mga2, which complained about the compression format.<br>
+I see in the change log, you have switched it back to gzip.  <br><br>Searching for the gzip signature, using<br> od -A d -t x1 vmlinuz-3.3.8-server-2.mga2 | grep &#39;1f 8b 08 00&#39;  does not find it, for 3.3.8, but searching for the xz sig, using<br>
+od -A d -t x1 vmlinuz-3.3.8-server-2.mga2 | grep -i &#39;fd 37 7a 58 5a 00&#39;, return a match.  <br><br>I found what is a little bit of a trap for people...  funny now I think about it. <br><br>the output from running file vmlinuz*<br>
+<br>vmlinuz-3.4.24-server-2.mga2:
+ Linux kernel x86 boot executable bzImage, version 3.4.24-server-2.mga2 
+(<a href="mailto:iurt@ecosse.mageia.org">iurt@ecosse.mageia.org</a>) #1 SMP Tue Dec 18, RO-rootFS, swap_dev 0x3, 
+Normal VGA<br>vmlinuz-3.3.8-server-2.mga2:  Linux kernel x86 boot 
+executable bzImage, version 3.3.8-server-2.mga2 (<a href="mailto:iurt@jonund.mageia.org">iurt@jonund.mageia.org</a>)
+ #1 SMP Mon Jul 30 , RO-rootFS, swap_dev 0x2, Normal VGA<br><br>It is easy to assume that bzImage mean&#39;s bzip.. but it does not.. it means big zimage.  the actual compression type is not displayed using the file command.<br>
+<br>I wonder if a patch to the file command to also output the compression type for kernel images, might be a good idea?<br><br>Regards<br>Glen Ogilvie<br></div></div>