Comments for Executing Gummiworms http://russelldavis.org The trials and tribulations of a grumpy curmudgeonly old git Thu, 09 Feb 2012 14:53:39 +0000 hourly 1 Comment on New Raspberry Pi development vm version 0.2 by sherif omran http://russelldavis.org/2012/01/20/new-raspberry-pi-development-vm-v0-2/#comment-466 sherif omran Thu, 09 Feb 2012 14:53:39 +0000 http://russelldavis.org/?p=829#comment-466 thank you for the nice work. I would recommend to add QT to the VM and adjust the environment for building software on it and compiling for arm. This is tricky. Please do it for us. thank you for the nice work. I would recommend to add QT to the VM and adjust the environment for building software on it and compiling for arm. This is tricky. Please do it for us.

]]> Comment on OpenWRT on the Zipit Z2 by Russell http://russelldavis.org/2011/10/26/openwrt-on-the-zipit-z2/#comment-456 Russell Sun, 05 Feb 2012 21:29:20 +0000 http://russelldavis.org/?p=524#comment-456 I don't have a zipit immediately available at the moment (they are all packed away as i'm working on some other projects at the moment) so can you check to see if /bin/bash is available in openwrt and that it isn't symlinked to ash, dash or something like that? ewoc REQUIRES bash as it uses arrays and other stuff not available in ash/dash..... I don’t have a zipit immediately available at the moment (they are all packed away as i’m working on some other projects at the moment) so can you check to see if /bin/bash is available in openwrt and that it isn’t symlinked to ash, dash or something like that? ewoc REQUIRES bash as it uses arrays and other stuff not available in ash/dash…..

]]> Comment on Additional Raspberry Pi VM Information by Russell http://russelldavis.org/2012/01/31/additional-raspberry-pi-vm-information/#comment-455 Russell Sun, 05 Feb 2012 21:27:23 +0000 http://russelldavis.org/?p=1441#comment-455 Yes you can use the repository version of qemu and/or scratchbox2 i'm just loathed personally to trust 11.10 for anything because of the library problems that I have seen at least on the i386 version. You can solve them but my feeling is that if those slipped through the quality control (is there any? :) ) then what else slipped through that isn't as obvious. But if it works for you don't knock it :) Yes you can use the repository version of qemu and/or scratchbox2 i’m just loathed personally to trust 11.10 for anything because of the library problems that I have seen at least on the i386 version. You can solve them but my feeling is that if those slipped through the quality control (is there any? :) ) then what else slipped through that isn’t as obvious. But if it works for you don’t knock it :)

]]> Comment on Additional Raspberry Pi VM Information by Eric http://russelldavis.org/2012/01/31/additional-raspberry-pi-vm-information/#comment-454 Eric Sun, 05 Feb 2012 21:18:21 +0000 http://russelldavis.org/?p=1441#comment-454 I followed your directions with Ubuntu 11.10 and the only thing that didn't work for me was building scratchbox2. To resolve it, I simply did "sudo apt-get install scratchbox2" and everything else worked fine. I followed your directions with Ubuntu 11.10 and the only thing that didn’t work for me was building scratchbox2. To resolve it, I simply did “sudo apt-get install scratchbox2″ and everything else worked fine.

]]> Comment on OpenWRT on the Zipit Z2 by Steve http://russelldavis.org/2011/10/26/openwrt-on-the-zipit-z2/#comment-453 Steve Sun, 05 Feb 2012 20:38:47 +0000 http://russelldavis.org/?p=524#comment-453 Hi, hope you are feeling better these days. Hey, Still trying to sort out the wifi on my zipit z2. * I wiped the flash disk, and re-installed the Feb 6 openwrt tar image from http://www.chainxor.org/openwrt-zipit/snapshot/ * I downloaded and placed in root, made executable the ewoc script. * attempted to run the script (ewoc.sh, from here http://mozzwald.com/zipit/z2sid/ewoc-z2sid.fixed) with ash ewoc.sh This does not run at all! immediately complains. It is hard for me to capture this text since it is in the zipit. help! steve Hi, hope you are feeling better these days.
Hey, Still trying to sort out the wifi on my zipit z2.

* I wiped the flash disk, and re-installed the Feb 6 openwrt tar image from http://www.chainxor.org/openwrt-zipit/snapshot/

* I downloaded and placed in root, made executable the ewoc script.

