MX Linux Forum

fehlix: Thanks for the more detailed explanation of the code. However, GitHub Workflows suppresses the error output and thus prevents me from seeing which line of code triggered the error. So I'll have to change the code to perform the same step somewhat differently in the GitHub Workflows ...

I'm having difficulty making sense of the following line of code:

main_case 7>&1 1>&2 2>&7 \
| tee -a $err_file | sed -e "s/^/$red/" -e "s/$/$nc/"


More specifically, I'm having difficulty making sense of the portion of the first line after "main_case" and before the backslash.

I understand ...

I'm currently in the process of providing a GitHub Workflows solution to building the MX Linux ISO files. The idea is to provide a fully automatic solution to upload new ISO files. I know that this is do-able for the 64-bit editions. (This may or may not be possible for the 32-bit editions.) So far ...

What does the command "leave_stage notime" mean? I see that it's used at the end of Stage 1, in the chroot process, and when skipping steps.

by default build-iso asks if you want to go to the next stage. it does not have a stop other than that question. if you say no, then it exits. it does present all the errors at this point as well, for that stage.

you can start a stage over. lets say you get to stage 7 (squashfs) but you update ...

Is there a way to run just one stage of the build-iso script?

I'm trying to get the GitHub Workflows to build the MX Linux ISO. I'd like to have the GitHub Workflows execute just one stage at a time instead of all of them at once. If there's an error or failure, the troubleshooting is so much ...

The build is done in a chroot. It doesn’t matter what kernel the host system is using.

We specify the kernel at build and we build isos with different kernels. At least 5 kernels. So specifying the kernel is important.


If it doesn't matter what kernel the host system is using, then why does ...

To start the ISO build process WITHOUT being prompted for inputs along the way, I must use the --user-defaults parameter to specify a list of settings (from the Input directory) when calling the build-iso script.

Some questions:
1. The defaults-local file is the one with the highest priority. So ...

Is there any interest in adding continuous integration (GitHub Workflows) to the repositories at https://github.com/MX-Linux and https://github.com/antiX-Linux ?

I have experience with GitHub Workflows and other continuous integration solutions. Some great things about having continuous integration ...

I've revived Swift Linux, my project of MX Linux respins. Every edition of Swift Linux consists of updates, the addition of KeePassXC, and special themed wallpaper for the login screen and the desktop. Check it out at https://www.swiftlinux.org/. The current version is 19.2.0.

One of the new ...