Generated.

diff --git a/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html b/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
index 847666e1cbf67f6bdb53beeb4ef26acb228ec164..740d89b5690062d9079706436987e6da1349f516 100644 (file)
--- a/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
+++ b/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
@@ -103,10 +103,11 @@ SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001"
     SYMLINK+="rcx-%k", TAG+="uaccess"
 </pre></p>
 
     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
 
 <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/10.rss b/blog/archive/2016/10/10.rss
index 4f93c55b9b7e7f3feab713927975ce9cb08f3718..68c3529bda45a5a9abc40b79f3564458b5815b8c 100644 (file)
--- 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>
 
     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
 
 <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 3c0652325bd982419a29c6062dfff951ab9630c4..4a616657a50e3e5754bf870ba241ce5657c0e22b 100644 (file)
--- 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"
 </pre></p>
 
     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
 
 <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/index.html b/blog/index.html
index 7b6d01cc98d503ad5493c4e46a6da132d7e2ff8e..04d72d89e7daa3e64b481fe34f93a2f6666f86a8 100644 (file)
--- 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"
 </pre></p>
 
     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
 
 <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/index.rss b/blog/index.rss
index b2e2a84081f7167ca46df76554cf07844b3716ef..74a36c8e2291421a7cccce843a19a9d76ca0fb22 100644 (file)
--- 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>
 
     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
 
 <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 04364a547f18232fb20481cb24d57abd1014a10f..c2a7b99d7293f3eecae13922ad75ae58e701a90c 100644 (file)
--- 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>
 
     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
 
 <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 a0656f20cf1238617174a4bbd735d9d6b4f86880..92613b03363c968dea2bff5fa5b2f82fe74e6b69 100644 (file)
--- 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"
 </pre></p>
 
     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
 
 <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/english.rss b/blog/tags/english/english.rss
index 2bc0c4726ebbee428c4ea53deec0ef82e0f0f9c1..3271560a2692ee28590b5bc0e8c16b0b86f74dd4 100644 (file)
--- 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>
 
     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
 
 <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 8f21d8f091e7e2e28613b9c577115b06e4cb0bc5..b68fc403a5b4ae1140f7d2c4583205f936052d59 100644 (file)
--- 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"
 </pre></p>
 
     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
 
 <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/isenkram/index.html b/blog/tags/isenkram/index.html
index ecf39d963ac6702a31c14f93974e472c7628f291..1bef8617f9b988646de50d637e6fae62f80b8c63 100644 (file)
--- 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"
 </pre></p>
 
     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
 
 <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/isenkram/isenkram.rss b/blog/tags/isenkram/isenkram.rss
index 724609f31c194104155c517cbe78899cf149233b..8d0619273632b10eb9faf31ab724d5d6b94b18e9 100644 (file)
--- 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>
 
     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
 
 <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