misc/firestuff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

udev is your friend

Browse Source
This commit is contained in:
Ian Gulliver
2019-04-21 17:33:23 +00:00
parent f17582013b
commit 7858ef1fcd
4 changed files with 35 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
2006-03-02-udev-is-your-friend.html Normal file
View File

@@ -0,0 +1,17 @@
<!--# set var="title" value="udev is your friend" -->
<!--# set var="date" value="March 2, 2006" -->
<!--# include file="include/top.html" -->
<p>Well, not completely. Most of us have had a udev install eat /dev and make the machine unbootable at least once. However, when it works, it’s really neat.</p>
<p>We have cash register machines at CORESense with two touchscreens attached; one facing the cashier and one facing the customer (they work as kiosks when they’re not in use for checkout). The problem is that the touchscreen inputs are USB event interfaces which are sequentially numbered, and the startup order isn’t always the same. This means that you can’t give X a device name, because it changes every bootup. Enter udev.</p>
<p>I put this in /etc/udev/rules.d/coresense.rules:</p>
<pre><code>KERNEL==”event[0-9]*”, SYSFS{name}==”Elo *”, NAME=”coresense/elo-$sysfs{uniq}”
</code></pre>
<p>This matches event interface devices with the given name pattern, and creates device nodes in /dev/coresense with the device serial number in the device name. Poof - repeatable names.</p>
<!--# include file="include/bottom.html" -->

1
index.html
View File

@@ -40,6 +40,7 @@
<li>2009-Sep-11: <a href="2009-09-11-confusing-bind-with-cnames.html">Confusing BIND with CNAMEs</a></li>
<li>2009-Feb-19: <a href="2019-02-19-the-odd-case-of-my-mugging.html">The odd case of my mugging</a></li>
<li>2009-Feb-03: <a href="2009-02-03-5-packet-tcp-connection.html">5-packet TCP connection?</a></li>
<li>2006-Mar-02: <a href="2006-03-02-udev-is-your-friend.html">udev is your friend</a></li>
<li>2006-Mar-02: <a href="2006-03-02-why-is-my-directory-empty-and-large.html">Why is my directory empty and large?</a></li>
<li>2006-Feb-26: <a href="2006-02-26-why-isnt-mod_auth_pam-working-with-nis.html">Why isn’t mod_auth_pam working with NIS?</a></li>
<li>2006-Feb-26: <a href="2006-02-26-sctp-part-1.html">SCTP Part #1</a></li>

16
markdown/2006-03-02-udev-is-your-friend.md Normal file
View File

@@ -0,0 +1,16 @@
<!--# set var="title" value="udev is your friend" -->
<!--# set var="date" value="March 2, 2006" -->
<!--# include file="include/top.html" -->
Well, not completely. Most of us have had a udev install eat /dev and make the machine unbootable at least once. However, when it works, it’s really neat.
We have cash register machines at CORESense with two touchscreens attached; one facing the cashier and one facing the customer (they work as kiosks when they’re not in use for checkout). The problem is that the touchscreen inputs are USB event interfaces which are sequentially numbered, and the startup order isn’t always the same. This means that you can’t give X a device name, because it changes every bootup. Enter udev.
I put this in /etc/udev/rules.d/coresense.rules:
KERNEL==”event[0-9]*”, SYSFS{name}==”Elo *”, NAME=”coresense/elo-$sysfs{uniq}”
This matches event interface devices with the given name pattern, and creates device nodes in /dev/coresense with the device serial number in the device name. Poof - repeatable names.
<!--# include file="include/bottom.html" -->

1
markdown/index.md
View File

@@ -39,6 +39,7 @@
1. 2009-Sep-11: [Confusing BIND with CNAMEs](2009-09-11-confusing-bind-with-cnames.html)
1. 2009-Feb-19: [The odd case of my mugging](2019-02-19-the-odd-case-of-my-mugging.html)
1. 2009-Feb-03: [5-packet TCP connection?](2009-02-03-5-packet-tcp-connection.html)
1. 2006-Mar-02: [udev is your friend](2006-03-02-udev-is-your-friend.html)
1. 2006-Mar-02: [Why is my directory empty and large?](2006-03-02-why-is-my-directory-empty-and-large.html)
1. 2006-Feb-26: [Why isn’t mod\_auth\_pam working with NIS?](2006-02-26-why-isnt-mod_auth_pam-working-with-nis.html)
1. 2006-Feb-26: [SCTP Part #1](2006-02-26-sctp-part-1.html)