udev-cli 0.1.0__tar.gz

udev_cli-0.1.0/PKG-INFO

@@ -0,0 +1,55 @@
+Metadata-Version: 2.4
+Name: udev-cli
+Version: 0.1.0
+Summary: Print, filter, and react to udev events as JSON
+Author: readwithai
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/readwithai/udev-cli
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: System :: Hardware
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Requires-Dist: pyudev>=0.22
+
+# udev-cli
+Print udev events, filter udev events, and run commands on udev events.  udev is a system of events when hardware devices are plugged into a computer on linux.
+
+This is unreviewed AI-generated code. But will become more reviewed if people use it.
+
+## Motivation
+I have a tried to use udev a few times. But I always find it difficult to actually get my events to fire and debug what is going on. I've decied to just listen to events myself and trigger events rather than mess ith rules.
+
+
+## Alternatives and prior work
+`udev-monitor` is a pypi project which is very similar. However, it could not filter by UUID, so I decided to vibe code something up.
+
+`udev` itself has a rule system and 
+
+`udevadm monitor` can output events from udev put does not output JSON. I am also concerned about buffering.
+
+This uses pyudev internally. You could achieve this functionality with a little python script using `pyudev` and do other things - but it would involve a little more debugging to understand what is going on.
+
+ 
+## Installation
+pipx install udev-cli
+
+## Usage
+Print all udev events: `udev-cli`. You can use `jq` to help you work out what you want to match.
+
+block device events only: `udev-cli -s block`
+
+block devices added: `udev-cli -s block -a add`
+
+match specific UUID: `udev-cli -f ID_FS_UUID b9335c96-...`
+
+match any UUID in file: `udev-cli -f ID_FS_UUID @/etc/backup-uuids.txt`
+
+run a command: `udev-cli -s block -a add -f ID_FS_UUID @uuids --run ./backup.sh`
+
+## About
+I am @readwithai. I am making tools for reading and agency with and without AI.
+I also make a lot of small tools related to productivity. If this tool is useful you might like [follow me on github](https://github.com/talwrii) or [X](https://x.com/readwithai).
+

udev_cli-0.1.0/README.md

@@ -0,0 +1,39 @@
+# udev-cli
+Print udev events, filter udev events, and run commands on udev events.  udev is a system of events when hardware devices are plugged into a computer on linux.
+
+This is unreviewed AI-generated code. But will become more reviewed if people use it.
+
+## Motivation
+I have a tried to use udev a few times. But I always find it difficult to actually get my events to fire and debug what is going on. I've decied to just listen to events myself and trigger events rather than mess ith rules.
+
+
+## Alternatives and prior work
+`udev-monitor` is a pypi project which is very similar. However, it could not filter by UUID, so I decided to vibe code something up.
+
+`udev` itself has a rule system and 
+
+`udevadm monitor` can output events from udev put does not output JSON. I am also concerned about buffering.
+
+This uses pyudev internally. You could achieve this functionality with a little python script using `pyudev` and do other things - but it would involve a little more debugging to understand what is going on.
+
+ 
+## Installation
+pipx install udev-cli
+
+## Usage
+Print all udev events: `udev-cli`. You can use `jq` to help you work out what you want to match.
+
+block device events only: `udev-cli -s block`
+
+block devices added: `udev-cli -s block -a add`
+
+match specific UUID: `udev-cli -f ID_FS_UUID b9335c96-...`
+
+match any UUID in file: `udev-cli -f ID_FS_UUID @/etc/backup-uuids.txt`
+
+run a command: `udev-cli -s block -a add -f ID_FS_UUID @uuids --run ./backup.sh`
+
+## About
+I am @readwithai. I am making tools for reading and agency with and without AI.
+I also make a lot of small tools related to productivity. If this tool is useful you might like [follow me on github](https://github.com/talwrii) or [X](https://x.com/readwithai).
+

udev_cli-0.1.0/pyproject.toml

@@ -0,0 +1,30 @@
+[build-system]
+requires = ["setuptools>=68.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "udev-cli"
+version = "0.1.0"
+description = "Print, filter, and react to udev events as JSON"
+readme = "README.md"
+license = "MIT"
+requires-python = ">=3.9"
+authors = [
+    { name = "readwithai" },
+]
+dependencies = [
+    "pyudev>=0.22",
+]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Topic :: System :: Hardware",
+]
+
+[project.scripts]
+udev-cli = "udev_cli.main:main"
+
+[project.urls]
+Homepage = "https://github.com/readwithai/udev-cli"

udev_cli-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

udev_cli-0.1.0/udev_cli/main.py

@@ -0,0 +1,134 @@
+"""udev-cli: Print, filter, and react to udev events."""
+
+from __future__ import annotations
+
+import argparse
+import json
+import subprocess
+import sys
+from typing import Optional
+
+
+def device_to_dict(device, action: Optional[str] = None) -> dict:
+    """Convert a pyudev Device to a JSON-serialisable dict."""
+    d = {
+        "action": action or device.action,
+        "sys_path": device.sys_path,
+        "sys_name": device.sys_name,
+        "device_node": device.device_node,
+        "device_type": device.device_type,
+        "subsystem": device.subsystem,
+        "driver": device.driver,
+        "device_path": device.device_path,
+        "tags": list(device.tags),
+        "properties": dict(device.properties),
+    }
+    return d
+
+
+def load_values_file(path: str) -> list[str]:
+    """Load values from a file, one per line."""
+    values = []
+    with open(path) as f:
+        for line in f:
+            line = line.strip()
+            if not line or line.startswith("#"):
+                continue
+            values.append(line)
+    return values
+
+
+def resolve_filters(raw_filters: list[list[str]]) -> list[tuple[str, list[str]]]:
+    """Resolve -f args into (key, [values]) pairs.
+
+    -f KEY VALUE  ->  (KEY, [VALUE])
+    -f KEY @file  ->  (KEY, [val1, val2, ...])
+
+    All pairs must match (AND). Multiple values = any can match (OR).
+    """
+    resolved = []
+    for parts in raw_filters:
+        if len(parts) != 2:
+            print(f"Error: -f expects KEY VALUE, got: {' '.join(parts)}", file=sys.stderr)
+            sys.exit(1)
+        key, value = parts
+        if value.startswith("@"):
+            path = value[1:]
+            values = load_values_file(path)
+            if not values:
+                print(f"Warning: no values in {path}", file=sys.stderr)
+            resolved.append((key, values))
+        else:
+            resolved.append((key, [value]))
+    return resolved
+
+
+def matches_filters(device, action: Optional[str], filters: list[tuple[str, list[str]]], actions: list[str]) -> bool:
+    """Check if a device event matches filters.
+
+    All filter keys must match (AND).
+    For each key, device value must be in the values list (OR).
+    """
+    act = action or device.action
+    if actions and act not in actions:
+        return False
+
+    for key, values in filters:
+        dev_value = device.get(key)
+        if dev_value is None or dev_value not in values:
+            return False
+
+    return True
+
+
+def cmd_monitor(args):
+    """Monitor udev events and print as JSONL."""
+    import pyudev
+
+    context = pyudev.Context()
+    monitor = pyudev.Monitor.from_netlink(context)
+
+    if args.subsystem:
+        for sub in args.subsystem:
+            monitor.filter_by(sub)
+
+    filters = resolve_filters(args.filter or [])
+    actions = [a.strip() for a in args.action.split(",")] if args.action else []
+
+    for device in iter(monitor.poll, None):
+        action = device.action
+
+        if not matches_filters(device, action, filters, actions):
+            continue
+
+        event = device_to_dict(device, action)
+
+        line = json.dumps(event)
+        print(line, flush=True)
+
+        if args.run:
+            try:
+                subprocess.Popen(
+                    [args.run, line],
+                    stdout=None, stderr=None,
+                )
+            except Exception as e:
+                print(json.dumps({"error": str(e)}), file=sys.stderr, flush=True)
+
+
+def main():
+    parser = argparse.ArgumentParser(
+        description="Print, filter, and react to udev events as JSONL",
+        prog="udev-cli",
+    )
+    parser.add_argument("-s", "--subsystem", action="append", help="Filter by subsystem (e.g. block, usb, input)")
+    parser.add_argument("-a", "--action", help="Filter by action (comma-separated: add,remove,change)")
+    parser.add_argument("-f", "--filter", nargs=2, action="append", metavar=("KEY", "VALUE"), help="Filter by property: KEY VALUE or KEY @filepath")
+    parser.add_argument("--run", help="Run command on match (event JSON passed as first arg)")
+
+    args = parser.parse_args()
+    cmd_monitor(args)
+
+
+if __name__ == "__main__":
+    main()

udev_cli-0.1.0/udev_cli.egg-info/PKG-INFO

@@ -0,0 +1,55 @@
+Metadata-Version: 2.4
+Name: udev-cli
+Version: 0.1.0
+Summary: Print, filter, and react to udev events as JSON
+Author: readwithai
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/readwithai/udev-cli
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: System :: Hardware
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+Requires-Dist: pyudev>=0.22
+
+# udev-cli
+Print udev events, filter udev events, and run commands on udev events.  udev is a system of events when hardware devices are plugged into a computer on linux.
+
+This is unreviewed AI-generated code. But will become more reviewed if people use it.
+
+## Motivation
+I have a tried to use udev a few times. But I always find it difficult to actually get my events to fire and debug what is going on. I've decied to just listen to events myself and trigger events rather than mess ith rules.
+
+
+## Alternatives and prior work
+`udev-monitor` is a pypi project which is very similar. However, it could not filter by UUID, so I decided to vibe code something up.
+
+`udev` itself has a rule system and 
+
+`udevadm monitor` can output events from udev put does not output JSON. I am also concerned about buffering.
+
+This uses pyudev internally. You could achieve this functionality with a little python script using `pyudev` and do other things - but it would involve a little more debugging to understand what is going on.
+
+ 
+## Installation
+pipx install udev-cli
+
+## Usage
+Print all udev events: `udev-cli`. You can use `jq` to help you work out what you want to match.
+
+block device events only: `udev-cli -s block`
+
+block devices added: `udev-cli -s block -a add`
+
+match specific UUID: `udev-cli -f ID_FS_UUID b9335c96-...`
+
+match any UUID in file: `udev-cli -f ID_FS_UUID @/etc/backup-uuids.txt`
+
+run a command: `udev-cli -s block -a add -f ID_FS_UUID @uuids --run ./backup.sh`
+
+## About
+I am @readwithai. I am making tools for reading and agency with and without AI.
+I also make a lot of small tools related to productivity. If this tool is useful you might like [follow me on github](https://github.com/talwrii) or [X](https://x.com/readwithai).
+

udev_cli-0.1.0/udev_cli.egg-info/SOURCES.txt

@@ -0,0 +1,10 @@
+README.md
+pyproject.toml
+udev_cli/__init__.py
+udev_cli/main.py
+udev_cli.egg-info/PKG-INFO
+udev_cli.egg-info/SOURCES.txt
+udev_cli.egg-info/dependency_links.txt
+udev_cli.egg-info/entry_points.txt
+udev_cli.egg-info/requires.txt
+udev_cli.egg-info/top_level.txt

udev_cli-0.1.0/udev_cli.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

udev_cli-0.1.0/udev_cli.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+udev-cli = udev_cli.main:main

udev_cli-0.1.0/udev_cli.egg-info/requires.txt

@@ -0,0 +1 @@
+pyudev>=0.22

udev_cli-0.1.0/udev_cli.egg-info/top_level.txt

@@ -0,0 +1 @@
+udev_cli