Search Results for 'boot from iso'

[Member marcelocripe]

Hello John Biles.

Welcome to antiX Linux and the forum.

I don’t know how to write in English and I send my texts translated by the internet translator. I hope you can understand everything, if your native language is not English, please translate my original Brazilian Portuguese text directly into your language with the help of internet translators.

When you upload the LegacyOS ISO to SourceForge, if you want you can make an announcement in the area antiX Respins.

When I was looking for a GNU/Linux community and distribution, I came across LegacyOS. But due to lack of information, I haven’t tested LegacyOS (because it’s frustrating to download an ISO, prepare the USB device and not be able to boot on the computer). You can detail everything that will be in the new ISO here on the forum, like the other ISOs based on antiX.

– – – – –

Olá John Biles.

Seja bem-vindo(a) ao antiX Linux e ao fórum.

Eu não sei escrever em idioma Inglês e envio os meus textos traduzidos pelo tradutor da internet. Eu espero que você consiga compreender tudo, caso o seu idioma nativo não seja o Inglês, por favor, traduza o meu texto original em idioma Português do Brasil diretamente para o seu idioma com a ajuda dos tradutores da internet.

Quando você enviar a ISO do LegacyOS para o SourceForge, se você quiser poderá fazer um o anúncio na área antiX Respins.

Quando eu procurava uma comunidade e uma distribuição GNU/Linux, eu me deparei com o LegacyOS. Mas por falta de informações, eu não testei o LegacyOS (porque é frustante baixar uma ISO, preparar o dispositivo USB e não conseguir inicializar no computador). Você poderá detalhar tudo que estará na nova ISO aqui no fórum, a exemplo das outras ISOs baseadas no antiX.

[Moderator caprea]

I just created a snapshot of my system antiX21, tf10 is installed but is not activated (but was before now and then), also not during the creation of the snapshot, the default session is rox-icewm.
Created a live stick of the snapshot and now, when the live-stick is booted and I change per menu entry the desktop to zzz-fluxbox or fluxbox or rox-fluxbox the desktop changes to tf10 activated on fluxbox.

Changing to the other desktops works, also min fluxbox.
Quite strange behaviour.Md5sum from the iso is checked, also from the live stick.

[Member olsztyn]

anticapitalista wrote:

PCmanfm is a dependncy of lxde and cannot be removed.
The lxde exit menu does not show all options such as reboot, halt since it need

Yes. I did not install LXDE. I installed just Openbox and LXpanel. In effect it is LX of LXDE but no PCmanfm or other LXDE fluff. In result it is libelogind0-free and elogind-free as well.

anticapitalista wrote:

The lxde exit menu does not show all options such as reboot, halt since it needs …. elogind (not just libelogind0).

Understood. LX WM is to use standard desktop-session-exit for this. Logout module is specified in LXpanel gui configuration. Therefore no need for elogind or libelogind0 requirement.
The resulting LX WM desktop (Openbox + Lxpanel) looks and operates just like LXDE desktop but it is using antiX standard infrastructure, no LXDE caboodle. It also resolved my wanting to get rid of PCmanfm, since no such stuff is installed in the first place. zzzFM is default FM

I am still testing but there seem to be clear advantages to IceWM. Toolbar app launcher and panel configuration is included with LXpanel config gui. No need for a custom IceWM toolbar configuration app. No app duplicates there…

Memory footprint appears to be slightly larger than IceWM in my setting. It appears to be about 10M larger, but I have not done exact apple to apple comparison yet. Small enough though.
Update: Memory footprint seems less than originally reported and it looks more like 5-10M with the same setting.

My JWM is still my primary, but this LX WM seems gaining quickly to fit my second choice…
I am not suggesting anything, just reporting surprising to me findings…

• This reply was modified 4 months, 1 week ago by olsztyn.
• This reply was modified 4 months, 1 week ago by olsztyn.
• This reply was modified 4 months, 1 week ago by olsztyn.

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

[Member 10Thumbs]

