Testing current daily ISOs to go towards new release

Hi,

the current Grml daily ISOs (http://daily.grml.org/) feature a fresh
3.3.4 Linux kernel and I plan to work towards a 2012-05-rc0 release
throughout the next days.

Everyone who wants to see 2012-05-rc0 actually happen is invited to
grab the current daily ISOs (the testing flavours of grml-full +
grml-small, 64bit and 32bit) and report any issues we should address
before releasing rc0.

Let's get ready to rumble :)

regards,
-mika-

Hi,

the current Grml daily ISOs (http://daily.grml.org/) feature a fresh
3.3.4 Linux kernel and I plan to work towards a 2012-05-rc0 release
throughout the next days.

Everyone who wants to see 2012-05-rc0 actually happen is invited to
grab the current daily ISOs (the testing flavours of grml-full +
grml-small, 64bit and 32bit) and report any issues we should address
before releasing rc0.

Let's get ready to rumble :)

Re: Testing current daily ISOs to go towards new release

Hello

> the current Grml daily ISOs (http://daily.grml.org/) feature a fresh
> 3.3.4 Linux kernel
>
> grab the current daily ISOs (the testing flavours of grml-full +
> grml-small, 64bit and 32bit)

I just downloaded the ISOs for the 64bit full versions testing and sid.
But uname -r gives me 3.3.0-1-grml-amd64... what am I doing wrong?
_
And while am at it... after the last release, some of my favorite
packages where missing and I didn't took the time to post while the
discussion was hot. So if it's possible to include the following, this
would help me to not have to roll my own grml-live:
xmount
ewf-tools
guymager

But that's just part of my own favorites. Needing 25MB additional space
while uncompressed. Hope this wish doesn't comes close to release now.

Didn't had enough time yet to find some more interesting issues... ;)

Best regards
Ursus

Re: Testing current daily ISOs to go towards new release

> > So if it's possible to include the following, this
> > would help me to not have to roll my own grml-live:
> > xmount
> > ewf-tools
> > guymager
> 
> Those tools don't touch the scope of Grml close enough, 25MB
> is also quite large overall, so I'm afraid they won't reach the Grml
> release, sorry.

I don't know about the size requirements. Withoug guymager, it would
be 225kB, maybe a more acceptable size. Of course something like
aimage would be needed for the non-ewf part of the world, but sadly
this went out of debian some time ago. Maybe I should learn to package
stuff some day and help out on the upstream front...

As there's a forensic boot option and stuff like afflib-tools
provided, I don't understand the "don't touch the scope of Grml" part
too well. But of course that's my personal view and the reason I
started to use in the first place.

Best regards
Ursus

Re: Testing current daily ISOs to go towards new release

<div>
<div class="gmail_quote">On 10 May 2012 12:10, Michael Prokop <span dir="ltr">&lt;<a href="mailto:mika <at> grml.org" target="_blank">mika <at> grml.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">

* Urs Blaser [Thu May 10, 2012 at 04:29:37PM +0200]:<br><div class="im">
<br>
&gt; &gt; Those tools don't touch the scope of Grml close enough, 25MB<br>
&gt; &gt; is also quite large overall, so I'm afraid they won't reach the Grml<br>
&gt; &gt; release, sorry.<br><br>
&gt; I don't know about the size requirements. Withoug guymager, it would<br>
&gt; be 225kB, maybe a more acceptable size. Of course something like<br>
&gt; aimage would be needed for the non-ewf part of the world, but sadly<br>
&gt; this went out of debian some time ago. Maybe I should learn to package<br>
&gt; stuff some day and help out on the upstream front...<br><br>
</div>Ok, I'll discuss the situation for xmount and ewf-tools within the<br>
team again. NACK for guymager though.<br><div class="im">
<br>
&gt; As there's a forensic boot option and stuff like afflib-tools<br>
&gt; provided, I don't understand the "don't touch the scope of Grml" part<br>
&gt; too well.<br><br>
</div>The forensic boot option is a feature which was contributed back<br>
by the commercial Grml-Forensic flavour.<br><div class="im">
<br>
&gt; But of course that's my personal view and the reason I<br>
&gt; started to use in the first place.<br><br>
</div>Grml focuses on sysadmin needs, we used to include a bunch of tools<br>
that where actually outside of our scope but we had to re-focus the<br>
project to get our available manpower at the right place.<br><br>
regards,<br>
-mika-≤br><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br><br>
iEYEARECAAYFAk+r2nEACgkQ2N9T+zficuim+wCfQL56ZVi3iHP9wHaT5dA1wlTs<br>
yi8An0HutxUNAc8QJR9LIhFGBO64gdDv<br>
=YJME<br>
-----END PGP SIGNATURE-----<br><br>_______________________________________________<br>
Grml mailing list - <a href="mailto:Grml <at> ml.grml.org">Grml <at> ml.grml.org</a><br><a href="http://ml.grml.org/mailman/listinfo/grml" target="_blank">http://ml.grml.org/mailman/listinfo/grml</a><br>
join #grml on <a href="http://irc.freenode.org" target="_blank">irc.freenode.org</a><br>
grml-devel-blog: <a href="http://blog.grml.org/" target="_blank">http://blog.grml.org/</a><br>
</blockquote>
</div>
<br><br>Excellent news!<br clear="all"><br>-- <br>-msx<br>
</div>

Re: [Grml-devel] Testing current daily ISOs to go towards new release

Michael Prokop wrote...

> Everyone who wants to see 2012-05-rc0 actually happen

Count me in.

> is invited to
> grab the current daily ISOs (the testing flavours of grml-full +
                                   ^^^^^^^
> grml-small, 64bit and 32bit) and report any issues we should address
> before releasing rc0.

My bad, I tried "sid" first. In Virtualbox this just stalls the entire
virtual machine, and kvm (both Debian wheezy) almost instantly gives ...

    $ kvm --cdrom grml32-small_sid_latest.iso
    KVM internal error. Suberror: 1
    emulation failure
    EAX=00000200 EBX=00000ee3 ECX=00001e00 EDX=00004b04
    ESI=0000bed3 EDI=efa60000 EBP=0000b905 ESP=00000010
    EIP=000001b8 EFL=00013086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
    ES =0000 00000000 0000ffff 00009300
    CS =0004 00000040 0000ffff 00009b00
    SS =0004 00000040 0000ffff 00009300
    DS =b905 000b9050 0000ffff 00009300
    FS =0000 00000000 0000ffff 00009300
    GS =0000 00000000 0000ffff 00009300
    LDT=0000 00000000 ffffffff 00000000
    TR =0008 00000580 00000067 00008b00
    GDT=     0000aa80 0000002f
    IDT=     00000000 0000ffff
    CR0=00000012 CR2=00000000 CR3=00000000 CR4=00000000
    DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
    DR6=00000000ffff4ff0 DR7=0000000000000400
    EFER=0000000000000000
    Code=00 00 46 00 3f 01 79 00 00 00 46 00 8f 01 79 00 00 00 46 00 <df> 01 79 00 00 00 46 00 2f 01 79 00 00 00 46 00 7f 01 79 00 00
00 46 00 cf 01 79 00 00 00

Perhaps this needs some attention.

FWIW, "testing" does fine at a first glance, then virtualbox crashed
due to PEBKAC. More testing during the weekend.

> Let's get ready to rumble :)

I'll do my very best.

Cheers,

    Christoph

making hardware speech work

I was wondering if the grml team would be interested in making hardware 
speech work in grml. I have a kernel patch that fixes a problem in the linux 
screen reader, speakup, to make it work with certain hardware speech 
synthesizers.  I don't know how to get it into the actual kernel code and I 
haven't even tried yet.  But the patch file can be downloaded here:

http://www.math.wisc.edu/~jheim/downloads/patch-2012-03-06.patch

Then you cd to your linux source dir and do this:
patch -i patch-2012-03-06.patch drivers/staging/speakup/serialio.c"

If you do that, you could also include a udev rules file that starts speech 
automatically if certain hardware synths are connected at boot time. That 
file is here:

http://www.math.wisc.edu/~jheim/downloads/10-speakup.rules

Re: making hardware speech work

Hi John,

* John Heim [Fri May 11, 2012 at 09:24:11AM -0500]:

> I was wondering if the grml team would be interested in making
> hardware speech work in grml.

If we get feedback and patches like yours: sure :)

> I have a kernel patch that fixes a problem in the linux screen
> reader, speakup, to make it work with certain hardware speech
> synthesizers.  I don't know how to get it into the actual kernel
> code and I haven't even tried yet.  But the patch file can be
> downloaded here:

> http://www.math.wisc.edu/~jheim/downloads/patch-2012-03-06.patch

Thanks for the patch, could you by any chance try to get it
applied upstream? We try to stay as close to upstream and Debian
kernel as possible and we'd like to see improvements taking place
there so it's not just the Grml users who can benefit from it. :)

> Then you cd to your linux source dir and do this:
> patch -i patch-2012-03-06.patch drivers/staging/speakup/serialio.c"

> If you do that, you could also include a udev rules file that starts
> speech automatically if certain hardware synths are connected at boot
> time. That file is here:

> http://www.math.wisc.edu/~jheim/downloads/10-speakup.rules

Hm, this might be interesting also to Debian in general?
Maybe it would fit into the speakup-tools package. John, are you
familiar with reporting a bug within Debian using reportbug?

Thanks, John.

regards,
-mika-

Re: [Grml-devel] Testing current daily ISOs to go towards new release

* Christoph Biedl [Thu May 10, 2012 at 11:57:08PM +0200]:
> Michael Prokop wrote...

> > Everyone who wants to see 2012-05-rc0 actually happen

> Count me in.

\o/

> > is invited to
> > grab the current daily ISOs (the testing flavours of grml-full +
>                                    ^^^^^^^
> > grml-small, 64bit and 32bit) and report any issues we should address
> > before releasing rc0.

> My bad, I tried "sid" first. In Virtualbox this just stalls the entire
> virtual machine, and kvm (both Debian wheezy) almost instantly gives ...

Interesting

>     $ kvm --cdrom grml32-small_sid_latest.iso
>     KVM internal error. Suberror: 1
>     emulation failure
>     EAX=00000200 EBX=00000ee3 ECX=00001e00 EDX=00004b04
>     ESI=0000bed3 EDI=efa60000 EBP=0000b905 ESP=00000010
>     EIP=000001b8 EFL=00013086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
>     ES =0000 00000000 0000ffff 00009300
>     CS =0004 00000040 0000ffff 00009b00
>     SS =0004 00000040 0000ffff 00009300
>     DS =b905 000b9050 0000ffff 00009300
>     FS =0000 00000000 0000ffff 00009300
>     GS =0000 00000000 0000ffff 00009300
>     LDT=0000 00000000 ffffffff 00000000
>     TR =0008 00000580 00000067 00008b00
>     GDT=     0000aa80 0000002f
>     IDT=     00000000 0000ffff
>     CR0=00000012 CR2=00000000 CR3=00000000 CR4=00000000
>     DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
>     DR6=00000000ffff4ff0 DR7=0000000000000400
>     EFER=0000000000000000
>     Code=00 00 46 00 3f 01 79 00 00 00 46 00 8f 01 79 00 00 00 46 00 <df> 01 79 00 00 00 46 00 2f 01 79 00 00 00 46 00 7f 01 79 00 00
00 46 00 cf 01 79 00 00 00

> Perhaps this needs some attention.

I can reproduce this issue. My bet is on the syslinux boot code.
AFAICS the working ISO is using syslinux 2:4.05+dfsg-2 while the
broken one provides 2:4.05+dfsg-3.

Might be:

| syslinux (2:4.05+dfsg-3) unstable; urgency=low
|
| [...]
|   * Cherry-picking patch from Matthew Garrett <mjg <at> redhat.com> for
|     isohybrid to generate MBR even when in EFI mode.

Could anyone further investigate on this one?

> FWIW, "testing" does fine at a first glance, then virtualbox crashed
> due to PEBKAC. More testing during the weekend.

> > Let's get ready to rumble :)

> I'll do my very best.

thanks :)

regards,
-mika-

* Christoph Biedl [Thu May 10, 2012 at 11:57:08PM +0200]:
> Michael Prokop wrote...

> > Everyone who wants to see 2012-05-rc0 actually happen

> Count me in.

\o/

> > is invited to
> > grab the current daily ISOs (the testing flavours of grml-full +
>                                    ^^^^^^^
> > grml-small, 64bit and 32bit) and report any issues we should address
> > before releasing rc0.

> My bad, I tried "sid" first. In Virtualbox this just stalls the entire
> virtual machine, and kvm (both Debian wheezy) almost instantly gives ...

Interesting

>     $ kvm --cdrom grml32-small_sid_latest.iso
>     KVM internal error. Suberror: 1
>     emulation failure
>     EAX=00000200 EBX=00000ee3 ECX=00001e00 EDX=00004b04
>     ESI=0000bed3 EDI=efa60000 EBP=0000b905 ESP=00000010
>     EIP=000001b8 EFL=00013086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
>     ES =0000 00000000 0000ffff 00009300
>     CS =0004 00000040 0000ffff 00009b00
>     SS =0004 00000040 0000ffff 00009300
>     DS =b905 000b9050 0000ffff 00009300
>     FS =0000 00000000 0000ffff 00009300
>     GS =0000 00000000 0000ffff 00009300
>     LDT=0000 00000000 ffffffff 00000000
>     TR =0008 00000580 00000067 00008b00
>     GDT=     0000aa80 0000002f
>     IDT=     00000000 0000ffff
>     CR0=00000012 CR2=00000000 CR3=00000000 CR4=00000000
>     DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000
>     DR6=00000000ffff4ff0 DR7=0000000000000400
>     EFER=0000000000000000
>     Code=00 00 46 00 3f 01 79 00 00 00 46 00 8f 01 79 00 00 00 46 00 <df> 01 79 00 00 00 46 00 2f 01 79 00 00 00 46 00 7f 01 79 00 00
00 46 00 cf 01 79 00 00 00

> Perhaps this needs some attention.

I can reproduce this issue. My bet is on the syslinux boot code.
AFAICS the working ISO is using syslinux 2:4.05+dfsg-2 while the
broken one provides 2:4.05+dfsg-3.

Might be:

| syslinux (2:4.05+dfsg-3) unstable; urgency=low
|
| [...]
|   * Cherry-picking patch from Matthew Garrett <mjg <at> redhat.com> for
|     isohybrid to generate MBR even when in EFI mode.

Could anyone further investigate on this one?

> FWIW, "testing" does fine at a first glance, then virtualbox crashed
> due to PEBKAC. More testing during the weekend.

> > Let's get ready to rumble :)

> I'll do my very best.

thanks :)

