Search Results for 'boot from iso'

Hello all!
I’m very interested in trying out antiX but unfortunately I’ve been having a really hard time booting from a USB. No matter how I create bootable USBs they open onto the initial installation menu and then no matter what I pick just go to black and stay there.
I’ve tried both “antiX-17.4.1_x64-full.iso” and “antiX-19.4_x64-full.iso,” created on two different USB drives, from both Etcher (on Mac OSX system), Startup Disk Creator and the antiX Live USB creator. I can navigate in the menu to the Failsafe mode but that doesn’t change anything.
I’m wondering if maybe the graphics for my machine just isn’t loading? But I’m surprised I’m able to get the initial menu then.
First little bit of system information gleaned from lscpu below – I’m a pretty big Linux novice so let me know what other information you all might need!

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 44 bits physical, 48 bits
virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 8
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 23
Model: 96
Model name: AMD Ryzen 7 4700U with Ra
deon Graphics

Thank you!

[Member Bajingan]

The latest version (19.2)

System:
  Host: antix1 Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64 
  compiler: gcc v: 8.3.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.0-264-antix.1-amd64-smp 
  root=UUID=676125fb-0862-438d-b0d5-85714580c0ae ro quiet 
  Desktop: IceWM 2.3.4 dm: SLiM 1.3.6 
  Distro: antiX-19.4_x64-full Grup Yorum 20 May 2021 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: N/A 
  Chassis: Oracle Corporation type: 1 serial: N/A 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: N/A BIOS: innotek 
  v: VirtualBox date: 12/01/2006 
Battery:
  ID-1: BAT0 charge: 48.5 Wh condition: 50.0/50.0 Wh (100%) volts: 10.0/10.0 
  model: innotek 1 type: Unknown serial: N/A status: Unknown 
Memory:
  RAM: total: 995.3 MiB used: 575.5 MiB (57.8%) 
  RAM Report: message: No RAM data was found. 
PCI Slots:
  Message: No PCI slot data found. 
CPU:
  Topology: Single Core model: Intel Core i5-8250U bits: 64 type: MCP 
  arch: Kaby Lake family: 6 model-id: 8E (142) stepping: A (10) 
  microcode: N/A L2 cache: 6144 KiB bogomips: 3600 
  Speed: 1800 MHz min/max: N/A Core speed (MHz): 1: 1800 
  Flags: 3dnowprefetch abm aes apic avx avx2 clflush clflushopt cmov 
  constant_tsc cx16 cx8 de flush_l1d fpu fsgsbase fxsr ht hypervisor invpcid 
  invpcid_single kaiser lahf_lm lm mca mce md_clear mmx monitor movbe msr 
  mtrr nonstop_tsc nopl nx pae pat pcid pclmulqdq pge pni popcnt pse pse36 
  rdrand rdseed rdtscp rep_good sep sse sse2 sse4_1 sse4_2 ssse3 syscall tsc 
  vme x2apic xsave xtopology 
  Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
  Type: l1tf mitigation: PTE Inversion 
  Type: mds mitigation: Clear CPU buffers; SMT Host state unknown 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass status: Vulnerable 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Unknown: Dependent on hypervisor status 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: InnoTek Systemberatung VirtualBox Graphics Adapter 
  vendor: VMware driver: vboxvideo v: 6.1.20_Debian r143896 bus ID: 00:02.0 
  chip ID: 80ee:beef 
  Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
  alternate: vboxvideo resolution: 1366x663_vbox~N/A 
  OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.3.6 
  compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 
  v: kernel bus ID: 00:05.0 chip ID: 8086:2415 
  Sound Server: ALSA v: k4.9.0-264-antix.1-amd64-smp 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 chip ID: 8086:100e 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 08:00:27:69:fc:4a 
  IP v4: 10.0.2.15/24 scope: global broadcast: 10.0.2.255 
  IP v6: fe80::a00:27ff:fe69:fc4a/64 scope: link 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge 
  driver: piix4_smbus v: N/A port: d200 bus ID: 00:07.0 chip ID: 8086:7113 
  WAN IP: 115.178.248.106 
