SoaS: can't transfer files on USB to/from journal

[jpritikin]

First, some background: Due to poverty, we have 100+ students and 36 XO laptops. Our idea is to buy 2G USB thumb drives for the students so they can develop their portfolio. This isn't ideal, but that's the best we can do given the financial constraints. Now, some of the students have a computer at home. (Not all of our students suffer from poverty.) Our idea is to use the USB key in two ways: as storage and as SOAS.

The problem is the journal when we boot SOAS. The journal correctly shows "journal" storage and USB storage separately. However, when I click on USB storage, I get a progress bar that seems to wait forever. At this point, there is nothing else on the SOAS key besides SOAS so I wouldn't expect it to take a long time to scan the top level directory (or wherever) and display the files as being on the USB key.

On the other hand, when we insert the SOAS key into an XO laptop (build 802), it shows all the files. This is not ideal because all the syslinux and LiveOS files are there, but it is tolerable. User files are visible.

In brief, it should be possible to copy files from within SOAS to the top-level directory (or somewhere) of the USB key so they are visible to an XO laptop.

[alsroot]

Replying to jpritikin:

The problem is the journal when we boot SOAS. The journal correctly shows "journal" storage and USB storage separately. However, when I click on USB storage, I get a progress bar that seems to wait forever. At this point, there is nothing else on the SOAS key besides SOAS so I wouldn't expect it to take a long time to scan the top level directory (or wherever) and display the files as being on the USB key.

After fixing #1412, sugar will process usb drives like XO-802 does.

On the other hand, when we insert the SOAS key into an XO laptop (build 802), it shows all the files. This is not ideal because all the syslinux and LiveOS files are there, but it is tolerable. User files are visible.

In brief, it should be possible to copy files from within SOAS to the top-level directory (or somewhere) of the USB key so they are visible to an XO laptop.

Maybe create to partitions on usb drives, one for soas and another for users files. So, user open second partition and only his files.

[alsroot]

Replying to alsroot:

Replying to jpritikin:

The problem is the journal when we boot SOAS. The journal correctly shows "journal" storage and USB storage separately. However, when I click on USB storage, I get a progress bar that seems to wait forever. At this point, there is nothing else on the SOAS key besides SOAS so I wouldn't expect it to take a long time to scan the top level directory (or wherever) and display the files as being on the USB key.

After fixing #1412, sugar will process usb drives like XO-802 does.

On the other hand, when we insert the SOAS key into an XO laptop (build 802), it shows all the files. This is not ideal because all the syslinux and LiveOS files are there, but it is tolerable. User files are visible.

In brief, it should be possible to copy files from within SOAS to the top-level directory (or somewhere) of the USB key so they are visible to an XO laptop.

Maybe create to partitions on usb drives, one for soas and another for users files. So, user open second partition and only his files.

And in addition, we can not show soas drive, see #626

[jpritikin]

Sounds like a reasonable plan. Thanks.

[martin.langhoff]

The desired workflow is also affected by this problem:  http://dev.laptop.org/ticket/9657

[sascha_silbe]

Bulk change distribution=SoaS -> component=SoaS

[sdz]

Assigning back to Journal.