On Sun, 2007-08-26 at 20:05 -0400, Mike C. Fletcher wrote: > Ivan Krstić wrote: > > On Aug 26, 2007, at 7:07 PM, Mike C. Fletcher wrote: > > > >> Still, building them somewhere not behind a cable modem would be a > >> good idea. > > > > Right, I assumed giving you a shell on dev would let you convert the > > images right on that machine. Are there other requirements? > There's a few: > > * Qemu installation (for the qemu-img tool that converts to VMWare > disks) > * VirtualBox installation (for the vboxmanage tool that converts to > VirtualBox disks)
No need for this as VB can run VMWare disk fine. > * The overlay stuff also requires: > o ability to mount a loopback partition (to modify the ext3 > image with the overlay) > o ability to do an rsync over top of the mounted image > (requires super-user access AFAICS) > > The first two might be something you could run on dev (though I'd be > hesitant to increase your attack surface for the machine that way), but > the overlay operations are not the kind of thing you want running on a > publicly accessible server AFAICS, just too many security issues, > really. You'd want to run it on an old box somewhere with nothing > sensitive on it and then push the images up to dev I would think. I already have scripts in pilgrim to do a sdk build which outputs a vmware image with vmware and VB meta files. Let's build on that and I can do sdk builds along with regular builds. I just need to know what people think should be in a development image. BTW the build servers run as root and have qemu on them. -- John (J5) Palmieri <[EMAIL PROTECTED]> _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel