<br><br><div class="gmail_quote">On Wed, Sep 23, 2009 at 10:19 PM, Gary C Martin <span dir="ltr"><<a href="mailto:gary@garycmartin.com">gary@garycmartin.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Dave,<div class="im"><br></div></blockquote><div><snip> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"></div>
<br>
** unless you put the whole damn vdi on the stick and forgo the idea of booting the stick independently as a normal OS, though there could be room to investigate booting of a small partition with a reliable host OS that did nothing but dive right into the VM for those cases. Seems doable, but scary. Would much rather spend effort in finding a way to boot a USB directly – likely requires providing a Mac only image, though they can quite happily boot from USB, they just require correct boot formats (EFI for Intel Macs) but current Linux's seems well behind that curve. Most other HW manufacturers are still on old BIOS set-ups, Macs can support this for booting, Boot Camp does just this, but not for booting from USB devices unfortunately.<br>
<br></blockquote><div><br>SoaS does include EFI. I am not sure how it works. Macbooks do support booting from a USB hard drive, but I am not sure about a USB memory stick.<br><br>Dave<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Regards,<br><font color="#888888">
--Gary</font><div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dave<br>
<br>
<br>
On Wed, Sep 23, 2009 at 8:12 PM, Gary C Martin <<a href="mailto:gary@garycmartin.com" target="_blank">gary@garycmartin.com</a>> wrote:<br>
Hi Bill,<br>
<br>
On 24 Sep 2009, at 00:17, Bill Bogstad wrote:<br>
<br>
> On Wed, Sep 23, 2009 at 4:26 PM, Gary C Martin<br>
> <<a href="mailto:gary@garycmartin.com" target="_blank">gary@garycmartin.com</a>> wrote:<br>
><br>
>> Sure, you could just link the ~/default/datastore directory on the VM<br>
>> to the matching location on the stick. I'm not sure how the pretty<br>
>> way<br>
>> to do this would be (likely at this moment in time would be just<br>
>> tweaking the VMs to assume the stick was there). Pop stick in, then<br>
>> run the VM would be the workflow once set-up. From a future stand<br>
>> point, you'd likely want to push upstream for a feature where Sugar<br>
>> checked for valid (and correct version) data-stores on start-up<br>
>> (perhaps with a UI if more than one valid data-store was found), so<br>
>> any external media device, or perhaps even mounted network volume<br>
>> could become the default data-store for that session.<br>
><br>
> Could you clarify what you are suggesting? Most VMs (including<br>
> VirtualBox) typically use large files within the host environment to<br>
> provide the contents of virtual disks to the OS running under<br>
> virtualization. By default VirtualBox uses a format that dynamically<br>
> allocates in the real filesystem as the guest OS actually writes to<br>
> the virtual disk. I don't think this file is going to be directly<br>
> compatible with any file (or filesystem image) that SoaS is storing on<br>
> a USB stick. If you were thinking of something else, please let me<br>
> know.<br>
<br>
Yes, I routinely use the "Shared Folders" feature for VirtualBox on<br>
the Mac :-) Every thing Sugar flavour I work on resides there for easy<br>
access between different VMs. VirtualBox treats this as a device<br>
(after installing guest additions) so after a reboot I run:<br>
<br>
sudo mount -o uid=500 -t vboxsf <name_you_give_share><br>
<name_of_intended_mount_point><br>
<br>
...which should should do the trick.<br>
<br>
Also be aware that you need to tell VirtualBox it's allowed to use<br>
USB, I think it defaults to allow, but you can also filter for named<br>
devices if that makes more sense in a deployment. I would also want to<br>
sanity check the shut down process to make sure we didn't bork users<br>
sticks at the end of a session.<br>
<br>
Ping if you'd like to work this through, should be easy enough for me<br>
to set up a test cycle here if you think this is valuable.<br>
<br>
Regards,<br>
--Gary<br>
<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
<br>
<br>
-- <br>
Dave Bauer<br>
<a href="mailto:dave@solutiongrove.com" target="_blank">dave@solutiongrove.com</a><br>
<a href="http://www.solutiongrove.com" target="_blank">http://www.solutiongrove.com</a><br>
<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dave Bauer<br><a href="mailto:dave@solutiongrove.com">dave@solutiongrove.com</a><br><a href="http://www.solutiongrove.com">http://www.solutiongrove.com</a><br>
<br><br>