Přeskočit na obsah
DOKUMENTACE

Frequently asked questions

Tato stránka zatím není přeložená, zobrazuje se anglická verze.

No. UFLinux pins an Alpine stable release, builds a set of custom packages on top of it, and assembles them into images. Alpine’s official main and community repositories stay enabled, so ordinary Alpine packages work as usual.

Pre-release. The baseline is version 0.1.0 on Alpine 3.24. Only the x86_64 ISO has been boot-tested; device images are a preview. Read Downloads and verification before relying on it.

The installed root must be XFS with a separate /boot. It is a deliberate single choice: one filesystem means one initramfs configuration, one set of resize and recovery behaviours, and one thing the project has actually tested. The installer never partitions or formats in “prepared” mode, so the filesystem is fixed rather than negotiated. Installation covers the layout.

Networking is ConnMan with iwd. It is small, it starts fast, and it covers personal and enterprise Wi-Fi plus Ethernet, DHCP, IPv4/IPv6, DNS and proxies. WireGuard VPNs are supported through ConnMan’s VPN daemon and managed from Settings. The remaining gaps are hotspot, tethering and modem support. Do not enable networking, dhcpcd or another resolver alongside it.

ConnMan’s built-in SNTP client is the only time synchronizer — no ntpd, chronyd or openntpd. It slews small offsets and steps large ones through adjtimex(), and Settings reports the kernel’s actual synchronization state rather than whether a lookup succeeded.

No. It is OpenRC, as Alpine is. Boot services run in parallel where dependencies allow; set rc_parallel="NO" in /etc/rc.conf.d/uflinux.conf when diagnosing a boot problem. elogind provides session actions and backlight control.

Not supported. UEFI images boot with Secure Boot disabled, and no UEFI signature is enrolled. APK and modloop signatures are separate mechanisms and are unaffected.

An installed system is developed and accepted at 512 MiB with one display and no swap. A live image needs at least 4 GiB, because it unpacks the desktop and the full icon theme into a tmpfs root. See Validation record for measured figures.

Neither. The session is labwc, the uflinux-desktop taskbar shell, and UFLinux’s own GTK4 applications. Nothing pulls in a desktop environment. Settings deliberately avoids libadwaita.

Yes — put a file in the right place and it replaces the packaged default rather than extending it. Personal compositor config goes in ~/.config/labwc/, UFLinux preferences in ~/.config/uflinux/, and pinned taskbar favourites in ~/.config/uflinux/taskbar.json. Package upgrades preserve all three.

Administration goes through a named user with doas or sudo, and the root account stays locked. On the live image, live has passwordless local doas, and the image also provides a user / user account with password-authenticated sudo and doas. On an installed system, the user you create has password-authenticated doas. Some Settings operations go through a polkit-authenticated helper instead, using your own password.

Yes. BlueZ ships in the desktop meta, and Settings and the quick-settings flyout have a Bluetooth tab that appears when an adapter is present: adapter power, scanning, pairing, trusting and connecting. Pairing uses BlueZ’s agent-less flow, so devices that need an exchange of I/O capabilities can still fail to pair. Bluetooth is verified only at fixture level, not on physical hardware.

WireGuard, through ConnMan’s VPN daemon (connman-vpnd, from the separate connman-vpn package). Import a client configuration in Settings → Network → VPN to create a tunnel, then connect, disconnect or remove it. Private keys stay in the daemon and are never echoed back.

Use the issue tracker of the documentation repo for anything wrong or missing on these pages, and UFlinux-project/uflinux3 for the distribution itself. See Contributing.

Derived from README.md inUFlinux-project/uflinux3(b4f4817). Report documentation problems inUFlinux-project/docs.