- This topic has 709 replies, 38 voices, and was last updated Jan 30-4:02 pm by Brian Masinick.
-
Posts
-
dolphin_oracle
Dear @dolphin_oracle
I can confirm that my antiX 25 Full 64-bit beta 2 version is installed on an external SATA SSD drive.
For my MX Linux 25 version installed on the same external SATA SSD, the /tmp directory is mounted directly in RAM.
The command lines confirm the tmpfs mount.
The MX Linux 25 installer did this automatically without asking about the tmpfs mount.wallon@msi:~ $ LANGUAGE=C mount | grep /tmp tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=8165268k,nr_inodes=1048576,inode64) wallon@msi:~ $ LANGUAGE=C df -h /tmp Filesystem Size Used Avail Use% Mounted on tmpfs 7,8G 292K 7,8G 1% /tmp wallon@msi:~ $ LANGUAGE=C df -hT | grep tmpfs udev devtmpfs 7,8G 0 7,8G 0% /dev tmpfs tmpfs 1,6G 4,8M 1,6G 1% /run tmpfs tmpfs 7,8G 24M 7,8G 1% /dev/shm tmpfs tmpfs 5,0M 20K 5,0M 1% /run/lock tmpfs tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-journald.service tmpfs tmpfs 7,8G 292K 7,8G 1% /tmp tmpfs tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-networkd.service tmpfs tmpfs 1,0M 0 1,0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1,6G 124K 1,6G 1% /run/user/1000 wallon@msi:~ $I thought that antiX users could also benefit from a modern installation like MX Linux 25.
Best,
WallonSystem: Kernel: 6.12.57+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.57+deb13-amd64 root=UUID=<filter> ro nvidia-drm.modeset=1 nvidia-drm.fbdev=1 quiet splash Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0 with: xfce4-panel tools: avail: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0 Distro: MX-25_Xfce_x64 Infinity Nov 9 2025 base: Debian GNU/Linux 13 (trixie) Machine: Type: Desktop Mobo: MSI model: H170M PRO-VDH (MS-7982) v: 1.0 serial: <superuser required> uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: 2.F0 date: 06/27/2018 CPU: Info: model: Intel Core i5-6400 bits: 64 type: MCP arch: Skylake-S gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xF0 Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB Speed (MHz): avg: 800 min/max: 800/3300 scaling: driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Vulnerable: No microcode Type: indirect_target_selection status: Not affected Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled Type: mds mitigation: Clear CPU buffers; SMT disabled Type: meltdown mitigation: PTI Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled Type: reg_file_data_sampling status: Not affected Type: retbleed mitigation: IBRS Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds mitigation: Microcode Type: tsa status: Not affected Type: tsx_async_abort status: Not affected Type: vmscape mitigation: IBPB before exit to userspace Graphics: Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Micro-Star MSI driver: nvidia v: 550.163.01 non-free: 550-570.xx+ status: current (as of 2025-04; EOL~2026-12-xx) arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3,DVI-I-1 bus-ID: 01:00.0 chip-ID: 10de:1401 class-ID: 0300 Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:7 chip-ID: 046d:082d class-ID: 0102 serial: <filter> Display: x11 server: X.Org v: 21.1.16 compositor: xfwm4 v: 4.20.0 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1017x286mm (40.04x11.26") s-diag: 1056mm (41.59") Monitor-1: DP-1 mapped: DP-0 note: disabled pos: primary,left model: AOC 2590G5 serial: <filter> built: 2021 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 90 gamma: 1.2 size: 544x303mm (21.42x11.93") diag: 623mm (24.5") ratio: 16:9 modes: max: 1920x1080 min: 640x480 Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: right model: MD20830 serial: <filter> built: 2016 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 640x480 API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.163.01 glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 960/PCIe/SSE2 memory: 1.95 GiB API: Vulkan v: 1.4.309 layers: 4 device: 0 type: discrete-gpu name: NVIDIA GeForce GTX 960 driver: nvidia v: 550.163.01 device-ID: 10de:1401 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256 bits) driver: mesa llvmpipe v: 25.0.7-2 (LLVM 19.1.7) device-ID: 10005:0000 surfaces: xcb,xlib Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings gpu: nvidia-settings,nvidia-smi x11: xdriinfo, xdpyinfo, xprop, xrandr Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403 Device-2: NVIDIA GM206 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fba class-ID: 0403 Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:7 chip-ID: 046d:082d class-ID: 0102 serial: <filter> API: ALSA v: k6.12.57+deb13-amd64 status: kernel-api tools: alsactl,alsamixer,amixer Server-1: PipeWire v: 1.4.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Info: services: NetworkManager, nfsd, smbd, systemd-networkd, wpa_supplicant Drives: Local Storage: total: 1.59 TiB used: 412.39 GiB (25.3%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1SB102 size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: CC43 scheme: GPT ID-2: /dev/sdb maj-min: 8:16 vendor: Kingston model: SUV400S37240G size: 223.57 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: D6SD scheme: GPT ID-3: /dev/sdc maj-min: 8:32 model: SATA SSD size: 476.94 GiB block-size: physical: 512 B logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter> scheme: MBR SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? Partition: ID-1: / raw-size: 68 GiB size: 66.38 GiB (97.62%) used: 14.19 GiB (21.4%) fs: ext4 dev: /dev/sdc1 maj-min: 8:33 Swap: Kernel: swappiness: 5 (default 60) cache-pressure: 50 (default 100) zswap: no ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap Sensors: System Temperatures: cpu: 23.0 C pch: 38.0 C mobo: N/A gpu: nvidia temp: 38 C Fan Speeds (rpm): N/A gpu: nvidia fan: 0% Repos: Packages: pm: dpkg pkgs: 2355 libs: 1232 tools: apt, apt-get, aptitude, nala, synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 0 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/debian.sources 1: deb http://mirror.unix-solutions.be/debian/ trixie main contrib non-free non-free-firmware 2: deb http://security.debian.org/debian-security/ trixie-security main contrib non-free non-free-firmware 3: deb http://mirror.unix-solutions.be/debian/ trixie-updates main contrib non-free non-free-firmware Active apt repos in: /etc/apt/sources.list.d/mx.sources 1: deb http://nl.mxrepo.com/mx/repo/ trixie main non-free Info: Memory: total: 16 GiB available: 15.57 GiB used: 1.76 GiB (11.3%) Processes: 281 Power: uptime: 24m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.17 GiB services: upowerd,xfce4-power-manager Init: systemd v: 257 default: graphical tool: systemctl Compilers: gcc: 14.2.0 Client: shell wrapper v: 5.2.37-release inxi: 3.3.38 Boot Mode: BIOS (legacy, CSM, MBR)that’s the default case for systemd’s configuration. our sysVinit configuration mounts directly to drive, just like antiX’s. the “installer” doesn’t do anything with the init system configurations.
andfree
Both packages at-spi2-common & at-spi2-core appear to be upgradable, but:
(…)don’t upgrade to the backports version
The only apps that should come from backports repos are libreoffice, yt-dlp and firmware-linux-nonfree, otherwise you will get issues like you see especially when backports updates packages that use elogind/systemd
trixie-backports source appeared to had been enabled in Repo Manager. I disabled it and the “strange” packages got out from the list of upgradable packages.
If you disable trixie backports, you will not get any upgrades of libreoffice, yt-dlp and firmware-linux-nonfree.
I enabled trixie backports again and fortunately at-spi2-common & at-spi2-core don’t appear to be upgradable. I don’t know what went wrong before.
antiX utilities for processing PDF files (posted by ChPol)
Wallon
Thank you @ProwlergG, your command works very well.
echo "Alpha=0" >> ~/.icewm/preferences && icewm --rewrite-preferences && icewm -rBut conky isn’t displaying the correct init! Does anyone know why?
With “runit,” conky shows “init.”
- This reply was modified 8 months, 3 weeks ago by Wallon.
- This reply was modified 8 months, 3 weeks ago by Wallon.
ProwlerGr
With “runit,” conky shows “init.”
I’m pretty sure you are running sysvinit…
@anticapitalista & I are aware of the issue that beta2 came with sysvinit-core preinstalled which when updated hijacks the primary init (replaces /sbin/init).
This happened because the sysvinit service manager (a tool that manages sysv runlevels & services) had a dependency to sysvinit-core which got pulled by mistake into the beta2 iso.This will be resolved with the next RC release, that service manager has been rebuilt without the sysvinit-core dependency.
I enabled trixie backports again and fortunately at-spi2-common & at-spi2-core don’t appear to be upgradable. I don’t know what went wrong before.
Backports get pulled when you have a local package installed (not in active repos) which has a higher version in the backports repo.
If a package is installed & its version is contained in an active repo, the backports higher version gets ignored & needs to be specifically targeted for installationI hope this makes sense
@anticapitalista
Just more of a nitpick rather than a bug to report:
runit-service-manager comes under Applications –> System
s6-rc & dinit service (dialogbox) managers come under Applications –> Preferences
I can’t spot sysv-rc-conf (I only see it in Control Centre)I think it would be good (for consistency) that all fall under the same submenu
Brian Masinick
Just more of a nitpick rather than a bug to report:
runit-service-manager comes under Applications –> System
s6-rc & dinit service (dialogbox) managers come under Applications –> Preferences
I can’t spot sysv-rc-conf (I only see it in Control Centre)I think it would be good (for consistency) that all fall under the same submenu
I agree with you.
--
Brian Masinick
Alternate "Search B":
This search pageWallon
Bonjour,
[BUG REPORT] antiX‑25 runit: APT silently switches init system from runit to sysvinit during full-upgrade
Hello,
I would like to report a critical issue encountered on a fresh installation of antiX‑25-b2 (runit edition).
During the very first apt full-upgrade, the system silently switched from runit to sysvinit, without asking for confirmation and without any explicit user action.
This behavior appears unintended and may cause serious problems for users relying on runit.
Summary of the issue
• Fresh installation: antiX‑25-b2_x64-full (runit)
• First update: apt update && apt full-upgrade
• APT upgraded several sysvinit-related packages:
◦ sysvinit-core
◦ sysvinit-init-antix
◦ sysv-rc
◦ initscripts
• The post-install script of sysvinit-init-antix regenerated GRUB and removed the runit boot option.
• After reboot, the system no longer used runit and booted into SysVinit.
• APT never asked for confirmation about changing the init system.
Evidence from the APT log1. The system was running runit before the upgrade
Multiple lines confirm this:
runit is running as the system’s init system – starting service ssh
runit is running as the system’s init system – starting service rc-local
runit is running as the system’s init system – starting acpi-fakekeyd2. APT upgraded sysvinit packages without warning the user
Excerpt:
Upgrading:
sysvinit-core
sysvinit-init-antix
sysv-rc
initscripts
APT did not display any message indicating that the init system would be changed, nor did it request confirmation.3. The sysvinit post-install script modified GRUB
This is the key part:
Reinstating multi-init poweroff function
Reinstating multi-init reboot function
Reinstating multi-init shutdown function
Reinstating multi-init runlevel function
Reinstating multi-init rc function
Reinstating multi-init rcS function
Updating GRUB to reveal the updated init entry
Generating grub configuration file …
This step removed the runit boot parameter (init=/sbin/runit-init) from GRUB.4. After reboot, the system was no longer using runit
Confirmed by:
Init: SysVinit v: 3.14 runlevel: 2
Impact
• The user loses runit without being informed.
• The system changes its init system silently.
• This may break services, scripts, or configurations specific to runit.
• The behavior is unexpected and potentially dangerous.Expected behavior
• APT should never switch init systems without explicit user confirmation.
• The sysvinit-init-antix post-install script should not modify GRUB when runit is active.
• The installer’s chosen init system should always be respected.Request
Please review:
1. The behavior of the sysvinit-init-antix post-installation scripts.
2. The detection logic for the currently active init system.
3. The GRUB regeneration step that overwrites the runit boot parameter.
4. The multi-init integration in antiX‑25 beta 2.You will find the log in attachment.
Best,
Wallon- This reply was modified 8 months, 3 weeks ago by Wallon.
anticapitalista
With “runit,” conky shows “init.”
I’m pretty sure you are running sysvinit…
@anticapitalista & I are aware of the issue that beta2 came with sysvinit-core preinstalled which when updated hijacks the primary init (replaces /sbin/init).
This happened because the sysvinit service manager (a tool that manages sysv runlevels & services) had a dependency to sysvinit-core which got pulled by mistake into the beta2 iso.This will be resolved with the next RC release, that service manager has been rebuilt without the sysvinit-core dependency.
@Wallon – we know
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
@Wallon
To fix the issue while on beta 2 you can run:
sudo apt update && sudo apt -y upgrade sysv-rc-conf && sudo apt -y purge --allow-remove-essential sysvinit-core && sudo apt -y -o Dpkg::Options::="--force-confmiss" install --reinstall sysvinit-init-antix && sudo ln -sf /usr/lib/runit/runit-init /usr/sbin/init- This reply was modified 8 months, 3 weeks ago by ProwlerGr.
- This reply was modified 8 months, 3 weeks ago by ProwlerGr.
Wallon
To fix the issue while on beta 2 you can run:
sudo apt update && sudo apt -y upgrade sysv-rc-conf && sudo apt -y purge --allow-remove-essential sysvinit-core && sudo apt -y -o Dpkg::Options::="--force-confmiss" install --reinstall sysvinit-init-antix && sudo ln -sf /usr/lib/runit/runit-init /usr/sbin/initThank you. It works. Conky shows “runit”!
Bug Report – antiX 25 Full beta 2 (runit)
Title
udev: ALSA restore rule contains invalid GOTO targetSystem
• Distribution: antiX 25 Full
• Version: beta 2
• Architecture: amd64
• Init: runit
• Kernel: 6.6.101-antix.1-amd64-smpDescription
At every boot, dmesg reports udev errors related to ALSA restore rules.
The errors indicate a missing label referenced by a GOTO directive.
Observed Messages
udevd: GOTO ‘alsa_restore_std’ has no matching label in:
‘/usr/lib/udev/rules.d/90-alsa-restore.rules’
The message appears multiple times during early boot.Expected Result
• No udev error messages for ALSA restore when sound configuration is valid.Actual Result
• udev reports an error, although ALSA and audio output work normally.Impact
• No functional regression detected.
• Sound works as expected.
• Issue appears to be cosmetic / rules inconsistency, but may confuse testers.Analysis / Hypothesis
The file 90-alsa-restore.rules contains a GOTO=”alsa_restore_std” directive without a corresponding label definition.
This is likely caused by a mismatch between alsa-utils, alsa-ucm-conf, and udev rule versions in beta 2.
Reproducibility
• 100% reproducible on every boot.Workaround
• None required.
• Ignoring the message has no negative effect.Best,
Wallon- This reply was modified 8 months, 3 weeks ago by Wallon.
Wallon
Bonjour @Brian
Perhaps THIS will help to explain my “frustration”. I just hand timed how long it takes to get into the system straight to the desktop. With sysVinit, it’s NICE – rough estimate is seven seconds. With the others, more than FOUR times longer, more like 4 1/2 times longer. Just hand estimated with dinit and it was between 32 and 33 seconds. I have NO IDEA what’s holding up the other four init alternatives, but for me to be frustrated it takes a lot. I’ve had no success looking in various logs for any kind of reasonable explanation to this, so it’s difficult for me to provide anything to the team; I’ll keep trying; maybe my head will bump into the answer!Dear Brian,
I installed antix 25 beta 2 (64-bit) twice on the same external SATA SSD and timed the time between the multi-boot grub message and the login.
For the SysVinit version = 19.70 seconds
For the Runit version = 18.45 secondsI don’t see as big a difference as you do.
Best,
Wallon- This reply was modified 8 months, 3 weeks ago by Wallon.
- This reply was modified 8 months, 3 weeks ago by Wallon.
- This reply was modified 8 months, 3 weeks ago by Wallon.
Xunzi_23
Hi Brian,
also not seeing big differences in boot times across inits.
Running live so can not compare actual time to an installed system.Brian Masinick
I reinstalled; so far it’s working. I’ll reboot and confirm this.
--
Brian Masinick
Alternate "Search B":
This search page
marcelocripe
Please I ask the developers to please pay attention to the topic “Programs Without Translations on antiX 23.2 Full” so that some of the problems I mentioned do not continue in the antiX 26 full ISO..
- You must be logged in to reply to this topic.