Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Sun, Mar 15, 2009 at 5:21 AM, Sebastian Dziallas wrote: > Wade Brainerd wrote: >> On Thu, Mar 12, 2009 at 7:04 PM, Dave Bauer wrote: >>> Actually, you can create a .vmdk from .img using the QEMU tools.  It's just that .vmdk is much more widely supported that .img so it would >>>

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Mar 15, 2009, at 6:21 AM, Sebastian Dziallas wrote: > Wade Brainerd wrote: >> On Thu, Mar 12, 2009 at 7:04 PM, Dave Bauer >> wrote: >>> Actually, you can create a .vmdk from .img using the QEMU tools. It's just that .vmdk is much more widely supported that .img so i

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

Wade Brainerd wrote: > On Thu, Mar 12, 2009 at 7:04 PM, Dave Bauer wrote: >> >>> >>> Actually, you can create a .vmdk from .img using the QEMU tools. It's >>> just that .vmdk is much more widely supported that .img so it would >>> save a conversion step for most VM users. >>> >>> I agree that we

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 9:55 PM, S Page wrote: > On Thu, Mar 12, 2009 at 4:04 PM, Dave Bauer wrote: >>  I haven't found an easy way to get QEMU working with acceleration on OS X. > > QEMU on Windows is also confused, or I am. > > http://sugarlabs.org/go/Supported_systems/Windows still points to >

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On 12.03.2009, at 21:12, Dave Bauer wrote: > Ok, I was able to take the Virtualbox VM and conver it to run in > Parallels, but its not easy and you definitely need to install the > Parallels Tools. I also have created a new Parallels native VM based > on SoaS slightly modifying the instructi

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 4:04 PM, Dave Bauer wrote: >  I haven't found an easy way to get QEMU working with acceleration on OS X. QEMU on Windows is also confused, or I am. http://sugarlabs.org/go/Supported_systems/Windows still points to Wade's fine bundle and detailed steps from Ton van Overbee

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 7:16 PM, Wade Brainerd wrote: > I brought up VMware Virtual Appliances as an option at one point, has > anyone tried creating one of those? I'm not sure how close to "one > click" they are though. > My main problem wiht VMWare is that it's closed-source and hard to conve

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 7:04 PM, Dave Bauer wrote: > > >> >> >> Actually, you can create a .vmdk from .img using the QEMU tools.  It's >> just that .vmdk is much more widely supported that .img so it would >> save a conversion step for most VM users. >> >> I agree that we should be providing 1 cli

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

> > Actually, you can create a .vmdk from .img using the QEMU tools. It's > just that .vmdk is much more widely supported that .img so it would > save a conversion step for most VM users. > > I agree that we should be providing 1 click solutions *in addition* to > providing .vmdk files for people

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 5:45 PM, Luke Faraone wrote: > On Thu, Mar 12, 2009 at 4:12 PM, Dave Bauer wrote: But really, all we need to be doing is producing .vmdk files (virtual disk images) for our SoaS snapshots.  These files can be loaded in any of VMware, VirtualBox and Para

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 4:12 PM, Dave Bauer wrote: > But really, all we need to be doing is producing .vmdk files (virtual >>> disk images) for our SoaS snapshots. These files can be loaded in any >>> of VMware, VirtualBox and Parallels, and can be used with QEMU after a >>> command line convers

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Thu, Mar 12, 2009 at 1:44 PM, Dave Bauer wrote: > > > On Wed, Mar 11, 2009 at 1:17 PM, Wade Brainerd wrote: > >> On Tue, Mar 10, 2009 at 11:08 PM, Luke Faraone wrote: >> Virtualbox is Free and potentially similar. Also, coLinux >> requires Administrator privileges to run, so stude

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

Removed iaep from CC as I we're just talking about technical details without educational impact now. On Tue, Mar 10, 2009 at 10:44:32PM -0400, Benjamin M. Schwartz wrote: [Sugar _does_ work (natively) over an ssh tunnel] Are you using the "sugar-emulator" command? Usually, but I've also run s

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Wed, Mar 11, 2009 at 1:17 PM, Wade Brainerd wrote: > On Tue, Mar 10, 2009 at 11:08 PM, Luke Faraone wrote: > Virtualbox is Free and potentially similar. Also, coLinux > requires Administrator privileges to run, so students on school > computers > probably can't use it.[1] > >>

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Tue, Mar 10, 2009 at 11:08 PM, Luke Faraone wrote: Virtualbox is Free and potentially similar.  Also, coLinux requires Administrator privileges to run, so students on school computers probably can't use it.[1] >>> Don't VMs on Windows require admin privileges to install and/or ru

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

I used to use coLinux regularly when my contracts required me to work on Windows, and I contributed various info to their Wiki. If Sugar on coLinux turns out to be worthwhile, I will be happy to help with documentation. On Tue, Mar 10, 2009 at 3:10 PM, Chris Ball wrote: > Hi, > >   > Hi all, I w

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On 3/10/09, Benjamin M. Schwartz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Sascha Silbe wrote: >> On Tue, Mar 10, 2009 at 09:26:59PM -0400, Benjamin M. Schwartz wrote: >> >>> So, the principal difficulty with using coLinux with Sugar is that it >>> uses >>> a Windows-side X serv

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sascha Silbe wrote: > On Tue, Mar 10, 2009 at 09:26:59PM -0400, Benjamin M. Schwartz wrote: > >> So, the principal difficulty with using coLinux with Sugar is that it >> uses >> a Windows-side X server, which provides its own window manager. We need

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Tue, Mar 10, 2009 at 09:26:59PM -0400, Benjamin M. Schwartz wrote: So, the principal difficulty with using coLinux with Sugar is that it uses a Windows-side X server, which provides its own window manager. We need to use our own, custom-configured window manager, in order for the GUI to w

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Luke Faraone wrote: > On Tue, Mar 10, 2009 at 7:55 PM, Martin Dengler > wrote: > >> Interesting but you'd need an X server running on Windows, according >> to http://colinux.wikia.com/wiki/XCoLinux (IIUC). So you're still >> going to have to get the

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Tue, Mar 10, 2009 at 7:55 PM, Martin Dengler wrote: > Interesting but you'd need an X server running on Windows, according > to http://colinux.wikia.com/wiki/XCoLinux (IIUC). So you're still > going to have to get them not only an EXE with coLinux, but one with > cygwin/X or another (do free o

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

On Tue, Mar 10, 2009 at 06:00:02PM -0400, Luke Faraone wrote: > Hi all, > > I was musing on ways to ease demoing for Windows users, and I thought of > something: why not leverage the work done by coLinux? > They already have prebuilt > images

Re: [Sugar-devel] [IAEP] Running sugar at almost-native speeds in Windows

Hi, > Hi all, I was musing on ways to ease demoing for Windows users, and > I thought of something: why not leverage the work done by > coLinux? dogi tried this, and it didn't work because HAL didn't want to run on a kernel without inotify, which it claimed was true of the colinux kernel