From: Petter Reinholdtsen
I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via 70-uaccess.rules). Perhaps a lintian check should be -created to detect this?
+The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +70-uaccess.rules). Perhaps a lintian check should be created +to detect this?
I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/archive/2016/10/10.rss b/blog/archive/2016/10/10.rss index 4f93c55b9b..68c3529bda 100644 --- a/blog/archive/2016/10/10.rss +++ b/blog/archive/2016/10/10.rss @@ -92,10 +92,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694& SYMLINK+="rcx-%k", TAG+="uaccess" </pre></p> -<p>I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be -created to detect this?</p> +<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created +to detect this?</p> <p>I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/archive/2016/10/index.html b/blog/archive/2016/10/index.html index 3c0652325b..4a616657a5 100644 --- a/blog/archive/2016/10/index.html +++ b/blog/archive/2016/10/index.html @@ -110,10 +110,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001" SYMLINK+="rcx-%k", TAG+="uaccess"
-I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via 70-uaccess.rules). Perhaps a lintian check should be -created to detect this?
+The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +70-uaccess.rules). Perhaps a lintian check should be created +to detect this?
I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/index.html b/blog/index.html index 7b6d01cc98..04d72d89e7 100644 --- a/blog/index.html +++ b/blog/index.html @@ -103,10 +103,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001" SYMLINK+="rcx-%k", TAG+="uaccess"
-I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via 70-uaccess.rules). Perhaps a lintian check should be -created to detect this?
+The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +70-uaccess.rules). Perhaps a lintian check should be created +to detect this?
I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/index.rss b/blog/index.rss index b2e2a84081..74a36c8e22 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -92,10 +92,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694& SYMLINK+="rcx-%k", TAG+="uaccess" </pre></p> -<p>I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be -created to detect this?</p> +<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created +to detect this?</p> <p>I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss index 04364a547f..c2a7b99d72 100644 --- a/blog/tags/debian/debian.rss +++ b/blog/tags/debian/debian.rss @@ -92,10 +92,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694& SYMLINK+="rcx-%k", TAG+="uaccess" </pre></p> -<p>I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be -created to detect this?</p> +<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created +to detect this?</p> <p>I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index a0656f20cf..92613b0336 100644 --- a/blog/tags/debian/index.html +++ b/blog/tags/debian/index.html @@ -109,10 +109,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001" SYMLINK+="rcx-%k", TAG+="uaccess"
-I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via 70-uaccess.rules). Perhaps a lintian check should be -created to detect this?
+The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +70-uaccess.rules). Perhaps a lintian check should be created +to detect this?
I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index 2bc0c4726e..3271560a26 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -92,10 +92,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694& SYMLINK+="rcx-%k", TAG+="uaccess" </pre></p> -<p>I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be -created to detect this?</p> +<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created +to detect this?</p> <p>I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index 8f21d8f091..b68fc403a5 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -109,10 +109,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001" SYMLINK+="rcx-%k", TAG+="uaccess"
-I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via 70-uaccess.rules). Perhaps a lintian check should be -created to detect this?
+The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +70-uaccess.rules). Perhaps a lintian check should be created +to detect this?
I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/tags/isenkram/index.html b/blog/tags/isenkram/index.html index ecf39d963a..1bef8617f9 100644 --- a/blog/tags/isenkram/index.html +++ b/blog/tags/isenkram/index.html @@ -109,10 +109,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001" SYMLINK+="rcx-%k", TAG+="uaccess"
-I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via 70-uaccess.rules). Perhaps a lintian check should be -created to detect this?
+The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +70-uaccess.rules). Perhaps a lintian check should be created +to detect this?
I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation diff --git a/blog/tags/isenkram/isenkram.rss b/blog/tags/isenkram/isenkram.rss index 724609f31c..8d06192736 100644 --- a/blog/tags/isenkram/isenkram.rss +++ b/blog/tags/isenkram/isenkram.rss @@ -92,10 +92,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694& SYMLINK+="rcx-%k", TAG+="uaccess" </pre></p> -<p>I suspect all packages using plugdev in their /lib/udev/rules.d/ -files should be changed to use this tag (either directly or indirectly -via <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be -created to detect this?</p> +<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all +packages using plugdev in their /lib/udev/rules.d/ files should be +changed to use this tag (either directly or indirectly via +<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created +to detect this?</p> <p>I've been unable to find good documentation on the uaccess feature. It is unclear to me if the uaccess tag is an internal implementation