First thanks to anticapitalista for being brave enough to give this experiment a try

and to consider smxi for antiX.
Installing smxi first time
To make smxi install easier, I created a new method that is simple:
First, test that you have unzip installed, by simply running any unzip command, like: unzip xyz
If it's installed, great, you're ready to proceed, if not:
- Code: Select all
apt-get update;apt-get install unzip
Next, as root in console, execute this command string (downloads zip file, unzips, and starts smxi):
- Code: Select all
cd /usr/local/bin; wget techpatterns.com/smxi.zip;unzip smxi.zip;smxi
That's it, the zip files contains smxi, sgfxi (the graphics installer module), and svmi. Note: svmi is NOT tested on antix, so any user feedback is welcome.
Alternate method, only installs smxi:
- Code: Select all
cd /usr/local/bin; wget -Nc techpatterns.com/smxi; chmod +x smxi; smxi
This just downloads and makes executable the primary smxi core engine, and it will pull in anything else you run, like sgfxi or svmi, which can after that be started independently.
Quick explanation of core features
smxi, svmi, and sgfxi all update themselves automatically, so you only need to install them once.
The scripts MUST be located in /usr/local/bin, otherwise weird and impossible to debug errors can and do arise, but they test that anyway. But please don't put them anywhere else then ask for support in the future if something goes wrong.
Except for -v and -h options, smxi and sgfxi must be run out of X, period. Doing an upgrade with your desktop / xorg running is long term system suicide, so sgfxi and smxi simply will not let you do it.
The -v option in smxi is a very useful one, it tells you a bunch of information about your system, like when the last upgrade with smxi was, last apt use, kernel version, etc.
smxi now offers a 3 level hold/warning system, for systems base Debian Stable, Debian Testing, and Debian Sid. An unconverted Antix would be system base Testing, and will not see warnings/holds that a Sid based system will see.
sgfxi usually has the latest nvidia / fglrx drivers the day of release, and often sgfxi has the latest nvidia betas as well, but only installable by manual option. Otherwise it detects your card automatically and downloads the correct nvidia driver and applies any patches.
Note: currently, sidux kernels that are new do NOT work with fglrx, sorry. I'm not sure about the Debian driver install method. Fglrx users should be very careful about updating their kernels, support is very weak. Since antix does not currently support vanilla debian sid kernels, which do work with fglrx drivers, you're basically out of luck, unless they install on the mepis kernel, if they do, let me know.
Also, debian testing systems nvidia debian method driver install is NOT working due to missing sources in testing.
AntiX + smxi issues and problems
Bugs I've found: when running antix + sid sources + sidux sources, a new sidux kernel install only works without vga=xxx (like 791) in /boot/grub/menu.lst, otherwise I get weird green blocks instead of console text output.
By the way, I liked antix's light but clean fluxbox so much that I added a fluxbox package group to smxi package install options, but don't use it, anticapitalista already has a really good package selection.
Other bugs are debian kernels failed to install at all, so antix users will not be given a debian kernel install option because it destroys the system in tests. At least not until that feature is debugged.
Re new kernels
Mepis/Antix appears to be using a non standard /boot/grub/menu.lst layout, and my tests show that the new kernels are NOT default as they should be, so you have to edit the default kernel directly in /boot/grub/menu.lst, or move down to the correct kernel when grub boot loader shows you the options on boot.
smxi support issues
Please post any smxi, or sgfxi/svmi issues, in the
smxi support forums, it's more likely I'll see those posts. All real bug reports will be handled as quickly as I can get to them if there's enough data to figure out the issue.
If you post smxi/sgfxi related issues here, I am very likely to not see them at all because I only check these forums once in a while.
I want this to be VERY clear however, smxi use on AntiX is not a sidux support issue. smxi is an automomous project that has very close ties to sidux, and that's how I hope to keep it. So don't ask sidux people for support with smxi please, it's not fair to them, and it will just make them grouchy, heh heh...
smxi, sgfxi, and svmi are tested on Debian Stable, Debian Testing, sidux, and AntiX. I assume Debian Sid works fine too, although you should be aware that if you are going to run sid, it is highly recommended to use sidux sources (without running the conversion) because sidux injects hot fixes into Debian Sid directly when required, and smxi does not have those fixes in it, since they are often patched deb packages. Testing based distros should work totally fine for everyone. Stable I've found most major bugs, just have one or two more issues to handle.
Closing
I'd like to thank anticapitalista for giving me the excuse I was waiting for to finally put in the extended distro support model I'd been thinking about for the last 6 months. AntiX testing and debugging exposed a bunch of weak spots in smxi and sgfxi that I'm slowly working through, and all of which make smxi/sgfxi much more robust, dynamic, flexible scripts.
Remember, things will not be perfect, this is as Anticapitalista notes, experimental, so watch for problems.
Have fun with it.