Search Results for 'boot from iso'

[Member marcelocripe]

Would you be able to be so kind to give me some ammo next time they come to atack me on Debian vs Antix? So I can baffle them on why Antix is better then debian + wm?

Konstantina, there are several possible answers to this, you will need to choose the right answer for the right taunt.

1-The antiX is free from SystemD.
2-The antiX is designed to consume the least possible amount of computer resources (I understand this as processing and RAM memory).
3-An old computer that is working, with a 32-bit processor and only 1 GB of RAM memory is considered electronic waste and has suffered the effects of “planned obsolescence” by large corporations. I have two options, use this computer with antiX Linux or throw it in the trash.
4-Although antiX is based on stable Debian, we can use antiX with many programs that are not in official Debian repositories.
5-The antiX community is the best, because… (you fill in the answer you wrote in your text) and there is no other like it.
6-With antiX Linux it is possible to revive old computers that are not suitable for current Windows, it is possible to watch television channels, watch YouTube videos without advertisements, access my emails, produce texts and spreadsheets, play games electronics, etc., even on an old computer. Are you going to get rid of your old computer by any chance?
7-If your old computer is worthless to you, with antiX your old computer is worth a lot to me.
8-I use antiX because I am free to choose what I want for myself and what is best for me and you have nothing to meddle with my life or with the operating system I use on my computer. (Maybe you have to clench your fists or start running… lots of laughter)
9-Invent your powerful phrase to justify your reasons for using antiX Linux.

The creator of antiX wrote (December 1, 2020):
We will try to keep CPU and RAM usage at idle down to a minimum. We mainly achieve this through not running unnecessary services on boot.

In June 2023 I will complete 3 years participating in this community and I am sure of one thing, if I read your topic 3 years from now, I will have many sentences much better than these. And there’s another important thing, the people in this community welcomed me here very well, even though I don’t know how to write or read in English.

– – – – –

Would you be able to be so kind to give me some ammo next time they come to atack me on Debian vs Antix? So I can baffle them on why Antix is better then debian + wm?

Konstantina, existem várias respostas possíveis para isso, você precisará escolher a resposta certa para a provocação certa.

1-O antiX é livre do SystemD.
2-O antiX é projetado para consumir a menor quantidade possível de recursos de um computador (eu compreendo isso como processamento e memória RAM).
3-Um computador antigo que esteja funcionado, com um processador de 32 bits e apenas 1 GB de memória RAM é considerado lixo eletrônico e sofreu os efeitos da “obsolescência programada” pelas grandes corporações. Eu tenho duas opções, utilizar este computador com o antiX Linux ou jogar no lixo.
4-Apesar do antiX ser baseado no Debian estável, nós podemos utilizar o antiX com vários programas que não estão nos repositórios oficiais do Debian.
5-A comunidade do antiX é a melhor, porque… (você preenche com a sua resposta que você escreveu no seu texto) e não tem outra igual.
6-Com o antiX Linux é possível reviver os computadores antigos que não servem para um Windows atual, é possível assistir canais de televisão, assistir aos vídeos do YouTube sem propagandas, acessar os meus e-mails, produzir textos e planilhas eletrônicas, jogar jogos eletrônicos, etc., mesmo em um computador antigo. Por acaso você vai se desfazer do seu computador antigo?
7-Se o seu computador antigo não vale mais nada para você, com o antiX o seu computador antigo vale muito para mim.
8-Eu utilizo o antiX porque eu sou livre para escolher o eu quero para mim e o que é melhor para mim e você não tem nada que se intrometer na minha vida ou com o sistema operacional que eu utilizo no meu computador. (Talvez você tenha que fechar os seus punhos ou começar a correr… muitos risos)
9-Invente a sua frase poderosa para justificar os seus motivos para utilizar o antiX Linux.

The creator of antiX wrote (December 1, 2020):
We will try to keep CPU and RAM usage at idle down to a minimum. We mainly achieve this through not running unnecessary services on boot.

Em junho de 2023 eu irei completar 3 anos participando desta comunidade e eu tenho certeza de uma coisa, se eu ler o seu tópico daqui 3 anos, eu terei muitas frases muito melhores do que estas. E tem outra coisa importante, as pessoas desta comunidade me receberam aqui muito bem, mesmo eu não sabendo escrever ou ler em idioma Inglês.

[Member Girafenaine]

I have checked md5 sum with success on the iso.

I tried again the live USB with same results : I can only edit the boot line manually, no option in the menus had any effect. I added on the boot line : menus persist=all toram. I got the text menus at boot and I was able to set languages and so on, and to ask to save.

At the next boot no options was saved, and live menu did not show any options anymore : no «advanced options» line, nor «languages»… There was only one line, the one with the linux kernel to launch (and without previous «saved» options).

From Strange to Stranger…

Girafenaine
----
Antix 19 - Fluxbox - Live USB stick and frugal / MX 19 - Fluxbox - Dell XPS 7590

Hello,

I have been a regular and happy antiX user since a few years, especially on a frugal install.

I tried to get freshly downloaded antiX 22 core on a quite recent 16 Gb USB key. I use the live USB creating tool on MX Linux to create a “full featured” live USB.

I used following options : encrypted, additional storage space (50%, NTFS format)

The resulting Live USB is booted on UEFI mode on my laptop. On the UEFI live menu, i can choose my options : language, persist_all, toram. And… save. I tried both “save” options, “grub” and “gfx”.

But it does not save anything ! Actually, it does not change the kernel boot line, the line you can edit with “e” key. No options seems to be taken into account.

If I edit manually the boot line with “e” key, I can get some persistance and change language.

Is that a common issue ? I don’t remember to have encounter such an issue on antiX live USB. Should I check iso integrity or something else ?

Thanks for your help or ideas !

Girafenaine
----
Antix 19 - Fluxbox - Live USB stick and frugal / MX 19 - Fluxbox - Dell XPS 7590

[Member marcelocripe]

Frugal installation of ISO “antiX-23-beta1-runit_x64-full.iso”.

The only observation is that it always starts with the 800×600 resolution. On the tube monitor, ARandR is able to display other resolution options 1024×768, 640×480 and 720×400. I’m going to install antiX 22 on this computer and give it to its owner, however this computer helped me to do some successful tests on this beta 1 of antiX 23.

demo@antix1:~
$ inxi -Fxz
System:
Kernel: 6.1.18-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
v: 12.2.0 Desktop: IceWM v: 3.3.2 Distro: antiX-23-beta1-runit_x64-full
Grup Yorum 21 March 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: MICRO-STAR model: G31M3-L V2(MS-7529) v: 1.0
serial: <superuser required> BIOS: American Megatrends v: 2.4
date: 03/26/2009
CPU:
Info: dual core model: Intel Pentium Dual E2180 bits: 64 type: MCP
arch: Core2 Merom rev: D cache: L1: 128 KiB L2: 1024 KiB
Speed (MHz): avg: 1696 high: 1769 min/max: N/A cores: 1: 1624 2: 1769
bogomips: 7999
Flags: ht lm nx pae sse sse2 sse3 ssse3
Graphics:
Device-1: Intel 82G33/G31 Express Integrated Graphics vendor: Micro-Star MSI
driver: i915 v: kernel arch: Gen-4 bus-ID: 00:02.0
Display: server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: i915
gpu: i915 resolution: 800×600~85Hz
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: i915 (: G33) direct-render: Yes
Audio:
Device-1: Intel NM10/ICH7 Family High Definition Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound API: ALSA v: k6.1.18-antix.1-amd64-smp running: yes
Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
driver: 8139too v: 0.9.28 port: e800 bus-ID: 01:01.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 89.18 GiB used: 8.52 GiB (9.6%)
ID-1: /dev/sda vendor: Western Digital model: WD800BB-00JHC0
size: 74.53 GiB
ID-2: /dev/sdb type: USB model: N/A size: 14.65 GiB
Partition:
Message: No partition data found.
Swap:
ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%)
file: /live/boot-dev/swap-file
Sensors:
System Temperatures: cpu: 57.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 125 Uptime: 8m Memory: 2.9 GiB used: 1.65 GiB (57.0%) Init: runit
runlevel: 2 Compilers: gcc: 12.2.0 Packages: 1632 Shell: Bash v: 5.2.15
inxi: 3.3.25
demo@antix1:~
$

[Forum Admin Dave]

@RJP,
What is the difference between “xdg-user-dir DESKTOP” and $XDG_DESKTOP_DIR?
As expected (to me) these produce the same result in the random languages I have chosen booting from ISO.
Both reference ~/.config/user-dirs.dirs; “xdg-user-dir DESKTOP” references it when the command is run and $XDG_DESKTOP_DIR is an environment export when the desktop environment is started (in /usr/local/lib/desktop-session/desktop-session-xdg-dirs.sh).

Maybe I am missing a reason why “xdg-user-dir DESKTOP” is preferred over an environment variable?

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member RJP]

Dave wrote:

@Caprea:
I booted the antiX 23 beta iso with the German language selected and 2 issues I noticed.
1. add-desktop had the path for the desktop directory hard coded as $HOME/Desktop. This has been changed to use $XDG_DESKTOP_DIR to account for the locale change. )

The same problem is in add-desktop script, which does not work other locales than english. The fix is change FILE_WRITE_LOCATION line as

FILE_WRITE_LOCATION="$(xdg-user-dir DESKTOP)"

Attachments:

1. add-desktop-fixed.zip

[Forum Admin Dave]

@Caprea:
I booted the antiX 23 beta iso with the German language selected and 2 issues I noticed.
1. add-desktop had the path for the desktop directory hard coded as $HOME/Desktop. This has been changed to use $XDG_DESKTOP_DIR to account for the locale change. For the personal menu, there was an extra menu refresh line that was also static/hard coded and not needed. After fixing these items, add-desktop would add the app to the desktop folder if manually running the string from app-select (like: add-desktop -a some|information|about|the|app) but app-select would not work. Which brings up issue number 2.
2. Though the files in lib-app-select/plugins in my gitlab are symlinks to add-desktop and desktop-defaults-run; twice during testing when I copied them over to a fresh boot of the iso the symlinks became copies of the file. This is why app-select acted like it was using an old copy (not working) of add-desktop even though the newer copy was in /usr/local/bin/ as noticed after repairing issue number 1. After removing these files and making new symlinks to /usr/local/bin/ app-select was working for both send to desktop and send to personal.

These should be repaired in the newest add-desktop from https://gitlab.com/antiX-Dave/add-desktop-antix/ and by verifying that the file in /usr/lib/app-select/plugins are actually symlinks to /usr/local/bin/(add-desktop|desktop-defaults-run)

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member Wallon]

Dear Master PPC,

The automatic update also works.
I did this on an extended partition with several logical partitions. The whole procedure was in French.

wallon@dell:~
$ lsblk -f
NAME         FSTYPE FSVER LABEL        UUID                                 FSAVAIL FSUSE% MOUNTPOINT
mmcblk0                                                                                    
├─mmcblk0p1                                                                                
├─mmcblk0p5  ext4   1.0   boot1antix23 cbd203c2-f329-4f4a-a597-a4ebeb08fc9e                
├─mmcblk0p6  swap   1     swap1antiX23 76c9de40-48f0-422a-bf28-eb4b7b2cb1c0                [SWAP]
├─mmcblk0p7  f2fs   1.15  root1antiX23 3e02bf2f-e441-4966-b1ce-ff58bf6a984c                
├─mmcblk0p8  vfat   FAT32 LINUXDATA    8806-3C53                                           
├─mmcblk0p9  ext4   1.0   boot2antix22 198c5b99-2b88-4a4c-baa0-2fef122fc204  258,4M    27% /boot
├─mmcblk0p10 swap   1     swap2antix22 9e4d0234-e71e-4209-8428-c50cbb6a92df                [SWAP]
└─mmcblk0p11 f2fs   1.14  root2antix22 c2870479-ded8-4fca-af6c-fe1a6906a953   32,3G    15% /