* attempted to run the script (ewoc.sh, from here http://mozzwald.com/zipit/z2sid/ewoc-z2sid.fixed) with

ash ewoc.sh

This does not run at all! immediately complains.
It is hard for me to capture this text since it is in the zipit.

help!

steve

]]> Comment on New Raspberry Pi development vm version 0.2 by Russell http://russelldavis.org/2012/01/20/new-raspberry-pi-development-vm-v0-2/#comment-439 Russell Thu, 02 Feb 2012 05:29:57 +0000 http://russelldavis.org/?p=829#comment-439 I have actually been looking at how sbrsh/sbrshd (scratchbox remote shell) works these days (it seems to have been abandoned, the git repository that did exist is gone and just legacy tarballs lying around). I seem to have found two "forks" of it before it got dropped. one seems to have sshfs support and the other has the original nfs support but I haven't yet found time to investigate further. If i can get versions compiled for the raspi and qemu then we can use sb2 with either the real hardware and/or a running qemu-system-arm system to handle the ARM emulation required when doing things like ./configure However if you have a running qemu-system-arm with a compatable rootfs to the one sb2 is using e.g. fedora and have networking working in the qemu-system-arm emulation then because I installed (or you have) apache2 and symlinked it to the build directory you can wget programs built using sb2 into the running qemu-system-arm system. I did try to be a clever wotsit a couple of days ago and used a virtualbox emulated harddisk containing the seed rootfs that scratchbox2 uses and used that with qemu-system-arm instead of a disk image. so that things compiled and installed to the rootfs in scratchbox2 would show up in the running qemu-system-arm and vice versa. Probably not exactly a wise thing to do and i probably wouldn't recommend it if you want to keep a stable rootfs but it did work :) I'm having to put most Raspberry Pi things (other than the forum and twitter) on the back burner for a little while but as soon as I get a chance i'll continue looking at sbrsh. If anyone wants to speed up the time it takes for me to get back to raspi related activities I could do with some help with opencv and python and webcams in linux :) I have actually been looking at how sbrsh/sbrshd (scratchbox remote shell) works these days (it seems to have been abandoned, the git repository that did exist is gone and just legacy tarballs lying around). I seem to have found two “forks” of it before it got dropped. one seems to have sshfs support and the other has the original nfs support but I haven’t yet found time to investigate further. If i can get versions compiled for the raspi and qemu then we can use sb2 with either the real hardware and/or a running qemu-system-arm system to handle the ARM emulation required when doing things like ./configure

However if you have a running qemu-system-arm with a compatable rootfs to the one sb2 is using e.g. fedora and have networking working in the qemu-system-arm emulation then because I installed (or you have) apache2 and symlinked it to the build directory you can wget programs built using sb2 into the running qemu-system-arm system.

I did try to be a clever wotsit a couple of days ago and used a virtualbox emulated harddisk containing the seed rootfs that scratchbox2 uses and used that with qemu-system-arm instead of a disk image. so that things compiled and installed to the rootfs in scratchbox2 would show up in the running qemu-system-arm and vice versa. Probably not exactly a wise thing to do and i probably wouldn’t recommend it if you want to keep a stable rootfs but it did work :)

I’m having to put most Raspberry Pi things (other than the forum and twitter) on the back burner for a little while but as soon as I get a chance i’ll continue looking at sbrsh. If anyone wants to speed up the time it takes for me to get back to raspi related activities I could do with some help with opencv and python and webcams in linux :)

]]> Comment on New Raspberry Pi development vm version 0.2 by PC Pete http://russelldavis.org/2012/01/20/new-raspberry-pi-development-vm-v0-2/#comment-438 PC Pete Thu, 02 Feb 2012 04:56:16 +0000 http://russelldavis.org/?p=829#comment-438 G'day Russell! Mate, thanks so much for providing the whole kit & kaboodle! It's an intimidating step for many people, jumping into the world of VMs and filesystems (let alone toolchains!), and this seems to be a great way to start. Luckily for me, I'm well versed in VMs (from Z80,CP/M to DOS to Win 3.x to W95 to XP to linux now, all running simultaneously if needed!), but it's still a big step to go from "I'm so excited about the Pi" to "sb2 gcc hello.c -o hello"!! And QEMU has more than its share of quirks and undocumented features that it could still trip novices (and not-so-novices *cough*). However, since QEMU does emulate the ARM, I'm wondering if you've had a chance to (or interest in) getting code (compiled on your Pi-kit) to somehow run in an ARM instance of QEMU? If so, what would be your recommended way of achieving that? Is it possible? Or is the instruction set hoohaa (Thumb vs RISC, et al) going to be a showstopper? The reason I ask is that it would be really nice to get a software mirror of the hardware Pi working so that folks can test something simple out by building it on the PiKit, running it on the ARM VM, and then putting on the Pi to see it work in hardware. Is this feasible? Is it worthwhile doing, or am I just adding more complexity to an already well-complicated situation? I do realise that there's a lot of stuff that can't be emulated (graphics, networking, GPIO, etc), but the stuff that can be would be nice to see running before the hardware hits our desks. In any case, thanks so much for taking so much trouble to help us noobs out. I really do appreciate it. As do quite a few others, judging from the 18,000+ available copies of the torrent! Best wishes from Down Under, Pete (aka Cephas Borg). G’day Russell!

