Skip to content
Librux Runtime Kernel for Robotics development
Librux Runtime Kernel for Robotics development

    Runtime Layout

    This page is a path lookup table for installed Librux runtimes. It does not describe private runtime implementation structure.

    The default product prefix is /opt/librux. Custom prefixes use the same shape under the selected installation directory.

    Installed Tree

    Path Meaning
    <prefix>/env.sh shell environment helper for the installed runtime
    <prefix>/runtime/bin user-facing CLI entry points
    <prefix>/runtime/lib native libraries required by the installed SDK/runtime
    <prefix>/runtime/config.yaml base runtime configuration
    <prefix>/runtime/spec installed fallback copy of public specs
    <prefix>/runtime/frontend packaged Web Console assets
    <prefix>/sdk/python installed Python SDK wheel payloads
    <prefix>/sdk/cpp installed C++ SDK payload
    <prefix>/tutorials installed tutorial source and runnable fixtures
    <prefix>/benchmarks installed benchmark runners
    <prefix>/licenses runtime EULA, open-source notices, and install notices
    <prefix>/systemd service unit source files linked into the host systemd directory
    <prefix>/var Librux-owned state, package registry, logs, and service home data
    <prefix>/bin/librux-uninstall uninstaller for service links and the selected prefix

    Installed product bundles expose these convenience paths.

    Path Target
    <prefix>/bin <prefix>/runtime/bin
    <prefix>/spec <prefix>/runtime/spec
    <prefix>/config.yaml <prefix>/runtime/config.yaml

    Common Commands

    Command Use
    lbx or librux top-level CLI dispatcher
    librux-config inspect or modify runtime configuration
    librux-doctor run host and runtime checks
    librux-launch launch managed subsystem packages
    librux-subsystem inspect subsystem status, sessions, and lifecycle state
    librux-package inspect and validate packages
    librux-timesync inspect or run time-sync helpers

    Service Names

    Product installs can register these system services.

    Service Purpose
    librux-control.service host control backend and Web Console
    librux-resourced.service resource broker and launch-time resource authority
    librux-timesyncd.service managed time-sync observation and helper ownership

    Runtime sockets normally live under /run/librux. Product installs prepare that directory for the librux group so non-root SDK processes can use the runtime boundary without opening arbitrary device or network paths.