So, for me, everything is fine. I validate your program. Anticapitalista can put the new translation and your new program on github, in the iso of antiX 23 and send an update of your package for all installations.

This is really a great day for both of us.

Thanks again for your support.

Best regards,
Wallon

Attachments:

1. 

   PPC-file-testing-6.jpg
   

[Member Robin]

Many thanks @verdy for these comprehensive analysis.

verdy wrote:

There are two translation data for Japanese localization, ja.tr and ja_JP.tr, and it seems that ja_JP.tr is preferentially used.
If ja_JP.tr is missing, ja.tr will be used (I actually tried that).

Yes, that’s the way it is supposed to work.

verdy wrote:

To correct the Japanese localization of the Boot menu,
(1) Use only ja.tr.

I consider this the proper solution. I don’t see any reason why the additional outdated jp_JP.tr file was kept all the time in the boot menu archives or folders of the ISOs. It was probably simply overlooked, and nobody before you had reported the issue all the years.

This will be fixed in antiX 23, as a consequence of your report. Many thanks again for focusing it. Your analysis confirmed what I had suspected about the changed string position in the .tr file causing the item mismatch in translation in boot menu.

verdy wrote:

Because there is ja in antix-development of transifex, but there is no ja_JP.

This is intentional, since ja should be the base file in the ISOs, and no additional ja_JP should be present.

While ja_JP is clearly redundant to ja, we can discuss whether one of these is needed:
Hiragana (ひらがな), Kanji (漢字 / 和製漢字) or Katakana (片仮名) ?
Do you think one of them should be added (and can be maintained by volunteer translators at transifex)?

Many greetings
Robin

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

[Member Robin]

Some1 wrote:

I still wonder if it can be installed in a Windows machine within the “S mode” on

You could try it the way this video describes:

https://www.youtube.com/watch?v=ILl4GuVAY5o

– At 00:02:29 select the antiX 17.3 ISO instead of the Windows 8 ISO.
– At 00:04:38 you should see then the antiX 17.3 live boot menu instead of Windows 8 welcome, then just fire it up.
– Check the settings from 00:08:59 to 00:09:26

If this fails with the antiX 17.3 ISO, you’ll have to ask Microsoft Support about the details how to make it run on windows in s-mode, they do know their OS. This is not an antiX issue then, the modern microsoft hyper-v systems can’t even run their own Win-XP as guest without generating BSODs on install already.

