Search Results for 'boot from iso'

[Member eric]

Ok i found the trouble. The slim service made by the script was not correct and stuck the service database. So, i post again the script, it should works as expected now

#!/bin/bash

#antix from full iso

TMP="/tmp/install"

skalibs_tag="v2.10.0.0"
execline_tag="v2.7.0.0"
s6_tag="v2.10.0.0"
s6_rc_tag="v0.5.2.1"
oblibs_tag="v0.1.3.0"
_66_tag="v0.6.1.1"
_66_tools_tag="v0.0.7.1"
s6_linux_utils_tag="v2.5.1.4"
s6_portable_utils_tag="v2.2.3.1"

flags_path=(

    --prefix=/usr
    --libexecdir=/usr/libexec
    --bindir=/bin
    --shebangdir=/bin
    --sbindir=/sbin
    --enable-shared
    --disable-allstatic
    --disable-static
)

# lowdown package doesn't exist on Antix, so do not try to build
# the documentation

_sed_lowdown() {

    sed 's:^LOWDOWN.*$::' -i ${1}
}

prepare_build() {
    apt update || return 1
    apt install git || return 1
    apt install build-essential || return 1

    mkdir ${TMP}
}

## skalibs
build_skalibs() {

    cd ${TMP}

    git clone https://github.com/skarnet/skalibs

    cd skalibs

    git checkout tags/"${skalibs_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## execline
build_execline() {

    cd ${TMP}

    git clone https://github.com/skarnet/execline

    cd execline

    git checkout tags/"${execline_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## s6
build_s6() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6

    cd s6

    git checkout tags/"${s6_tag}"

    ./configure ${flags_path[@]} --with-dynlib=/usr/lib/execline

    make clean

    make install || return 1
}

## s6-rc
build_s6_rc() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6-rc

    cd s6-rc

    git checkout tags/"${s6_rc_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## s6-linux-utils
build_s6_linux-utils() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6-linux-utils

    cd s6-linux-utils

    git checkout tags/"${s6_linux_utils_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## s6-portable-utils
build_s6_portable-utils() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6-portable-utils

    cd s6-portable-utils

    git checkout tags/"${s6_portable_utils_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## oblibs
build_oblibs() {

    cd ${TMP}

    git clone https://framagit.org/obarun/oblibs

    cd oblibs

    git checkout tags/"${oblibs_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## 66
build_66() {

    cd ${TMP}

    git clone https://framagit.org/obarun/66

    cd 66

    _sed_lowdown Makefile

    git checkout tags/"${_66_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1

}

## 66-tools
build_66-tools() {

    cd ${TMP}

    git clone https://framagit.org/obarun/66-tools

    cd 66-tools

    _sed_lowdown Makefile

    git checkout tags/"${_66_tools_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

cp_skeleton() {
    cp -f /etc/66/{init,halt,reboot,poweroff,shutdown} /sbin/ || return 1
    sed 's:^66-boot.*$:66-boot -m:' -i /sbin/init
}

prepare_boot() {

    cd ${TMP}

    git clone https://framagit.org/pkg/obmods/boot-66serv

    cd boot-66serv

    _sed_lowdown Makefile

    ./configure

    make install || return 1

}

build_tree() {

    ## don't crash here in case of multiple use of the script
    66-tree -n boot

    66-enable -t boot boot@system || return 1

    BOOT_CONF="$(readlink /etc/66/conf/boot@system/version)"

    cp "${BOOT_CONF}/.boot@system" "${BOOT_CONF}/boot@system" || return 1

    66-env -t boot -r 'CGROUPS=!no' boot@system || return 1

    66-enable -F -t boot boot@system || return 1

    dd if=/dev/urandom of=/var/lib/random-seed count=1 bs=512 status=none || return 1

}

build_tree_root() {

    66-tree -cnE root

    exec 3>&1 1>/etc/66/service/slim
cat <<EOF
[main]
@type = longrun
@version = 0.0.1
@description = "Slim daemon"
@user = ( root )

[start]
@execute = ( slim -nodaemon )

EOF
    exec 1>&3 3>&-

    66-enable slim
}

_run() {

    if ! ${1} ; then
        printf "%s\n" "unable to ${2} ${1#*_}"
        exit 1
    fi
}

## do it

_run prepare_build "install"
_run build_skalibs "skalibs"
_run build_execline "execline"
_run build_s6 "s6"
_run build_s6_rc "s6-rc"
_run build_s6_linux-utils "s6-linux-utils"
_run build_s6_portable-utils "s6-portable-utils"
_run build_oblibs "oblibs"
_run build_66 "66"
_run build_66-tools "66-tools"

cd ${TMP}

_run cp_skeleton "copy"

# build and remove a dummy tree to have the /usr/share/66 created
66-tree -n dummy
66-tree -R dummy
_run prepare_boot "build"
_run build_tree "build"
_run build_tree_root "build"

# reboot of the machine
66-hpr -r -f

I saw that Antix rely on elogind. You can make a service for it easily.

Create the file /etc/66/service/elogind with:

[main]
@type = longrun
@version = 0.0.1
@description = "elogind daemon"
@user = ( root )

[start]
@execute = ( elogind )

[stop]
@execute = ( s6-rmrf ${pid_file} )

[environment]
pid_file=!/run/elogind.pid

I don’t know if its works or not on Antix. Not tested. Maybe a dependency to dbus need to be made?!?.

Note: usually distro install the services at /usr/share/66/service and sysadmin install it at /etc/66/services. The /etc/66/services take precedence over /usr/share/66/service.

So, now to enable it
# 66-enable elogind

and to start it
# 66-start elogind

Also, to configure your boot you can use

# 66-env -t boot -e mcedit boot@system

Change what you want and enable it again to apply the changes

# 66-enable -t boot -F boot@system

To reboot the machine correctly

sudo 66-shutdown -r now

To power off the machine correctly

sudo 66-shutdown -p now

Enjoy 🙂

• This reply was modified 2 years, 2 months ago by eric.
• This reply was modified 2 years, 2 months ago by eric.
• This reply was modified 2 years, 2 months ago by eric.

[Member dshoover54]

Special shout out to BobC and Xecure, and his reference to Xecure pseudo-antix19.3.iso work and link. I used rufus to burn iso. Reboot into ISO menu. GUI and text mode options left me staring at the same Black screen, again. Next I tried advance and option for lower resolution (1024 / 780). ALL GOOD.

Started LIVE session and I had no trouble with install to SSD partition.

I’ve really enjoyed Antix over the years, so this is a big win for me.

[Member eric]

I installed Antix on a VM from the antiX-19.2_x64-full.iso

I modified the /etc/apt/sources.list.d/antix.conf to get a correct repo.

then i launched this script below.

It install all the necessary things and reboot the machine, easy peasy!

I didn’t did any more test but surely some adjustment need to be made for Antix policies. Anyway, the machine boot correctly and launch the X with slim.

#!/bin/bash

#antix from full iso

TMP="/tmp/install"

skalibs_tag="v2.10.0.0"
execline_tag="v2.7.0.0"
s6_tag="v2.10.0.0"
s6_rc_tag="v0.5.2.1"
oblibs_tag="v0.1.3.0"
_66_tag="v0.6.1.1"
_66_tools_tag="v0.0.7.1"
s6_linux_utils_tag="v2.5.1.4"
s6_portable_utils_tag="v2.2.3.1"

flags_path=(

    --prefix=/usr
    --libexecdir=/usr/libexec
    --bindir=/bin
    --shebangdir=/bin
    --sbindir=/sbin
    --enable-shared
    --disable-allstatic
    --disable-static
)

# lowdown package doesn't exist on Antix, so do not try to build
# the documentation

_sed_lowdown() {

    sed 's:^LOWDOWN.*$::' -i ${1}
}

prepare_build() {
    apt update || return 1
    apt install git || return 1
    apt install build-essential || return 1

    mkdir ${TMP}
}

## skalibs
build_skalibs() {

    cd ${TMP}

    git clone https://github.com/skarnet/skalibs

    cd skalibs

    git checkout tags/"${skalibs_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## execline
build_execline() {

    cd ${TMP}

    git clone https://github.com/skarnet/execline

    cd execline

    git checkout tags/"${execline_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## s6
build_s6() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6

    cd s6

    git checkout tags/"${s6_tag}"

    ./configure ${flags_path[@]} --with-dynlib=/usr/lib/execline

    make clean

    make install || return 1
}

## s6-rc
build_s6_rc() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6-rc

    cd s6-rc

    git checkout tags/"${s6_rc_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## s6-linux-utils
build_s6_linux-utils() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6-linux-utils

    cd s6-linux-utils

    git checkout tags/"${s6_linux_utils_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## s6-portable-utils
build_s6_portable-utils() {

    cd ${TMP}

    git clone https://github.com/skarnet/s6-portable-utils

    cd s6-portable-utils

    git checkout tags/"${s6_portable_utils_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## oblibs
build_oblibs() {

    cd ${TMP}

    git clone https://framagit.org/obarun/oblibs

    cd oblibs

    git checkout tags/"${oblibs_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

## 66
build_66() {

    cd ${TMP}

    git clone https://framagit.org/obarun/66

    cd 66

    _sed_lowdown Makefile

    git checkout tags/"${_66_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1

}

## 66-tools
build_66-tools() {

    cd ${TMP}

    git clone https://framagit.org/obarun/66-tools

    cd 66-tools

    _sed_lowdown Makefile

    git checkout tags/"${_66_tools_tag}"

    ./configure ${flags_path[@]}

    make clean

    make install || return 1
}

cp_skeleton() {
    cp -f /etc/66/{init,halt,reboot,poweroff,shutdown} /sbin/ || return 1
    sed 's:^66-boot.*$:66-boot -m:' -i /sbin/init
}

prepare_boot() {

    cd ${TMP}

    git clone https://framagit.org/pkg/obmods/boot-66serv

    cd boot-66serv

    _sed_lowdown Makefile

    ./configure

    make install || return 1

}

build_tree() {

    ## don't crash here in case of multiple use of the script
    66-tree -n boot

    66-enable -t boot boot@system || return 1

    BOOT_CONF="$(readlink /etc/66/conf/boot@system/version)"

    cp "${BOOT_CONF}/.boot@system" "${BOOT_CONF}/boot@system" || return 1

    66-env -t boot -r 'CGROUPS=!no' boot@system || return 1

    66-enable -F -t boot boot@system || return 1

    dd if=/dev/urandom of=/var/lib/random-seed count=1 bs=512 status=none || return 1

}

build_tree_root() {

    66-tree -cnE root

    exec 3>&1 1>/etc/66/service/slim
cat <<EOF
[main]
@type = oneshot
@version = 0.0.1
@description = "Slim daemon"
@user = ( root )

[start]
@execute = ( slim )

EOF
    exec 1>&3 3>&-

    66-enable slim
}

_run() {

    if ! ${1} ; then
        printf "%s\n" "unable to ${2} ${1#*_}"
        exit 1
    fi
}

## do it

_run prepare_build "install"
_run build_skalibs "skalibs"
_run build_execline "execline"
_run build_s6 "s6"
_run build_s6_rc "s6-rc"
_run build_s6_linux-utils "s6-linux-utils"
_run build_s6_portable-utils "s6-portable-utils"
_run build_oblibs "oblibs"
_run build_66 "66"
_run build_66-tools "66-tools"

cd ${TMP}

_run cp_skeleton "copy"

# build and remove a dummy tree to have the /usr/share/66 created
66-tree -n dummy
66-tree -R dummy
_run prepare_boot "build"
_run build_tree "build"
_run build_tree_root "build"

# reboot of the machine
66-hpr -r -f

• This reply was modified 2 years, 2 months ago by eric.
• This reply was modified 2 years, 2 months ago by eric.

[Member seaken64]

I’ve read in this thread a couple of times. Maybe I didn’t follow everything being said or suggested. But isn’t the issue often raised that new users have only one computer running an older version of Windows, like maybe XP or Vista? And maybe they have only one USB key and do not have experience with creating live bootable devices?

They want to try antiX but can’t quite follow the instructions, or maybe don’t have internet access to download a copy of Rufus and the antiX ISO. They can’t get access to Live USB Maker yet, until after they get antiX booted somehow. To a newbie this is a catch-22. Need to use Live USB Maker to make a Live antiX bootable persistant USB but can’t boot antiX to use said Live USB Maker.

In the old days (a little over a year ago) one could purchase a LiveCD/LiveDVD with antiX on it. Or, if they didn’t have an optical drive they could purchase a LiveUSB with antiX on it. But now it has to be downloaded? as an ISO and then “burned” or “made” into a LiveCD/LiveDVD/LiveUSB. What if that person does not have the internet? Or if they only have a smart phone?

How can we help make it easier for these folks to try out antiX? Is that the question?

If they do have reliable internet then it seems the best path is to download Rufus and the antix ISO and create LiveUSB that will boot in their Windows computer. Then use Live USB Maker to create a full featured antiX LiveUSB.

If they do not have good internet can we make it easier to purchase/share a LiveCD/DVD/USB created by someone else? Can we make a version of the ISO that can be launched from Windows?

If a person can figure out how to create bootable Live CD/DVD/USB then what difference does it make if they use Ventoy, belanaEtcher or Rufus? Is there going to be a different outcome in being able to run Live USB Maker after live antiX boots? (I really don’t know, will a non-Rufus tool disable the ability of LUM?) I previously used LinuxLive in Vista/Win7 to create bootable USB drives. It worked to get me started until I learned of other ways. Before that I used ImgBurn to create bootable CD/DVD’s. I also used VirtualBox in Windows to create a virtual antiX machine and created bootable USB’s from there.

I have tried Ventoy and bellenaEtcher, etc. But I would not recommend them over Rufus in Windows or LUM in antiX. But if someone can be successful using these tools to create a bootable antiX USB then they should be good to go. And I have often used Plop successfully on old equipment just to “boot” from USB. Once I have antiX “live” I use LUM to create a new Live USB. But I am not typical. I have access to a lot of computers and high speed internet and multiple USB keys, etc. But what if I only have an old Windows XP computer and no (or poor) internet connection? I can see that being a challenge.

Seaken64

[Anonymous]

But the point is that this problem is probably with more than one package, and it will get more common with newer packages.

Let’s park the “probably”.
The devuan project Devuan currently maintains only 118 packages.
https://gitea.devuan.dev/devuan?page=8
I say “only” because
1) this total is less than when previously checked (back a few years when updating the nosystemd.org wiki)
2) many casual users falsely believe Devuan has “rescued” a huge number of systemd-tainted packages

.
Of those 118 packages, 60 are related to devuan infrastructure or are otherwise unuseful uninteresting to anyone running a desktop, non-devuan, system:
linux-raspi
linux-sunxi
devuan-baseconf
pkgsel
unattended-upgrades
devuan-keyring
www.devuan.org (web docs packagename)
documentation (was devuan-doc)
infrastructure_doc
installer-iso
gitea.devuan.dev (web assets)
clearlooks-phenix-lightpurpy-theme
clearlooks-phenix-darkpurpy-theme
clearlooks-phenix-purpy-theme
darkpurpy-icon-theme
clearlooks-phenix-cinnabar-theme
cinnabar-icon-theme
devuan-lintian-profile
choose-mirror
choose-init
live-build
openstack-devuan-images
pdns-recursor
debootstrap
base-files
apt-setup
net-tools
reportbug
rootskel-gtk
anna
base-installer
lsb
ltsp
ltspfs
ldm
pcsc-lite
ansible-role-nginx
jenkins-debian-glue
releasebot
jessie-support
cryptsetup-modified-functions
desktop-base
389-ds-base
tellpackage
debian-installer
gitea-spammerblock
sacc
dak
tasksel
sanity
britney2
main-menu
popularity-contest
distro-info-data
devuan-sanity
debian-config-override
amprolla3
pinthread
rrqnet

.
Another 30 or so packages are unappealing (same/older versions, or lesser functionality) compared to packages available via antiX repo or MX Linux repo:
refractasnapshot-base
refractasnapshot-gui
refractainstaller-gui
refractainstaller-base
xfce4-session
xfce4-systemload-plugin
xfce4-settings
xfce4-panel
plymouth
lightdm
dbus
policykit-1
cowdancer
xlennart
rsyslog
bash-completion
firejail
util-linux
valgrind
procps
apt
gpsd
colord
consolekit2 (deprecated, unneeded in antiX 19)
udev (unneeded in antiX 19)
libvirt
sysvinit
gdisk
cups
slim
apulse
elogind
eudev

Having discounted the above, only a short “shortlist” remains. Notes-to-self from my recent check show the following as the only noteworthy packages “of possible interest”:

dnscrypt-proxy
fontsnaps (for xfce-4)
gvfs
init-system-helpers
iwd
meson
net-tools
network-manager
openvpn
packagekit
pulseaudio
python3-fusepy
seatd (nascent project, elogind alternative)
setnet
sshguard
surf2
tomcat9
udisks2
upower
vdev
wicd
lxc-templates
cgroupfs-mount
cgmanager

[Member Dzhigit]

andyprough wrote:

Thanks for the info. I did have trouble with networking, particularly wireless. I added the Devuan iwd package, and now I can get networking by killing and restarting NetworkManager, and wireless by running the ‘wifi on’ command. Not sure if iwd was a help for that at all or not, but suddenly I can get it working whereas before I could not.

https://wiki.debian.org/NetworkManager/iwd
There are some steps to use iwd as the backend for network-manager.

andyprough wrote:

So far, what works is that iso-snapshot-antix and live-usb-maker installed on Devuan with some dependencies including antix-libs, antix-viewer, cli-shell-utils, iso-template-antix, live-usb-maker-gui-antix, and remaster-antix. I also installed format-usb, and from the Devuan repo I installed lockfile-progs to allow antiX persistence to work. All these programs seem to work on Devuan as they would on antiX.

Devuan boots from the antiX boot screen, and root persistence works, and saving persistence works. That’s what I’ve tested. I tried to do a frugal install but I’m getting a failure message. I’ll try again and copy the failure message to this thread. Hopefully it’s just a missing package. If anyone knows a package I should install to try getting frugal install working, please leave a comment for me.

Wow, thanks for the info! I will download antiX-net ISO and try changing to Devuan repos.

• This reply was modified 2 years, 2 months ago by Dzhigit.
• This reply was modified 2 years, 2 months ago by Dzhigit.

[Member andyprough]

Dzhigit wrote:

Unfortunately some newer Debian packages do not have LSB init scripts. For example, Intel’s iwd, a replacement for wpasupplicant, works very nicely with connman. Devuan tries to add scripts to these packages, and it did so in the case of iwd. So, I am also curious about antiX with Devuan repos. Will look in to it.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966518

Thanks for the info. I did have trouble with networking, particularly wireless. I added the Devuan iwd package, and now I can get networking by killing and restarting NetworkManager, and wireless by running the ‘wifi on’ command. Not sure if iwd was a help for that at all or not, but suddenly I can get it working whereas before I could not.

So far, what works is that iso-snapshot-antix and live-usb-maker installed on Devuan with some dependencies including antix-libs, antix-viewer, cli-shell-utils, iso-template-antix, live-usb-maker-gui-antix, and remaster-antix. I also installed format-usb, and from the Devuan repo I installed lockfile-progs to allow antiX persistence to work. All these programs seem to work on Devuan as they would on antiX.

Devuan boots from the antiX boot screen, and root persistence works, and saving persistence works. That’s what I’ve tested. I tried to do a frugal install but I’m getting a failure message. I’ll try again and copy the failure message to this thread. Hopefully it’s just a missing package. If anyone knows a package I should install to try getting frugal install working, please leave a comment for me.

The toram option didn’t work the first time I tried it. I’ll mess around with that a bit more, I didn’t put any effort into it.

The nice thing was that ISO Snapshot copied everything, down to my wifi password and my browser extensions. antiX has turned the entirety of my Devuan desktop into a Live USB with persistence, which is very awesome.

UPDATE – frugal and toram not working were my fault. I had too little ram for toram and I needed to reformat my frugal partition for the frugal install.

• This reply was modified 2 years, 2 months ago by andyprough.

[Forum Admin rokytnji]

Beating a dead horse. LQ members sig. I kinda like what he says about ventoy in his sig.

Ancient Warrior
I Recommend Debian or a spinoff for home, RHEL for business
I recommend E2B for USB booting to run or install ISO images
https://www.easy2boot.com/download/
https://www.easy2boot.com/make-an-easy2boot-usb-drive/
I own no stock in E2B, it just answers a regularly recurring question.
I boot both Linux and Windows ISOs, and for both traditional and UEFI installation.
I suggest Ventoy https://www.ventoy.net/en/index.html for less complex USB key situations.

The less complex is a very good bye.

• This reply was modified 2 years, 2 months ago by Brian Masinick.
• This reply was modified 2 years, 2 months ago by Brian Masinick.

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]

the antiX tools could just be dropped in so simply to another distro and still retain all the functions.

careful, that’s an overly broad inference. Some of the tools absolutely cannot “just be dropped in”.

The appimage version of live-usb-maker distributed by MX Linux, it can be used ala MintStick (“dd mode”) in other distros.

Usage of { isosnapshot, live-remaster, live-usb-maker, live-kernel-updater } will require, for instance:

‣ adding antiX repository, if compatible (??? Devuan “beowulf” <–> antiX19 <–> Debian ‘buster”)
or retrieving the source code of the various dependent “moving parts” and repackinging for the other distro.

‣ unpacking the initrd.gz, customizing its content to suit the other distro, and repacking. (ref: /usr/local/lib/cli-shell-utils/bin/unpack-initrd or /usr/local/bin/ps_initrd.sh)

edited to add:

Someone can chime in if I’ve missed anything, but at a minimim the list of “moving parts” includes:

remaster-antix (depends: antix-libs)
live-usb-maker (depends: cli-shell-utils and others)
live-kernel-updater (depends: cli-shell-utils)
iso-snapshot-antix (depends: iso-template-antix, remaster-antix, antix-viewer and others)
iso-template-antix
antix-libs
cli-shell-utils
antix-gfxboot
-=-
squashfs-tools
syslinux-utils
xorriso

additional edit:

antiX kernels include fbcondecor patch. Several of the “moving parts” listed above probably expect, if not require, components provided by the “fbsplash-antix” package.

[Member marcelocripe]

I thank everyone for their explanations. Especially the details that helped me understand a little more about Live USB Maker (olsztyn), about PLoP (Xecure) and the alternative through a smartphone (ModdIt).

We have to remember about some conditions:

1-User finds a video on Youtube about antiX or on a website.
2-“Live USB Maker.AppImage” does not work on Windows and does not work on all Linux distributions. Some Linux distributions that I tested, do not run programs/files in “.AppImage” format.
3-Back to the user coming from Windows, this person does not know what is a persistence in USB devices.
4-Can we indicate which or which programs for this user to prepare the bootable pendrive in Windows?
5-If we indicate Rufus and it does not work at the motherboard startup of this user, it will certainly blame antiX. This happened to me, I know that antiX is not to blame, so I kept looking for another program that could boot on most motherboards. Mr. Brian, kindly referred me to ventoy and this program worked to install antiX on most computers that I tested, so much so that it motivated me to create a topic on how to use ventoy. But when it doesn’t work with ventoy, unfortunately the program that worked best was precisely the one I didn’t like, balenaEtcher. What I liked most was the flexibility and facilities offered by ventoy regarding the replacement of ISOs to be installed hard disk.

My opinion is that we need to help people solve problems and difficulties. Rather than creating more and more problems, if we do that, people will surely give up before they can see antiX working.

After a long time in the spam box, the Matheus post is available, according to him , used Yumi and luckily antiX was installed on the computer hard drive. Okay, now we can start explaining to him about persistence. I, for example, have no knowledge of antiX persistence, so I cannot help others on this topic. Fortunately we have other topics about persistence in antiX Live USB (https://www.antixforum.com/forums/topic/live-architecture-of-antix-can-be-applied-to-other-linux-distros/).

Even after reading the MX Linux forum thread, there were more questions than answers:

6-If it is not to “recommend” the use of ventoy and balenaEtcher, what other option for the Windows user when Rufus does not work?

7-Skidoo, what is your conclusion on this topic and the MX Linux forum topic?

I thank everyone for sharing their knowledge.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Eu agradeço a todos por suas explicações. Em especial aos detalhes que me ajudaram a compreender um pouco mais sobre o Live USB Maker (olsztyn), sobre o PLoP (Xecure) e da alternativa através de um smartphone (ModdIt).

Temos que nos lembrar sobre algumas condições:

1-Usuário encontra um vídeo no Youtube sobre o antiX ou em um site.
2-O “Live USB Maker.AppImage” não funciona no Windows e não funciona em todas as distribuições Linux. Algumas distribuições Linux que eu testei, não executam programas/arquivos em formato “.AppImage”.
3-De volta ao usuário vindo do Windows, esta pessoa não sabe o que é uma persistência em dispositivos USBs.
4-Podemos indicar qual ou quais programas para este usuário preparar o pendrive inicializável no Windows?
5-Se indicarmos o Rufus e ele não funcionar na inicialização da placa-mãe deste usuário, certamente irá culpar o antiX. Isso aconteceu comigo, eu sei que a culpa não é do antiX, então eu continuei procurando outro programa que conseguisse inicializar na maioria das placas-mãe. O sr. Brian, gentilmente me indicou o ventoy e este programa funcionou para fazer a instalação do antiX na maioria dos computadores que eu testei, tanto que me motivou a criar um tópico sobre o como usar do ventoy. Mas quando não funciona com o ventoy, infelizmente o programa que melhor funcionou foi justamente aquele que eu não gostei, o balenaEtcher. O que eu mais gostei foi da flexibilidade e das facilidades oferecidas pelo ventoy quanto a substituição das ISOs para serem instaladas disco rígido.

A minha opinião é que precisamos ajudar as pessoas a resolverem os problemas e as dificuldades. Ao invés de criar mais e mais problemas, se fizermos isso, certamente as pessoas irão desistir antes de conseguir ver o antiX funcionando.

Após muito tempo na caixa de spam, a postagem do Matheus está disponível, segundo ele, utilizou o Yumi e felizmente o antiX foi instalado no disco rígido computador. Pronto, agora sim podemos começar a explicar para ele sobre persistência. Eu, por exemplo, não possuo conhecimentos sobre persistência do antiX, então, eu não posso ajudar outras pessoas sobre este tema. Felizmente temos outros tópicos sobre persistência em Live USB do antiX (https://www.antixforum.com/forums/topic/live-architecture-of-antix-can-be-applied-to-other-linux-distros/).

Mesmo após a leitura do tópico do fórum do MX Linux, ficaram mais dúvidas do que respostas:

6-Se não é para “recomendar” o uso de ventoy e do balenaEtcher, qual outra opção para o usuário do Windows quando o Rufus não funcionar?

7-Skidoo, qual é a sua conclusão sobre este tópico e o tópico do fórum do MX Linux?

Eu agradeço a todos por compartilharem os seus conhecimentos.

marcelocripe
(Texto original em Português do Brasil)

[Anonymous]

facts that I am confident are known to antiX developers:
Live/Frugal antiX architecture can be applied to other distros as well, having tested so far on some Debian derivatives with the following results:
– ISO-Snapshot of antiX appears to work well on other distros once installed with appropriate dependencies.
– Resulting ISO can be processed into Live-USB using Live-USB-Maker.
– Such created Live-USB is an antiX-packaged ‘other’ distro squashed into linuxfs. It boots with antiX Live menu along with typical options such as setting persistence and/or Frugal installation of the ‘other’ distro on hard drive. When booting Live it continues with antiX boot scheme, until un-squashing linuxfs and starts booting the ‘other’ distro, although initially with message ‘antiX 17 Live (generic)’, but such message can be changed appropriately…
– Such ‘other’ distro can be installed or Frugal-installed and such Frugal instance of the ‘other’ distro can be configured with persistence modes per antiX Live architecture.

Well, I am NOT confident the developers are aware of all those things you’ve mentioned.
I suspect they are busy being busy, doing what they do, knowing what they know.
Via your extensive experimentation/observation, olsztyn, you have become one of experts of this niche.

Wannabe cross-pollinators like you and I, we are probably both blessed, and cursed (at).
BusterDog ships a cool mkqsuashfs GUI utility that even enables a user to choose the compression method to be applied. Yet when you notice such a thing and mention it to “across the pond” others… the comfy-in-their-own-pond others are likely to shrug and utter “meh, sqoosheffess, who would wanna mess with those!?!”

> Since you speak as an antiX Moderator
> therefore I take your word as an official word of antiX strategy management,

Naw, the forum moderators here are just helperbots, not policymakers. Maybe your face doesn’t realize it, but even loudmouth skidoo served a yearlong stint as moderator here. Ah, retirement ~~ still a loudmouth, but without the risk of mis-representing the fine “official” folks whenever I’m compelled to call a potatohead a potatohead.

Please let me know (antiX developers and/or owner) if this topic should not be continued any further…
First, I want to again emphasize that IMHO Live/Frugal architecture developed in antiX is far superior in design to anything I encountered out there. This meaans something about genius of antiX developers… I did play with linux-live.org of Tomas-M, which sounded very good and general across Linux but so far I have not been successful enough in making it work for me. In addition, examining how live file system is packaged, I still think that the way antiX Live/Frugal is architected to package into squashed fs linuxfs file is more general than SBs implemented by Linux-Live.org.
Having said that I just want to bring up some facts that I am confident are known to antiX developers:
Live/Frugal antiX architecture can be applied to other distros as well, having tested so far on some Debian derivatives with the following results:
– ISO-Snapshot of antiX appears to work well on other distros once installed with appropriate dependencies.
– Resulting ISO can be processed into Live-USB using Live-USB-Maker.
– Such created Live-USB is an antiX-packaged ‘other’ distro squashed into linuxfs. It boots with antiX Live menu along with typical options such as setting persistence and/or Frugal installation of the ‘other’ distro on hard drive. When booting Live it continues with antiX boot scheme, until un-squashing linuxfs and starts booting the ‘other’ distro, although initially with message ‘antiX 17 Live (generic)’, but such message can be changed appropriately…
– Such ‘other’ distro can be installed or Frugal-installed and such Frugal instance of the ‘other’ distro can be configured with persistence modes per antiX Live architecture.

All this means that Live architecture developed for antiX is more general and can be applied to other distros as well, along with it’s superior functionality.
Is this not something that Linux community could be made aware of such superiority of antiX Live architecture as applicable also to their respective distros?
Or rather it should be kept restricted to antiX and only for the benefit of antiX?
Just my two cents…

• This topic was modified 2 years, 2 months ago by olsztyn.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member Xecure]

It should just work after installing. I am not sure if you have to “unmount” the ISO after shutting down the VM before the next Boot, but installing should just work.

I haven’t used any of the programs you mention myself, but they should work the same for installing MX as for installing antiX.
Video using Virt-manager to install MX: https://www.youtube.com/watch?v=FoTLBGb6ls8

A question. Did you select to install GRUB during the installation process (no matter what it says, you NEED grub to boot into the OS)?

I only have experience with Virtualbox, so no idea if you need to set something extra before booting.

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

Hello all,

Everyone has been very helpful so far. I have now ditched the Ubuntu partition, dedicated Antix to said partition (dual booting with original Mac OS using Refind boot manager) and have installed the OS with all my settings from the backup iso using live USB creator.

The following has happened but not a major problem as can live with it:

1. During install (used minstall via terminal as booted from live USB) it went fine until the part where you had to create user accounts. As I already had this setup I created a dummy account called test gave it a pw and set the root pw. I then got error creating accounts. Not a major problem exited and system is installed on my HD and works with the accounts previously setup.

2. When trying to delete the snapshot folder after creating one it said i didn’t have permission to delete the folder from downloads (thats where I told it to output to). I got around that by right clicking and selecting rox as root.sh

3. The attached error message now appears when I login, no idea why or how to fix it just started doing it.

I am using the default repos as told the setup wizard to use those. Is this the best setup or are there better ones I should be using (I am UK based but didn’t choose London or Manchester). running Antix 19 Manolis Glezos on my 2008 Mac Mini

If anyone has any ideas or suggestions I would be grateful for your input

• This topic was modified 2 years, 2 months ago by Crashed Disk.
• This topic was modified 2 years, 2 months ago by Crashed Disk.

Attachments:

1. 

   screenshot.jpg
   

[Member olsztyn]

olsztyn wrote:

So, taking from this, as LUM has another input option to use ‘From Running System’ instead of ISO image, would this create a Live USB of the Linux system on which it is being executed?
I will be glad to test and confirm this but I think reaching out to our experts skidoo and possibly BitJam if still available would be more viable path to officially confirm…

Just to update, so I do not waste precious time of antiX experts:
The answer to my question appears to be negative. Executing Live USB Maker from a running Linux system makes the check box ‘From Running System’ grayed out (not selectable) unless the running system is itself an antiX Live instance. The only input option is the actual ISO.

anticapitalista wrote:

antiX devs have never recommended use of ventoy and balenaEtcher.

I appreciate this official declaration and elsewhere documentation that Rufus is the one recommended tool. However my experience taught me to be careful about Rufus as the one to be used based on these declarations. I had numerous experience that using Rufus on antiX ISO created by ISO-Snapshot to create a bootable antiX Live resulted in failure. Not that it did not boot at all but rather did not progress to far with options to retry or reboot, which led to the same. I remember vaguely that this happens on mismatch of boot files. USB created by balenaEtcher from the same ISO booted just fine and did not experience this issue. My understanding is this was happening to me when ISO-Snapshot was run on antiX Live system where kernel was changed from the original. I remember there was an explanation in this forum by BitJam about one and half year ago and such issue was regardless whether Rufus or Live-USB-Maker would be used on input created by ISO-Snapshot on antiX Live with updated kernel.
One way or the other, my point is that declaring Rufus vs. balenaEtcher as the one to use for antiX depends on certain conditions, which my experience exemplifies.
My extended point is however that the the topic of this thread by skidoo exposes a valid and more important issue that seems brushed aside by experienced Linux users, as certain Linux knowledge of the onboarding users is taken for granted. It is the lack of onboarding clarity I think that resulted in the question by Marcello, whether the itemized by Marcello procedure would work, after all…
Just MHO…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters