| 2015-09-18 13:52:10 |
Carlo Lobrano |
description |
Each call to hw-assign for a given snap overwrites the (possibly) existing udev rule in 70-snappy_hwassign_<snapname>.rules.
The list "write_path" in <snapname>.json.additional is correctly updated, instead.
Expected behavior:
The udev rule "70-snappy_hwassign_<snapname>.rules" contains all the device nodes also present in <snapname>.json.additional's write_path.
Following a copy of the content of both file after a sequence of calls to hw-assign:
(amd64)ubuntu@localhost:/var/lib/apparmor/clicks$ sudo cat minicom.saviq.json.additional
{
"write_path": [
"/dev/ttyUSB*",
"/dev/simlink",
"/dev/simlink2",
"/dev/simlink3"
],
"read_path": [
"/run/udev/data/*"
]
}
(amd64)ubuntu@localhost:/var/lib/apparmor/clicks$ cat /etc/udev/rules.d/70-snappy_hwassign_minicom.saviq.rules
KERNEL=="simlink3", TAG:="snappy-assign", ENV{SNAPPY_APP}:="minicom.saviq"
(amd64)ubuntu@localhost:/var/lib/apparmor/clicks$ |
Each call to hw-assign for a given snap overwrites the (possibly) existing udev rule in 70-snappy_hwassign_<snapname>.rules.
The list "write_path" in <snapname>.json.additional is correctly updated, instead.
Expected behavior:
The udev rule "70-snappy_hwassign_<snapname>.rules" contains all the device nodes also present in <snapname>.json.additional's write_path.
Following a copy of the content of both files after a sequence of calls to hw-assign:
(amd64)ubuntu@localhost:/var/lib/apparmor/clicks$ sudo cat minicom.saviq.json.additional
{
"write_path": [
"/dev/ttyUSB*",
"/dev/simlink",
"/dev/simlink2",
"/dev/simlink3"
],
"read_path": [
"/run/udev/data/*"
]
}
(amd64)ubuntu@localhost:/var/lib/apparmor/clicks$ cat /etc/udev/rules.d/70-snappy_hwassign_minicom.saviq.rules
KERNEL=="simlink3", TAG:="snappy-assign", ENV{SNAPPY_APP}:="minicom.saviq"
(amd64)ubuntu@localhost:/var/lib/apparmor/clicks$ |
|
