Search Results for 'boot from iso'

[Member 3guesses]

OK, so I’ve not been able to post because I followed the instructions for updating my kernel to a Surface-specific one and unfortunately errors occurred which meant that antiX would then not boot. And before rebooting I tried to post with the upgrade output (showing the errors) and the forum software wouldn’t let me because it thought I was posting SPAM (the irony). It has taken me this long to get a working system up and running – I wanted to install antiX 19.4, but the live ISO never loaded the desktop (or it didn’t for the several minutes I left it to do so). So real fun and games. But I have to say, this illustrates perfectly why Linux is not mainstream – I would probably be classified as a computer expert (not so where Linux is concerned, obvs), but it is far, FAR from straightforward to get it fully functional on devices.

[Forum Admin anticapitalista]

User can use cli-installer to install net, core, base and full versions.
You need to be booting from each one.
eg antiX net iso cannot install any other version except net, same with core, base, full.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Forum Admin rokytnji]

All I got to say. No matter how I make my live usb for my toshiba touchscreen with a fubar hard drive wiring harness.

Will never run as fast as it used to. Can’t beat choke points. Turns a I-5 laptop into circa single core pentium 4.

Plus side. I can use it. It , , boots on anything. Posting this from a chromebook install. Small hard drive. 16 gig.

Live sessions are cool. We are not limited like other distros. When it comes to using /user/local/bin.

Seeing that systemd likes to be tyrant with our file systems.

I use MX toolbox. Mx Linux. AntiX full iso mostly. Ubuntu on one box to keep my foot in the water. Don’t spend much time on it though.
Seems Ubuntu is going snap all the way in a few years for packaging .
Then I will dry my foot.

I don’t have the frugal antix install skill nailed down yet. Have other stuff going on.

Edit: Thanks for your hard work at the lug. It takes courage to stand in front of a group and answer questions. The ones with more knowledge should understand. Can’t argue with opinionated ignorance or just meanness.

• This reply was modified 1 year, 6 months ago by rokytnji.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Anonymous]

You’re right once again sir.

I wanted to reply sooner, but it took me longer to review what I thought I knew and do some additional searches…

Certainly we don’t know how 3rd-party applications do their stuff, but regarding the multiboot tool I mentioned here, well… most likely I’m ignorant but I’m not sure how much of a “3rd-party” it would be…

Tool uses just Grub2 and Bash stuff to do everything. In fact, it is essentially just a set of Bash and Grub2 scripts.
Script for every supported distro uses commands and parameters proper of each distro precisely.

So for the question “how does this app set up booting ‘fromiso’?”, I think the answer would be “just the way distro itself sets it up”. At least as far as I understand it.

I post here in an attempt to help indeed, just as you said.
And again, NOT to minimze AntiX USB maker at all.
However, if it still doesn’t help at all, I won’t be bothering with the same thing neither.

Thanks again.

I did a presentation for my local user group meeting about the Live USB features of Antix/MX. Many thanks to DolphinOracle for his AWESOME videos. I used them in my presentation 😉

I have here, a kinda friendly “Devil’s Advocate” question regarding Antix and Live USB from one of the LUG members. I’m going to post it here but would GREATLY appreciate any responses. So here it is! Many thanks for any responses!
—

You asked me for a my question in writing too. Let me prefix this with
stating, that I’m simply trying to understand the “why” here. Why would
I want to use Antix (or MX) and particular why would I want to use this
method for USB based Linux vs. the other LiveUSB solutions out there?
When it comes to desktop use, I am most likely way outside the typical
end-user so I may be seeing challenges that aren’t there provided the
use-case for this.

OSTREE based OSes have existed for 10+ years. It’s a rather proven
technology that’s in use for not only embedded devices but it’s how
Fedora’s Silverblue is done, but you’ll find a very similar but scaled
down version for LiveUSB images, a system I see duplicated on lots of
embedded devices: R/O system file system (usually an img file) that some
system call “firmware” – this image is a full rootfs, often bootable etc
so the image can be positioned on a usual boot devices. Once the system
boots a separate volume/file system is added a COW system, it turns the
system image in to full R/O and any change done to temporary files or
permanent configuration files are written to this new system. When you
get an update of the “firmware” it’s simply rolled into the partition
where the other image was (or you have support for more than one image
so failures don’t brick your system), and when the system boots the COW
is added on top again. This is targeted towards systems where you don’t
“dnf update” – all updates comes from a new image, and the COW is for
dynamic files, log files, configuration files etc. that you want to
preserve across upgrades. This makes making embedded devices using Linux
simple – and it doesn’t have any distro-dependencies.

