MX Tools made available to Debian and Q4OS

[olsztyn]

Just as an introduction:
I have been an antiX user for a number of years, checking out MX often, primarily as Live, testing on my various Thinkpads...
Just found out on the Web that 'A great set of tools from MX Linux is now available for Debian and Q4OS users', as of March 2021. Now, considering this a new frontier for me to test (as antiX appears to me tested thoroughly and no longer a challenge for further improvements) I have set out to test out MX Tools, using Q4OS Trinity as base, rather than Debian.
Performed the following sequence:
- Executed MX-Snapshot on installed Q4OS Trinity - ran perfectly, no errors.
- Executed MX-Live-USB-Maker on such snapshot - created Live USB without a hitch.
- Booted the resulting Live.
Live booted, although with the following observations:
- During booting process at some point it it waits for 1m30s with the following message: 'Wait on sys-subsystem-net-devices-multiuser.device'.
- After 1m30s it proceeds with boot but stops at CLI prompt to log in, rather than GUI login.
As MX Tools, and MX-Snapshot and MX-Live-USB-Maker in particular, have been developed by MX team I felt this more appropriate to ask on this MX forum, rather than on Debian or Q4OS, for which these MX Tools are something new:
- Is there anything I should be doing (such as turning off some services prior to Snapshot) to resolve the above?

Also I want to thank MX team for gracious decision to contribute MX tools to Debian community. I am confident this is greatly appreciated.
Thanks and Regards...

[Stevo]

Also I want to thank MX team for gracious decision to contribute MX tools to Debian community. I am confident this is greatly appreciated.

Like so much else for Linux, the MX Tools are open source and free for all. Making them so is pretty much standard, so we aren't that gracious, speaking only for myself, of course.

[olsztyn]

Thank you Stevo for your quick comment. Understood, but when I saw this loud on the Web as 'A great set of tools from MX Linux is now available for Q4OS users', my impression was that it would not have happened without MX team active involvement, adapting this great, unique set of MX tools to wider Debian community...
Regardless of details, this is appreciated...
My thinking is that just as for antiX these tools are the greatest asset, they could become such great value to some other distros as well, once their value is fully realized...
Thanks and Regards...

[SwampRabbit]

... 'A great set of tools from MX Linux is now available for Q4OS users' ...

Got a link to this? you've mentioned it twice now...

Would be interested in knowing if the Q4OS team packaged it up for them or whatever.

If it is a Q4OS built package of the MX tool sources, they probably need some info on what is causing the issues you mentioned, since they may need to do something on their end too.

[AVLinux]

Not really a huge surprise even without special 3rd party packaging... @sunrat for one has had success with using these tools with straight Debian and there is another recent thread here where the person got it all working on Debian Bullseye. I also managed to get it to work on straight Debian Buster but there were just too many other great reasons to join up here where the tools are actually developed and where the community is so good!

[SwampRabbit]

nvm... I found some of the stuff really quick

https://www.q4os.org/forum/viewtopic.php?id=3477
https://github.com/q4os-installers/mx-tools
https://sourceforge.net/projects/q4os/f ... ntal_apps/

Please consider this compilation of MX tools for Debian as a testing attempt so far, so it may not work as expected in all cases. Testing and reporting is highly appreciated.

Not sure if they are keeping up with it, seems a big dated, and from the looks of it ... it isn't each MX Tool individually.

[dolphin_oracle]

those time outs are due to the way systemd treats various hardware bits. the networking parts in particular are annoying and don't work very well with the live system. there are pieces you can do without (most folks can anyway), and I've experimented with just disabling certain services. most of the systemd-network ones you can disable if you are using network-manager.

[olsztyn]

My installation of MX tools using the MX Tools installer provided there on the Q4OS page results in the following my observation:
- Special icon to MX Tools folder provided on desktop, appropriately shows MX logo.
- MX Tools app folder is titled with 'These MX applications save time and effort with important tasks'.
The entire kaboodle of MX Tools appears to be installed in sections:
- Live: Live USB Maker and Snapshot
- Maintenance: Chroot, Boot Options, Boot Repair, Cleanup, User Manager
- Setup: Bash Config, nVidia, Conky, etc., etc...
- Software: Fix GPG keys, Package Installer, Repo Manager
- Utilities: Quick system Info, Format USB, iDeviceMounter

I have not tested yet much beyond Live tools with the results I posted above, and it is expected there might be some work to make all this set of MX Tools work correctly. However it seems a great plan and recognition for MX accomplishments...
Regards...

[olsztyn]

those time outs are due to the way systemd treats various hardware bits. the networking parts in particular are annoying and don't work very well with the live system. there are pieces you can do without (most folks can anyway), and I've experimented with just disabling certain services. most of the systemd-network ones you can disable if you are using network-manager.

Thanks for the info dolphin_oracle...
I will try to identify those services to disable...
Thanks and Regards...

[dolphin_oracle]

I find the ones to disable are several of the wpa-supplicant, and the network ones with *-wait in them. you'll need to disable and mask them, or else some depend will also start them up.