Forum › Forums › News › Announcements › antiX-25-full-beta2 for public testing
- This topic has 709 replies, 38 voices, and was last updated Jan 30-4:02 pm by Brian Masinick.
-
AuthorPosts
-
January 28, 2026 at 1:12 pm #195198
rokytnjiForum AdminDone. I thought service support was needed?
Sometimes I drive a crooked road to get my mind straight.
I don't suffer from insanity. I enjoy every minute of it.
Motorcycle racing is rocket science.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsJanuary 28, 2026 at 3:13 pm #195211
Brian MasinickModeratorThere will be updated iso files coming very soon.
They’re here!
See the RC1 announcement. I believe that updates will bring this to the antiX 26 release.--
Brian Masinick
Alternate "Search B":
This search pageJanuary 28, 2026 at 6:17 pm #195221grindstone
MemberFloating an 11th-hour enhancement request to do with what you wish. When I get to this screen, it’d be a “nice to have” to be able to see, right where user input is requested, what time the system thinks it is. Sorta whatever one “date” and two hwclock equivalents (–localtime and –utc) say like this screenie.
I know it’s not that simple, esp in C++ gazelle, but I don’t know C++ to even be able to correct whatever the LLMs might but it spit-out some logic, FWIW.
#include <QProcess> #include <QMessageBox> #include <QInputDialog> #include <QStringList> #include <QFile> #include <QTextStream> #include <QDateTime> // Function to get current system time QString getSystemTime() { return QDateTime::currentDateTime().toString(Qt::ISODateWithMs); } // Function to get hardware clock time QString getHardwareTime() { QProcess process; process.start("hwclock -r"); process.waitForFinished(); if (process.exitCode() != 0) { return "Error reading hardware clock"; } return QString::fromLocal8Bit(process.readAllStandardOutput()).trimmed(); } // Function to detect current hwclock mode from /etc/adjtime bool isHwClockUTC() { QFile file("/etc/adjtime"); if (!file.open(QIODevice::ReadOnly | QIODevice::Text)) { // Default to UTC if adjtime is unreadable or non-existent return true; } QTextStream in(&file); QString lastLine; while (!in.atEnd()) { lastLine = in.readLine(); } file.close(); return lastLine.trimmed().toUpper() == "UTC";Attachments:
January 30, 2026 at 3:34 pm #195352
anticapitalistaForum AdminI’m going to close this thread in a day or so.
I’d like to thank everyone who has posted in this thread.
It is really appreciated.
Let’s hope we have managed to squash the bugs.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
January 30, 2026 at 4:02 pm #195353
Brian MasinickModeratorLet’s hope we have managed to squash the bugs.
Most of them are taken care of, but there remain a few weird quirks that I’ve never seen before.
THIS is actually true for the RC1 build; didn’t spot it until then; don’t know if it was also present in Beta 2, but probably yes.Today I figured out how to fix one of them:
In the past I’ve first created a USB Flash Drive containing the image I want to use, then I update and configure the system as I want it. Then I create an ISO Snapshot, run Live USB Maker, creating another snapshot image of my completed system. At that point I take that drive to my other systems and install it.
Two great examples of this from the antiX 23.2 project were Calcium Sodium’s “Privacy Respin”, which I put on a drive, configured it the way I like it, then generated the image with ISO Snapshot, made another snapshot image with Live USB Maker, and put it on my various systems. The other excellent example was the @abcnix November 2024 snapshot. I’ve used that one repeatedly as my antiX 23.2 image, and I’ve also used live-remaster on it too.
I did the same with RC1. At first it seemed to work. When I tried it straight from the Flash Drive I was able to boot it. However when I installed it and went through the different alternatives, most worked, but s6-66 oddly did not work; in fact it generated a kernel dump! This same image worked perfectly.
Last night on my HP-14 I tried to FIX it by booting into another init, then I used synaptic to find ALL of the 66 packages, and reinstalled them ALL, then rebooted. Guess what? It WORKED. That tells me that something in 66 doesn’t build properly with the ISO Snapshot and Live USB Maker tools, yet the OTHER FOUR init alternatives did not mind this method at all; they worked fine.
This may not be that big of a deal since I figured out a work around, but it does indicate a defect somewhere that necessitates the packages for 66 being reinstalled when copied to another platform. That’s not right, but I’ve now replicated both the problem and the solution on three different hardware platforms.
To summarize: a snapshot image created on one system is installed on another system. Runit, SysVinit, S6-rc, and dinit work fine on the other systems, but S6-66 kernel dumps until each 66 package is reinstalled from another init. This IS reproducible on an HP-14 (AMD Ryzen 5), HP ENVY x360 (AMD Ryzen 5), and Dell Inspiron 5558 (Intel Core i7).
- This reply was modified 7 months, 4 weeks ago by Brian Masinick.
--
Brian Masinick
Alternate "Search B":
This search page -
AuthorPosts
- You must be logged in to reply to this topic.