SilverBlue https://silverblue.fedoraproject.org/download is Fedora’s
attempt to move this idea into the desktop. It is NOT created with
little memory in mind – it’s a full Fedora setup that defaults to GNOME
after all, but it is created with the idea of easy management and setup.
It’s OSTREE based and created/configured with running containers and
flatpaks in mind. In other words, users are not allowed to change system
files – they are managed through replacing the “system file” that OSTREE
mounts. Instead users install/instantiate containers where they can
change/set whatever they want – even older and conflicting versions of
system libraries in the system. The update is a single command that
replaces the system image.

As to LiveUSBs I loved seeing a very different angle from what I’m used
to. If you look at (1) you’ll see what I mean by different. “Fedora
Media Writer” is all that is needed. I cannot remember what the same
type of tool is called on the Ubuntu side, but gone are the days of
needing to DD anything. WORSE, you had to use sudo to run your installer
– that raised alarms for me, we can definitely do better as it comes to
end-user tools. The Media Writer is a download, validate and write to
USB in one. As you can see from the attached screendump you pick “what
you want” and hit the “create live USB” button. The rest is automatic.
It will download (if you don’t have it already) and write to the USB all
without needing root rights. You can pick from all the spins available.
Or, when you become an advanced user, you can create your own “Live ISO”
that has the content you want, the configurations you want, to be
available out of the box. Provide that as a URL and others can now use
it too. I say all of this to make this question easier to understand:

* What/who is targeted with MX and Antix’s many questions during
install? Understanding concepts like rootfs, file systems,
partitions/volumes etc. are all concepts non IT people will have issues
with, so if this is targeted towards IT users under what conditions does
this make sense? What’s the use-case for something this complex?

Recall we’re talking USB based systems – so why would I need to save USB
images with customizations over and over again? Once the USB is created,
I can keep using it? Of course USB based OSes – something that only
exists and runs from the USB – are slow as molasses. USBs are not meant
to handle the writes needed to support a modern OS. So if you instead
move it all to RAM, what’s the point of talking how little RAM is used
by the OS running when the FS is all located in RAM too?

* It’s been many years since I saw USB sticks with 4GB or less. What is
the use-case trying to make it all fit into 2MB? With Fedora’s Live
Image, if there’s enough space you get the option to setup a part of the
USB as a large COW for /home and other changes. In some cases I’ve had
/home mounting a local file system while the USB itself is
self-contained. This is something I can setup once I have installed the
USB – or the user can choose FUSE land to add user-only file systems later.

* The desktops I use have VMs and/or containers running on them. The
idea of having to rsync these files on a regular basis scares me. Again,
from a use-case perspective is there a limited scope here? My general
fear is that “grandma” won’t have a clue how to use the features you
outlined, so even as a low-level user-workstations it seems you’ll need
regular IT help to keep it updated/managed? I get the feeling that the
use-case is not for permanent use, but something that you can easily
instantiate “in the field” and take down again when done, not something
you leave behind? And if that’s true, I don’t understand the “only a
few hundred MB of RAM” requirement – even the motel6 computer in the
lobby has more than 2GB of RAM – most likely 4 or 8GB.

You mentioned mass installation at one point. I would definitely not use
LiveUSBs as a system admin in charge of hundreds or thousands of
workstations. That would be old fashioned PXE and a local repository,
with a management access to control each workstations with centralized
settings/configurations etc. To make something others can use, see my
comment about creating a custom ISO and making it available for
download. That’s not as hard as it may sound (2). And yeah, all the
spins provide their “source” in this manner – so if you like the
Electronics Workstation but want to add your own twist on it, it’s
really simple.

Sorry, this became much longer than I wanted. The short version: Help me
understand the use-case for MX and Antix?

1) https://silverblue.fedoraproject.org/download
2)
https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/

• This topic was modified 1 year, 6 months ago by Danathar.
• This topic was modified 1 year, 6 months ago by Danathar.

[Member tamix]

@moderators this one should be ok

The init breakpoint interactive session. A few suggestions about it.

A special kudo to @BitJam.

The test described below has been run several times similarly in 3 antiX releases by using the read-only LiveUSB:

