Search Results for 'boot from iso'

I tried to make a live usb with persistence. Downloaded the ISO, burned it to a 16GB usb flash drive with RUFUS.
Rebooted and chose the “F4 toram” option. When booted went to menu for “Live USB maker” but I keep getting a pop up bx asking for password. I saw in instructions the password is”root”. I keep typing it in but keeps getting rejected. What am I missing here? I simply want to make a bootable USB flash drive with persistence to use on an older machine. None of the other menu items for making/adjusting persistence work either cause I keep getting pop up asking for a password. I never set up a password. And the manual says for the live usb the password for root is “root”….please help! very annoying.

[Member marcelocripe]

Xecure,

I send the test results with the ISO “antiX-19-legacy-bet2_386-base.iso”.

Gigabyte GA-8S661FXM-775 brand motherboard:

I started in normal mode, Rox-IceWM, did not display a message on the screen “No frames were in use… the‘ Standard ’frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

The images of the menu icons disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized.

Conky displays the 60.9 MB RAM consumption of the 256 MB available (it was 1 GB, but I had to use the cards on another computer), $ sudo free {Enter} 62.07 MB RAM consumption of the 285 MB.

After the command “sudo” and click “Update Menus”, the submenus of “Applications” are in the normal order and appear organized. The images of the menu icons disappear when the mouse arrow passes over the menus. The “bet2” system is more fluid than the “bet1” version, there is a clear improvement in the response and movement of the windows of open programs. A freeze has occurred. I need to check if it occurred again on the same motherboard or if it was on a different motherboard.

demo @ antix1: ~
$ inxi -G
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
driver: N / A
Display: x11 server: X.Org 1.16.4 driver: fbdev unloadede: modesetting, vesa
resolution: 1024 × 768 ~ N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Table 18.3.6

$ inxi -S
System:
Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32
Desktop: IceWM 1.9.2 Distro: antiX-19-legacy-bet_386-base Lazarus 29 November 2020

I restarted the computer, started again in normal video mode, changed from Rox-IceWM to Space-IceWM, the images of the menu icons disappear when the mouse arrow passes over the menus, after clicking on “Update the Menu”, the submenus “Applications” are in normal order.

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM.

In the work areas: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox, all menus and submenus are OK and have no defects.

In the work areas: Minimal-JWM, Rox-JWM, Space-JWM, all menus and submenus are OK and have no defects.

As in this test the computer is less than 512MB, it will not be possible to test behavior with Firefox 78.5.0esr (32 bit) and playing a 21min36s YouTube video.

I restarted the computer, secure video mode, Rox-IceWM, did not display a message on the screen “No frames were in use… the‘ Standard ’frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

The images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are in the normal order, I checked in all work areas, everything is ok with the menus.

demo @ antix1: ~
$ inxi -G
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
driver: N / A
Display: x11 server: X.Org 1.16.4 driver: vesa resolution: 1024×768 ~61Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6

Xecure, at the end of all tests I realize that loading the “driver: vesa” is always the best option for the three computers.

My doubts:

1-To install the ISO “antiX-19-legacy-bet2_386-base.iso”, should I start in secure video mode and then start the installation process?

2-After installation, will “antiX-19-legacy-bet2_386-base.iso” start normally in the normal video mode with vesa?

Xedure wrote:
Remember that antiX has a Snapshot tool that lets you create your won ISO files with the customization you make. Some people who have created “re-spins” have moved some of the home configs to / etc / skel / before creating the snapshot so that their customized version of antiX can be easily installed on any system. This way you can set it up for the users before even booting and installing antiX on their machines.

These guidelines are very important to me, I still don’t know how to use Snapshot and create an ISO from a complete system and even with this ISO it is possible to install it on any other computer. In the case of the ISO “antiX-19-legacy-bet2_386-base.iso”, it will be dedicated to make computers with a motherboard with SIS or VIA chipset work with antiX.

The next tests I will send will be the result of the installation process.

Thank you.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Xecure,

Envio os resultados dos testes com a ISO “antiX-19-legacy-bet2_386-base.iso”.

Placa-mãe da marca Gigabyte GA-8S661FXM-775:

Iniciei no modo normal, Rox-IceWM, não exibiu uma mensagem na tela “Nenhum quadro estava em uso … o quadro ‘Padrão’ foi selecionado. Use ‘rox -p=Defaut’ para habilitá-lo no futuro.”.

As imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados.

O Conky exibe o consumo de memória RAM de 60,9 MB dos 256 MB disponíveis (estava com 1 GB, mas precisei utilizar as placas em outro computador), $ sudo free {Enter} consumo de memória RAM de 62,07 MB dos 285 MB.

Após o comando “sudo” e clicar em “Atualizar o Menus”, os submenus de “Aplicativos” estão em da ordem normal e surgem organizados. As imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus. O sistema “bet2” está mais fluído do que a versão “bet1”, é nítido a melhora na resposta e na movimentação das janelas dos programas abertos. Ocorreu um congelamento. Eu preciso verificar se ocorreu novamente na mesma placa-mãe ou se foi em uma placa diferente.

demo @ antix1: ~
$ inxi -G
(Dados do comando no texto em inglês)

 

$ inxi -S
(Dados do comando no texto em inglês)

Reiniciei o computador, iniciei novamente no modo de vídeo normal, alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus somem quando a seta do mouse passa sobre os menus, após clique em “Atualizar o Menu”, os submenus de “Aplicativos” estão em ordem normal.

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM.

Nas áreas de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox, todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Nas áreas de trabalho: Minimal-JWM, Rox-JWM, Space-JWM, todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Como neste teste o computador está com menos de 512MB, não será possível testar comportamento com o Firefox 78.5.0esr(32 bit) e tocando um vídeo de 21min36s do YouTube.

Reiniciei o computador, modo de vídeo seguro, Rox-IceWM, não exibiu uma mensagem na tela “Nenhum quadro estava em uso … o quadro ‘Padrão’ foi selecionado. Use ‘rox -p=Defaut’ para habilitá-lo no futuro.”.

As imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão na ordem normal, eu conferi em todas as áreas de trabalho, tudo está ok com os menus.

demo @ antix1: ~
$ inxi -G
(Dados do comando no texto em inglês)

Xecure, ao final de todos os testes eu percebo que carregar o “driver: vesa” é sempre a melhor opção para os três computadores.

As minhas dúvidas:

1-Para instalar a ISO “antiX-19-legacy-bet2_386-base.iso” eu devo iniciar no modo de vídeo seguro para depois inciar o processo de instalação?

2-Após a instalação o “antiX-19-legacy-bet2_386-base.iso” iniciará normalmente no modo de vídeo normal com o vesa?

Xecure wrote:
Remember that antiX has a Snapshot tool that lets you create your won ISO files with the customization you make. Some people who have created “re-spins” have moved some of the home configs to /etc/skel/ before creating the snapshot so that their customized version of antiX can be easily installed on any system. This way you can set it up for the users before even booting and installing antiX on their machines.

Estas suas orientações são importantíssimas para mim, eu ainda não sei utilizar o Snapshot e criar uma ISO a partir de sistema todo pronto e ainda com esta ISO ser possível de instalar em qualquer outro computador. No caso da ISO “antiX-19-legacy-bet2_386-base.iso”, ela será dedicada para fazer computadores com placa-mãe com chipset SIS ou VIA funcionarem com o antiX.

Os próximos testes que enviarei serão do resultado do processo de instalação.

Muito Obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Member marcelocripe]

Hello dear colleagues,

I hope you understand well the words that I will send translated by the internet translator from Brazilian Portuguese to English. I hope that there is no misunderstanding or that they understand my words as criticism or something that can discourage developers. My intention is to collaborate with suggestions, future vision and possibilities.

Guys, we have two different and very important topics in progress, dealing with practically the same subject:

https://www.antixforum.com/forums/topic/ideas-for-improvements-in-future-releases/
and
https://www.antixforum.com/forums/topic/release-recommendation-usability-improvements-4/

I’m trying to keep up with these topics, but I can’t keep up with the speed of most colleagues, you are extremely fast.

1 (one) year ago and 1 month ago I started researching Linux, then I started to understand about the existence of the various Linux distributions. 7 (seven) months ago I started on this forum. I intend to stay here on the forum as long as you allow me to stay. Since June 2020 I have been learning a lot from you and in a short time. I thank you all!

Anticapitalista wrote:
I think this is a very fruitful discussion and well worth continuing.
How I see future antiX (ie the next stable ‘bullseye’ version).

It is very good to be able to read your words (in my case, words translated by the internet translator into Brazilian Portuguese) about the future of antiX.

I believe that in order to have a future, the antiX community needs to grow, new users are needed and the existence of the new generation, after a few years, we need the new generation again and this cycle needs to continue repeating itself. Inevitably people get sick and unfortunately die. If there is no new generation of new antiX users, the community will languish and inevitably come to an end. Does anyone here want an end to antiX? My answer is “Eternal life to antiX!”.

Over the course of this 1 year and 1 month, I have seen more Linux distributions being discontinued than new Linux distributions being created.

The new generation is not only aimed at new users, but also the new generation of developers and programmers. In this regard, this community is excellent. We have people who are committed, participative and willing to collaborate even with programming codes. I don’t see such an optimistic scenario in other Linux communities.

Anticapitalista wrote:
Certainly, IMO, including user written scripts have made antiX more user friendly.
eg the IceWM toolbar script, antiX-wifi switcher, android-device-connect, fast_personal_menu_editor, icewm-menu-recent-files and others, though I personally don’t use any of them. The downside to including these useful scripts is that the menu could be considered to be ‘bloated’.

This is motivating, to see the work of several colleagues in the forum being accepted and implemented in antiX.

Making antiX more user friendly and easy to use is basically offering solutions through GUI. Who are the graphical interfaces for?

I myself have no skills at the terminal. However, I can edit text files, at least I’m “seeing” what I’m doing. At the terminal, I don’t “see” what the command does. But the question is: do the novice user, the basic user, or the average user really need this kind of knowledge?

Anticapitalista wrote:
What I don’t want is for antiX to be turned into something it is not meant to be.
For example, some in the past basically wanted it to be like a Debian lubuntu. If people want lxde, Xfce etc and ‘bells n whistles’ out of the box, then they really should try another distro.
We will always be systemd-free.
We will keep to IceWM / Rox default
We will ship with / promote our own (less known or even unknown) tools / apps over bigger and better known versions eg droopy, 1-1-voice etc.
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.

We have less and less options available for Linux distributions that have this objective “… try to keep CPU and RAM usage in idle to a minimum …”, this philosophy brought me here and keeps me, due to my goal of saving old computers ( that still work) from being thrown in the trash. But that’s not all that keeps me here, I just stayed here on the forum, due to the receptivity and all the support and help that we have from experienced colleagues (even with the daily challenge I have to interpret the translations). Without all the support and help needed, beginners in Linux distributions cannot start and continue alone, it is very difficult for anyone who is used to everything done in GUI mode on Windows, to start using Linux distributions that everything is done in CLI mode. It is unthinkable for a novice user, basic user or ordinary user to adjust the time the computer needs to apply commands on the terminal, this inevitably makes potential users end up giving up using the operating system.

PPC wrote:
@anticapitalista – as always, I greatly value your opinion! After all this fine OS is almost your “one man show” – and performs miracles of what would be, any other way, almost useless computers…

Among so many very important considerations made by the PPC, this represents the main one, the starting point. AnitX serves the layer that has been abandoned by most Linux distributions and Windows.

According to some Brazilian colleagues who have many years in this “world of Linux distributions”, Debian himself seems to seek self-isolation since he started using systemd. Also according to them, systemd tends to make life difficult for developers of Linux distributions based on Debian. And another issue repeatedly cited by them is the concern that capital would be forcing the end of Linux distributions to take Linux users for themselves.

SamK wrote:
Focusing on new users coming from Windows is in my view a fruitless exercise. The basic concept is flawed but is raised every few years. If it was going to work there would be a distro in existence that had already succeeded, to which all would go.

Microsoft itself throughout history has forced the user to abandon Windows or abandon the computer, forcing the user to buy new equipment. Unfortunately, several Linux distributions follow the same path, the planned or forced obsolescence of technology. These users are looking for an operating system similar to antiX, sooner or later they will arrive here on the forum.

SamK wrote:
It must be remembered, antiX is not Windows (or any other distro) and will never try to be. From its inception antiX had, and continues to have, a goal which is discussed less often than being lean and mean. Encouraging the user to learn Linux and understand what they are doing rather than just blindly clicking on an icon is every bit an antiX tenet as being lean and mean.

I believe that the first contact of new users with antiX needs to be as friendly as possible, so there is a greater chance that the community will grow and the greater the chances that more people will “fall in love” with antiX. Once this user “falls in love” with antiX, then he will be interested in studying and learning Linux, specifically antiX. In people’s lives, there are already many problems, operating systems need to offer solutions, instead of new problems.

Have you tried to identify the different levels of computer users that still exist in the 21st century?

1- Learner user – is learning to use a computer.

2- Beginner user – already learned to turn on the computer and identifies the internet browser and some programs.

3- Basic user – has already gone through the previous steps and already knows how to use the internet browser, Office package and already knows how to use the File Manager, but presents several difficulties in using these basic programs.

All of these users must use the antiX full ISO. Therefore, the full version needs to have many GUI, welcome screens, manual, shortcut icon on the desktop and everything that can show the simplest and easiest way. They probably don’t know how to install the operating system, CLI or even think, black screen keeps “normal” people away, that reminds MS-DOS, their answer is on the tip of the tongue “Linux is difficult!”. They are afraid of damaging the computer, in fact the operating system.

4- Ordinary user – learned to install and uninstall programs, it is curious, eventually destroys the operating system. You already know how to install an operating system. I believe that you still have to use the ISO of antiX full.

5- Average user – knows exactly what he wants, already knows how to do and does not destroy the operating system. You can probably use the base antiX ISO and have some kind of CLI skills.

6- Intermediate user – can use the base ISO, net and core and probably solve almost everything via CLI. The base antiX ISO should be considered by these users as “very easy” or “full” of menus.

7- Advanced user, developer, programmer, remasterizer and etc. – they do not need a GUI, I believe they should solve everything via CLI and sometimes they end up forgetting about “normal” users.

Guys, I don’t want to offend anyone with the definitions above, but this is the reality that I can identify in Brazil. How is it in your country?

The distance of knowledge between the basic user and the average user is years of study and research. We have to be aware that not everyone wants to learn that much just to use a computer.

In some Linux distributions, the community is simply not interested in apprentice, beginner, basic or even ordinary users. So, what should be the future of these Linux distributions? My answer: They will end, they just don’t know it!

I leave here my doubts:

1-Who are the team of developers?

2-Is there an organization chart specifying what each member of the developer team does or is responsible for?

3-How can the participants of this forum collaborate in any way with the work teams?

4-How can I collaborate with what little I know?

I’ve been here for seven months and I don’t know who the antiX developers are, I can identify the developers who create solutions to make antiX easier and easier to use, including PPC, Xecure and BobC (sorry if I still haven’t been able to identify all).

If there is an organization chart specifying what each member of the developer team does, in addition to the work to be performed, it may be that the members of the forum can identify work that can collaborate.

I hope you can reflect on my words.

If you do not speak English, I recommend translating my text in Brazilian Portuguese to your language.

Thank you.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Olá caros colegas,

Eu espero que compreendam bem as palavras que eu enviarei traduzidas pelo tradutor da internet do idioma Português do Brasil para o idioma Inglês. Eu espero que não haja mal entendido ou que entendam as minhas palavras como crítica ou algo que possa desanimar os desenvolvedores. A minha intenção é de colaborar com sugestões, visão futura e sobre as possibilidades.
Pessoal, temos dois tópicos diferentes e importantíssimos em andamento, tratando praticamente do mesmo assunto:

https://www.antixforum.com/forums/topic/ideas-for-improvements-in-future-releases/
e
https://www.antixforum.com/forums/topic/release-recommendation-usability-improvements-4/

Eu estou tentando acompanhar estes tópicos, mas eu não consigo acompanhar a velocidade da maioria do colegas, vocês são extremamente rápidos.

Há 1(um) ano e 1 mês atrás eu comecei a pesquisar sobre Linux, depois fui compreender sobre a existência das várias distribuições Linux. Há 7 (sete) meses atrás eu iniciei neste fórum. Eu pretendo ficar aqui no fórum enquanto vocês me permitirem permanecer. Desde de junho de 2020 eu venho aprendendo muito com vocês e em pouco tempo. Eu agradeço a todos!

Anticapitalista wrote:
I think this is a very fruitful discussion and well worth continuing.
How I see future antiX (ie the next stable ‘bullseye’ version).

É muito bom poder ler as suas palavras (no meu caso, palavras traduzidas pelo tradutor da internet para o idioma Português do Brasil) sobre o Futuro do antiX.

Eu acredito que para haver futuro, a comunidade do antiX precisa crescer, para isso é necessários novos usuários e a existência da nova geração, após alguns anos, precisamos novamente da nova geração e este ciclo precisa continuar se repetindo. Inevitavelmente as pessoas adoecem e infelizmente falecem. Se não houver a nova geração de novos usuários do antiX, a comunidade vai definhando e inevitavelmente chega ao fim. Alguém aqui deseja o fim do antiX? A minha resposta é “Vida eterna ao antiX!”.

Ao longo deste 1 ano e 1 mês, eu vi mais distribuições Linux serem descontinuadas do que novas distribuições Linux sendo criadas.

A nova geração, não é apenas direcionada aos novos usuários, mas também a nova geração de desenvolvedores e programadores. Neste quesito esta comunidade está excelente. Temos pessoas empenhadas, participativas e dispostas a colaborar inclusive com códigos de programação. Eu não enxergo um cenário tão otimista assim em outras comunidades Linux.

Anticapitalista wrote:
Certainly, IMO, including user written scripts have made antiX more user friendly.
eg the IceWM toolbar script, antiX-wifi switcher, android-device-connect, fast_personal_menu_editor, icewm-menu-recent-files and others, though I personally don’t use any of them. The downside to including these useful scripts is that the menu could be considered to be ‘bloated’.

Isso é motivador, ver os trabalhos de vários colegas do fórum sendo aceitos e implementados no antiX.

Tornar o antiX mais amigável e fácil de utilizar, basicamente é oferecer soluções por meio de GUI. Para quem são as interfaces gráficas?

Eu mesmo não possuo habilidade no terminal. Contudo, eu consigo fazer edições de arquivos de textos, ao menos eu estou “vendo” o que estou fazendo. No terminal, eu não “enxergo” o que o comando realiza. Mas a pergunta é: o usuário iniciante, usuário básico ou o usuário comum precisam realmente possui deste tipo de conhecimento?

Anticapitalista wrote:
What I don’t want is for antiX to be turned into something it is not meant to be.
For example, some in the past basically wanted it to be like a Debian lubuntu. If people want lxde, Xfce etc and ‘bells n whistles’ out of the box, then they really should try another distro.
We will always be systemd-free.
We will keep to IceWM/Rox default
We will ship with/promote our own (less known or even unknown) tools/apps over bigger and better known versions eg droopy, 1-1-voice etc.
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.

Cada vez temos menos opções disponíveis de distribuições Linux que possuem este objetivo “… tentar manter CPU e RAM uso em inatividade ao mínimo…”, esta filosofia me trouxe aqui e me mantém, devido ao meu objetivo de salvar computadores antigos (que ainda funcionem) de serem jogados no lixo. Mas não é só isso que me mantém aqui, eu só fiquei aqui no fórum, devido a receptividade e a todo o apoio e ajuda que nós temos dos colegas experientes (mesmo com o desafio diário que eu tenho em ter que interpretar as traduções). Sem todo apoio e ajuda necessário, iniciantes em distribuições Linux não tem como começar e continuar sozinho, é muito difícil para quem está acostumado com tudo feito em modo GUI no Windows, passar a utilizar distribuições Linux que tudo é feito em modo CLI. É impensável para um usuário iniciante, usuário básico ou usuário comum ajustar a hora do computador necessitar aplicar comandos no terminal, isso inevitavelmente faz usuários em potencial acabarem desistindo de utilizar o sistema operacional.

PPC wrote:
@anticapitalista – as always, I greatly value your opinion! After all this fine OS is almost your “one man show”- and performs miracles of what would be, any other way, almost useless computers…

Entre tantas considerações importantíssimas feitas pelo PPC, esta representa a principal, o ponto de partida. O anitX atende a camada que foi abandonada pela maioria das distribuições Linux e pelo Windows.

Segundo alguns colegas Brasileiros que possuem muitos anos neste “mundo das distribuições Linux”, o próprio Debian parece buscar o auto isolamento desde quando passou a utilizar o systemd. Ainda segundo eles, o systemd tende a dificultar a vida dos desenvolvedores das distribuições Linux baseadas em Debian. E outra questão repetidamente citadas por eles, são a preocupação de que o capital estaria forçando o fim das distribuições Linux para tomarem para si os usuários Linux.

SamK wrote:
Focusing on new users coming from Windows is in my view a fruitless exercise. The basic concept is flawed but is raised every few years. If it was going to work there would be a distro in existence that had already succeeded, to which all would go.

A própria Microsoft ao longo da história obrigou o usuário a abandonar o Windows ou a abandonar o computador, forçando o usuário a comprar outro equipamento novo. Infelizmente, várias distribuições Linux seguem o mesmo caminho, a obsolescência programada ou forçada de tecnologia. São estes usuários que buscam um sistema operacional semelhante ao antiX, cedo ou tarde chegarão aqui no fórum.

SamK wrote:
It must be remembered, antiX is not Windows (or any other distro) and will never try to be. From its inception antiX had, and continues to have, a goal which is discussed less often than being lean and mean. Encouraging the user to learn Linux and understand what they are doing rather than just blindly clicking on an icon is every bit an antiX tenet as being lean and mean.

Eu acredito que o primeiro contato dos usuários iniciantes com o antiX precisa ser o mais amigável possível, assim existe uma chance maior da comunidade crescer e maior será as chances de mais pessoas se “apaixonarem” pelo antiX. Uma vez que este usuário se “apaixone” pelo antiX, aí sim terá interesse e em estudar e aprender Linux, em específico o antiX. Na vida das pessoas, já existem muitos problemas, os sistemas operacionais precisam oferecer soluções, ao invés de novos problemas.

Já tentaram identificar os diversos níveis de usuários de computador que existem ainda no século XXI?

1- Usuário aprendiz – está aprendendo a utilizar um computador.

2- Usuário iniciante – já aprendeu a ligar o computador e identifica o navegador de internet e alguns programas.

3- Usuário básico – já passou pelas etapas anteriores e já sabe usar o navegador de internet, pacote Office e já sabe utilizar o Gerenciador de Arquivos, mas apresenta várias dificuldades em utilizar estes programas básicos.

Todos estes usuários tem que utilizar a ISO do antiX full. Por isso, a versão full precisa possuir muitas GUI, telas de boas vindas, manual, ícone de atalhos na área de trabalho e tudo que puder mostrar o caminho mais simples e fácil. Provavelmente não sabem instalar o sistema operacional, CLI nem pensar, tela preta afasta as pessoas “normais”, isso lembra o MS-DOS, a reposta deles estão na ponta da língua “Linux é difícil!”. Eles possuem medo de danificar o computador, na verdade o sistema operacional.

4- Usuário comum – aprendeu a instalar e desinstalar programas, é curioso, eventualmente destrói o sistema operacional. Já sabe instalar um sistema operacional. Eu acredito que ainda tem que utilizar a ISO do antiX full.

5- Usuário médio – sabe exatamente o que quer, já sabe fazer e não destrói o sistema operacional. Provavelmente consegue utilizar a ISO do antiX base e possui algum tipo de habilidade com CLI.

6- Usuário intermediário – consegue utilizar a ISO base, net e core e provavelmente resolvem quase tudo via CLI. A ISO do antiX base deve ser considerada por estes usuários como “muito fácil” ou “cheia” de menus.

7- Usuário avançado, desenvolvedor, programador, remasterizador e etc – não precisam de GUI, eu acredito que devem resolver tudo via CLI e às vezes acabam se esquecendo dos usuários “normais”.

Pessoal, eu não quero ofender ninguém com as definições acima, mas esta é a realidade que eu consigo identificar no Brasil. Como é no seu país?

A distância do conhecimento entre o usuário básico e o usuário médio são anos de estudo e pesquisa. Temos que ter a ciência de que, nem todas as pessoas pretendem aprender tanto assim só para utilizar um computador.

Em algumas distribuições Linux, a comunidade simplesmente não se interessa pelos usuários aprendiz, iniciante, básico ou até mesmo o comum. Então, qual deverá ser o futuro destas distribuições Linux? A minha resposta: Irão acabar, só não sabem disso!

Eu deixo aqui as minhas dúvidas:

1-Quem são a equipe de desenvolvedores?

2-Existe um organograma especificando o que cada integrante da equipe de desenvolvedores faz ou é responsável?

3-Como os participantes deste fórum podem colaborar de alguma forma com as equipes de trabalho?

4-Como eu posso colaborar com o pouco que eu sei?

Eu estou aqui há sete meses e não sei quem são os desenvolvedores do antiX, eu consigo identificar os desenvolvedores que criam soluções para tornar o antiX cada vez mais fácil de utilizar, entre eles PPC, Xecure e BobC (perdão se eu ainda não consegui identificar todos).

Se houver um organograma especificando o que cada integrante da equipe de desenvolvedores faz, além dos trabalhos a serem desempenhados, pode ser que os integrantes do fórum possam identificar um trabalho que possa colaborar.

Eu espero que possam refletir sobre as minhas palavras.

Quem não domina o idioma Inglês, eu recomendo traduzir o meu texto em idioma Português do Brasil para o seu idioma.

Muito Obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Member Xecure]

Thanks, Marcelo, for the feedback. It seems the VIA graphic chips don’t have the “disappearing icons” glitch, but the SIS do when running fbdev.

You are better off only testing on safe video mode. The VIA chips have better resolution and work well on them, and the SIS chips don’t have the “icon glitch” if they use vesa drivers (safe video mode).

So, when you test the installation, try it only with safe video mode and see if vesa drivers continue to be loaded on the installed system.

About streaming youtube, you are better off testing it using Streamlight as SamK recommends on a separate topic. You will probably have much better video experience.

About Porteus, it is unfortunate. But I understand they cannot attend to all posts. You were also testing a non-final release (it was a release candidate, which means it may need polish, fixing but is more stable than a beta). They are more interested in feedback of normal use, and it isn’t intended as a final stable release.

About more fluidity in this beta2, not much has changed, except for better installation sequence and package holding (but that shouldn’t influence much else). Performance is entirely thanks to the antiX Linux dev team’s effort. I barely only changed some things on what to add/remove from the build-iso process. Nothing can be attributed to me.

About firefox and drivers, Firefox may be replaced at some time in the future with a non-sse2 supported browser. Drivers are the same (they are in the 4.4 kernel) and I will not change that. I saw that “presumably” (not confirmed), a amd firmware update made an antiX user not able to boot (after said update). The firmware update was suspected, but not confirmed. This could mean that an update brought a regression for some older chips. If more people confirm this, I may pin (hold back) a certain firmware version that is known to work on those machines.

As there is little information related to this, I will wait for more confirmed cases.

Thanks again for testing things out. If after confirming that installation works and the system performs well, I think you can use this version.
Remember that antiX has a Snapshot tool that lets you create your won ISO files with the customization you make. Some people who have created “re-spins” have moved some of the home configs to /etc/skel/ before creating the snapshot so that their customized version of antiX can be easily installed on any system. This way you can set it up for the users before even booting and installing antiX on their machines.

Regards.

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

[Member marcelocripe]

Xecure,

I did test Porteus, but they weren’t good tests (I think I wasted my time …):

The latest version “Porteus-OPENBOX-v5.0rc2-x86_64.iso” has not even booted in graphical mode. I reported the tests I did and the flaws I found in the English language and in Portuguese.

The Porteus community, unfortunately, falls far short of this antiX community, the answers were extremely technical and aimed at those who have known Porteus for many years, they are not useful or sufficient for a beginner in this operating system.

The previous version “Porteus-OPENBOX-v5.0rc1-x86_64.iso”, starts in graphical mode, in a fluid way similar to the ISO “antiX-19-legacy-bet2_386-base.iso”. But, as the Porteus RAM memory consumption is approximately 155 MB, the response when opening programs is slower than in antiX. When trying to install, the Porteus partition manager does not start, I tried to install on an existing partition and the process started, I received the message “completed successfully”. After restarting the computer (which I described in the tests below with the ISO “antiX-19-legacy-bet2_386-base.iso”) it stopped on the black screen, in addition to displaying several errors. I will not waste any more time reporting failures in that community. I reported on the 17th and 18th of November 2020, I returned to the forum today, just to be able to inform you of the links and answer you with as much information as possible and complete. The forum answers do not help a beginner to solve the problem alone. The problem seems to be with the ISO. I got tired of seeing this in SliTaz, with each new ISO several new problems for users to be testing and having to solve everything on their own. In people’s lives, there are already many problems, operating systems need to offer solutions, instead of new problems.

Let’s go to what really interests us, antiX. This one is worth it, the community and antiX make every minute spent worthwhile, whether in tests or to collaborate with the operating system.

Results of tests with ISO “antiX-19-legacy-bet2_386-base.iso”.

ASUS P5V800-MX motherboard:
-I started in normal mode, Rox-IceWM, displayed a message on the screen “No frame was in use … the ‘Standard’ frame was selected. Use ‘rox -p = Defaut’ to enable it in the future. ”

Conky displays the 79.4 MB RAM consumption of the 936 MB available, $ sudo free {Enter} 75.16 MB RAM consumption of the 958 MB.

The images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are out of the normal order and appear disorganized, it has only antiX and Graphics. Program opening is faster than antiX 19.3 on a compatible motherboard. The “bet2” system is more fluid than the “bet1” version, there is a clear improvement in the response and in the movement of the windows of open programs, I opened several programs until the consumption of RAM reached 181 MB. It is interesting how the same ISO “antiX-19-legacy-bet2_386-base.iso” behaves differently, initialized in normal mode, but on a different motherboard. While I was looking for the programs through the menus that were disorganized, at some point, the “Applications” submenus organized themselves.

demo @ antix1: ~
$ inxi -G
Graphics:
Device-1: VIA CN700 / P4M800 Pro / P4M800 CE / VN800 Graphics [S3 UniChrome Pro]
driver: N / A
Display: x11 server: X.Org 1.16.4 driver: openchrome unloaded: fbdev, modesetting, vesa resolution: 800 × 600 ~ 85Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Table 18.3.6

demo @ antix1: ~
$ inxi -S
System:
Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32
Desktop: IceWM 1.9.2
Distro: antiX-19-legacy-bet2_386-base Lazarus 29 November 2020

I changed from Rox-IceWM to Space-IceWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are in the normal order after they have been organized by themselves.

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM, after organizing themselves.

I kept the various programs open and checked how the menus behave in each work area: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. All menus and submenus are OK and are free from defects.

I kept the various programs open and checked how the menus behave for the desktop for JWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are all OK and not have any type of defect. Then Minimal-JWM, Rox-JWM, Space-JWM, all behave as I described JWM.

I went back to Rox-IceWM, closed the various programs that I had opened, the RAM memory displayed by Conky went down to about163 MB, I opened Firefox 78.5.0esr (32 bit), playing a 21min36s video from YouTube, antiX started in normal mode has a low quality, but the idea of ​​this test is to simulate the condition that requires more processing resources and RAM memory, Conky displays consumption at about 487 MB while the video is played, $ htop {Enter} command CPU: between 67% and most of the time at 100%, Mem 582MB / 936MB and Swp 18.4MB / 1.89GB .

I restarted the computer, safe video mode, Rox-IceWM, the message that occurs in normal video mode did not appear that the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications ”Are out of the normal order and appear disorganized, have only antiX and Development.

Conky displays the 70.5 MB RAM consumption of the 936 MB available, $ sudo free {Enter} 72.97 MB RAM consumption of the 958 MB.

demo @ antix1: ~
$ inxi -G
Graphics:
Device-1: VIA CN700 / P4M800 Pro / P4M800 CE / VN800 Graphics [S3 UniChrome Pro]
driver: N / A
Display: x11 server: X.Org 1.16.4 driver: vesa resolution: 1024 × 7680 ~ N / A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Table 18.3.6

demo @ antix1: ~
$ inxi -S
System:
Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32
Desktop: IceWM 1.9.2
Distro: antiX-19-legacy-bet2_386-base Lazarus 29 November 2020

Still on Rox-IceWM, without opening any other program, besides the terminal, using Firefox 78.5.0esr (32 bit) playing a 21min36s YouTube video (the same test video with the normal video mode), the RAM memory displayed by Conky 407MB while the video is played, in secure video mode has a better quality than normal video mode, but the idea of ​​this test is to simulate the condition that requires more processing resources and RAM, Conky displays consumption in less than about 80 MB, command $ htop {Enter} CPU: between 67% and most of the time at 100%, Mem 511MB / 936MB and Swp 31.8MB / 1.89GB.

I changed from Rox-IceWM to Space-IceWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are in the normal order. I returned to Rox-IceWM and the “Applications” submenus are now in the normal order. Only the Package Manager (Synaptic) menu that is not in the “System” list. In the Control Center Synaptic opens

The Minimal-IceWM and IceWM workspace menus are similar to Rox-IceWM, after organizing themselves.

I kept the various programs open and checked how the menus behave in each work area: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. All menus and submenus are OK and are free from defects.

I kept the various programs open and checked how the menus behave for the desktop for JWM, the images of the menu icons do not disappear when the mouse arrow passes over the menus, the submenus of “Applications” are all OK and not have any type of defect. Then Minimal-JWM, Rox-JWM, Space-JWM, all behave as I described JWM.

Before doing the installation test, I would like to repeat the same tests on the other computer that is missing, so we will have more information available.

Xecure wrote:
I will probably experiment a bit more in the future by holding older amd/intel graphics firmware package if more people report having issues with antiX 19.3 (for now only one case).

My opinion is to have as many drivers available as possible. Thus it serves as many people as possible. Even if it makes the ISO bigger than a CD.

Removing Firefox can make the initial user experience bad if you access YouTube or other sites that require a more complete internet browser. Dillo and Links 2 have very specific characteristics. The way to watch YouTube videos that @PPC explained is the next step for the average or basic user, when they want to explore and learn about the available antiX resources (Thanks PPC). Myself, I haven’t had time to study and learn these valuable antiX resources, like watching videos without advertisements.

