[RFC] Improving hardware access for snaps
Sergio Schvezov
sergio.schvezov at canonical.com
Sat Jan 31 21:37:17 UTC 2015
On sábado 31 de enero de 2015 10h'52:01 ART, Jamie Strandboge wrote:
> On 01/30/2015 04:42 PM, Sergio Schvezov wrote:
>> On viernes 30 de enero de 2015 19h'31:44 ART, Jamie Strandboge wrote:
> ...
>
> It's funny because I initially had '_' because it works better
> with the APP_ID
> concept and therefore the security policy. I picked '.' for
> consistency with the
> cli binaries, but forgot that those will use '/' in the future, so I
think I
> picked the worst one.
>
> Choices:
> 1. foo.bar
> $ snappy add-hw foo.bar /dev/ttyS0
>
>
> 2. foo_bar
> $ snappy add-hw foo_bar /dev/ttyS0
>
>
> 3. foo/bar
> $ snappy add-hw foo/bar /dev/ttyS0
>
>
> I think I slightly prefer '3' visually, but would be happy with '2' for
the
> reasons stated above. I don't like '1' because it is inconsistent with
the
> future experience and is the most confusing.
I've had that feeling for most of today, but just now took a look at my
email; 3 is the best option in my opinion too.
More information about the snappy-devel
mailing list