Search Results for 'boot from iso'

[Member ex_Koo]

@Xecure
I have made a ventoy disk and did every thing you said to do named a mount for /dev/sdd1 changed the the fstab to auto all seemed good, sdd1 which is 14gb and stores the iso’s. I can open sdd2 no worry’s which is the boot portion.
Just get this error if try and open sdd1 FUSE exfat 1.3.0 ERROR: invalid VBR checksum 0x55e0cb9 (expected 0x565cdb9). This error makes no sense at all as ventoy works just fine to install systems from iso files, not only that I can read , write , mount and umount to sdd1 & sdd2 with an arch based system.

[Anonymous]

https://github.com/BitJam/Live-initrd/blob/master/init
init#Line1957
tracing through the functions, I can sense the problem (mountpoint + {squashfs vs iso} path)…

oldForum search (via duckduckgo): fromiso
^—v

https://antixlinux.com/forum-archive/using-plop-boot-manager-to-boot-antix-from-pendriv-t2248-s30.html#p18157
BitJam
posted: 2010-11-17

I ran into this problem a while ago and it drove me crazy for a while. The design flaw is using the /antix/antix (or /mepis/mepis) location for the squashfs file system.

The problem is that the linuxrc script inside of initrd.gz searches just about every possible partition and stops as soon as it finds /antix/antix. It mounts just about every partition searching for that file. As you’ve seen, this is fine for the LiveCD because in that case it looks at the cdroms first but it fails when using a LiveUSB if that file already exist on a hard drive partition (which is not unlikely because frugal installs can put the file there). This problem also makes it impossible to boot more than one version of Mepis or antiX from the same LiveUSB.

The solution I came up with was to use a directory structure for the LiveUSB that is different from the directory structure for the LiveCD. If the LiveUSB directories contain the OS and version number then even if it finds the wrong squashfs file system it will still work because the OS and version number should match.

Therefore I put everything under: /boot/$OS-$VERSION

For example: /boot/antiX-M8.5

The three files I put there are vmlinuz,initrd.gz, and squashfs (the squashfs file is a copy of /antix/antix from the LiveCD). The corresponding Grub entry would be:

title antiX-M8.5
kernel /boot/antiX-M8.5/vmlinuz bootdir=antiX-M8.5
initrd /boot/antiX-M8.5/initrd.gz

The bootdir parameter is saying to look for a file called: /boot/antiX-M8.5/squashfs and use that as the squashfs file system.

My antix2persist-usb.sh does all of this for you automatically. I’ve advocated that all LiveUSB scripts should use this superior directory structure but I don’t think that was done. People don’t work for me so I can’t force them to do things in a way that I think is better.

[Member rayluo]

Thanks Brian and Skidoo for trying to help.

That “breakpoint=3” thing was a new toy in itself but, alas, it does not really bring me closer.

During boot, one of the previously-existing message was “Mounted boot device. Mounted device /dev/sdb1 at /live/iso-dev”, so my choice of “fromiso=/live/iso-dev/Live-usb-storage/demo/xyz.iso” seem correct. But the next line of error message is still this, and its last line seems leaving a hint here 🙂

Fatal Error
File /live/iso-file/antiX/linuxfs not found on device /dev/sdb1
     Searched devices: /dev/sdb2 /dev/sdb1 /dev/sdb /dev/sr0
       Searched types: usb,cd
    All block devices: /dev/sdb2 /dev/sdb1 /dev/sdb /dev/sr0 /dev/sda3 /dev/sda2 /dev/sda1 /dev/sda

Please contact BitJam at https://www.antixforum.com/

@bitjam ?

[Anonymous]

I dynamically type in “fromiso=/live/iso-dev/Live-usb-storage/demo/xyz.iso” and then boot

At that point during early boot, I reckon switch_root has not yet occurred ~~ the path you are typing does not yet exist. Try adding a boot cheat code Breakpoint 3 and browse what paths {{{ /dev/sdb1 ? }}} are recognized at that point, then revise your typed path accordingly.