Thanks.

marcelocripe
(Original text in Brazilian Portuguese)

———-

Xecure,

Eu testei sim o Porteus, mas não foram bons testes (eu acho que perdi o meu tempo …):

A versão mais recente “Porteus-OPENBOX-v5.0rc2-x86_64.iso” sequer inicializou em modo gráfico. Eu relatei os testes que fiz e as falhas que encontrei na área em idioma Inglês e em Português do fórum.

A comunidade do Porteus, infelizmente, está muito aquém desta comunidade antiX, as repostas foram extremamente técnicas e direcionadas para aqueles que conhecem o Porteus há muitos anos, não são úteis ou suficientes para um iniciante neste sistema operacional.

A versão anterior “Porteus-OPENBOX-v5.0rc1-x86_64.iso”, inicia em modo gráfico, de forma fluída semelhante a ISO “antiX-19-legacy-bet2_386-base.iso”. Mas, como o consumo de memória RAM do Porteus é de aproximadamente 155 MB, a resposta na abertura dos programas é mais lenta do que no antiX. Nas tentativas de instalação, o gerenciador de partições do Porteus não inicia, eu tentei instalar em uma partição existente e o processo iniciou, recebi a mensagem de “concluído com sucesso”. Após reiniciar o computador (que descrevei nos testes abaixo com a ISO “antiX-19-legacy-bet2_386-base.iso”) parou na tela preta, além de exibir vários erros. Eu não vou perder mais tempo reportando falhas naquela comunidade. Eu reportei nos dias 17 e 18 de Novembro de 2020, retornei no fórum no dia de hoje, só para poder te informar os links e te responder com o máximo de informações possíveis e completas. As repostas do fórum não ajudam um iniciante a resolver sozinho o problema. O problema parece estar mesmo na ISO. Eu cansei de ver isso no SliTaz, a cada nova ISO vários problemas novos para os usuários ficarem testando e terem que resolverem tudo sozinho. Na vida das pessoas, já existem muitos problemas, os sistemas operacionais precisam oferecer soluções, ao invés de novos problemas.

Vamos para o que realmente nos interessa, o antiX. Este sim vale a pena, a comunidade e o antiX fazem valer a pena cada minuto desprendido, seja em testes ou para colaborar com o sistema operacional.

Resultados dos testes com a ISO “antiX-19-legacy-bet2_386-base.iso”.

Placa-mãe da marca ASUS P5V800-MX:
-Iniciei no modo normal, Rox-IceWM, exibiu uma mensagem na tela “Nenhum quadro estava em uso … o quadro ‘Padrão’ foi selecionado. Use ‘rox -p=Defaut’ para habilitá-lo no futuro.”.

O Conky exibe o consumo de memória RAM de 79,4 MB dos 936 MB disponíveis, $ sudo free {Enter} consumo de memória RAM de 75,16 MB dos 958 MB.

As imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX e Gráficos. A abertura dos programas está mais rápida do que no antiX 19.3 em placa-mãe compatível. O sistema “bet2” está mais fluído do que a versão “bet1”, é nítido a melhora na resposta e na movimentação das janelas dos programas abertos, eu abri vários programas até o consumo de memória RAM chegar até 181 MB. É interessante como se comporta diferente a mesma ISO “antiX-19-legacy-bet2_386-base.iso” inicializada em modo normal, mas em placa-mãe diferente. Enquanto eu ia buscando os programas pelos menus que estavam desorganizados, em algum momento, os submenus de “Aplicativos” se organizaram sozinho.

demo @ antix1: ~
$ inxi -G
Dados do comando no texto em inglês

demo @ antix1: ~
$ inxi -S
Dados do comando no texto em inglês

Alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão na ordem normal após se organizaram sozinho.

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM, após se organizaram sozinho.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam em cada área de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. Todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam para a área de trabalho para JWM, as imagens dos ícones dos menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão todos Ok e não apresentam qualquer tipo de defeito. Em seguida Minimal-JWM, Rox-JWM, Space-JWM, todos se comportam como descrevi o JWM.

Voltei para o Rox-IceWM, fechei os vários programas que eu havia aberto, a memória RAM exibida pelo Conky baixou para cerca de 163 MB, abri o Firefox 78.5.0esr(32 bit), tocando um vídeo de 21min36s do YouTube, no antiX iniciado em modo normal possui uma qualidade baixa, mas a ideia deste teste é simular a condição que exige mais recursos de processamento e memória RAM, o Conky exibe consumo em cerca de 487 MB enquanto o vídeo é tocado, comando $ htop {Enter} CPU: entre 67% e na maior parte do tempo em 100%, Mem 582MB/936MB e Swp 18.4MB/1.89GB.

Reiniciei o computador, modo de vídeo seguro, Rox-IceWM, não foi a exibida a mensagem que ocorre no modo de vídeo normal que as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão fora da ordem normal e surgem desorganizados, possui apenas antiX e Desenvolvimento.

O Conky exibe o consumo de memória RAM de 70,5 MB dos 936 MB disponíveis, $ sudo free {Enter} consumo de memória RAM de 72,97 MB dos 958 MB.

demo @ antix1: ~
$ inxi -G
Dados do comando no texto em inglês

demo @ antix1: ~
$ inxi -S
Dados do comando no texto em inglês

Ainda no Rox-IceWM, sem abrir qualquer outro programa, além o terminal, utilizando o Firefox 78.5.0esr(32 bit) tocando um vídeo de 21min36s do YouTube (o mesmo vídeo do teste com o modo de vídeo normal), a memória RAM exibida pelo Conky 407MB enquanto o vídeo é tocado, em modo de vídeo seguro possui uma qualidade melhor do que modo de vídeo normal, mas a ideia deste teste é simular a condição que exige mais recursos de processamento e memória RAM, o Conky exibe consumo em menor de cerca de 80 MB, comando $ htop {Enter} CPU: entre 67% e na maior parte do tempo em 100%, Mem 511MB/936MB e Swp 31.8MB/1.89GB.

Alterei de Rox-IceWM para Space-IceWM, as imagens dos ícones do menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão na ordem normal. Voltei para o Rox-IceWM e os submenus de “Aplicativos” agora estão na ordem normal. Só o menu do Gerenciador de Pacotes (Synaptic) que não está no sumenu “Sistema”. No Centro de Controle o Synaptic abre

O menus da área de trabalho Minimal-IceWM e IceWM estão semelhantes ao Rox-IceWM, após se organizaram sozinho.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam em cada área de trabalho: Fluxbox, Minimal-Fluxbox, Rox-Fluxbox, Space-Fluxbox. Todos os menus e submenus estão Ok e não apresentam qualquer tipo de defeito.

Eu mantive os vários programas abertos e verifiquei como os menus se comportam para a área de trabalho para JWM, as imagens dos ícones dos menus não somem quando a seta do mouse passa sobre os menus, os submenus de “Aplicativos” estão todos Ok e não apresentam qualquer tipo de defeito. Em seguida Minimal-JWM, Rox-JWM, Space-JWM, todos se comportam como descrevi o JWM.

