| |
|---|
| | |
|---|
| | |
|---|
| | :Author: Tim Daneliuk (tundra@tundraware.com) |
|---|
| | |
|---|
| | :Version: ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.125 2013/11/01 13:35:01 tundra Exp $`` |
|---|
| | :Version: ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.126 2013/11/01 13:39:13 tundra Exp $`` |
|---|
| | |
|---|
| | |
|---|
| | Précis |
|---|
| | ====== |
|---|
| |
|---|
| | Key-value pairs either *match* or *assign*. Match key-value pairs |
|---|
| | check to see if a particular thing "matches" what we're looking for. |
|---|
| | Think of them as ``if`` statements in a programming language. |
|---|
| | |
|---|
| | Assignment key-value statements take some sort of action * usually on |
|---|
| | Assignment key-value statements take some sort of action *usually on |
|---|
| | the thing that was previously matched*. But, you're not restricted to |
|---|
| | this. It's entirely possible to write a rule that operates on |
|---|
| | something completely unrelated to the matched condition. For |
|---|
| | instance, you could write a rule that says, *reboot the computer every |
|---|
| |
|---|
| | |
tundra
authored
on 1 Nov 2013