From 066c1f70130513cc00fc90f501a458f64e6316b1 Mon Sep 17 00:00:00 2001 From: Maxime Date: Tue, 26 May 2026 10:37:18 -0700 Subject: [PATCH 1/2] docs(linux): add RPM download URLs and clean up Custom/Uninstall sections The .rpm package install procedure is already documented, but the section was missing the per-architecture download URLs (deb64/debarm64 list them; rpm64/rpmarm64 did not). Also fold .rpm into the Custom Installation framing and add an RPM-based Systems entry under uninstall. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../endpoint-agent/linux/installation.md | 23 +++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/docs/2-sensors-deployment/endpoint-agent/linux/installation.md b/docs/2-sensors-deployment/endpoint-agent/linux/installation.md index 10b24ee65..183a07c3d 100644 --- a/docs/2-sensors-deployment/endpoint-agent/linux/installation.md +++ b/docs/2-sensors-deployment/endpoint-agent/linux/installation.md @@ -131,9 +131,14 @@ sudo dnf remove limacharlie Uninstall stops the service and removes the sensor binary, identity files, and the package staging directory. +RPM packages are offered for the architectures the Linux sensor supports, like: + +- **x64**: +- **arm64**: + ### Custom Installation -For non-Debian systems, download the installer using the following command: +For systems where neither the `.deb` nor the `.rpm` package fits (e.g. distributions without `dpkg` or `rpm`, or installs that need a non-standard layout), download the installer directly using the following command: ```python wget https://downloads.limacharlie.io/sensor/linux/64 -O /tmp/lc_sensor @@ -170,7 +175,7 @@ By default, when running on a kernel where eBPF is unavailable, the Linux sensor For additional agent uninstall options, see [Endpoint Agent Uninstallation](../uninstallation.md) -Linux agent uninstallation depends on how the sensor was installed. For example, if installed via a Debian package (`dpkg` file), you should uninstall via the same mechanism. If you installed via the SystemV installation method, please utilize the bottom of [this script](https://github.com/refractionPOINT/lce_doc/blob/master/docs/lc_linux_installer.sh#L97). +Linux agent uninstallation depends on how the sensor was installed. For example, if installed via a Debian package (`dpkg` file) or an RPM package (`rpm` / `dnf` / `yum`), you should uninstall via the same package manager. If you installed via the SystemV installation method, please utilize the bottom of [this script](https://github.com/refractionPOINT/lce_doc/blob/master/docs/lc_linux_installer.sh#L97). ### Sensor Command @@ -189,3 +194,17 @@ If the sensor was originally installed with the .deb file, this option is the cl ```bash apt remove limacharlie ``` + +### RPM-based Systems + +If the sensor was originally installed with the .rpm file, use the matching package manager: + +```bash +sudo dnf remove limacharlie +``` + +or + +```bash +sudo rpm -e limacharlie +``` From 33b919469b71eb3c0fa802aae596dc24c046c465 Mon Sep 17 00:00:00 2001 From: Maxime Date: Tue, 26 May 2026 10:41:15 -0700 Subject: [PATCH 2/2] docs(story-tags): fix broken cross-page link to lc:asset:* page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The intro paragraph linked to a sibling asset-tags.md, but the page lives under 2-sensors-deployment/. Line 186 of the same file already uses the correct path; this aligns the first reference. Driveby — link-check fails on every PR until this is fixed. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/8-reference/story-tags.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/8-reference/story-tags.md b/docs/8-reference/story-tags.md index 194f16c16..92901a293 100644 --- a/docs/8-reference/story-tags.md +++ b/docs/8-reference/story-tags.md @@ -40,7 +40,7 @@ Every segment that isn't a fixed keyword has a strict regex: | `TARGET_NAME` | `^[a-z0-9][a-z0-9_.-]{0,127}$` | Same as `STORY_NAME` plus `.` (covers Hive record keys with dots). | | `LABEL_SLUG` | `^[a-z0-9][a-z0-9_-]{0,63}$` | Same as `STORY_NAME`. Rendered with `-` and `_` turned into spaces. | -Tags that violate any gate are **silently dropped** by the assembler — they never produce phantom nodes or edges. This matches the [`lc:asset:*`](asset-tags.md) convention: malformed metadata must never show up in a dashboard. +Tags that violate any gate are **silently dropped** by the assembler — they never produce phantom nodes or edges. This matches the [`lc:asset:*`](../2-sensors-deployment/asset-tags.md) convention: malformed metadata must never show up in a dashboard. ### Canonical type slugs