Just let me venture a guess: you’ll have to tweak the Windows registry (delete some specific keys mentioned in https://learn.microsoft.com/en-us/windows/security/threat-protection/device-guard/enable-virtualization-based-protection-of-code-integrity ) and after that activate and deactivate again the Kernel-isolation features Memory-integrity and Firmware-protection in order to recreate the registry entries properly. After reboot the hyper-v should work with virtualbox 6.x at least and let you boot other guest systems.

– General information on how to run linux on windows hyper-v hosts: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-for-running-linux-on-hyper-v
– Virtualbox specific information how to run Linux on Windows in “S” mode (hyper-v) can be found here also: https://forums.virtualbox.org/viewforum.php?f=6

Again: Good luck. Microsoft will put a spoke in your wheel wherever they can, to avoid you running anything they don’t like.

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

[Member Xunzi_23]

Another method I find very useful. EtchDroid USB writer
Requires a reasonably powerful Android Phone.
But not Samsung with OneUI 3.0+, recent Huawei and OnePlus devices
which tend to hang.

Download from FDroid, is very useful to create a bootable linux USB Stick.
Got me out of trouble a couple of times.
Homepage is https://etchdroid.depau.eu/ Sets analytics cooky unless do not
track enabled. Er illegal in EU.

It does not require crazy permissions or call home.

For some phones ISO 2 USB https://sourceforge.net/projects/iso2usb-project/
is a better option. Not been updated for a long time but works fine on my non
google Huawei Phone.

• This reply was modified 1 month, 2 weeks ago by Xunzi_23.

[Member Robin]

Some1 wrote:

since it has Windows OS as main host

There is a windows version of virtualbox on their website. ( Direct windows installer download https://download.virtualbox.org/virtualbox/7.0.6/VirtualBox-7.0.6-155176-Win.exe ) from https://www.virtualbox.org/wiki/Downloads (There you’ll find also the very latest linux versions (downloadable .deb packages) you can run on antiX 23)

Some1 wrote:

vbox plus downgraded ver. from antiX in, sounds like lotta of work, thinking that I would pick persistent file to void all these tasks again next time it wanna play.

No, all these tasks need to be done once only. Once installed, all this it will come up within seconds, just like all other programs installed on your PC. Moreover you can port your virtualbox container with the installed antiX system within it, completely installed and set up with all flash games you like to play) even to another PC by simply copying the virtual hard drive file virtualbox creates. If you want to save disk space you can place the container to an USB pen drive (USB-stick) rather than to the built in hdd. (The virtual hard drive file will take 4 GB ~ 12 GB file size, depending how much programs you plan to install in it. You may want to strip the system down so it boots directly to firefox rather than to default antiX desktop. The path how to achieve this was discussed some time ago here in forum. Then you can purge all unneeded components and might be fine with a virtual hdd size of 1.5 ~ 3 GB already, resulting in a more handy vdi container).

Just watch the video before, to which I had linked above, it is done on a Windows PC 🙂 and it takes about 15 minutes to install everything needed. Follow exactly the cooking recipt described there.

No need to downgrade antiX, just install it to the virtualbox container from ISO directly. Here you’ll get the 17.3 ISOs. The full version contains already the old fierefox installation still running flash.
https://sourceforge.net/projects/antix-linux/files/old/antiX-17.3/

I have done a bit testing, since I wanted to see this lovely old Svensk swf singing horses again I had accidentally came across in the early 2k years (probably 2002) twenty years ago. It took me 20 minutes to make it run within a virtualbox container, installing virtualised antiX 17.3 on top of antiX 23. It should work as smoothly on Windows OS.

In antiX 17.3 the firefox browser is completely ready, the outdated flash plugins are installed in this ISO. So just start the browser and connect to e.g. https://web.archive.org/web/20060110040935/http://svt.se/hogafflahage/hogafflaHage_site/Kor/hestekor.swf for testing. (These are the original singing horses from Swedish Television, this flash content should not contain any malware, it was captured and hosted by internet wayback machine, archive.org, so I consider it to be safe to run this very flash content) Additional hint: configure the virtual network adapter to “Bridged mode” instead of “NAT”.

WARNING: Don’t use the outdated firefox browser from within the virtual box environment to connect to any websites besides the ones you completely trust and want to play on! By all means, use the recent browser on your host (linux or windows) instead, to browse web. Keep a backup copy of the virtualbox container in order to be able to simply restore it completely from this backup in case of any signs of malware. (Keep in mind you are running outdated software with unpatched security issues huge as barn doors within this virtual sandboxed environment. Be carefully!).

Good luck!

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

[Member ile]

March 24
Hi dazz
We have a brother name’ rufus; his Mother’s name is panz.

Thirty-three months has passed since our previous trial of rufus making a usb live antiX boot.
(I think that our son has done it more recently..) We recommend antiX-full.

Installed the rufus version TODAY’S.
antiX 22 Base x64 iso ;md5sum bdc19b660ce781cd13d3a87aab88ba89

rufus write mode Image, success, the usb, it, antiX, boots.
rufus write mode dd , , , success, the usb, it, antiX, boots.

Hi
I am trying to install antilinux on an old Asus eeePC R101 with 2G RAM.
I tried following the instructions here using Rufus to create an ISO/DD image on a Windows machine.
My version of Rufus is: Version 2.18 (Build 1213)

It appears there is a mismatch between the Rufus version and the downloadable versions of antiX.
Screen shots of the Rufus error messages are attached.
The resulting ISO/DD usb won’t boot.

Attachments:

1. 

   Rufus-AntiLinux-Error-Messages-ISO.png
   

dazz

[Member marcelocripe]

No space available on device

I used all the default settings offered in the frugal installation process. The 80GB IDE hard disk being used for full frugal persistence is no longer able to be used for installing an operating system because the MBR of this hard disk is damaged.

Could it be that the default values offered in the frugal installation process are no longer appropriate for the latest antiX?

I booted with LiveUSB and can look at the folders “antiX-Frugal-6.1.18-antiX.1-amd64-smp” which is 19.6 GB and 1025 files, “Live-usb-storage” which is 60 KB and 5 files, “lost+found” which is 16 KB and 1 file and “swap-file” which is 4 GB.

I’m going to redo the frugal installation and set a size of 60GB to help with testing this ISO.

Dear Marcelo (and all): one of the reasons antiX-Updater always shows the terminal, even in the “Automatic Mode” is so users have an easy way to see what the system is doing and also reading the reason for any error.

It’s always great to be able to see what’s going on, even with the “Auto Update” option.

Now I was curious, how did you find out that it could be a lack of space?

I’m please to see that your revised localization works perfectly 🙂

I think you misunderstood, I revised the line breaks after seeing the initial translation work which will not display correctly on small screens due to the lack of line breaks. That is, I needed to see the initial translation work to be able to adjust the texts in Transifex. I hope that today’s revised text can be re-downloaded and used in a new “yad-updater” program package.

Sir Brian, I thank you for these commands. I’ll save them in my notes for future use.

– – – – –

No space available on device

Eu utilizei todas as configurações padrões oferecidas no processo de instalação frugal. O disco rígido IDE de 80 GB que está sendo utilizado para a persistência frugal total não é mais capaz de ser utilizado para a instalação de um sistema operacional, porque a MBR deste disco rígido está danificada.

Será que os valores padrões oferecidos no processo de instalação frugal não são mais apropriados para o antiX mais recente?

Eu iniciei com o LiveUSB e posso olhar as pastas “antiX-Frugal-6.1.18-antiX.1-amd64-smp” que possui 19,6 GB e 1025 arquivos, “Live-usb-storage” que possui 60 KB e 5 arquivos, “lost+found” que possui 16 KB e 1 arquivo e o “swap-file” que possui 4 GB.

Eu vou refazer a instalação frugal e definir um tamanho de 60 GB para ajudar com os testes desta ISO.

Dear Marcelo (and all): one of the reasons antiX-Updater always shows the terminal, even in the “Automatic Mode” is so users have an easy way to see what the system is doing and also reading the reason for any error.

É sempre muito bom podermos ver o que está acontecendo, mesmo com a opção “Atualização Automática”.

Agora eu fiquei curioso, como vocês descobriram que poderia ser falta de espaço?

I’m please to see that your revised localization works perfectly 🙂

Eu acho que você não entendeu, eu revisei as quebras de linhas após ver funcionado a tradução inicial que não será exibida corretamente em telas pequenas, devido a falta das quebras de linhas. Ou seja, eu precisei ver a tradução inicial funcionado para conseguir ajustar os textos no Transifex. Eu espero que o texto revisado no dia de hoje possa ser baixado novamente e ser utilizado em um novo pacote do programa “yad-updater”.

Senhor Brian, eu agradeço por estes comandos. Eu vou guardá-los em minhas anotações para uso futuro.