[Member rayluo]

Thanks for the super quick response, AntiCapitalista! Are the grub menu required? Can this param be used “the other way around”, i.e. I copy a different OS’s ISO file into my antiX liveUSB’s Live-usb-storage folder (because the root folder “/” of the liveUSB seems not writable), and then during the antiX boot time, I dynamically type in “fromiso=/live/iso-dev/Live-usb-storage/demo/xyz.iso” and then boot into that XYZ OS? I tried but ended up with a Fatal Error. Perhaps I did not get the path right and I could give it more try, but do you know whether such direction is ever possible?

[Member Xecure]

Once you are happy with your system, create the iso.
Then, decompress the iso and edit the files /boot/grub/grub.cfg (for efi boot), and /boot/syslinux/syslinux.cfg and /boot/isolinux/isolinux.cfg for Legacy-BIOS boot (inside the decompressed iso folder). When finished, compress the iso again.

Keeely wrote:

can anyone tell me what mkisofs (or other tool) command-line is usually used to generate the ISOs?

Use the default Iso Snapshot tool inside antix?

For real advanced system and ISO building, use https://gitlab.com/antiX-Linux/Build-iso
That is the official tool used to build antiX isos for each release.

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

I’d like to change some boot options on the ISO and then recreate it, can anyone tell me what mkisofs (or other tool) command-line is usually used to generate the ISOs? I wondered if there’s a script somewhere that generates them.

All I found was this: https://antixlinux.com/forum-archive/how-to-create-a-remastered-iso-t7072.html

Note that I have no issue creating bootable ISOs using mkisofs so I can guess the options to use for antiX but I’d like to try to get the created ISO as close as possible to the shipped one. In particular I noticed that antiX uses the AAIP SUSP extension (and therefore fails to load with pycdlib). I raised a ticket against pycdlib for that:
https://github.com/clalancette/pycdlib/issues/54

thanks!

[Forum Admin anticapitalista]

fromiso boot ‘cheat’ allows user to directly boot the downloaded iso file.
No need to put the iso file on a disk or usb. So it saves one step.

For those with very old hardware and no usb device (or even a cd/dvd),
it is possible to download the iso, boot it and install.
This is much faster and less taxing on such old hardware.

Here is part of my grub for fromiso boot.

menuentry "antiX-19 32 ISO boot" {
     echo Boot disk address is: $root

     set iso='/antiX-19.2_386-full.iso'
     set bootparms='from=all quiet persist nocheckfs'

     search -f $iso --set=root

     echo ISO root is:          $root
     echo ISO is:               $iso
     echo Boot parms are:       $bootparms
     echo
     loopback loop $iso
     linux (loop)/antiX/vmlinuz fromiso=$iso $bootparms
     initrd (loop)/antiX/initrd.gz
     echo Booting $iso}

Hope this helps.

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

antiX with runit - leaner and meaner.

Hi antiX tribe,

I came across this FAQ kind-of mentioning “fromiso” parameter: https://download.tuxfamily.org/antix/docs-antiX-17/FAQ/boot-params.html#_other_booting_options

Yes the doc did say “deprecated”, but it seems it is behavior is still there. At least, if I try to dynamically type that param with a path, the boot behavior would be different (though I ended up with a Fatal Error in my experiments). Can anyone give an example of how to use it, and when to use it? Could it possibly be used when booting from LiveUSB, and then we tell antiX to load a different ISO, potentially an ISO of other-than-antiX image, i.e. starts with antiX boot process to load a different OS?

Regards,
Ray

[Member rayluo]

Anonymous wrote:

In the top level directory of the liveUSB, a file named “version” contains details
(I can’t recall whether that ever gets changed, i.e. if you perform a remaster operation)

Perhaps the recent LiveUSB has been changed to NOT contain that version file anymore? This is a newly created LiveUSB.

