Trixie, testing and sid users beware!

thanks for the heads up!
was planning to use antiX + init-diversity (sid) repos to convert current devuan setup, but i guess i should wait till after antiX 25 is released.. (?)

anticapitalista wrote:

Trixie, testing and sid are not officially supported by antiX, though we do try to help users of testing/sid when we can.
Our trixie based iso files (antiX-25 alpha) were only to play with and for us devs to get feedback and were not meant to be used as a daily driver.

There have been huge changes since antiX-23 and it is very likely that upgrading from 23-25 will cause issues.
antiX-25-alpha should be removed and users should start with the upcoming beta release.

Sid and testing users will also see huge changes hitting the repos soon which may also cause breakage.

So if you are a sid/testing user, prepare a backup plan for yourself and whoever you support.
If you were using antiX-25-alpha or upgraded antiX-23 to trixie, do the same.

Those sticking with antiX-23 will not be affected.

Changes will come through in a week or so, so you have plenty of warning.

I’ve been recently messing around with my own Trixie-based variation; I practically destroyed it at one point, but I managed to retain a dinit setup that’s usable enough to keep, so I removed the other variations; it was the @ProwlerGr build on our initial Alpha 1. Today it’s been behaving well, but I’m not counting on any “miracles” with it; I just use it for Web browsing and simple editing and it handles those functions well. Other stuff I’ve had to hand graft in place, so to call it a hack is an understatement, but for me it actually works.

I WOULD NOT RECOMMEND what I’ve been doing for anyone who 1) doesn’t back stuff up 2) doesn’t have other alternatives, and 3) can’t solve their own problems without help. As a hacker though it’s been a fun exercise! 🙂

It’s keeping me occupied until we get more images to test and evaluate. It’s also keeping me off the streets so South Carolina residents are safe a little more often (not really; I try to be safe).

anticapitalista wrote:

if you are a sid/testing user, prepare a backup plan for yourself and whoever you support.
If you were using antiX-25-alpha or upgraded antiX-23 to trixie, do the same.

As I wrote elsewhere:

andfree wrote:

I’m going to replace every crashed antiX-25-alpha installed system with antiX 23.2-runit and continue the tests in frugal

antiX 23.2 is still the latest stable version.
I’m going to install the recommended full iso and continue testing with other iso(s) frugal.
I was thinking of runit because “antiX with runit – leaner and meaner”, but i’m having second thoughts because of this:

If you don’t know or care about init systems, choose the sysVinit version.

I actually don’t know, but I care and would like to know.
I also wonder if it would better to give a try to a Mont(h)ly Snapshot. I suppose it would reduce the downloading and updating time, but I also suppose that if something went wrong, it would be my mistake that I chose an “unofficial” iso.
I’d like to know your own ideas, not only about these specific concerns of mine, but also how organizing the time period waiting for and planning about antiX-25-beta in general.

ProwlerGr wrote:

The init-diversity variant of 25a1 is subject to the same instability as the official runit 25a1.

I can say it is worth to wait for the official antiX-25-beta version, most of the init-diversity related software will be making it into the official antiX repos anyway.

True, though if the excellent work of @ProwlerGr results in yet another init-diversity edition, official or not, it’s good stuff; if you read my regular threads, you’ll notice that whenever there is a new init-diversity respin, I’m all over it.

When “stable” stuff comes out, it’s infinitely more solid than Sid. While the content of Sid packages is solid, at times there can be discrepancies where a newer library is available, but not all apps that depend on the library, or the opposite, an app is available, but some dependencies are lacking; this can change from day to day; though it’s not constant, and quite often Sid works just fine, it’s a volatile environment to rely upon. Though I like using it, I always have other more stable alternatives available, just in case Sid is going through a particularly volatile point in time (or if I expect a volatile environment, I pause updating Sid).

andfree wrote:

Thanks for all this info. Is @ProwlerGr’s antiX-23.2 – init-diversity – 2025 remaster edition the latest “stable” init-diversity edition? Would it be a good choice for a “normal” (non-frugal) installation? 25 pages of posts are too many for me to read at this point of time.

Yes, that’s a really nice “init-diversity” release. It contains sysVinit, runit, s6 release, s6-66, OpenRC and dinit. 66 is a different service manager that @eric from Obarun Linux created. @ProwlerGr does really nice work. If you do try this out, you’ll discover that there really is not much performance difference between the different implementations; there are significant differences in the services that are available in the service managers of each init.

andfree wrote:

anticapitalista wrote:

(…) it is very likely that upgrading from 23-25 will cause issues.

Does this statement refer to the upcoming antiX-25 official released? Is it likely that a fresh install of it will be recommended, rather than an upgrading from antiX-23?
Sorry if it’s too early to ask such a question, but I still haven’t figured out how it would be better for me to organize my installs at this point of time. This uncertainty, combined with some technical issues, has held me back in testing beta.

With this one mostly not,
http://www.antixforum.com/forums/topic/antix-25-full-beta1available-for-public-testing/

It’s being used for development of antiX-25 but be aware there are some issues already mentioned,
I advice you to read the thread to understand them,
also be patient about new updates if you opt to go with this beta
packages will hit antiX-25 main that were moved from dev has @anticapitalista said

Thanks for the replies, although they don’t really answer my concerns. It’s not your fault, of course. I find it difficult to express them clearly.
I have already installed @ProwlerGr’s init-diversity variant of antiX-23.2 (bookworm) on a Toshiba Satellite A300 and I was going to run the testing (beta) version of antiX-25 frugal. I hoped that this would give me the opportunity to compare the various init alternatives in both antiX versions. But when I tried to set the options on the liveUSB, runit version was booted before I can do anything. When I tried to reboot on the liveUSB, operation system was not recognized anymore and, instead of that, the installed on the hard drive system was booted.
But, after that, I successfully used this same liveUSB for a frugal install of antiX-25-beta on an Asus VivoBook X540MA (with antiX-23.2-runit-full already installed on the hard drive). So, I suppose it’s not a problem related with that USB.
I wonder if the combination of the two multi-init systems was too “heavy” for that old Satellite and I should erase everything from the disk and try another combination. I also wonder if I’m going to test that “heavy” combination to the VivoBook (which means to erase everything from that disk, too). Last, I wonder if I’m going to make antiX-25-beta my main (non-frugal) install of at least one of these laptops.
In such a context I asked how likely it would be an upgrading from antiX-23.2 to (official, not beta) antiX-25 (when released), although an answer to this wouldn’t make my position much easier.

• This reply was modified 10 months, 3 weeks ago by andfree.