Thanks for your help. I went ahead and used the AntiX 22 full x64 iso and switched the kernel to 5.10 in the Live usb advanced boot options. The WiFi worked straight away! I’ve now installed this version and doing the updates across wifi 🙂
I’m happy to close this now. Best wishes for the new year. Thank you

[Member PPC]

A bit off topic – why I made FT10 available:

*About me (you can skip this section):
When I began using antiX, over 6 years ago, I was no novice computer user – I started using computers when DOS 6.1 was the latest craze, I began using some strange “program” that ran on top of it, called Windows 3, and I used all versions until windows XP, with occasional use of Windows 7 (that still is my netbook’s secondary OS), windows Vista (via VM) and some Windows 8.1 (my ex’s laptop) and Windows 10 (when I collaborated with an office that used it). I tried Windows 11 on my brother’s laptop. I was the go to guy to install software, solve B.S.O.D.’s, get printers and scanners working, clean viruses, etc…
I’ve been using Linux for some 15+ years, hard to tell. Before antiX, my desktop, a 32bits machine, had Mint installed – I knew a bit of CLI, I knew of several “interfaces” available under Linux, like KDE, Gnome, the Mint ones, etc. I could edit config files, following examples and extrapolating what I needed. use synaptic and apt just fine – a middle grade/advanced user.
antiX was love at first sight, because it was much faster than anything I tested until then (perhaps on par with those distros that run from RAM, but they never felt like a “real complete OS” to me).
But I hated Rox with a passion- I could not use it. I installed some other FM, probably PCManfm or something similar, and used it… For perhaps weeks to a couple of months, I had no idea that SpaceFM (ZZZfm grand daddy) was included in antiX. I had no idea what Window Managers were, and why antiX included so many “desktops”. I spent a lot of time not noticing antiX did not update automatically too (and I quickly noticed why – to save resources and also, leave that choice to the user).

I was no “Linux newbie”, I did know how to configure my BIOS to boot from a pen-drive, and burn pen-drives with Linux ISO’s… and still had a terrible time adjusting to antĩX!
That’s why I though FT10 was a nice idea – specially if it was in the repository (which it is now) and in Package Installer (so users that only know how to use a “store” can install it). But like I said, what I would have loved, when I came to antiX, was all it’s goodness, well, without the bad part- of having to adapt to the concept of a very powerful and light but (for me, and some other users) default File Manager, and there is a secondary FM that was much more “standard”- for me, antiX does not really have to come with FT10 for be easy to use- I agree that have it pre-installed, on the Full ISO would be great, but having it activated would be too much of a change from antiX’s defaults…

* An easier way to make antiX more user friendly, without a full departure from it’s current defaults (I mentioned a few times before, sorry for pushing this once again, anticapitalista):
– Use Zzzfm as default FM, with a more standard configuration (enable the usual Bookmarks by default, maybe even include my script to connect to Shared Folders)
– Include a few more items on the toolbar by default (mainly Toolbar Icon Manager, but also Searchmonkey, hell maybe even my DuckDuckGo GUI- those 2 buttons give most of the functionality of that horrible “Search” field that people are used from other OSes, without compromising privacy) and also add antiX updater’s icon.
– Have a more “modern looking” theme for IceWM by default (BobC already provided a great one)
– Reorder the menu – add app-select as the first entry of the menu, to make it obvious what it does. Since app-select takes a while to load on slower devices, maybe include a rofi launcher as first menu entry entry – it’s a small package and literally starts instantly, even on the slowest computer- it’s a great way to add instant “menu search”.
– just to make antiX look a bit more modern, include a window switcher that previews open windows in real time (skippy-xd is tiny, and there’s a more powerful app that allows user to drag previews of open windows between virtual desktops, and it’s available in the repo)- have an icon for that window switcher on the default toolbar- advanced users can delete it, newbies would probably think antiX looks modern, with that tiny touch of unneeded luxury.
EDIT:
– If possible, use MX’s Package Installer that Skidoo adapted for antiX and published here in the Forum- It’s basically the same as the one antiX currently uses but with these changes: it has a tab that allows users to install any package available in the repo (so, the user does not have to use synaptic, but just one single GUI app) and it also has a tab that displays what the terminal is doing (it’s more “modern” than showing the user the Terminal itself- It’s not essential, just a nice touch). That way the user can install literally anything, from P.I…. “One ring to rule them all”, sorry, I meant one “App store”…
EDIT 2:
– This suggestion may seem strange, since many people complain antiX’s menu is “bloated”/too complex,/whatever – make App Categories available in the first layer of the menu – this gives quick access to everything and makes the menu more intuitive to use (at least it does to me)- so we have: appselect/rofi (as “Menu searchers), the pinned default apps (Terminal, File Manager, Browser, Text Editor, etc), antiX category, all other categories, then everything else (I would move the Help section, that maybe a couple of users ever read- and I was one of them, somewhere else other than the first layer, maybe, inside “antiX”?)
Also: if not fixed, please give elevated privileges to menu updater (and also include my proposal, so it also includes eventual flatpak apps to the menu – run that script in the final hookup, it costs no system resources if flatpak is not installed, and it can be great for people that, for some reason, want to use flatpaks. I have to study something equivalent, for Appimages that are “added to the menu”)

