Brian Masinick
I have a small bug/defect to report with the iso-snapshot tool.
When I change /etc/iso-snapshot.conf to have option “edit_boot_menu=yes”, when the snapshot is paused to edit the live boot menu it just brings-up an empty isolinux.cfg file (from a wrong /tmp location)
The MX-snapshot tool used to have very similar issue that has now been resolved (it now opens all 3 controlling files isolinux.cfg syslinux.cfg grub.cfg – which is great).
Certainly not a priority, but it would be good to have this attended for antiX as well
I don’t know if it has anything to do with this or something else. Late yesterday afternoon I was testing the Pipewire enable/disable, both installed and live. On my configurations, both live and installed, only enabled Pipewire was delivering sound, regardless of the init, and regardless of whether live or installed.
One of the last things I did before shutting down for the evening was to run an update and there was a reinstallation of several of the inits, maybe all of them. I did not login to them until this morning, but the first one I tried was completely broken: runit. It would start to boot, then after recognizing /dev it ran into serious problems, not finding much of anything, and it kept repeating some ch* command over and over. I had to halt the system. The other inits weren’t affected, though at first it looked like dinit had a problem too; I don’t believe that was the case. In any case, for my system, the Lenovo Thinkpad T14 Gen 3 (AMD processor) the series of init updates had some major problems, mostly affecting runit. I believe any and all changes that are suspect occurred on what was to me December 29, 2025 – my timezone is GMT-5 and I ran the changes between 6 – 8 PM Eastern Time, (GMT-5). Not sure precisely when the changes were built but that’s when I ran them; only today, December 30 did I notice the problem.
I’m writing now from antiX 23.2 because I also cannot directly access root – the /root directory has -drwx—— (700) permissions, so I cannot login to root and I cannot su to root either. That’s a problem because some things cannot be repaired from an ordinary user because there is no root access. Worse, I was unable to sudo synaptic because there has been a synaptic change that moves the /root/.synaptic directory elsewhere and it’s quite the hack to get rid of it.
Is anyone else experiencing this after updating the system with 12/29/2025 changes?
--
Brian Masinick
Alternate "Search B":
This search page