regards,
-mika-

Re: [Grml-devel] Testing current daily ISOs to go towards new release

* Michael Prokop [Sun May 13, 2012 at 07:33:58PM +0200]:
> * Christoph Biedl [Thu May 10, 2012 at 11:57:08PM +0200]:

> >     $ kvm --cdrom grml32-small_sid_latest.iso
> >     KVM internal error. Suberror: 1
> >     emulation failure
[...]
> I can reproduce this issue. My bet is on the syslinux boot code.
> AFAICS the working ISO is using syslinux 2:4.05+dfsg-2 while the
> broken one provides 2:4.05+dfsg-3.
[...]

Yes, it's syslinux:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672520

regards,
-mika-

* Michael Prokop [Sun May 13, 2012 at 07:33:58PM +0200]:
> * Christoph Biedl [Thu May 10, 2012 at 11:57:08PM +0200]:

> >     $ kvm --cdrom grml32-small_sid_latest.iso
> >     KVM internal error. Suberror: 1
> >     emulation failure
[...]
> I can reproduce this issue. My bet is on the syslinux boot code.
> AFAICS the working ISO is using syslinux 2:4.05+dfsg-2 while the
> broken one provides 2:4.05+dfsg-3.
[...]

Yes, it's syslinux:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672520

regards,
-mika-

Re: Testing current daily ISOs to go towards new release

Hello,
Just a quick note that I tried GRML daily ISO here. I tried the 
full-64-bit one. I was mainly checking that the accessibility stuff 
worked and I successfully got brltty and speakup with espeak for output 
working. My only comment is that the volume was initially very low, but 
I know setting the audio levels is difficult to do automaticaly as it 
can vary between sound cards. I know in some earlier GRML releases there 
was a kernel option to set the volume level, is that still present?

Also, as a separate note: Having the testing and unstable daily ISOs 
caught me out, I initially downloaded the unstable/sid one but realised 
before booting the CD, so I downloaded and tested the testing one.

Michael Whapples
On 08/05/2012 14:35, Michael Prokop wrote:
> Hi,
>
> the current Grml daily ISOs (http://daily.grml.org/) feature a fresh
> 3.3.4 Linux kernel and I plan to work towards a 2012-05-rc0 release
> throughout the next days.
>
> Everyone who wants to see 2012-05-rc0 actually happen is invited to
> grab the current daily ISOs (the testing flavours of grml-full +
> grml-small, 64bit and 32bit) and report any issues we should address
> before releasing rc0.
>
> Let's get ready to rumble :)
>
> regards,
> -mika-