Antes de fazer o teste de instalação, eu gostaria de repetir os mesmos testes no outro computador que falta, assim teremos mais informações disponíveis.

Xecure wrote:
I will probably experiment a bit more in the future by holding older amd/intel graphics firmware package if more people report having issues with antiX 19.3 (for now only one case).

A minha opinião é de ter disponível o maior número possível de drivers disponíveis. Assim atende um maior número possível de pessoas. Mesmo que isso faça a ISO ficar maior que um CD.

Remover o Firefox pode tornar a experiência inicial do usuário ruim, no caso de acessar o Youtube ou outros sites que exigem um navegador de internet mais completo. O Dillo e o Links 2 possuem características bem específicas. A forma de assistir vídeos do Youtube que o @PPC explicou é a próxima etapa do usuário comum ou básico, quando desejar explorar e conhecer os recursos disponíveis do antiX (Obrigado PPC). Eu mesmo, ainda não tive tempo de estudar e aprender estes recursos valiosos do antiX, como por exemplo assistir vídeos sem propagandas.

Obrigado.

marcelocripe
(Texto original em Português do Brasil)

[Member Xecure]

Thanks for the tests, marccelocripe. If you see safe video works as fast as with normal video on the SIS systems, try installing the beta2 on the machine (booted in safe video mode) and see how it goes. You installed porteus in one of them, so install antiX and compare the fluidity in comparison. It should work exactly the same as normal antiX on a similar system.

I think the ISO already is production ready for your machine. I will probably experiment a bit more in the future by holding older amd/intel graphics firmware package if more people report having issues with antiX 19.3 (for now only one case).

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

[Member olsztyn]

olsztyn wrote:

I am using SpaceFM as File Manager only. No Space-IceWM, no Icons on desktop and by doing just that the memory use is significantly less than Space-IceWM. I may try Rox and compare if any memory savings at all, not to flip to RoxFM, but just for benchmark.

Just to update:
I have done a rudimentary benchmark on freshly booted antiX with SpaceFm/IceWM and then RoxFM/IceWM and my memory reading was with my setup on Thinkpad X61/4Gb:
– antiX with SpaceFM/IceWM with no icons on desktop, so just IceWM – 223Mb
– antiX with Rox/IceWM – 229Mb

I am not sure if it is comparing apples to apples or apples to oranges, as someone may point me to imprecision in such testing but with this comparison I did I have slightly better memory footprint with IceWM with SpaceFM (Not Space-IceWM) comparing to Rox-IceWM.
So if if my testing is valid and not comparing apples to oranges then my conjecture would be that there is no particular evidence RoxFM saves memory footprint of antiX vs. SpaceFM.
Please correct me where my testing is not precise and result should be different…
Thanks and Regards…

• This reply was modified 2 years, 5 months ago by olsztyn.

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

[Member olsztyn]

SamK wrote:

I also find a welcome screen unappealing, particularly if it is shown by default.

I am just a user, so I do not mean to influence decisions and direction but let me just mention my perspective as user:
– antiX should maintain being lean and fast as much as possible under circumstances. It should boot to user desktop without any intermediary such as ‘welcome screen’. Lean does not need to imply mean however. IceWM as default is usable enough and can be made aesthetic too, if you find a good theme out there… However it took me long time to tweak parameters to make it behave correctly, with the help in this forum. After benchmarks of various ‘DEs’ I came to conclusion that unfortunately none of the common ones is code efficient, being just bloat, so not worth wasting memory footprint. The only one that is lean and almost matches overall memory footprint of antiX/IceWM is DE called ‘Fly’ adopted by Linux Astra (Thanks again Dzhigit!). But it seems not open source, so unlikely to be added to antiX.
– I agree with much of what SamK pointed out that default menu screen became way too crowded. I had to simplify by removing some entries, e.g. most IceWM configuration items and more. Once IceWM is configured they become just noise on the menu and prone to accidental changes if left there.
– antiX should maintain Debian compatibility. This is as long as it does not defeat the identity of being lean. I do not know gtk2/gtk3 difference but it seems in general that Linux in general has lost its own identity by blindly trying to follow Windows bloat, while past efficiency could have been still maintained with old leaner programming.

christophe wrote:

We will always be systemd-free.
We will keep to IceWM/Rox default
We will ship with/promote our own (less known or even unknown) tools/apps over bigger

– I like systemd-free architecture. But is it not going to become increasing difficult to maintain? This is just a question, not questioning…
– IceWM default is fine with some tuning. However you not want to enhance Fluxbox with Tint2 or something, so as memory footprint is maintained low and usability is enhanced? Also Rox seems entailing additional complexity of maintaining older, unsupported by Debian libraries going forward, so why not SpaceFM, which seems much superior to Rox? Just a question…
– Provided with antiX tools such as ISO-Snapshot, Live-USB-Maker and Remaster are a great value of antiX and should be maintained at all cost.

christophe wrote:

he live-system (including frugal, remaster, snapshot etc) seems to be working ok. However, the UEFI side probably needs to be improved to cater for more and more frugal/live users booting via UEFI since they have newer hardware.

– Indeed. Boot enhancements would be great, and to simplify boot process. I would suggest also bringing up in the boot menus the discovery of bootloaders and grubmenus, currently nested in deep submenus.

Just my two cents as user…
Thanks and Regards…

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

[Moderator christophe]

anticapitalista wrote:

Any official position by the main devs? I think this is a fruitless discussion if we are going to get shut down.

I think this is a very fruitful discussion and well worth continuing.

How I see future antiX (ie the next stable ‘bullseye’ version).

Due to many upstream changes in Debian, python2 and a lot of gtk2 will go.
That includes a few apps that have been ‘standard’ on antiX eg disk-manager, lxkeymap, lxappearance(?), gtkdialog and others.

Our in-house apps also have to be ported from python2/gtk2 as well.
Dave has already started porting them (in testing/sid branch). Most seem to work ok, but there are bugs – testing will be needed.

The live-system (including frugal, remaster, snapshot etc) seems to be working ok. However, the UEFI side probably needs to be improved to cater for more and more frugal/live users booting via UEFI since they have newer hardware.

Documentation certainly needs updating.

All the above will need to be done for the next stable release once Debian11 is out.

Making antiX more usable:

Certainly, IMO, including user written scripts have made antiX more user friendly.
eg the IceWM toolbar script, antiX-wifi switcher, android-device-connect, fast_personal_menu_editor, icewm-menu-recent-files and others, though I personally don’t use any of them. The downside to including these useful scripts is that the menu could be considered to be ‘bloated’.

Having some sort of script/app for hd screens is necessary.
Updating the control centre from gtkdialog to using Xecure’s dialogbox version will probably be needed at some point.
I’m not too keen on the idea of a Welcome app. However, that doesn’t mean that it will not be included if most of us here want it.