– If anticapitalista wants a middle ground, instead of jumping straight into using FT10 as default, antiX could run the default window manager toolbar, but have an icon to launch one of my customized jgmenus (with their companion GUI scripts to pin/manage menu favorites)- and right clicking the desktop still summoned the default antiX menu…
– Any of the scripts I include in FT10 (mainly Debinstaller and the script to mount Shared Folders) can be added to antiX right now.

All this proposed changes make antiX much easier to use, for newbies/ordinary computer users (such as I was, when I first came to antiX), without alienating the folks that love it’s current interface – they can just ignore the changes or edit 2 config files and have everything back to the way they love!

The future can go many ways! I hope it’s bright!

P.

• This reply was modified 4 months, 2 weeks ago by PPC.
• This reply was modified 4 months, 2 weeks ago by PPC.
• This reply was modified 4 months, 2 weeks ago by PPC.

[Member olsztyn]

Robin wrote:

Why should FT-10 not set up as default? Well, very easy explained. FT-10 is a set-on-top of the other desktops, not vice versa. So it delivers and provides some additional features and functions, different ways of user interaction. If this would be the default in antiX, in the consequence future development and future scripts will probably rely on the presence of FT-10, and not being able to run without it on the other desktops. This would be very bad. Only way to avoid this concequence is to treat FT-10 as what it is: A set-on-top desktop, users can switch to (or even boot with, it can be added to F7 boot menu also as a desktop option users can boot to). So FT-10 can take care of all needed adaptions itself when needed, just following its concept.
To put int in a nutshell, my advice: Include it as a switchable desctop selection into antiX full iso, but please don’t make it the default desktop. I believe we should stick to the default desktop we recently have

Thank you @Robin!
If anticapitalista decides to add FT10 to antiX I hope it will be as a ‘fifth windows manager’ choice, not default IceWM or Fluxbox. However, if on the contrary, it ends up as a ‘standard’ modification on top of IceWM or Fluxbox, please ensure a clear option to cleanly remove it completely, not just an option to ‘disable’ FT10.

Just to further clarify/summarize this concept if antiX must include FT10 by default:
– Make FT10 modified Ice/Flux as the Fifth WM, leaving the current pure Ice, Flux and JWM alone as they are.
– Clear option to Cleanly and Completely remove such FT10 modified desktop option, not touching any existing Ice or Flux.

In case it ends up as not such Fifth option but just a modification on top of existing Ice or Flux, then:
– Please ensure a visible and easy option to cleanly and completely remove all modifications, not just ‘Disable’ option as mentioned by @PPC in the preceding post.
– Please leave JWM alone, separate and untouched by any modification
– Please ensure that at least uninstallation of IceWM and Fluxbox would also completely remove all FT10 modifications and all related files from antiX. This would leave just JWM and Herbsluftwm in their original and untouched form.