demo@antix1:/media/demo/Live-usb$ ls -ltra
total 44
-rw-r--r--  1 root root   894 Oct 10  2019 cdrom.ico
drwx------  2 root root 16384 Oct  1 03:21 lost+found
drwxr-xr-x  6 root root  4096 Oct  1 03:31 boot
drwxr-xr-x  2 root root  4096 Oct  1 03:31 antix19-2-x64-full-gvmcf
drwxr-xr-x  3 root root  4096 Oct  1 03:31 EFI
-rw-r--r--  1 root root   122 Oct  1 03:31 made-by-live-usb-maker
drwxr-xr-x  2 root root  4096 Oct  1 03:31 antiX
drwxr-xr-x  7 root root  4096 Oct  1 03:31 .
drwxr-x---+ 5 root root   100 Oct  1 03:33 ..

Anonymous wrote:

Also, you can mount the rootfs and
$ cat //path_to///var/log/live/initrd.log | grep Welcome
$ cat //path_to//etc/lsb-release

I found no rootfs from the newly created LiveUSB. I think that file would only exist when I start to use this LiveUSB (and when/if I also enable root persistence). But, if you just hinted to do “grep Welcome /var/log/live/initrd.log” and “cat /etc/lsb-release”, I can do that when the LiveUSB is booted normally. They are all “antiX 19.2 (Hannie Schaft) 64-bit”. Even the “/Live-usb/antix…(my_iso_file_name)…/package_list” contains exact same content.

Now the funny part. My newly created LiveUSB (i.e. the 3rd one) does not (currently?) have that “Internet Systems Consortium DHCP Client” thing during the boot process. So, I still don’t know why my 2nd LiveUSB behaves differently, I’ll revisit this if my 3rd LiveUSB develop same symptom again. Thanks for your time!

Part 1

Recently I created a new antiX 19.2 64bit LiveUSB flash drive to boot my computers. The boot time was longer than usual, and I notice that there is an extra “Internet Systems Consortium DHCP” step during boot.

[ ok ] Setting up resolvconf...done.
[ ok ] Skip starting firewall: ufu (not enabled)...done.
[....] Configuring network interfaces in background...Internet Systems Consortium DHCP Client 4.4.1
Copuright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/f0:de: f1:1e:12:7b
Sending on   LPF/eth0/f0:de: f1:1e:12:7b
Sending on   Socket/fallback
Created duid "\000\001\000\001'\007\3261\360\336\361\036\822(".
DHCPDISCOVER on ethe to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on ethe to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on ethe to 255,255.255.255 port 67 interval 19

It won’t discover anything, and eventually it will proceed to the rest of the boot process, and everything will be fine. But it consumes some 20~30 extra seconds during each boot, for nothing.

Q1: Any idea where this “Internet Systems Consortium DHCP Client” step comes from, and how can I disable it?

Part 2

I have another LiveUSB drive that was created months ago. It works just fine, without such new extra “Consortium DHCP Client” thing. The 2 LiveUSB drives were most likely created with SAME iso snapshot, although I am not entirely sure, because it has been months between them. So,

Q2: How do I know for sure that which version of antiX my LiveUSB was using?

I tried getting the “full info” from “Control Centre -> Hardware -> PC Information”, and they both output same System information: “Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 … Distro: antiX-19.2_x64-full Hannie Schaft 27 March 2020

[Member marcelocripe]

Anticapitalista,

I know that this topic is focused on ISO images for CD.

As CD and DVD media, in Brazil, they still have much lower prices when compared to pendrives and memory cards.

After these updates to the base versions, will the full versions match the next ones?

There is some possibility that you can make these new versions of antiX 19.3 (32-bit and 64-bit) full available in a single ISO image, where no boot menu for this ISO image would be possible to select which version the user wants to boot, a 32-bit version or the 64-bit version.

Maintaining as antiX 19.3 ISOs (32-bit and 64-bit) remain useful for those with a pendrive with a storage capacity of around 2GB.

