Opened 12 years ago

Last modified 7 years ago

#995 assigned defect

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

Reported by: jpritikin Owned by: alsroot
Priority: Normal Milestone: Unspecified
Component: Sugar on a Stick (SoaS) Version: 0.84.x
Severity: Unspecified Keywords:
Cc: Distribution/OS: Fedora
Bug Status: Unconfirmed

Description

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.

Change History (10)

comment:1 Changed 11 years ago by tomeu

  • Milestone changed from Unspecified by Release Team to 0.86

comment:2 in reply to: ↑ description ; follow-up: Changed 11 years ago by 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.

comment:3 in reply to: ↑ 2 Changed 11 years ago by alsroot

  • Milestone changed from 0.86 to Unspecified by Release Team

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

comment:4 Changed 11 years ago by jpritikin

Sounds like a reasonable plan. Thanks.

comment:5 Changed 11 years ago by martin.langhoff

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

comment:6 Changed 11 years ago by sascha_silbe

  • Component changed from journal to SoaS
  • Distribution/OS changed from SoaS to Unspecified

Bulk change distribution=SoaS -> component=SoaS

comment:7 Changed 11 years ago by sdz

  • Component changed from SoaS to journal
  • Owner changed from tomeu to alsroot
  • Status changed from new to assigned

Assigning back to Journal.

comment:8 Changed 8 years ago by manuq

  • Distribution/OS changed from Unspecified to Fedora
  • Summary changed from can't transfer files on USB to/from journal to SoaS: can't transfer files on USB to/from journal

comment:9 Changed 8 years ago by dnarvaez

  • Component changed from journal to sugar

comment:10 Changed 7 years ago by dnarvaez

  • Component changed from Sugar to Sugar on a Stick (SoaS)

As far as I can tell the sugar side has been addressed, though Soas would need to create multiple partitions or something for this to work.

Note: See TracTickets for help on using tickets.