Drives:
  Local Storage: total: 15.00 GiB used: 5.57 GiB (37.2%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 15.00 GiB 
  block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  serial: VB4fa638c2-cad865d7 rev: 1.0 scheme: MBR 
  Optical-1: /dev/sr0 vendor: VBOX model: CD-ROM rev: 1.0  
  dev-links: cdrom,dvd 
  Features: speed: 32 multisession: yes audio: yes dvd: yes rw: none 
  state: running 
RAID:
  Message: No RAID data was found. 
Partition:
  ID-1: / raw size: 8.82 GiB size: 8.61 GiB (97.72%) used: 3.96 GiB (45.9%) 
  fs: ext4 block size: 4096 B dev: /dev/sda1 label: rootantiX19 
  uuid: 676125fb-0862-438d-b0d5-85714580c0ae 
  ID-2: /home raw size: 5.40 GiB size: 5.26 GiB (97.27%) 
  used: 1.62 GiB (30.8%) fs: ext4 block size: 4096 B dev: /dev/sda3 
  label: homeantiX uuid: 47dfee91-d1d9-4d03-98a4-3559d5eefed8 
  ID-3: swap-1 size: 768.0 MiB used: 400 KiB (0.1%) fs: swap 
  swappiness: 10 (default 60) cache pressure: 50 (default 100) 
  dev: /dev/sda2 label: swapantiX uuid: 8a55e19c-4856-43c2-93f1-47194ea51746 
Unmounted:
  Message: No unmounted partitions found. 
USB:
  Hub: 1-0:1 info: Full speed (or root) Hub ports: 12 rev: 2.0 
  speed: 480 Mb/s chip ID: 1d6b:0002 
  Hub: 2-0:1 info: Full speed (or root) Hub ports: 12 rev: 1.1 
  speed: 12 Mb/s chip ID: 1d6b:0001 
  Device-1: 2-1:2 info: VirtualBox USB Tablet type: HID 
  driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 12 Mb/s 
  chip ID: 80ee:0021 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://kartolo.sby.datautama.net.id/mx-packages/antix/buster buster main nonfree nosystemd
  Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
  1: deb http://deb.debian.org/debian buster-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.sg.debian.org/debian/ buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.sg.debian.org/debian/ buster main contrib non-free
  2: deb http://security.debian.org/ buster/updates main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list 
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes:
  CPU top: 5 
  1: cpu: 12.2% command: firefox-esr pid: 1711 mem: 194.7 MiB (19.5%) 
  2: cpu: 2.5% command: firefox-esr pid: 1634 mem: 315.8 MiB (31.7%) 
  3: cpu: 0.4% command: xorg pid: 381 mem: 70.4 MiB (7.0%) 
  4: cpu: 0.3% command: conky pid: 741 mem: 9.82 MiB (0.9%) 
  5: cpu: 0.3% command: firefox-esr pid: 1755 mem: 141.0 MiB (14.1%) 
  Memory top: 5 
  1: mem: 315.8 MiB (31.7%) command: firefox-esr pid: 1634 cpu: 2.5% 
  2: mem: 194.7 MiB (19.5%) command: firefox-esr pid: 1711 cpu: 12.2% 
  3: mem: 141.0 MiB (14.1%) command: firefox-esr pid: 1755 cpu: 0.3% 
  4: mem: 134.0 MiB (13.4%) command: firefox-esr pid: 1867 cpu: 0.0% 
  5: mem: 123.8 MiB (12.4%) command: firefox-esr pid: 1813 cpu: 0.1% 
Info:
  Processes: 138 Uptime: 13h 10m Init: SysVinit v: 2.93 runlevel: 5 
  default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash (su) v: 5.0.3 
  running in: roxterm inxi: 3.0.36 

[Moderator christophe]

Xecure wrote:

Also, on Legacy Boot, F8 menu (save boot changes) selecting the legacy kernel doesn’t work (at least on my tests). Could anyone else check if this also happens to them?

I see that (on my system) the F8 menu saves the changes to Grub menu, but the syslinux/isolinux doesn’t remember them.

I am experiencing this also when booting from live-USB & frugal-from-USB via F5 key. F8 does not save as expected, using syslinux/isolinux, with legacy bios. This is testing on bare metal, not VM.

confirmed antiX frugaler, since 2019

[Member Xecure]

@calciumsodium, thanks for testing. I am glad it is working OK now. This ISO is just a test to see if everything can live together, so that people are not forced to switch (and even if they have both slim/slimski or spacefm/zzzfm installed it should still work without the user noticing anything). The final ISO should only have one of each.

@anticapitalista, no idea what skidoo wanted for slimski, but the original SLiM (Simple Log-in Manager), makes sense if you know the meaning behind it. I would leave slimski as it is, a lowercase words (Or maybe first letter upper-case), but it no longer has any meaning.

About the multiple space-<wm> entries, I think we could remove them from each desktop-defaults-<wm>-antix package and move them all to desktop-defaults-spacefm-antix. So, if spacefm is removed, it will also remove the xsessions .desktop entries. That is what I finally decided for zzzfm (they are included in desktop-defaults-zzzfm-antix). It is not the best solution (as files would still remain even when removing a window manager), but the best I could come up with. I may modify desktop-session-antix to also filter out missing window managers from the final session list.

I have sent merge requests for:

https://gitlab.com/antiX-Linux/gazelle-installer
https://gitlab.com/antiX-Linux/antix-goodies
https://gitlab.com/antiX-Linux/desktop-session-antix
https://gitlab.com/antiX-Linux/Build-iso

The last one is optional, and only a hint to possible changes. The most important one is slimski.local.conf, injected directly when creating the sqfs folder.
I was going to send a merge request for antix-gfxboot, but I see there are a lot of translated files, and I am not sue if replacing all the “space-<wm>” options for “zzzfm-<wm>” will break the translations. Also, the min-<wm> option command should change to minimal-<wm> so that they work with slimski, but I find I may cause the same translation breakage. If you don’t mind it, I will send the merge request for them. Let me know.

The extra packages needed are:

https://gitlab.com/antix-contribs/slimski
https://gitlab.com/antix-contribs/zzzfm
https://gitlab.com/antix-contribs/desktop-defaults-zzzfm-antix
https://gitlab.com/antix-contribs/slimski-themes-extras-antix

Those would be the only new packages needed for switching from antiX 19 to 21 and should be optional (they should not install if the user doesn’t want to make the switch). The update in antix-goodies for switching login-manager should create a slimski.local.conf when missing, but slimski would still work without that file and all the other modifications too.

Let me know if there is something missing.

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

[Member Xecure]

New ISO with fixes for most problems explained before except for installer (cannot figure out how to build).
* I have removed some programs like libreoffice to make it lighter (around 1.3 GBs)
* I couldn’t get virtualbox-guest-* to work properly (getting 100% CPU use) so I am not including them in the ISO.
* Grub desktop menus fixed (zzz-<wm> desktop options replace the original space-<wm>)
* Included both zzzfm and spacefm (both can live together and switch from one another).
* Included both slim and slimski in the ISO. No problem at all. You can even decide which one to use before booting with this boot parameter:
login=slim
to boot with slim instead of slimski (Good when you see that slimski doesn’t start).
* Included the slimski fix (it should not segfault anymore).
* You can now remove zzzfm or spacefm (or both) and the other-desktop menus (and slimski login session options) will update to remove their options (slim still displays them as options, as I am not removing the xsession .desktop files). This is the only thing I cannot figure out (a non-destructive method for slim to not display them at boot).
* Fixed the login-config-antix launcher from menus (uses gksu now; I forgot to add it in the .desktop file but yest to the control centre).
* enable numlock is disabled now by default (sorry for the problems marcelo).
* I now realized that most of the slimski themes are optimized for 1366×768. I will have to look at them in other monitors and not only my laptop screen.

I haven’t sent any merge request yet. Just finished testing. I will send them tomorrow. Sorry, anticapitalista.
https://drive.google.com/file/d/1IAhyMKUu_xKYYZaGNiSf0j4SNwzBEW5z/view?usp=sharing
No urgency to test. I don’t think I will touch anything until the weekend.

Thanks for reading.

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

[Member marcelocripe]

Hello everyone,

Complementing with some information about the use of Ventoy that was covered in the topic https://www.antixforum.com/forums/topic/please-stop-recommending-use-of-ventoy-and-balenaetcher/.
I was able to verify that Ventoy can boot several different ISOs and on different motherboards, but on some motherboards Ventoy just crashes after selecting the ISO and when it starts loading the OS. On some motherboards Ventoy cannot load your options menu screen.

marcelocripe

———-

Olá a todos,

Complementando com algumas informações sobre o uso do Ventoy que foram abordadas no tópico https://www.antixforum.com/forums/topic/please-stop-recommending-use-of-ventoy-and-balenaetcher/.
Eu consegui verificar que o Ventoy consegue inicializar várias ISOs diferentes e em diferentes placas-mães, mas em algumas placas-mães, o Ventoy simplesmente dá erro após a seleção da ISO e no momento que começa a carregar o sistema operacional. Em algumas placas-mães o Ventoy não consegue carregar a sua tela do menu de opções.

marcelocripe

[Member Xecure]

calciumsodium wrote:

I got the same error message:
starting slimski: slimskiSegmentation fault
failed!

T[…]

This time, I selected lang=

That is what I got yesterday after debugging. If the boot parameter lang=”” is not set, it would default to a LANG variable which, at that point in time, was still not set as environment variable. As the variable was missing, it couldn’t get the allocated space for that variable in ram, causing the process to crash (segmentation fault). The next version I upload will include the fix I was testing yesterday, which directly loads the LANG value from /etc/default/locale
It is a stupid error I should have been able to figure out sooner. The solution was also pretty simple.

I can’t right now, but in a few hours I will try to build the ISO (much smaller I hope), with both grub fixes, and have both slim and slimski installed and easily switchable, to see if they can exist side by side (so that updating from 19 to 21 doesn’t bring any incompatibilities). I have everything mostly figured out, but lack the time right now to create the proof of concept.

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

[Member marcelocripe]

Xecure,

Thank you very much for all your work, commitment and for this construction of ISO.

I managed to boot in pt-BR, the ISO boot menus are OK, I selected the desktop with zzzFM as the default file manager, used zzzFM to navigate between folders and then compared it with SpaceFM. It’s easily noticeable that zzzFM responds faster and also doesn’t crash like SpaceFM does on low-resource computers (1GB or 2GB RAM and single core processor).

I went to Control Center > Session > Login Manager, I get a message that you must be root. I tried to run the “Login Manager” through the Terminal window, I found the shortcut icon “.deskptop” in the folder “/usr/share/applications” to know its correct name to be typed in Terminal, but when I start it typing “sudo”, in place of the letter “u” the number is displayed “4” and in the letter “o” it displays another number, so I couldn’t execute it. Unfortunately I couldn’t have free time to test anymore. With this ISO we can compare the behavior of zzzFM and SpaceFM easily. Later, we will need to pay attention to the new shortcut icons “.deskptop”, including the “Login Manager” to be translated into the final/official ISO.

I’m following zzzFM and slimski with a lot of enthusiasm and I believe they will be very good for antiX, of course these changes will require a lot of technical work and knowledge about antiX that I don’t have yet, because if I knew how to do it, I certainly would. be able to help them solve problems, rather than just testing. Calciumsodium’s wise words reflect my case well.

Anticapitalista, please consider implementing Debinstaller (the white one, created by PPC) in place of GDebi. PPC managed to modify the Debinstaller, it’s not in GitLab yet (https://gitlab.com/antix-contribs/) and it turned the terminal window white so people won’t have to look at the “fearful” terminal in color black, has a little more sentences than the sentences that are in the transifex Debinstaller (https://www.transifex.com/antix-linux-community-contributions/antix-contribs/translate/), unfortunately the content of the address Pastebin URL that PPC shared with me is no longer available. Debinstaller installs local package dependencies when needed, GDebi does not install local package dependencies, even if the dependencies are in the local folder. We can use in the menus instead of the official name “Debinstaller”, the phrase “Package Installer .deb”, something similar to the GDebi menu.

Thank you very much.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Xecure,

Muito obrigado por todo o seu trabalho, empenho e por mais esta construção de ISO.

Eu consegui iniciar em pt-BR, os menus de inicialização da ISO estão OK, selecionei a área de trabalho com o zzzFM sendo o gerenciador de arquivos padrão, utilizei zzzFM para navegar entres as pastas e depois comparei com o SpaceFM. É facilmente perceptível que o zzzFM responde mais rápido e também não trava como ocorre com o SpaceFM em computadores com poucos recursos (1 GB ou 2 GB de memória RAM e processador de um núcleo).

Eu acessei o Centro de Controle > Sessão > Gerenciador de Início de Sessão, eu recebo uma mensagem que é necessário ser root. Eu tentei executar o “Login Manager” através da janela de Terminal, eu encontrei o ícone de atalho “.deskptop” na pasta “/usr/share/applications” para saber o seu nome correto para ser digitado no Terminal, mas quando começo a digitar “sudo”, no lugar da leta “u” é exibido o número “4” e na letra “o” exibe outro número, por isso eu não consegui executá-lo. Infelizmente eu não consegui ter tempo livre para testar mais. Com esta ISO podemos comparar o comportamento do zzzFM e do SpaceFM facilmente. Posteriormente, precisaremos dar atenção aos novos ícones de atalho “.deskptop”, inclusive ao “Login Manager” para serem traduzidos na ISO final/oficial.

Eu estou acompanhando o zzzFM e slimski com muito entusiasmo e acredito que serão muito bons para o antiX, é claro que estas alterações exigirão muito trabalho e conhecimento técnicos sobre o antiX que eu ainda não possuo, pois se eu soubesse como fazer, certamente eu iria poder ajuda-los a resolver os problemas, ao invés de apenas testar. As sábias palavras do Calciumsodium refletem bem o meu caso.

Anticapitalista, por favor, considere a possibilidade da implementação do Debinstaller (o de cor branca, criado pelo PPC) no lugar do GDebi. O PPC conseguiu modificar o Debinstaller, ainda não está no GitLab (https://gitlab.com/antix-contribs/) e tornou a janela do terminal em cor branca, assim as pessoas não precisarão olhar para o “temível” terminal em cor preta, possui um pouco mais de frases do que as frases que estão no Debinstaller do transifex (https://www.transifex.com/antix-linux-community-contributions/antix-contribs/translate/), infelizmente o conteúdo do endereço de URL do Pastebin que o PPC compartilhou comigo, não está mais disponível. O Debinstaller faz a instalação das dependências do pacote local quando é necessário, já o GDebi não faz a instalação das dependências do pacote local, mesmo se as dependências estiverem na pasta local. Poderemos utilizar nos menus no lugar do nome oficial “Debinstaller”, o a frase “Instalador de Pacotes .deb”, algo semelhante ao menu do GDebi.

Muito obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Moderator Brian Masinick]

BobC wrote:

Linuxdaddy, I think he can’t boot it from his Ventoy flashdrive.

Ventoy works for some ISO’s, and not for others. I suggest burning it to a separate flashdrive using antiX’s or MX’s Live-USB-Maker program if possible after checking that the file being burned was good.

I agree; this has come up multiple times, and I remember a strong advisory to use either the Live USB Maker or a standard Linux utility (like dd) as an alternative. If you use Ventoy at all, restrict its usage to storing images; again, be advised that even this was discouraged in an earlier thread.

--
Brian Masinick

[Member matematico65]

PPC wrote:

@matematico65- like suggested before- please try using other way to burn the 64 bits iso to your thumbdrive, other than Ventoy- it sometimes refuses to boot some distros- it may work with antiX 32bits but refuse to boot antiX 64bits…

P.

Certainly i will try to make this attempt.
I see that you are all in agreement on this point.
Thank you.

[Moderator BobC]

I have gotten that error when booting a number of distros with Ventoy. I already suggested above what to do. Linuxdaddy is correct that if you can boot the 32 bit version from Ventoy, you could then use it to burn another flashdrive with the 64 bit version.

PS: I never was able to predict precisely which ISO’s would work booting from Ventoy or MultiBootUSB, it was easier to just assume there was a problem and try a different method on any that didn’t work. I would suspect maybe the UEFI stuff might be involved. If you run into problems, the best bet is always to try doing it the way the Dev’s that created it would have tried.

• This reply was modified 1 year, 9 months ago by BobC.
• This reply was modified 1 year, 9 months ago by BobC.
• This reply was modified 1 year, 9 months ago by BobC.

Attachments:

1. 

   screenshot-2021Jul19_153108.jpg
   

[Member calciumsodium]

Xecure wrote:

WARNING: ISO IS 1.5 GBs!!!! I don’t know what I did wrong, but it is heavy!
https://drive.google.com/file/d/1M75uhoFgHyWE9Hbd1LuXKmLKeDpz40LZ/view?usp=sharing

Hi @Xecure,
I successfully created the liveUSB for this antiX concept 21-b1 (Kaze no den wa). In the all cases so far, I have not been able to get pass this error during boot:

starting slimski: slimskiSegmentation fault
failed!

In the grub text menus, I was able to select the different desktops, but I could not find an option to choose slim vs slimski. The iso seems to select slimski as the default?

• This reply was modified 1 year, 9 months ago by calciumsodium.

[Member PPC]

@matematico65- like suggested before- please try using other way to burn the 64 bits iso to your thumbdrive, other than Ventoy- it sometimes refuses to boot some distros- it may work with antiX 32bits but refuse to boot antiX 64bits…

P.

[Moderator BobC]

Linuxdaddy, I think he can’t boot it from his Ventoy flashdrive.

Ventoy works for some ISO’s, and not for others. I suggest burning it to a separate flashdrive using antiX’s or MX’s Live-USB-Maker program if possible after checking that the file being burned was good.

[Member Xecure]

anticapitalista wrote:

How would users feel if you were ‘forced’ to (automatically) switch from SpaceFM to zzzFM (and slim to slimski) if dist-upgrading from antiX-19 (or earlier) to antiX-21?

I think it isn’t the best option. I think many will prefer the already-known and configured spacefm (I saw that for example icons view was removed; I am waiting for skidoo to visit the forums so I can ask if this was for reducing RAM use or if this was a personal preference) than being forced to change. Also, the only things that would permanently change would be the boot menus, which shouldn’t inconvenience the people with antiX installed.
Slim should still be optional and can live with slimski, if the init script for both is available (runit should use the init scripts for slim and slimski in /etc/runit-core/ instead of the runit service, to make sure that everything works).
I think it can be achievable to have them all working and installed at the same time. I am working on an apt hook to remove/add .desktop options in /usr(share/xsessions/ when any of the file managers are removed (so to only display the ones that are really installed and reduce the session options to real working options). But that will wait for now.

I have built a very bad ISO, with the changes that anticapitalista has already merged (including live menus fixes). Bad because:
– I haven’t replaced spacefm with zzzfm in the grub menus (they have changed in the legacy boot menus).
– I have both zzzfm and spacefm installed (to test if they can live together).
– slimski still fails sometimes (works for me most times on VM). slim is not installed (to test how slimski alone goes), and someties you need to move to Alt+F1 to log in as user, and run
sudo service slimski start
– The other desktop menus are still not updated to include zzzfm. You can force the update with
sudo /usr/local/lib/desktop-session/desktop-session-update-wm-menus -f
– VBox-utils are not installed (I forgot 🙁 ).
– Installer hasn’t been updated (don’t install this ISO), so it doesn’t replace user and autologin options for slimski.
– The ISO does NOT include 2 kernels (I have no idea what magic anticapitalista has done to achieve this).

What does work:
– The apt hook to update other-desktops (when a new DE or WM is installed.
– Switching to other zzz-<wm> sessions (from other desktops or from slimski).
– The new GUI to change slim/slimski option (Control Centre > Session > Login Manager).
– If running slimski (that is already there), the Login Manager app lets you test themes BEFORE setting them (to see how the look).
– ADD: slimski theme (both the BobC and the Space theme) are localized, so you can see how they look booting with different languages (and then log out).
– Can’t remember if other new things work OK.

Note: the custom live menus theming is just me testing things out (the usual live grub/sylinux themes we know and love have’t been changed, it is me playing aorund with how much I can change the live theming without braking things). Also, the default slimski theme is also me playing around. The default antiX theme that BobC designed will still be the default.

I need to invest some time investigating the antiX-Gfxboot project, so Spacefm can be replaced there with zzzfm.

WARNING: ISO IS 1.5 GBs!!!! I don’t know what I did wrong, but it is heavy!
https://drive.google.com/file/d/1M75uhoFgHyWE9Hbd1LuXKmLKeDpz40LZ/view?usp=sharing

My thanks to skidoo for creating the programs. I hope he can visit soon.
Very special thanks to anticapitalista, for being patient, guiding when I asked, and for all the tools he (and Dave, fehlix, D_O, Adrian, and all the devs from both antiX and the MX team) have created. The more I use and investigate them the more I learn.
Also, special thanks to all translators. Login Manager app was localized in record time (less than 3 days!!) for major languages, (the rest is Google-translator work).

Testing is not required. I just built it as a concept, so anyone interested can try it out only for the few changes I added. You can see everything that works (and doesn’t) in less than an hour.

I think building the betas with slim for now is the best decision. slimski’s init with its daemon initialization is a bit strange compared to slim, and maybe I can figure out changing it.

I will not be as active next week, at least nothing before the weekend, so I cannot advance too much on this. I will look at the antiX-Gfxboot repo to see how I need to add zzzfm there.

Thanks for reading this long post.

• This reply was modified 1 year, 9 months ago by Xecure. Reason: Add special thanks. I cannot forget the great people who got me here

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