- This topic has 31 replies, 13 voices, and was last updated Feb 21-8:34 pm by ModdIt.
-
Posts
-
Anonymous
That seems like the perfect placement. Others can followup with collaborative suggestions toward further shaping the content.
I’ll suggest: For brevity, omit the (parenthesized) spelled-out URLs
noticed one typo, “persitence”, toward the bottomFor the sourceforge project page, could just mention that additional download mirror servers are available & provide a link to this antixlinux.com/download page
ModdIt
Read earlier in thread.
I wonder how it would be possible to prepare a bootable flash drive without having an antiX.An alternative method, for example after a drive failure, no booting computer.
Grab an android phone with sufficient memory and internet access.
Etch Droid USB writer application from FDroid store can be used to write an image to a stick.
Also available from APK Pure and github.Download antiX ISO to an android phone, then use either a double plug usb stick or a USB OTG adapter/cable
to connect your stick for image write. This way many linux distros can be written in a bootable manner.Home page of the app is #https://etchdroid.depau.eu/
#https://github.com/EtchDroid/EtchDroid/releases
Known working OS images:
Ubuntu and derivatives, Debian, Fedora, Arch Linux
Raspberry Pi SD card images (you need to extract the zip file) and have a suitable adapter.Internal SD Card can not be written with an image!.
Leia mais cedo na linha.
Eu me pergunto como seria possível preparar um pen drive bootable sem ter um antiX.Um método alternativo, por exemplo, após uma falha de unidade, sem computador de inicialização.
Pegue um telefone android com memória suficiente e acesso à internet.
Etch Droid APLICATIVO de escritor USB da loja FDroid pode ser usado para escrever uma imagem para um bastão.
Também disponível na APK Pure, na https://github.com/EtchDroid/EtchDroid/releasesBaixe o ISO antiX para um telefone android e use um pendrive de plug duplo ou um adaptador/cabo USB OTG
para conectar sua vara para gravação de imagem. Desta forma, muitos distros linux podem ser escritos de forma inicializada.A página inicial do aplicativo é #https://etchdroid.depau.eu/
Imagens conhecidas do SO de trabalho:
Ubuntu e derivados, Debian, Fedora, Arch Linux
Imagens do cartão Raspberry Pi SD (você precisa extrair o arquivo zip) e ter um adaptador adequado.O Cartão SD interno não pode ser escrito com uma imagem!.
- This reply was modified 2 years, 2 months ago by ModdIt. Reason: Added git Hub
olsztyn
Does it work? (I have no way to test this process today, I would need to have another pendrive available)
1 Prepare the first bootable USB stick with a program that works on Windows and that works on computer startup.
2 Boot the computer with the first bootable flash drive.
3 After antiX starts, connect the second USB stick to be prepared with Live USB Maker.
4 Open the Live USB Maker program, select the second flash drive, locate the antiX ISO that was downloaded in Windows to prepare the second flash bootable with antiX.
5 Select “Full Mode – Recordable LiveUSB”This process seems to be very complicated for those who are leaving Windows and are arriving in antiX, especially for those who arrived here due to the possibility of having persistence through the bootable USB stick with antiX.
I am not clear if this Marcello’s question has been answered so please allow me to add my two cents:
1. This process works and I had been using this process in the past.
2. If booting antiX ISO from DVD drive you obviously do not need two USB sticks. After booting from DVD you can create antiX Live USB on the one USB drive you have. As I was using this process some time ago I am not quite sure it is still the case though…I think this would be the simplest for users not quite versed in Linux tools and crypto speak.
One news to me (apparently I fail to keep current on antiX documentation) is that Live USB Maker is available as appimage, which means you could start it on any Linux instance, even such as typical recovery boot CDs, such as GParted or Parted Magic. In such case either such tools can be booted and Live USB Maker started to create antiX Live on USB stick. The question to resolve however how in practice you address the antiX installation ISO location in such scenario. This in my opinion makes the use of Live USB Maker appimage on another Linux distro more complex than it seems at the first glance…
Just my two cents…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Xecure
Sorry to but in in the discussion.
The PLoP you mentioned, is it the program on this site https://www.plop.at/en/ploplinux/index.html?
I was hoping for @rokytnji to explain it, as he has waaaay more experience than me using it, and may know of other uses for plop.
Plop is a boot manager (as far a I know, please correct me), and it is useless for making a live USB with a antiX linux ISO. It use to be good for placing on a CD/floppy and using it for booting to/from USB when this option was not available from the BIOS, but now with antiX’ advance Boot menus and with the from= boot parameter, antiX live boot can now replace the need of plop (when booting from CD is possible), as we have seen on different cases in the forum.
Forget about plop.
Adding more info to olsztyn’s post.
You can do all this with only 1 USB if you have at least 2GBs of RAM available.
Use toram boot parameter in the boot menu of the live USB (you made with rufus or with whatever other Windows program), wait for antiX to load to ram and then to boot completely, and then use live USB maker to clone the live system in RAM to the same USB (made with rufus or with whatever program). I have done this a few times in the past, so I know it works.antiX Live system enthusiast.
General Live Boot Parameters for antiX.
rokytnji
Just that PLOP has it’s own site and can explain installing plop to hard drive to replace limited bioses that can’t boot cdrom,dvd, or usb.
It can be uninstalled also. https://www.plop.at/en/home.html Usually the source explains better than I do.I recommend searching archived forum also for this.
https://www.tapatalk.com/groups/antix/using-plop-boot-manager-to-boot-antix-from-pendrive-t2248.htmlYeah. I had a compaq laptop once with a cd drive and no way in bios to boot from it. HP also installed bios into hard drive back in the pentium 1 and 2 days
One had to jump through hoops to install linux on them. Through the floppy drive.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 problemsSo, 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.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> 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.That’s a valid point, and that detail is mentioned at t=136 seconds in this video
https://youtu.be/X5lgdxYi5Ro?t=136> I had numerous experience that using Rufus on antiX ISO
If one strays from the default rufus settings (isohybrid, no “persistence”), there’s certainly opportunity to wind up with an unexpected outcome. At some point, I had posted step-by-step screenshots + written description of what has unfailing worked for me (unfailingly, across 100+ operations).
declaring Rufus vs. balenaEtcher as the one to use for antiX depends on certain conditions
Then we should collectively identify which conditions and prepare a document which recommends the best tool for various particular situations.
p.s.
It’s not rufus’ fault if a kernel mismatch condition arises.
By the way, live-usb-maker now guards against mismatch, IIRC. It will instruct you to first perform live-remaster if it detects that a kernel change has been performed.Thank you skidoo for this additional info…
> 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.
That’s a valid point, and that detail is mentioned at t=136 seconds in this videoIndeed, my remark was not meant to point it as any defect but rather an observation, which you confirmed.
By the way, live-usb-maker now guards against mismatch, IIRC. It will instruct you to first perform live-remaster if it detects that a kernel change has been performed.
Digging into my memory:
– Live-USB-Maker was run after remaster.
– Specific condition: Encrypted USB.
– Result: Output from Live-USB-Maker initiated booting but failed when un-squashing linuxfs with two option: Shutdown or Reboot. This I think I remember was caused by kernel change on Live. I had to revert to the original kernel to make USB clone successful.
Since my experience I described was not recent it is great to know that now Live-USB-Maker should not experience these issues.
Thanks again and Regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameterscurrent events ~~ an ongoing topic at MX Linux forum
http://forum.mxlinux.org/viewtopic.php?f=92&t=63187
folks praising usefulness of Ventoy persistence.dat file
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)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.
This case falls into what skidoo was requesting in one of prior posts, namely try to identify conditions where these programs work and when they do not. I also ran into various cases of one vs. another, as it seems not one is sure to work in all cases, which makes it harder for new users…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Brian Masinick
My feedback on the tools:
1. Regarding the use of various device creation tools, especially for USB devices, since using the Live USB Maker, I do not know of a better tool. It works very well, and it allows for the possibility of setting the USB up as either a read only device or as a read/write device and therefore it works well with persistence. Alternatively, for those who do not care about persistence, the classic UNIX/Linux command line tool, dd, works efficiently to create a read only USB image.
2. Ventoy can be useful if you want to hold a LOT of different USB images on a single USB device for testing; it is NOT a suitable device to use for all of the capabilities found in antiX, as documented in many places in this and other threads. I’ve found this to be true myself, so I use Ventoy only to hold many copies of ISO images, but never for using the full capabilities of either MX Linux or antiX.
3. My impressions and feelings aside, I recommend that most people choose the tools that the developers have provided on our distribution; they provide the features, capabilities and efficiencies that they are designed for; use other tools at your own risks and for your own purposes, but if they do not work exactly as you expect, do not be surprised; only people who “experiment” and “break” things, as I often do, should even consider departing from the regular tools; in fact, now that I am retired I seldom “venture off course” unless I have hours to spend testing and breaking software (and therefore reinstalling and rebuilding it again).
--
Brian Masinick
andyprough
current events ~~ an ongoing topic at MX Linux forum
http://forum.mxlinux.org/viewtopic.php?f=92&t=63187
folks praising usefulness of Ventoy persistence.dat fileThe only one praising Ventoy in that MX thread is the OP who is a complete newbie. Also, Ventoy only showed up in the original antiX Portugese thread because that’s what the OP was using and the people who responded simply tried to help the OP deal with Ventoy – no one was praising or recommending it.
Brian Masinick
For what it’s worth, today I took a snapshot of my running instance of the antiX-Bullseye-a1 test instance.
Once the snapshot was created, I used two of our standard tools – first the Format USB tool to erase anything on one of my existing USB drives. Once that completed, I used Live USB Maker to write the snapshot to the USB. Once completed, I booted this image.
The result was the same as the image I had been running from, with the exclusion of any files or directories that I omitted from the snapshot.
NO nonstandard tools used; the results were perfect and I am writing this – no nonstandard tools involved whatsoever.
Since I have used the Format USB, Live USB Maker, and several of the other tools, both with the standard releases and now with snapshots and test images, they definitely work with antiX, and they also work in read-only “dd mode” when you are working with other distributions. No need to look elsewhere for most every day scenarios. This was on a 5 year old Dell Inspiron laptop; I’ve done similar things with a Lenovo (ex-IBM) Thinkpad X201, an HP d5000 series desktop system (which is actually a rebranded HP model from the very old Compaq stuff owned by HP, and another HP laptop. I’ve had similar results with other Dell, HP, Acer, Lenovo and Gateway systems in the past.--
Brian Masinickrokytnji
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
- You must be logged in to reply to this topic.