• This reply was modified 4 months, 2 weeks ago by olsztyn.
• This reply was modified 4 months, 2 weeks ago by olsztyn.

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

[Member marcelocripe]

Hello everybody.

Feel free to comment.

I’d like to start by thanking the creator and leader of antiX Linux for always wanting to listen. On how many GNU/Linux distributions does the leader or leaders ask the community’s opinion?

PPC’s FT10 transformation package is excellent.
It achieves its aim of making antiX more ‘modern’ and ‘familiar’ particularly to those used to Windows 10.

This is an undeniable fact, when an end user new to antiX does not immediately adapt to the various “aesthetic” and “behavioral” options available in antiX, FT10 fulfills its main objective is to make the antiX something “modern” and “familiar”. For those people who only know Windows, as if this operating system only existed on planet Earth, FT10 “cushions” the impact of the transition from a slow operating system to a fast and stable operating system that is antiX Linux.

It’s not my ‘cup of tea’ though and I would remove it instantly.

I think this anticapitalista quote reflects reality very well for most experienced antiX users or active users of this forum. That is, being in antiX or not, it won’t make any difference to us.

So should future antiX default to Ft10 or keep its current set up?

I don’t know if the information was lost in automatic translation, but I would like the anticapitalist to make it very clear to all people which antiX ISO (or which antiX ISOs) it intends to use FT10 as the default on boot. Without this information, we will see people using core or net ISOs saying that they don’t want FT10, and for these ISOs and for these users, FT10 doesn’t make any difference, because they build antiX from the “black screen” from Terminal.

I assume that the intention is to use the full antiX ISO, if that is the intention, I fully agree that the FT10 is available in the menu to be activated or not by the end user. This way we prevent some people from complaining in this thread or the other antiX-23 – based on Debian 12 Bookworm – ideas that ROX-IceWM is no longer the default. But the people who “complain” know very well how to change the window manager or window manager + file manager combination, with two clicks or a command in Terminal.

We have to think about the following situation, either the community grows or it inevitably ends. If there are no new antiX users, inevitably the experienced antiX users will one day die, as this is the only certainty we have in life. Simply put, we can’t get away from it…

Even after the detailed explanations of PPC in several threads and including here about the FT10, I still see some people looking at themselves and not the other. Or that you have never used the FT10, but have your opinion ready and then say “no”.

While the majority of active people on the forum have learned something new since they started using antiX, unfortunately, there are people who are unwilling or unwilling to learn something new (whether due to lack of free time, lack of interest or laziness ). Much of this is what I call “the consequences of the comfort zone created by Microsoft”, the user becomes dependent (on the operating system), but doesn’t even realize it and anything different becomes a “trauma”. If a toolbar, two first-level menu options, two-click Recycle Bin settings, and various other programs that complete FT10 can increase the number of antiX users, I’d vote “yes” for the full ISO of antiX (at least it’s available in the options menu). The full ISO size won’t get huge because of the FT10, in case that’s anyone’s concern.

As I already wrote some time ago, I am an antiX Linux multiplier here in Brazil. Every now and then we have a new Brazilian participant here on the forum, most of them are monoglots, just like I am. antiX increasingly translated to pt-BR and FT10 make an excellent impression in the eyes of people who receive antiX from the installations that I do on their computers.

What Madibi wrote is very similar to what happens here in Brazil, if the patterns and themes available in antiX don’t “please” the end user’s eyes, certainly FT10 will and I see that happening here frequently.

Before being against FT10, I suggest you do a test on a LiveUSB without persistence, put yourself in the shoes of a novice user who has never seen antiX before and who is seeing antiX for the first time with FT10.

Note: I do not consider any of the antiX users actively participating here in this forum to be end users.

Anticapitalista, I thank you for allowing us to express our opinions and suggestions.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá a todos.