What I don’t want is for antiX to be turned into something it is not meant to be.
For example, some in the past basically wanted it to be like a Debian lubuntu. If people want lxde, Xfce etc and ‘bells n whistles’ out of the box, then they really should try another distro.
We will always be systemd-free.
We will keep to IceWM/Rox default
We will ship with/promote our own (less known or even unknown) tools/apps over bigger and better known versions eg droopy, 1-1-voice etc.
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.

Of course, antiX is far from perfect and needs to adapt to changes posed upstream.
We have already done so eg by no longer making the base iso fit on a cd.
Other compromises will no doubt follow at some point in the future.

confirmed antiX frugaler, since 2019

[Member ArchiMark]

Xecure wrote:

ArchiMark wrote:

Tried opening roxterm from urxvt, but got error messages;

$ roxterm
Illegal instruction

Same thing happens if I try to open firefox in urxvt….

I have a fear I hope isn’t real.

If you load the DVD/USB and select from the F4 menu:
checkmd5
or add this boot parameter:
checkfs

Do the tests pass? If the download was defective, one of both tests won’t pass, and that can lead to some programs failing. Hopefully nothing else important got corrupted. Best case scenario is reinstalling some programs. Worse case scenario is re-downloading the ISO and reinstalling the whole operating system. Let us hope only some programs got corrupted and the rest works.

Thanks for the suggestions…..

I did check the file, before installing….either md5 or sha256….can’t remember…but it matched….

[Member Xecure]

ArchiMark wrote:

Tried opening roxterm from urxvt, but got error messages;

$ roxterm
Illegal instruction

Same thing happens if I try to open firefox in urxvt….

I have a fear I hope isn’t real.

If you load the DVD/USB and select from the F4 menu:
checkmd5
or add this boot parameter:
checkfs

Do the tests pass? If the download was defective, one of both tests won’t pass, and that can lead to some programs failing. Hopefully nothing else important got corrupted. Best case scenario is reinstalling some programs. Worse case scenario is re-downloading the ISO and reinstalling the whole operating system. Let us hope only some programs got corrupted and the rest works.

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

[Moderator BobC]

Thanks for everyone’s input and help.

Etcher didn’t notice the USB data was invalid until after writing the USB. I didn’t try booting to Windows and running Rufus.

My f3 tests completed overnight and it found about 14 mb of data out of the 3.68 gb were wrong as compared to the test data it wrote, which would be major if it was an area a program was trying to use. Previously this flashdrive had not had any apparent problems, but keep in mind that I was burning an iso snapshot as a main system backup to it with live-usb-maker and hadn’t been testing trying to boot or install from it afterwards. Maybe I should have been doing that.

I will continue trying to learn… I still want to know if what I created is good or not.

My next thought is the question of: If the flashdrive is stable where that 14 mb is and stays the only bad area, are there ways I can use the flashdrive for bootable iso’s or for storing data safely, or should I just hrow it away?

[Moderator BobC]

Yes, a long time ago, on small USB’s once when I had problems with cheap ones being fakes, h2w on Win and then f3 on Linux was able to test them, but with these newer, bigger ones it was taking a day. It’s been running 2 hours now. I am hoping it will be done tomorrow sometime. That is to check 4 gb flashdrive. A 32 gb one would take about a week, but I gave up the last time I tried it. I found a script called log-f3wr and had to modify it to get it to work. It does an f3write, then f3read and logs the output to a file. This is my modified version.

#!/usr/bin/env bash
LOG=$1
f3write "${@:2}" 2>&1 | tee -a "${LOG}" && \
echo -e "\n\n" >> "${LOG}" && \
f3read  "${@:2}" 2>&1 | tee -a "${LOG}"

I showed at the beginning what I found to check a flashdrive written with a “normal” iso that was written using dd, and it works. It takes a minute or two to run.

With the antiX iso it doesn’t normally use dd to write, so the test used to check dd files written to read it doesn’t work. I understand how to calculate an md5 or sha512 of a file. My problem is that I don’t know what to compare to what. For example antiX creates and writes 2 partitions, one with ANTIX-UEFI, and the other with antiX-Live-usb. There must be some way to find out if when I read them, the data is the same as what was written or not, and if not, then there are differences, and its “invalid” in my book. Maybe I just didn’t say that clearly.

I guess I will try again looking at the script to try to see what it wrote to where. Maybe that will provide a clue. I don’t have bad flashdrives often, but it bothers me that I spent 4 or 5 hours failinag at trying to boot it because I didn’t know it was bad, and had to resort to installing Etcher to figure it out (or I could have used Windows and maybe Rufus would have told me). It previously had held my antiX backup, so I’m glad I found out it was bad before I needed that.

[Member ModdIt]

Thanks for deeper insights skidoo.
Any ideas welcome as to why live sticks failed to boot repeatedly using the system
tools but could be used after reformatting with. sudo mkfs.vfat /dev/sdXX.

I am wondering if live usb maker does a quick format. The full format would
I assume cause the stick controller to mark any bad blocks, maybe quick
would not do that.

The latest spate of problems was with 3 Intenso 32GB USB 3 sticks.
All had boot failure until fully formatted.
I had doublechecked the downloaded iso files before writing. No errors
from usb writing tool.

From here what helped me, hopefully clearly understandable.

All sticks were checked with F3 Tool after a full format to vfat using quoted command..
Capacity and state tested OK.
An antiX ISO was written on each stick. Runit Full
other two normal full latest 64 bit. All checksums ok.
All drives are used for live sticks and now still working ok.
All have been remastered several times.

@ BobC
A while back I posted on checking flash media with F3
rather than another big post just a pointer to the website.
The application is available in the repos.
Website
https://fight-flash-fraud.readthedocs.io/en/stable/

Maybe you can gain some insights by using the tools on your stick.

[Anonymous]

very strange. My “too many words” post was posted after this long post and the up arrow was intended to point back to this message. At this point, although I am able to edit THIS post, I cannot edit/delete that other post.

No, the program did not check if it had written the usb correctly for an antix iso.
It said it was successful, but when i shutdown and rebooted to it,
the checkmd5 failed and when I tried again the checkfs crashed the computer.

That sounds like it could be due to a missed call to sync (which would be a fixable bug)
leaving you with the incorrect impression that the copy operation had completed & safe to shutdown.

If you post the exact commandline options you used and/or the menu selections you chose, we can trace the workflow, checking for a missed sync call (but I doubt that’s what is happening, b/c a sync op is called at the foot of the script’s main() routine).

Alternatively, for testing/demonstration, could create a wrapper fn instead of calling sync directly, pop a yad dialog to report “script called sync here, and the sync operation has completed”

If the program had an option to check, that would be great.
I don’t have any idea how to check an antix iso manually, or I could have done that before shutting down.

md5sum /path/tofileA /path/to/fileB

whenever “have no idea” strikes, apropos is your everpresent friend.
apropos integrity
apropos verify
apropos sum
apropos md5
aha…
man md5sum

Whether or not a clicky menu option, specific to (re)checking iso md5sum on-demand, will be added into the live-usb-maker script is not my decision. As with several of the antiX utilities, I ‘spect the current version of live-usb-maker is not posted to the gitlab project repo, so I can’t act on your suggestion by patching to add the menu entry and sending up a suggested merge request.