Maintenance, trust and software security
This page explains how Linxira is maintained, where software comes from, what AUR really costs you, and why a distro without a foundation behind it can still be worth trusting.
Maintenance: directly on Arch
- Security fixes come with Arch: the kernel, glibc, browsers and friends are Arch's own builds. Nothing is delayed or re-screened; once Arch's security team publishes an advisory, the fix arrives with your next
pacman -Syu. - No custom performance kernel: the kernel is Arch's
linux/linux-lts. No third-party patchset means no divergence that could lag behind upstream security work. - No delayed rolling: unlike derivatives that freeze packages for two weeks to several months, Linxira tracks Arch as it rolls.
- First-party components ship separately: config-hub, update, crash-watch and others carry their own
VERSION, CI build and signed repository, decoupled from the upstream cadence.
Check your machine for known issues with arch-audit; upstream advisories live at security.archlinux.org.
Software sources at a glance
| Source | Signed | Maintained by | Risk |
|---|---|---|---|
| [linxira] first-party repo | Yes | This project's CI | Low, build is inspectable |
| Arch official core / extra / multilib | Yes | Arch packagers | Low, officially maintained |
| AUR | No (built locally) | Any registered user | High — review it yourself |
AUR: disabled by default, read before you build
Only [linxira] and the official Arch repositories are enabled out of the box; no AUR helper is preinstalled. AUR is not a repository — it is a pile of user-submitted build scripts (PKGBUILDs). The package is compiled on your machine, so nobody vouches for its contents.
If you do use an AUR package:
- Read the whole PKGBUILD and any
.installfile. Watch wheresource=points, whethersha256sums=is complete, and what the install script touches. - Check the
# Maintainer:line and the commit history; be careful with packages that were abandoned and recently taken over. - Build as an ordinary user (
makepkgrefuses root) and only elevate for the install step. - A broken AUR package is the responsibility of its submitter. Neither Arch nor this project supports it, and we will not bend the system for it.
Trust model: no foundation, but verifiable
Linxira is maintained by an individual / small team, without a foundation or company behind it. Skepticism is reasonable, so here is what you can verify yourself:
| What we can do | What we cannot |
|---|---|
| Publish all sources, build scripts and CI config | Provide a 24/7 security response team |
Build every package in CI and sign it with the release key shipped in linxira-keyring | Offer a legal entity or commercial SLA |
Record repository ownership and lifecycle in governance/repositories.yaml | Match upstream's audit headcount |
| Keep releases traceable (tags, Releases, signed packages) | Take responsibility for third-party AUR packages |
No lock-in: this is standard Arch — pacman, systemd, the usual /etc layout, the official repositories. You can disable the [linxira] repository and keep only Arch's mirrors at any time; the system still works. That exit path is intentional.
No telemetry: nothing is collected. Only when you explicitly run linxira-config logs collect/upload does a diagnostic bundle leave the machine, through the channel you chose.
How this differs from other Arch derivatives
| Dimension | Linxira | Performance-tuned derivatives | Delayed-rolling derivatives |
|---|---|---|---|
| Kernel | Arch stock | Own patchset, self-built | Mostly stock |
| Package lag | Same as Arch | Same as Arch | Frozen 2 weeks to months |
| First-party layer | Integration and management tools (catalog, config-hub, update) | Schedulers, kernel flags, tuning | Installer, themes, separate repos |
The trade-off: no kernel-level tuning, in exchange for zero lag against Arch security fixes and the ability to debug problems against upstream documentation and forums.
Filesystem compatibility
| Filesystem | Linux support | Notes |
|---|---|---|
| NTFS | Read/write; ntfs3 (5.15+) coexists with the new NTFS driver merged in Linux 7.1 | Best choice for a shared data disk; make sure Windows is fully shut down (Fast Startup off) before mounting |
| exFAT | In-kernel driver, read/write | USB sticks and external drives, no permission headaches across systems |
| FAT32 | In-kernel driver, read/write | 4 GB per-file limit; fine for the EFI partition and small drives |
| ReFS | Not supported | Windows-proprietary (Dev Drive, Storage Spaces); there is no usable Linux driver, so it cannot be mounted |
| BitLocker | Limited | cryptsetup can unlock with a recovery key depending on the encryption mode; do not share an encrypted partition between both systems long term |
The safe pattern for shared storage: create a dedicated NTFS partition for both systems and never mount Windows' own system volume (C:) from Linux — especially not while Windows is hibernated.