Feel free to comment.

Eu gostaria de iniciar agradecendo ao criador e líder do antiX Linux por sempre querer nos ouvir. Em quantas distribuições GNU/Linux que o líder ou os líderes perguntam a opinião da comunidade?

PPC’s FT10 transformation package is excellent.
It achieves its aim of making antiX more ‘modern’ and ‘familiar’ particularly to those used to Windows 10.

Este é um fato inegável, quando um usuário final recém chegado no antiX não se adapta imediatamente as diversas opções “estéticas” e “comportamentais” disponíveis no antiX, o FT10 cumpre o seu objetivo principal é que tornar o antiX algo “moderno” e “familiar”. Para aquelas pessoas que só conhecem o Windows, como se só existisse este sistema operacional no planeta Terra, o FT10 “amortece” o impacto da transição de um sistema operacional lento para um sistema operacional rápido e estável que é o antiX Linux.

It’s not my ‘cup of tea’ though and I would remove it instantly.

Eu acho que esta frase do anticapitalista reflete muito bem a realidade para a maioria dos usuários experientes do antiX ou dos frequentadores ativos deste fórum. Ou seja, estando no antiX ou não, não fará diferença alguma para nós.

So should future antiX default to Ft10 or keep its current set up?

Eu não sei se a informação foi perdida na tradução automática, mas eu gostaria que o anticapitalista deixasse bem claro para todas as pessoas em qual ISO do antiX (ou quais ISOs do antiX) se pretende utilizar o FT10 como padrão na inicialização. Sem esta informação, veremos as pessoas que utilizam as ISOs core ou net dizendo que não querem o FT10, sendo que para estas ISOs e para estes usuários, o FT10 não faz diferença alguma, porque eles constroem o antiX a partir da “tela preta” do Terminal.

Eu suponho que a intenção seja utilizar na ISO full do antiX, se for esta a intenção, eu concordo plenamente que o FT10 esteja disponivel no menu para ser ativado ou não pelo usuário final. Desta forma, evitamos que algumas pessoas reclamem neste tópico ou no outro antiX-23 – based on Debian 12 Bookworm – ideas de que o ROX-IceWM não seja mais o padrão. Mas as pessoas que “reclamam” sabem muito bem como alterar o gerenciador de janelas ou a combinação gerenciador de janelas + gerenciador de arquivos, com dois cliques ou um comando no Terminal.

Nós temos que pensar a seguinte situação, ou a comunidade cresce ou inevitavelmente acabará. Se não houver novos usuários do antiX, inevitavelmente os usuários experientes do antiX um dia morrerão, pois esta é a única certeza que temos na vida. Simplismente, não temos como fugir disso…

Mesmo após as explicações detalhadas do PPC em vários tópicos e inclusive aqui sobre o FT10, eu ainda vejo algumas pessoas olhando para si e não para o outro. Ou que nunca utilizou o FT10, mas possui a sua opinião pronta e logo diz “não”.

Enquanto a maioria das pessoas ativas no fórum aprendeu alguma coisa nova desde que começou a utilizar o antiX, infelizmente, existem pessoas que não querem ou não estão dispostas a aprender algo novo (seja por falta de tempo livre, ou por falta interesse ou por preguiça). Muito disso é o que eu chamo de “as consequências da zona de conforto criada pela Microsoft”, o usuário se torna um dependente (do sistema operacional), mas nem percebe isso e qualquer coisa diferente, se torna um “trauma”. Se uma barra de ferramentas, duas opções do menu do primeiro nível, as configurações da Lixeira pronta com apenas dois cliques e vários outros programas que completam o FT10 possa aumentar o número de usuários do antiX, eu voto em “sim” para a ISO full do antiX (ao menos estar disponível no menu de opções). O tamanho da ISO full não ficará enorme por causa do FT10, caso seja a preocupação de alguém.