. antiX-21-b2_x64-full (bullseye-sysVinit)
. antiX-19.4_x64-full (buster-sysVinit)
. antiX-19.3_x64-full (buster-sysVinit)

System:
  Kernel: 4.9.0-279-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc 
  v: 10.2.1 Desktop: IceWM 2.7.0 
  Distro: antiX-21-b2_x64-full Grup Yorum 6 September 2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: ASUSTeK product: X456UVK v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: X456UVK v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: X456UVK.303 date: 10/05/2016 

Not sure the post is appropriate to this thread’s topic although it does include the 21-b2 release among the tests. Moderators might plan to redirect my post to another thread, they are most welcome.

Please note the three points discussed below affect in no way the basic components implied in the ‘initrd init’ process. They only concern a possible interaction with whoever wants to launch breakpoints – aka ‘bp’ – after boot. Finally our question sounds like: Is it possible to make the ‘init’ interactive menu only reflect what the set of breakpoints actually does? No less, no more. Necessary and sufficient “as required by law”.

The three points require adding tiny changes – but real changes though – in the ‘init’ file, which is a major component in the operating system. I ignore how changes are planned then propagated through the antiX architecture. May be the OS modular conception helps plan such changes. So whenever I mention below « Read the file /live/init », this only refers to my current live session. As for a real change done under control, we’d have to look into the original ‘init’ file stored in the ISO’s compressed file initrd.gz, then into a distro release, etc.: it is not the purpose of this post.

That’s why I suggest at first to check the new breakpoint interactive menu by using the terminal’s command line. Depending on your antiX flavour/context, the sudo command may be required to access the /live/init file. A particular init function to consider is called select_breakpoints() – lines 1166-1182 [1151-1167]. Every line number not put in square brackets is related to antiX-21-b2_x64-full. Those put in square brackets are related to antiX-19.4_x64-full.

After we set the boot option ‘bp=ask’ or ‘bp=?’ on the boot line, the next stage ‘initrd init’ currently displays an interactive menu by listing the following breakpoints then the prompt ‘:’ for reading our choice:

Remaining initrd init breakpoints:

  1) before welcome
  2) before coldplug
  3) before looking for linuxfs file
  4) after mounting boot device
  5) after mounting persistence device
  6) after mounting aufs
  7) after prepare switch_root
  8) before running live init.d scripts
  9) right before starting init
  e) On possibly fatal error

use "a" to set most breakpoints
use "A" to set all breakpoints
use "bash" to enter a Bash shell before system starts

:

As a matter of fact, the list above is incomplete because three options are missing: b8, b9 and 0. It also displays an extra option which should not exist: “bash”. What’s more, a short explanatory sentence is missing just before the prompt: ‘Enter breakpoints separated by commas’.

If everything is in order after a supposed change, we should get 15 separated options. Si we should see the complete menu:

Remaining initrd init breakpoints:

  0) before move
  1) before welcome
  2) before coldplug
  3) before looking for linuxfs file
  4) after mounting boot device
  5) after mounting persistence device
  6) after mounting aufs
  7) after prepare switch_root
  8) before running live init.d scripts
  9) right before starting init
  b8) Bash shell before running live init.d scripts
  b9) Bash shell before the system starts
  e) On possibly fatal error

use "a" to set most breakpoints
use "A" to set all breakpoints

Enter breakpoints separated by commas

:

As an example, at prompt we might select a single or combined options like:

0
0,9
1,2,3,A
4,5
A
a
b8
b8,b9
0,b8,b9,a
e

(note: line #3, ‘A’ supersedes 1, 2, and 3)
(note: line #9 is equivalent to line #5)

Let’s recall we can also write the same combinations on the boot line:

bp=0
bp=0,9
bp=1,2,3,A
bp=4,5
bp=A
bp=a
bp=b8
bp=b8,b9
bp=0,b8,b9,a
bp=e

Let’s see in detail what is going on.

1) When parameter ‘bp=ask’ is set on the kernel parameter line. All options currently displayed are valid except the ‘bash’ option which does nothing at all. It looks like the ‘bash’ option is quite not processed in the ‘init’ script. This is no critical point. The pointed breakpoint option is described as:

  use "bash" to enter a Bash shell before system starts

AFAIK the ‘bash’ option remains inactive as a breakpoint. Why not remove it? Unless it is considered a kind of “joker” reserved for later. It’s up to the antiX team to decide. In my opinion putting a comment is sufficient.

Read the init file:

$ sudo less -N /live/init

– Function: select_breakpoints()
– Line 1176 [1161]: echo “${m_co}Use \”bash\” …
– Suggestion: line 1176 [1161] to be commented.

2) No critical point. For a reason still unknown to me, a final sentence is missing just before the prompt when the boot option ‘bp=ask’ or ‘bp=?’ is set:

Enter breakpoints separated by commas

Read file: $ sudo less -N /live/init
– Function: select_breakpoints()
– Line 1178 [1163]: printf “${ok_co}%s$m_co: …
– Suggestion: line 1178 [1163]to be fixed/replaced.

A hypothesis. Let’s suppose the line is well printed on the standard output. Might it be overlapped by the following instruction? It is worth a further check: the cttyhack’s functionality is to give controlling tty to a shell then read the user’s answer. Anything more?

printf "${ok_co}%s$m_co: $nc_co"  "$_Enter_breakpoint_s_separated_by_commas_"
setsid cttyhack > /dev/null
read BREAK_POINTS;;

3) Adding only the missing options in the interactive menu.

3.1 The ‘b8’ and ‘b9’ options. They are not displayed when bp=ask or bp=? has been set on the boot line. However both options are valid if they are explicitly typed by the user at prompt. In other words, they flawlessly work! No critical point: a user could just remember that such options are valid either on the boot line – or at prompt if they had set ‘bp=ask’ previously.

Options ‘b8’ and ‘b9’ are shortly described in /live/README:

  b8) Bash shell before running live init.d scripts
  b9) Bash shell before the system starts

How to adjust 3.1?

Read file: $ sudo less -N /live/init
– Function: select_breakpoints()
– Line 1172 [1157]: sed -rn … sort
– Suggestion: line 1172 [1157] to be changed

For adjusting b8 and b9: the string {1,2} is appended to [1-9a-z]:

sed -rn 's/^\s*breakpoint ([1-9a-z]{1,2})\> */  \1) /p' $0 | sed "s/['\"]//g" | sort

3.2 The ‘0’ option. As a matter of fact, this ‘extra’ breakpoint option already exists and can be set on the boot line: ‘bp=0’. If that option is set by the user then two breakpoints occur just before the system starts. On the other hand, if ‘bp=ask’ is set then one just has to type ‘0’ at prompt with the same effect. We might evaluate the necessity of such a breakpoint in the init interactive menu. What for, precisely? So we need an answer, because I have no idea of it. No critical point: a user could just remember that such an option is valid either on the boot line or at prompt if they had set ‘bp=ask’ previously.

At execution, we get as expected two breakpoints occurring successively under their usual form:

==> limited shell @ breakpoint [0] before
    Use the exit command or press Ctrl-d to continue
    Use safe-poweroff and safe-reboot to poweroff and reboot
bp 0>

and

==> limited shell @ breakpoint [0] after
    Use the exit command or press Ctrl-d to continue
    Use safe-poweroff and safe-reboot to poweroff and reboot
bp 0>

How to adjust 3.2? (it’s assumed a first change was done in 3.1)

Let’s consider the same file, same function and same line number 1172 [1157]
Suggestion: line 1172 [1157] to be changed

For adjusting ‘0’: in string ‘[1-9a-z]’ replace the digit 1 with 0:

sed -rn 's/^\s*breakpoint ([0-9a-z]{1,2})\> */  \1) /p' $0 | sed "s/['\"]//g" | sort

At this step, there might be two instances of breakpoint 0 displayed. It is normal, considering the init specific context. We won’t complain! Two more breakpoint entries for the price of one, so we get:

  0) before move
  0) before move

However to make the interactive menu unambiguous, we are going on. We’ll just append the piped command ‘ | uniq‘ at end of line: line 1172 [1157] to be changed again:

sed -rn 's/^\s*breakpoint ([0-9a-z]{1,2})\> */  \1) /p' $0 | sed "s/['\"]//g" | sort  | uniq

You’ll note the instruction above scans the proper file it is written in. An elegant way of building a complete interactive menu (by staying at home) which involves a minimum cost in execution. Lean and mean so to speak.

Now our final check on the command line: Just copy the instruction above on the terminal’s command line and replace $0 with ‘/live/init’ (ie the init filename). The correct breakpoint list should be displayed:

$ sudo sed -rn 's/^\s*breakpoint ([0-9a-z]{1,2})\> */  \1) /p' /live/init | sed "s/['\"]//g" | sort | uniq

We are done. Now every antiX member can run the same tests on the fly.

4) The Breakpoint section in file /live/README might be updated if such changes are accepted and processed in a next antiX release.

A special kudo to @BitJam. Chapeau, l’artiste! Hopefully I’ll take time to read it through and think it over. The more we read this long complex file, the more we appreciate its architecture, the more we may consider it a masterpiece, smartly and rigorously developped according to the state of the art. In a nutshell I wish I were a co-designer of it… Such a result is also collective, a matter of nice cooperations among people sharing their know-how (why not, among people committed in fundamental forms of freedom). This gives us enthusiasm, indeed.

Additional note: To get a full idea of how the live init code is well structured, just type in the following commands which print the number and/or the list of all functions:

$ sudo grep -E -c '^\b[_[:alnum:]]*\b\(\)' /live/init

and

$ sudo grep -E -n '^\b[_[:alnum:]]*\b\(\)' /live/init > ~/init.func

Have also a look, among others, at a function named should_break_at(). Let’s consider it a tiny “jewel” for a while if you don’t mind. Getting to each breakpoint position during the init process, the function checks whether the bp has initially been selected or not by the user. Result is binary: 0/1. The algorithm is short, a bit tricky, however it *exactly* does what it was designed for. No less, no more. Hits the bull’s-eye. Hats off to the artist!

Hope all points are clear and helpful.

[Member marcelocripe]

Attention translators!

Some antix-bootscreen-helpmenu texts appear in other files: live-text-menus, live-grub, live-init, live-initrd-init, etc. So it is necessary to check if they are coherent between them, as they refer to the same thing.

– – – – –

Atenção tradutores!

Alguns textos do antix-bootscreen-helpmenu aparecem em outros arquivos: live-text-menus, live-grub, live-init, live-initrd-init, etc. Então é preciso conferir se estão coerente entre eles, pois referem-se a mesma coisa.

[Forum Admin anticapitalista]

No offense taken.

When 3rd party apps are involved such as (in this case) Multiboot or Ventoy we cannot guarantee anything will work because we have no idea how those apps set up booting ‘fromiso’.

Having said that, if anyone can help, please do.
We will all be the wiser.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member ModdIt]

No cloning issues for sure,

I disagree, cloning is not working for me..

No Persistence, just remastered fully updated system Init Runit.

Same issue with a freshly downloaded checked antiX 21 Beta 2 ISO, SysV, written to USB, updated as many packages are changed, remastered,
rebooted.

Initial window of Live USB Maker opens, Inserted a stick of fitting capacity same as boot stick. Marked clone a running live
USB system. Fails, no reaction or move from initial window.

Insert a USB stick then open live USB maker mark clone, same. Fail no reaction.

Initial fail on a runit fully updated system, present test with sysv init.

My USB sticks are fine, if I write an ISO to them no issues,
Clearing and reformatting before trying to clone makes no difference.

I can use snapshot tool to write an ISO, write that to my sticks and have a booting working customized/fully updated copy.

[Member pierro78]

Xecure wrote:

Thanks for the feedback, @bunkbail and @pierro78

pierro78 wrote:

(it could not get packages from an “ftp sthing fr” repository … but it was apparently only antixlinux helper packages)

Some mirrors are having problems. Would you mind using the repo manager (Control Centre > Software > repo manager) to switch to a different antiX mirro and then again run the antiX updater? Hopefully this is only a problem with the mirror that was assigned to you at boot. Let us know if a different mirror worked for you.

yes I made another install and it worked flawlessly 🙂 – thanks !

Hi! I’m not new to Linux, but I’m a new user of AntiX. I’d suffered HD crashes on 3 different machines, using Debian 10, and decided “never again” for D10. I eventually bought a 32/64 “Core Duo” Dell Precision M6300 Windows laptop. A friend recommended AntiX, so I dl’d the AntiX 19.3 ISO’s for both 32 & 64 bit, dl’d Rufus for making bootable ISO USB’s, set up 2 USB’s, and tried them out. (32-bit, also used on my old XP desktop machine.)

