Ticket #6430 (new defect)

Opened 6 years ago

Last modified 6 years ago

Autoinstallation of bundles.

Reported by: cscott Owned by: mstone
Priority: normal Milestone:
Component: distro Version:
Keywords: update.1.1? Cc: cscott, marco, tomeu, Eben, walter
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Bundles found with a magic name on a USB key should be automatically unpacked into /home.

This is to support the near-term use case of distributing large library content in a school deployment with limited network connectivity/bandwidth. Although in some cases it may be possible to have the kids individually click through the journal to install an .xol, if deployment team size/time is limited, a more efficient mechanism may be needed.

The size of the library bundle may prohibit installing via the journal (since that will result in a copy in the journal and another unpacked on disk).

Activities may be autoinstalled as static content in a library bundle (which may result in three copies of the activity ultimately ending up on the filesystem: one in the library, one in the journal, and one unpacked in /home) or directly (which raises some security issues, which may be partially addressed by activity isolation).

Target for this bug is update.1.1; we're assuming that we can't get a "better" solution in place in that timeframe.

Change History

Changed 6 years ago by tomeu

  • cc Eben, walter added

Is this a duplicate of #6254?

Please include Eben in all discussions regarding user experience.

Would be good to include also someone that knows the reality of the deployments, in order to not implement solutions that won't be used or that are not optimal. Walter, can you do something in this regard?

Changed 6 years ago by walter

I'm in Peru this week to find out the answer to questions like these... stay tuned.

Changed 6 years ago by mstone

Scott and I realized today that we might want to be able to perform customizations like this on un-activated machines or on activated-but-not-individualized machines. One fairly elegant mechanism that gracefully handles both of these cases (as well as the 'activated-and-individualized' case) is to write and sign an initramfs that can be booted from USB and that installs bundles and activation leases.

Changed 6 years ago by gregorio

  • milestone deleted

Milestone Never Assigned deleted

Note: See TracTickets for help on using tickets.