Como eu já escrevi há algum tempo atrás, eu sou um multiplicador do antiX Linux aqui no Brasil. Vez ou outra temos um novo participante Brasileiro aqui no fórum, na sua maioria são monoglotas, assim como eu sou. O antiX cada vez mais traduzido para pt-BR e o FT10 causam uma excelente impressão aos olhos das pessoas que recebem o antiX a partir das instalações que eu faço nos seus computadores.

O que o Madibi escreveu é muito semelhante ao que ocorre aqui no Brasil, se os padrões e os temas disponíveis no antiX não “agradam” aos olhos do usuário final, certamente o FT10 agradará e eu vejo isso acontecendo aqui com frequência.

Antes de ser contra ao FT10, eu sugiro que você faça um teste em um LiveUSB sem persistência, coloque se no lugar de um usuário iniciante que nunca viu o antiX antes e que esteja vendo pela primeira vez o antiX com o FT10.

Observação: Eu não considero nenhum dos usuários do antiX que participam de forma ativa aqui neste fórum como usuários finais.

Anticapitalista, eu agradeço por você nos permitir expressarmos as nossas opiniões e sugestões.

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

[Member Robin]

I support PPCs opinion not to make it the default in antiX.

But I believe it would be great as an hotswitchable option, like all the other desktops from the “antiX” → “Desktops” → “Additional desktops” menu.
Best would be users should be able to simply click on an FT-10 entry present there to switch to it:

https://i.imgur.com/tYeJY0N.jpg

My reasons:

I beleive there are at least as much users not using or wanting antiX to look or feel like Windows as users wanting it to have that way. If we don’t want to split the comunity of users into two, we need to have the design switchable, not forcing one of the two on them.

Why should FT-10 not set up as default? Well, very easy explained. FT-10 is a set-on-top of the other desktops, not vice versa. So it delivers and provides some additional features and functions, different ways of user interaction. If this would be the default in antiX, in the consequence future development and future scripts will probably rely on the presence of FT-10, and not being able to run without it on the other desktops. This would be very bad. Only way to avoid this concequence is to treat FT-10 as what it is: A set-on-top desktop, users can switch to (or even boot with, it can be added to F7 boot menu also as a desktop option users can boot to). So FT-10 can take care of all needed adaptions itself when needed, just following its concept.

To put int in a nutshell, my advice: Include it as a switchable desctop selection into antiX full iso, but please don’t make it the default desktop. I believe we should stick to the default desktop we recently have, which can be a great base for whatever directions of set-on-top flavours as FT-10. Maybe somebody else provides an Apple-style like transformation pack, or whatever. Or somebody invents a completely new concept of look and feel, who knows. All this can be done only when the default in antiX doesn’t predetermine a specific set-on-top.

—–
@PPC : Obviously I’m not allowed to answer to your PM for some reason: “You do not have permission to send reply to this message!”. So here my answer: You could set the aCSTV package simply as a dependency in your FT-10 package, then it will get installed along with by default it if you want to have it included and integrated in some way. Instead, If you’d include the complete package as a duplicate into yours, it will be difficult to keep track of updates, and the packages will conflict. So the direct inclusion of package content into your package is not a good idea, while there are no objections to add a dependency to it once it is available from the repos.

Windows is like a submarine. Open a window and serious problems will start.

[Member stevesr0]

Hi all,

I reinstalled the (so far) latest SID nosystemd VLC packages (3.0.18-1.0nosystemd1) on my working Pipewire nosystemd install. Required installing the specific version of vlc, vlc-bin, libvlc-bin, libvlc5, libvlccore9, vlc-plugin-base, vlc-plugin-qt, vlc-plugin-video-output and vlc-data. When I installed vlc-plugin-base, libprotobuf-lite32 also had to be installed.

It works (even after a reboot <g>).

As I wrote before, my next step will be to make a liveusb from an iso-snapshot of this install to try on my other systems.

In another thread (“vlc can’t be installed on antix-22”), I posted the standard way to install specific versions of packages.

stevesr0

• This reply was modified 4 months, 2 weeks ago by stevesr0.