I installed 32-bit Antix, & 32-bit Debian 11 onto the new used Precision’s HD in a dual-boot configuration. (I thought, maybe they’d fixed the D10 problems, in issuing D11?) 32-bit AntiX worked beautifully. 32-bit Debian 11 (“Bullseye”) crashed repeatedly, locking up the system. Every time I was forced to do a hard shut down via press & hold of the power button, it also crashed my external TrueCrypt-encrypted HD’s. The lockups were connected with opening text files in Pluma, as a triggering event. The mouse pointer continued to move, but the system didn’t react to mouse clicks, or to the keyboard. I quit using bullseye.

It was only after installing 32-bit AntiX onto the new Precision’s HD, that I discovered via the AntiX system info utility, that the Core Duo could also run in 64-bit mode. So, I replaced the 32-bit AntiX installation with a 64-bit installation – and, so far it hasn’t crashed even once. I also tried the 64-bit version of Bullseye – and, it crashed during the very first usage. Same failure as in the 32-bit version, with mouse pointer mobile, but the system incapable of reacting to clicks or keyboard. I quit using D11 on the spot, and haven’t gone back. AntiX is working beautifully, with only a few glitches.

The currently unresolved glitches in my 64-bit HD AntiX v19.3 installation include:

1) It’s skipping the login screen, during boot-up.

2) It’s not retaining the modified resolution setting, forcing me to reset the resolution during every boot. A side effect of this, is that all my desktop launchers get moved & shuffled every time I reset the resolution. I’ve finally stopped trying to keep them in a rational order…

You see, the Precision’s native mode is 1920×1200 pixels. In that mode, the mouse pointer and text cursor become almost invisible via being so tiny & thin. However, when I switch to 1440×900, the mouse pointer becomes almost easy to find on the screen, and the cursor in LibreOffice Writer becomes wide & tall enough to see. (I think LOW is defining the cursor size as an absolute # of pixels.)

3) All of the launchers I’ve placed on the Space-icewm (my favorite) desktop are either directories or files I use frequently. But, I haven’t figured out how to make a desktop launcher to trigger the VeraCrypt I found on the web, dl’d, & installed.

4) As an alternative to #3, I haven’t figured out yet, how to program the boot sequence to include launching VeraCrypt at startup.

Although it’s got its shortcomings, I’m quite grateful that I have AntiX to work with. Thank you!

• This topic was modified 1 year, 6 months ago by scruffyeagle. Reason: Adding info

[Anonymous]

Er, I meant, I also use AntiX live system for external works at times.
With the USB I have to unmount /live/iso-file and /live/iso-dev manually with sudo always after booting.
Could this make any kind of harm to the USB at long term?

Thanks.

[Moderator BobC]

Use the Forum >> Search >> for multiboot or ventoy.

Be sure to read skidoo’s post on the subject.

I had better luck with ventoy than multiboot USB but your experiences might vary.

I finally resorted to having a large partition on my system that holds many ISO files and just use Live USB Maker from the control panel to write a fresh (likely reused) 3.0 USB flashdrive when I want to test something on a distro.

[Member marcelocripe]

Hello ctcx.

… but I was wondering if there was a chance a more “native”, or “manual” way, to do this on Linux.

The closest I could do to the title of your topic was with Ventoy, in the topic “How to Create Bootable Pendrive Using Ventoy“. The topic is in Portuguese language, try to translate to your language with the help of internet translators and check if something might be useful for you.
I have not yet been able to find a program that will allow me to create on bootable DVD media containing multiple antiX ISO images.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá ctcx.

… but I was wondering if there was by chance a more “native”, or “manual” way, to do this on Linux.

O mais próximo que eu consegui fazer do título do seu tópico foi com o Ventoy, no tópico “Como Criar Pendrive Inicializável Usando o Ventoy“. O tópico está em idioma Português, tente traduzir para o seu idioma com o auxílio dos tradutores da internet e verifique se algo possa ser útil para você.
Eu ainda não consegui encontrar um programa que me permita criar em uma mídia de DVD inicializável contendo várias imagens ISOs do antiX.

marcelocripe
(Texto original em idioma Português do Brasil)

[Member Xecure]

I never use CD or ISO, not even on multiboot USB, so I cannot give any good advice.

When in the live boot menus, if you use the boot option
mount=off
with toram, does anything change in fstab at all? It is supposed to disable any mounting during the booting process, but I don’t know how compatible it is with the toram option.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.