To be able to gather the largest amount of ISOs on the same device, especially as 32 and 64 bit full versions and complete with base versions, I only managed to do so thanks to the suggestion of mr. Brian Masinick (https://www.antixforum.com/forums/topic/suggestions-about-antix-linux-to-developers-and-maintainers/page/4/), who motivated the topic (https: // www. antixforum.com/forums/topic/como-criar-pendrive-inicializavel-usando-o-ventoy-2/), but Ventoy only works on a USB stick, I would like to have ISOs on DVD media.

Thank you.

marcelocripe

————–

Anticapitalista,

Eu sei que este tópico é focado nas imagens ISO para CD.

As mídia de CD e DVD, no Brasil, ainda possuem preços bem inferiores se comparados aos pendrive e cartões de memória.

Depois destas atualizações das versões base, as versões full serão as próximas?

Existe alguma possibilidade de você disponibilizar estas novas versões do antiX 19.3 (32 bits e 64 bits) full em uma única imagem ISO, onde no menu de inicialização desta imagem ISO fosse possível selecionar qual versão o usuário deseja inicializar, a versão 32 bits ou a versão 64 bits.

Manter as ISOs do antiX 19.3 (32 bits e 64 bits) separadas continuam sendo úteis para quem possui pendrive com capacidade de armazenamento de cerca de 2GB.

Poder juntar a maior quantidade de ISOs em um mesmo dispositivo, em especial as versões 32 e 64 bits full e completar com as versões base, eu só consegui graças a sugestão do sr. Brian Masinick (https://www.antixforum.com/forums/topic/suggestions-about-antix-linux-to-developers-and-maintainers/page/4/), que motivou o tópico (https://www.antixforum.com/forums/topic/como-criar-pendrive-inicializavel-usando-o-ventoy-2/), mas o Ventoy só funciona em pendrive, eu gostaria muito de ter as ISOs em mídia de DVD.

Obrigado.

marcelocripe

[Member marcelocripe]

Xecure and PPC,

I am grateful for these further instructions and guidelines.

For the second one, you need to understand that “Boot” happens before “startup”, so I would keep the English word and leave it as “Repair Boot” (because this repairs grub, and not the WM startup process) .

So, I think you found an error in the original English version, the name of the item “Boot Repair” should be “GRUB Repair” or “Grub Repair”, as they have different functions, according to your explanation. In the translation of “Repair Boot” I can insert “Reparar o GRUB” or “Reparador do GRUB”, but the warning message on the website about the difference in context will remain.

Who can review this item and correct it?

If constant improvements and corrections depend on the antiX Linux community, I would always like to be able to do my part, collaborating with what I can or how I can …

This is the only way I could find to repay for everything I have been receiving here, the receptivity, the teachings, the patience, the friendships …

And after long months of searching, I can say that I found what I was looking for, the operating system that allows me to revive computers with little processing and RAM resources, in Portuguese and even with a community where good people are always available. trying to help in the best possible way.

I have great esteem for colleagues, friends and my teachers here on this forum, even though I don’t know them
physically …

Never forget this, even if I can never repay you for all the good and all the teachings you are doing for me, I will continue to multiply the knowledge and pass it on, especially on antiX.

So I will continue to strive to make the translation of antiX into Portuguese by Basil the best possible and in the meantime, I know that you strive to make antiX increasingly easy to use and with several light, simple solutions that solve big problems . which would only be solved using Terminal command lines.

I hope that when I can complete it I can see the result in some of the antiX online updates and in the next ISOs and versions.

When I am able to complete the corrections in the translations of the website, I also intend to send in this topic the files of the editions and corrections that I am remaking from the menus and also with the inclusion of a palliative solution for the translations of the “Applications” menu of the file contents applications ”, being added to the” Personal Menu “in a new sub menu called” Translated Applications Menu pt-BR “, the more content is translated or corrected, the easier it will be for new Brazilian users to use antiX.

Thank you all.

marcelocripe

————

Xecure e PPC,

Eu agradeço por mais estas instruções e orientações.

For the second one, you need to understand that “Boot” happens before “startup”, so I would keep the English word and leave it as “Reparar Boot” (because this repairs grub, and not the WM startup process).

Então, penso eu que você encontrou um erro na versão original em inglês, o nome do item “Boot Repair” deveria ser “GRUB Repair” ou “Grub Repair”, pois possuem funções diferentes, conforme a sua explicação. Na tradução de “Boot Repair” eu posso inserir “Reparar o GRUB” ou “Reparador do GRUB”, mas ficará a mensagem de aviso no site sobre a diferença de contexto.       

Quem pode rever este item e fazer a devida correção?

Se as melhorias e correções constantes dependem da comunidade do antiX Linux, eu gostaria sempre de poder fazer a minha parte, colaborando com o que eu puder ou como eu puder …

Esta é a única forma que eu consegui encontrar para retribuir por tudo que eu venho recebendo aqui, a receptibilidade, os ensinamentos, a paciência, as amizades … 

E após longos meses procurando, eu posso dizer que encontrei o que procurava, o sistema operacional que me permite reviver os computadores com pouco recursos de processamento e de memória RAM, em português e ainda com uma comunidade onde se encontram boas pessoas que estão sempre dispostas a tentar ajudar da melhor maneira possível.
Eu tenho grande estima aos colegas, amigos e aos meus professores daqui deste fórum, mesmo não os conhecendo fisicamente …

Nunca se esqueçam disso, mesmo que eu nunca consiga retribuir a vocês, todo o bem e todos os ensinamentos que vocês estão fazendo por mim, continuarei multiplicando o conhecimento e passando adiante, em especial sobre o antiX.

Então eu continuarei me empenhando para tornar a tradução do antiX em Português do Basil o melhor possível e enquanto isso, eu sei que vocês se esforçam para tornar o antiX cada vez mais fácil de ser utilizado e com várias soluções leves, simples que resolvem problemas grandes.que só seriam resolvidos por meio de linhas de comandos do Terminal.

Eu espero que quando eu conseguir concluir eu possa ver o resultado em alguma das atualizações online do antiX e ainda nas próximas ISOs e versões.

Quando eu conseguir concluir as correções nas traduções do site eu pretendo também enviar neste tópico os arquivos das edições e correções que estou refazendo dos menus e ainda com a inclusão de uma solução paliativa das traduções do menu “Aplicações” do conteúdo do arquivo “menu-applications”, sendo adicionado ao “Menu Pessoal” em um novo sub menu chamado “Menu Aplicativos Traduzidos pt-BR”, quanto mais conteúdo for traduzido ou corrigido, mais fácil será a adaptação para novos usuários Brasileiros do antiX. 

Muito obrigado a todos.

marcelocripe

[Member marcelocripe]

Hello Anti-capitalist and Xecure, how are you?

I need some information so that the translations or corrections of the Portuguese language (pt-Br) that I am doing on the website https://www.transifex.com are inserted in the correct form and in the correct places.

If you prefer, you can guide me through the private message.

The texts that occur during the installation I was able to easily understand and adapt them to make sense where they will be used. However, I was not able to be sure which is the file or which files (from the website) will be used for the menu texts.

For example:

– “Synchronize Directories” I changed the translation to “Sincronizar Diretórios/Pastas”, if this text is used in phrases or messages it will be understandable in this way, but if this text is related to the program or the tool and if it is used in the menu, it will be better translated to “Sincronizador de Diretórios/Pasta”;

– “Boot Repair” I changed the translation to “Reparar a Inicialização”, if this text is used in sentences or messages it will be understandable, but if this text is related to the program or the tool and if it is used in the menu, it will be better translated to “Reparador de Inicialização”

These two examples occur in various files on the site.

I asked for help from a colleague who speaks English and Brazilian Portuguese, he cannot help me without knowing the context or where the translated text will be used.

His answer confirmed my doubt, so that my translation work is done in the best possible way and so I can help mainly ordinary users or beginners in a Linux distro to understand the antiX operating system, I need information so that my contribution may contain more hits and fewer mistakes.

Even if I don’t master the English language, I am able to do it, because I am comparing the text translated into Portuguese from Portugal and comparing the text with the online translators, adapting to make sense, so I can make corrections / changes in the translation for en of the entire operating system, both antiX and MX Linux.

What I cannot understand I do not change. Some texts that I could not understand nor the text translated by the online translator, much less the text translated into Portuguese from Portugal, I only make occasional corrections, such as:

Portuguese from Portugal to Brazilian Portuguese:

-“actualizar” para “atualizar”;
-“ficheiro” para “arquivo”;
-“a instalar” para “instalando”;
-“aplicações” para “aplicativos”;
-e etc.

This work takes a long time, every day I do a little, I just hope I can see the result in the next updates and the next version of antiX.

marcelocripe

———-

Olá Anticapitalista e Xecure, tudo bem com vocês?

Eu preciso de algumas informações para que as traduções ou correções do idioma português (pt-Br) que eu estou fazendo no site https://www.transifex.com sejam inseridas na forma correta e nos locais corretos.

Se preferirem, podem me orientar na mensagem particular.

Os textos que ocorrem durante a instalação eu consegui perceber facilmente e adaptá-los para fazerem sentido onde serão utilizados. Contudo, eu não consegui ter certeza qual é o arquivo ou quais são os arquivos (do site) que serão utilizados para os textos dos menus.

Por exemplo:

– “Synchronize Directories” alterei a tradução para “Sincronizar Diretórios/Pastas”, se este texto for utilizado em frases ou mensagens ficará compreensível desta forma, mas se este texto estiver relacionado ao programa ou a ferramenta e se for utilizado no menu, ficará melhor traduzido para “Sincronizador de Diretórios/Pasta”;

– “Boot Repair” alterei a tradução para “Reparar a Inicialização”, se este texto for utilizado em frases ou mensagens ficará compreensível, mas se este texto estiver relacionado ao programa ou a ferramenta e se for utilizado no menu, ficará melhor traduzido para “Reparador de Inicialização”

Estes dois exemplos que ocorrem em várias arquivos do site.

Eu pedi ajuda para um colega que domina o idioma Inglês e o Português do Brasil, ele não consegue me ajudar sem saber o contexto ou onde será usado o texto traduzido.

A resposta dele confirmou a minha dúvida, para que o meu trabalho de tradução seja feito da melhor maneira possível e assim poder ajudar principalmente aos usuários comuns ou aos iniciantes em uma distro Linux a compreenderem o sistema operacional antiX, eu preciso de informações para que a minha contribuição possa conter mais acertos e menos erros.

Mesmo eu não dominando o idioma inglês, eu estou conseguindo fazer, pois eu vou comparando o texto traduzido em Português de Portugal e fazendo a comparação ao texto os tradutores online, adaptando para fazer sentido, assim eu consigo fazer as correções/alterações na tradução para pt-Br do sistema operacional inteiro, tanto do antiX quanto do MX Linux.

O que eu não conseguir compreender eu não faço alteração. Alguns textos que eu não consegui compreender nem o texto traduzido pelo tradutor online e muito menos pelo texto traduzido em Português de Portugal, só faço correções pontuais, como por exemplo:

Português de Portugal para Português do Brasil:

-“actualizar” para “atualizar”;
-“ficheiro” para “arquivo”;
-“a instalar” para “instalando”;
-“aplicações” para “aplicativos”;
-e etc.

É demorado este trabalho, todos os dias eu faço um pouco, eu só espero poder ver o resultado nas próximas atualizações e na próxima versão do antiX.

marcelocripe

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

Olá caros colegas.

O nosso colega, Brian Masinick, no tópico https://www.antixforum.com/forums/topic/suggestions-about-antix-linux-to-developers-and-maintainers/page/4/, sugeriu o Ventoy, esta é uma importante ferramenta para preparar o pendrive inicializável ou pendrive “bootável”.

Além da sugestão do Brian Masinick, outro colega do PCLinux Os Brasil, que eu o conheci no dia 20-09-2020, através do grupo do Telegram, também indicou o Ventoy para a criação de pendrive inicializável ou pendrive “bootável” e o vídeo.

O link abaixo do vídeo tutorial é preparado em uma distribuição Linux.

Eu encontrei também outro vídeo de tutorial que é preparado em um Windows

Baixe o Ventoy no site
https://www.ventoy.net/en/index.html

https://github.com/ventoy/Ventoy/releases

Arquivo SHA-256 Liberado Tamanho

ventoy-1.0.21-windows.zip 483ed9e698dd4a6d04d16ca58bfc406b55e69180fd061e1576ada16a130aa648 12-09-2020 7,3 MB
https://github.com/ventoy/Ventoy/releases/download/v1.0.21/ventoy-1.0.21-windows.zip
7.26 MB

ventoy-1.0.21-linux.tar.gz 170953248d5b30688d88ceae44cdc95d86a869fe3f58623b494e8ee60b5d2e1e 12-09-2020 7,5 MB
https://github.com/ventoy/Ventoy/releases/download/v1.0.21/ventoy-1.0.21-linux.tar.gz
7.42 MB

ventoy-1.0.21-livecd.iso 5be2660b776fe18d9f80a704e6e414c0cc8fbe853763c8c51bbc7edcc2d2460f 12-09-2020 38 MB
https://github.com/ventoy/Ventoy/releases/download/v1.0.21/ventoy-1.0.21-livecd.iso
37 MB

Caso você tenha usado o programa balenaEtcher anteriormente para preparar o pendrive inicializável, certamente você precisará formatar o pendrive, use um programa formatador de pendrive de sua preferência, por exemplo, o Formatador USB (Format USB) no antiX ou MiniTool Partition Wizard, ou USBUtil, ou guiformat no Windows.

No antiX, acessar o SpaceFM, encontrar a pasta de Downloads, descompactar o arquivo ventoy-1.0.21-linux.tar.gz, entrar na pasta ventoy-1.0.21, menu Arquivo, Terminal, o pendrive foi montado em sdb, no Terminal aplicar o comando abaixo:

antix1@antix1:~/Downloads/ventoy-1.0.21
$ sudo ./Ventoy2Disk.sh -i /dev/sdb {Enter}

**********************************************
      Ventoy: 1.0.21
      longpanda admin@ventoy.net
      https://www.ventoy.net
**********************************************

Disk : /dev/sdb
Model: Kingston DT 101 G2 (scsi)
Size : 7 GB
Style: MBR

Attention:
You will install Ventoy to /dev/sdb.
All the data on the disk /dev/sdb will be lost!!!

Continue? (y/n) y {Enter}

All the data on the disk /dev/sdb will be lost!!!
Double-check. Continue? (y/n) y {Enter}

Create partitions on /dev/sdb by parted in MBR style …
Done
mkfs on disk partitions …
create efi fat fs /dev/sdb2 …
mkfs.fat 4.1 (2017-01-24)
success
mkexfatfs 1.3.0
Creating… done.

Onde aparece {Enter}, significa que você deve ser pressionar a tecla Enter e não ser digitar {Enter}.

Será necessário digitar o y e pressionar o Enter para confirmar a formatação duas etapas.

Copiar as ISOs para a partição chamada ventoy.

Após a conclusão da cópia, clique no ícone da barra de tarefas remover dispositivo USB.

marcelocripe

• This topic was modified 2 years, 7 months ago by anticapitalista.
• This topic was modified 2 years, 7 months ago by anticapitalista. Reason: shrunk video