[Member iznit]

ben, to jog your memory: an iso is not intended to be directly “installed”. It is to be used to create a bootable device (((via live-usb-maker program or similar program))). After booting from that device ((( usb pendrive or CD or DVD ))), during a live session the “minstall” command is available to perform a permanent installation to hard drive or ssd.

Manual pages…..

Ben, don’t get confused by that “general” advice. minstall doesn’t actually have a manpage.

go look at the command itself before trying to run it.

again, this advice might be “generally” helpful, but minstall is a compiled program not a script. Trying to “look at” it would not be helpful unless you could find / read / understand its source code.

idea: We could gather questions and create a fresh topic to cover expected FAQ questions related to the installer and to more deeply explain the choices and options encountered during the installation process.

Example question ((( real question, my question )))
Is it true that older versions of the installer allowed keeping the username “demo”, to be carried over to the installed system….. but the installer version in antix 22 forces a new username to be chosen ((( demo cannot be used ))) during installation ?

[Moderator BobC]

If you were to reboot the machine, and after it comes up, wait a minute or two, then go to a terminal and type free, it will also tell you how much memory is being used.

Do that for each operating system to get a reasonable comparison, and post the results. My guess is there is 100 or 200 mb difference between them. If you run out of free memory trying to run programs it will swap out to disk, and that takes it a lot of time swapping things in and out, and the result is it will slow down significantly.

How do i install the iso snapshot after i bootet the system from the usb drive?

“sudo ./install” is not working anymore.

Hello.

Basically title, coming from this thread:
https://www.antixforum.com/forums/topic/doubts-about-antix-init-script/

After a LONG way studying the entire init script, I think I finally managed to successfully test some additions which fix some bugs/errors when using certain options for booting AntiX.

Beforehand, I’d like to clarify: I won’t be referencing the Gitlab repository links because, for some reason, stuff there is horribly outdated with respect to current stuff in the live ISO.

/live/init:

I found a couple of typo-like bugs:

find_crypt_or_linuxfs():
[ -n "$BOOT_ID" ] && ENCRYPT_MODE=$ENCRYPT_DiSABLE # <-- !!!

write_output_files():
TOORAM_ALL="$TOORAM_ALL" # <-- !!!

Should be “$ENCRYPT_DISABLE” and “TORAM_ALL=”$TORAM_ALL” respectively. The second one may be actually of little to no consequence, but the first one could lead to a malfunction when using LUKS stuff or the like.

find_linuxfs_file():

[...]
SQFILE_MP=$ISO_FILE_MP                            # <-- Existing line
BOOT_MP=$SQFILE_MP
SQFILE_DEV=$FOUND_DEV   # Used for toram-eject    # <-- Existing line
[...]

copy_to_ram():

[...]
log_cmd umount $SQFS_MP                           # <-- Existing line
mount_linuxfs "$SQFS_MP" "$SQFILE_FULL"           # <-- Existing line
[ "$DID_ISO" ] && log_cmd umount $ISO_FILE_MP
[...]

These finally solve problems when using “fromiso=” boot option to boot from an ISO, of which I once opened discussion here:
https://www.antixforum.com/forums/topic/booting-antix-with-multiboot-usb/
Now, booting from ISO seems to be *fully* functional, at least as far as I have tested. No errors in the boot process anymore, and when using “toram” and “automount=off” boot options, it’s completely safe to remove the boot device -usually USB stick- as soon as just entering the desktop; except if on UEFI and not using “automount=off”, because with this setting one will find that, just like with the live-usb-maker -made liveUSB, the ESP partition was mounted, although it can be just unmounted with no problems.

[Moderator BobC]

ant_222 wrote:

BobC wrote:

We have been trying to help, but you never even tried my solution. I went to the trouble of figuring it out for you, but you didn’t even try it. You only tried DaveW’s solution.