Mate, thanks so much for providing the whole kit & kaboodle! It’s an intimidating step for many people, jumping into the world of VMs and filesystems (let alone toolchains!), and this seems to be a great way to start.

Luckily for me, I’m well versed in VMs (from Z80,CP/M to DOS to Win 3.x to W95 to XP to linux now, all running simultaneously if needed!), but it’s still a big step to go from “I’m so excited about the Pi” to “sb2 gcc hello.c -o hello”!!

And QEMU has more than its share of quirks and undocumented features that it could still trip novices (and not-so-novices *cough*).

However, since QEMU does emulate the ARM, I’m wondering if you’ve had a chance to (or interest in) getting code (compiled on your Pi-kit) to somehow run in an ARM instance of QEMU? If so, what would be your recommended way of achieving that? Is it possible? Or is the instruction set hoohaa (Thumb vs RISC, et al) going to be a showstopper?

The reason I ask is that it would be really nice to get a software mirror of the hardware Pi working so that folks can test something simple out by building it on the PiKit, running it on the ARM VM, and then putting on the Pi to see it work in hardware. Is this feasible? Is it worthwhile doing, or am I just adding more complexity to an already well-complicated situation?

I do realise that there’s a lot of stuff that can’t be emulated (graphics, networking, GPIO, etc), but the stuff that can be would be nice to see running before the hardware hits our desks.

In any case, thanks so much for taking so much trouble to help us noobs out. I really do appreciate it. As do quite a few others, judging from the 18,000+ available copies of the torrent!

Best wishes from Down Under,
Pete (aka Cephas Borg).

]]> Comment on Additional Raspberry Pi VM Information by Homepage http://russelldavis.org/2012/01/31/additional-raspberry-pi-vm-information/#comment-437 Homepage Wed, 01 Feb 2012 18:59:23 +0000 http://russelldavis.org/?p=1441#comment-437 <strong>... [Trackback]...</strong> [...] Read More Infos here: russelldavis.org/2012/01/31/additional-raspberry-pi-vm-information/ [...]... … [Trackback]…

[...] Read More Infos here: russelldavis.org/2012/01/31/additional-raspberry-pi-vm-information/ [...]…

]]> Comment on Setting up a VM for Raspberry Pi development using Virtualbox, Scratchbox2 & qemu (Part 3) by Felix Gilcher http://russelldavis.org/2012/01/28/setting-up-a-vm-for-raspberry-pi-development-using-virtualbox-scratchbox2-qemu-part-3/#comment-436 Felix Gilcher Tue, 31 Jan 2012 22:11:11 +0000 http://russelldavis.org/?p=1209#comment-436 I took the liberty of transforming your instructions into a set of puppet recipes that vagrant can use to bootstrap a working virtualbox. It's still a bit rough around the edges and the readme is sorely lacking, but it should do the job. I'll improve on it tomorrow. You can find the repo here https://github.com/Asquera/raspberry-devbox Thanks for the guide. I took the liberty of transforming your instructions into a set of puppet recipes that vagrant can use to bootstrap a working virtualbox. It’s still a bit rough around the edges and the readme is sorely lacking, but it should do the job. I’ll improve on it tomorrow. You can find the repo here https://github.com/Asquera/raspberry-devbox

Thanks for the guide.

]]> Comment on Setting up a VM for Raspberry Pi development using Virtualbox, Scratchbox2 & qemu (Part 3) by Russell http://russelldavis.org/2012/01/28/setting-up-a-vm-for-raspberry-pi-development-using-virtualbox-scratchbox2-qemu-part-3/#comment-435 Russell Tue, 31 Jan 2012 21:19:43 +0000 http://russelldavis.org/?p=1209#comment-435 that sounds like an old qemu version. i used to get that a lot. what does qemu -version (or qemu-system-arm -version or ... ) give you? that sounds like an old qemu version. i used to get that a lot. what does qemu -version (or qemu-system-arm -version or … ) give you?

]]>