[RFC] Improving hardware access for snaps

[Jamie Strandboge]

On 02/04/2015 12:54 PM, Jamie Strandboge wrote:
> On 02/02/2015 04:34 AM, Martin Pitt wrote:
>> Hey all,
>>
>> Jamie Strandboge [2015-01-30 16:18 -0600]:
>>> $ snappy add-hw foo.bar /dev/ttyS0
>>> 'foo.bar' is now allowed to access /dev/ttyS0
>>
>> Would it be possible and prudent to allow hardware access not to a
>> particular program, but to an entire app? I think this would be better
>> in several ways:
>>

...
> I agree for the default case. I'm thinking that there may still be some utility
> for an admin to be able to specify the service if they prefer, but I don't feel
> passionately about this.

For now I'm going to defer per-service hardware access and pursue only per-app
hardware access as suggested by Martin. I'm not yet convinced of per-service's
general utility and it complicates the UX a bit. We can always add this later
easily enough if we think it is useful.

-- 
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/20150204/9c562cce/attachment.pgp>