As I have repatedly reported here, any non-antiX kernel I install (5.18, 6.*, Liquorix or Debian) seems unable to recognise any command-line options, e.g.:
[ 0.021360] Unknown kernel command line parameters "insmod i915 BOOT_IMAGE=/boot/vmlinuz-6.0.0-12.1-liquorix-amd64", will be passed to user space.
I can and will try your solution with the antiX 4.9 and 5.10 kernels, which at least report no errors in dmesg, although other members here and in the IRC have suggested that I need at least 5.18. I beg your pardon if I failed to make myself understood about it: experiments with kernel command-line options seems ineffectual as long a the kernel fails to recognise and proceess any of them. Let me know if you think I should disregard the error messages in dmesg, incduing crashing the kernel on kernel split_lock, and try your boot options anyway.

Also please bear in mind that my spare time every day is limited, so that I may not always perform all the test you and other memebers have suggested. But I am doing what I can.

As to installing Debian Dog Sid for side-by-side comparison, is it not equally possible to boot the Debian from its live USB and compare to the antiX system I have installed? Only frugal installation seems officially supported by Debian Dog Sid, and I have no skill yet for manual configuration of the GRUB on my main boot partiton to load Debian Dog. If possible, I should prefer not to do it for the time being. If, however, you think proper installation important, I will take a pause to get it installed and will come back once I manage it.

1. As you can see from the prior page’s comments starting at the one you quoted, I am nut using that exact same Liquorix kernel so cannot vouch for the one you are trying. I do know that the one I am using is working with antiX 64 (not base, not runit).
2. I don’t have an insmod 915 before my other boot parameters. I did tell you not to add parameters before the existing boot parameters. IMO, that is why you have at least one of the errors. Also, if I don’t need insmod 915, I doubt you do. That was not my suggestion.
3. I gave you the exact string to try, just reboot, when it gets to where you can edit the string, do it there and try it.
4. I don’t get those errors and don’t crash.
5. Debian Dog: I was able to boot and install it, but antiX’s grub boot system didn’t setup a boot for it that worked. I had to do that manually. Their full install did not delete my test system, but I couldn’t tell if the grub they used would support a UEFI system, so I didn’t install that. I don’t want my Win/10 or other half dozen distro’s o that system messed up. Few Linux distro’s have official support. Read the disclaimers.
6. I really think you should just get things working with a screen you can read and internet before messing with fancy things like frugal installs because they are more difficult

• This reply was modified 4 months, 4 weeks ago by BobC. Reason: typos

[Member ant_222]

BobC wrote:

We have been trying to help, but you never even tried my solution. I went to the trouble of figuring it out for you, but you didn’t even try it. You only tried DaveW’s solution.

As I have repatedly reported here, any non-antiX kernel I install (5.18, 6.*, Liquorix or Debian) seems unable to recognise any command-line options, e.g.:
[ 0.021360] Unknown kernel command line parameters "insmod i915 BOOT_IMAGE=/boot/vmlinuz-6.0.0-12.1-liquorix-amd64", will be passed to user space.
I can and will try your solution with the antiX 4.9 and 5.10 kernels, which at least report no errors in dmesg, although other members here and in the IRC have suggested that I need at least 5.18. I beg your pardon if I failed to make myself understood about it: experiments with kernel command-line options seems ineffectual as long a the kernel fails to recognise and proceess any of them. Let me know if you think I should disregard the error messages in dmesg, incduing crashing the kernel on kernel split_lock, and try your boot options anyway.

Also please bear in mind that my spare time every day is limited, so that I may not always perform all the test you and other memebers have suggested. But I am doing what I can.

As to installing Debian Dog Sid for side-by-side comparison, is it not equally possible to boot the Debian from its live USB and compare to the antiX system I have installed? Only frugal installation seems officially supported by Debian Dog Sid, and I have no skill yet for manual configuration of the GRUB on my main boot partiton to load Debian Dog. If possible, I should prefer not to do it for the time being. If, however, you think proper installation important, I will take a pause to get it installed and will come back once I manage it.

• This reply was modified 4 months, 4 weeks ago by ant_222.