[RFC] Improving hardware access for snaps

Jamie Strandboge jamie at canonical.com
Fri Feb 27 23:11:45 UTC 2015

On 02/27/2015 05:09 PM, Jamie Strandboge wrote:
> On 01/30/2015 04:18 PM, Jamie Strandboge wrote:
>> = Introduction =
>> Right now it is too difficult for snaps to access specific hardware, we've known
>> that and it is time to improve the situation.
>> First we want to improve things for people immediately but without sacrificing
>> on any of our goals[1]. We'll do this by adjusting snappy to give the snappy
>> core user (ie, the one running the 'snappy' command) the ability to add specific
>> device access to specific snaps. In essence you install a snap, you run a
>> command to give the snap access to a particular device, and you’re done. This
>> simple feature should unblock developers and snappy users immediately. Once this
>> is done, we can refine the experience to make it even snappier.
> As of the latest image (tested on kvm/amd64 ubuntu-core 314) this is implemented
> with the 'snappy-go' command (for those that don't know, 'snappy-go' is the Go
> rewrite of the python 'snappy' command).

I should have been more clear. This is not on the latest promoted image, but
rather the latest proposed image.

Jamie Strandboge                 http://www.ubuntu.com/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20150227/f61d5f85/attachment.pgp>

More information about the snappy-devel mailing list