Search Results for 'swap'

[Member evets 501]

System:
Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64
compiler: gcc v: 8.3.0 Desktop: IceWM 1.8.3
Distro: antiX-19.1_x64-full Marielle Franco 23 December 2019
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: Gigabyte model: GA-A75M-DS2 v: x.x serial: N/A
BIOS: Award v: F1 date: 03/27/2012
CPU:
Topology: Quad Core model: AMD A6-3650 APU with Radeon HD Graphics
bits: 64 type: MCP arch: Fusion L2 cache: 4096 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 20748
Speed: 800 MHz min/max: 800/2600 MHz Core speeds (MHz): 1: 800 2: 800
3: 800 4: 800
Graphics:
Device-1: AMD BeaverCreek [Radeon HD 6530D] vendor: Gigabyte Sumo
driver: radeon v: kernel bus ID: 00:01.0
Device-2: AMD Caicos PRO [Radeon HD 7450] vendor: Hewlett-Packard
driver: radeon v: kernel bus ID: 01:00.0
Display: server: X.Org 1.20.4 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1280×1024~60Hz
OpenGL:
renderer: AMD SUMO (DRM 2.49.0 / 4.9.235-antix.1-amd64-smp LLVM 7.0.1)
v: 3.3 Mesa 18.3.6 direct render: Yes
Audio:
Device-1: AMD FCH Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 00:14.2
Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: 2.3LK-NAPI port: de00 bus ID: 02:00.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 521.66 GiB used: 4.92 GiB (0.9%)
ID-1: /dev/sda vendor: Mushkin model: MKNSSDCR60GB-7 size: 55.90 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD5000LPVX-22V0TT0
size: 465.76 GiB
Partition:
ID-1: / size: 52.77 GiB used: 4.92 GiB (9.3%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 16.8 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: radeon temp: 46 C device: radeon temp: 21 C
Info:
Processes: 170 Uptime: 6m Memory: 6.81 GiB used: 474.8 MiB (6.8%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36
root@antix1:/home/Steve#
Habe ebenfalls den von anticapilatista genannten iptables fix ausgeführt. Offenbar bezieht sich dieser aber auf Kernel 4.9.200 wie von caprea beschrieben.Als ich diesen Fix ausführte kam darauf hin eine Meldung über”nur für manuellen Modus”Ansonsten habe ich “iptables-restore –h ausgeführt um an mehr Info zu kommen.Danach kamen tatsächlich eine Aufzählung mehrerer Punkte.Habe wohldie ersten 5 Punkte probiert ohne nennenswerten Ergebnisse.Die anderen Punkte schienen mir zu konkret in den Auswirkungen auf ufw um sie zu probieren

[Member kawe]

This is the most disappointing of my up to now reported starting troubles.
I am not even close to understand what is going on here.
And it pretty hard to trial and error if you have reboot (and additionally with orphaned file nodes to be cleaned up).

And rayluo is right to point to older topics (and lots around the Acer Extensa 5220). This was helpful. Thank you.

However, things got more complicated as before.

1. Some people reports that there troubles started with a kernel update (many years ago).
2. Some people think this might be rather a problem of the video driver than of the apm/acpi management.
3. It is reported that hibernate should work at least (but it fails with very similar problems also).
4. To my knowledge, there are no suspend/hibernation issues using other OSs including Win Vista that had been lived on the laptop for years (but has wiped out successfully now, 🙂 )

So all I can give for now are more symptoms but nothing close to a solution:

a) there in no single entry in the BIOS setup of this machine concerning APM/ACPI and restoring setup defaults doesn’t help either.
b) this issue is *not* antiX specific. I get the very same behavior if trying and resuming from a USB-Puppy Linux (BionicPup32, and it *does* suspend other machines correctly, ;-)).
c) reinstalling / reconfiguring acpi-support and even partly or totally (acpi-base) removing as Xecure suggested was virtually effectless.
d) I tried to add (yet) one kernel parameter (‘acpi_sleep=nonvs’, see: https://ubuntuforums.org/showthread.php?t=1556934) – didn’t help
e) I tried uswsusp (s2ram) instead: same issue (and: even s2disk first seems to work but fails in the last stages of reactivation)

What happens:
1) Entering the suspend mode seems to work very much like expected. After a friction of second the screen gets blank, hdd and fan stop and the power LED turns from steady green to blinking orange.
2) Waking the system starts also as expected: LED turns to steady green again, hdd awakes and the fan make some noises every now and then …
3) …an that’s it. The screen remains blank, no sound, (virtually) no keyboard response.
4) The systems remains stuck until hard shut down and rebooted.

You may also “wake up” the system by power switch. No difference.
O.k., maybe sometimes, maybe depending on my config trials, the system switches on then immediately (what is better than getting stuck, :-)).

And finally, when I tried s2disk to hibernate, the system hibernated to swap partition and switched off. The screen output is very hopeful.
Starting the system by power switch will (decompress and) resume from the swap image and finally – fail (and turns off again automatically).

So all I know for now is:

a) it is not antiX but likely Linux
b) it happens on acpi events but it might be some other hardware and I suspect the video system at first.

So filnally my next silly question:

The Acer seems to run with a i915 driver.
What is the best option to change this (temporarily) to a reasonable gereric (vbe?) driver in antiX?

Thank you all.

Greetings from Latvia!

Attention to broken Audacity 2.4.1 package.
Practically – there are no entry ‘Silence finder’ in menu “Analyze”.
Further – everything is missing that uses ‘Nyquist’ library.

Audacity team acknowledges problem.
(bad Nyquist library used when compiling … )

Every other [version of] Audacity within reach works good (for me):
[2.1.2; 2.2.2; 2.3.3; 2.4.2 …]

Problem is not recent; but I thought that some other will find it out. Sorry.

I do not understand how to install other version of Audacity that
differs from one in repository … .

If it is not possible to correct repository (seems to be — MX repository)
may be there are some method how to get working version of Audacity??

=====

After long time spent seeking other Linux I am back with AntiX … .

Best regards …

=============================================

I am on

System: Host: my Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: IceWM 1.8.3
dm: SLiM 1.3.6 Distro: antiX-19.2_x64-full Hannie Schaft 27 March 2020 base: Debian GNU/Linux 10 (buster)
Machine: Type: Laptop System: Hewlett-Packard product: HP ProBook 645 G1 v: A3009CD10203 serial: <filter> Chassis:
type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 1992 v: KBC Version 05.2E serial: <filter> BIOS: Hewlett-Packard
v: L72 Ver. 01.21 date: 09/16/2014
Battery: ID-1: BAT0 charge: 46.1 Wh condition: 46.1/46.1 Wh (100%) volts: 12.5/10.8 model: Hewlett-Packard Primary
type: Li-ion serial: <filter> status: Full
Memory: RAM: total: 14.88 GiB used: 319.3 MiB (2.1%)
Array-1: capacity: 16 GiB slots: 2 EC: None max module size: 8 GiB note: est.
Device-1: Bottom-Slot 1(top) size: 8 GiB speed: 1600 MT/s type: DDR3 detail: synchronous bus width: 64 bits
total: 64 bits manufacturer: Kingston part-no: 99U5428-018.A00LF serial: <filter>
Device-2: Bottom-Slot 2(under) size: 8 GiB speed: 1600 MT/s type: DDR3 detail: synchronous bus width: 64 bits
total: 64 bits manufacturer: Kingston part-no: 99U5428-018.A00LF serial: <filter>
CPU: Topology: Dual Core model: AMD A6-5350M APU with Radeon HD Graphics bits: 64 type: MCP arch: Piledriver rev: 1
L1 cache: 96 KiB L2 cache: 1024 KiB bogomips: 11578
Speed: 1400 MHz min/max: 1400/2900 MHz boost: enabled Core speeds (MHz): 1: 1400 2: 1400
Flags: 3dnowprefetch abm aes aperfmperf apic arat avx bmi1 clflush cmov cmp_legacy constant_tsc cpb cr8_legacy
cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid fma fma4 fpu fxsr fxsr_opt ht hw_pstate ibs
lahf_lm lbrv lm lwp mca mce misalignsse mmx mmxext monitor msr mtrr nodeid_msr nonstop_tsc nopl npt nrip_save
nx osvw pae pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_nb pfthreshold pge pni popcnt pse pse36
rdtscp rep_good sep skinit ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 svm svm_lock syscall tbm tce topoext tsc
tsc_scale vmcb_clean vme vmmcall wdt xop xsave

Audio: Device-1: Advanced Micro Devices [AMD/ATI] Trinity HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus ID: 00:01.1 chip ID: 1002:9902
Device-2: Advanced Micro Devices [AMD] FCH Azalia vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169
v: 2.3LK-NAPI port: 4000 bus ID: 01:00.0 chip ID: 10ec:8168
IF: eth0 state: down mac: <filter>
Device-2: Broadcom Limited BCM43228 802.11a/b/g/n driver: wl v: kernel port: 4000 bus ID: 03:00.0
chip ID: 14e4:4359
IF: wlan0 state: up mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> scope: link
WAN IP: <filter>
Drives: Local Storage: total: 465.76 GiB used: 5.58 GiB (1.2%)
ID-1: /dev/sda vendor: Seagate model: ST500LM012 HN-M500MBB size: 465.76 GiB speed: 6.0 Gb/s
rotation: 5400 rpm serial: <filter> rev: 0001 scheme: MBR
Message: No Optical or Floppy data was found.
Partition: ID-1: / size: 455.45 GiB used: 5.58 GiB (1.2%) fs: ext4 dev: /dev/sda1 label: rootantiX19
uuid: 73b184dd-e4b7-448b-a6d6-1b78e712ca24
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 label: swapantiX
uuid: f8726aca-2c62-4fe8-977e-51f136f2b63d
Unmounted: Message: No unmounted partitions found.
Sensors: System Temperatures: cpu: 48.8 C mobo: 0.0 C gpu: radeon temp: 45 C
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://ftp.cc.uoc.gr/mirrors/linux/mx/antix/buster buster main nonfree nosystemd
Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
1: deb http://deb.debian.org/debian buster-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.gr.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.gr.debian.org/debian/ buster main contrib non-free
2: deb http://security.debian.org/ buster/updates main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/onion.list
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
1: cpu: 3.8% command: xorg pid: 2797 mem: 54.8 MiB (0.3%)
2: cpu: 1.0% command: sudo pid: 30889 mem: 3.71 MiB (0.0%)
3: cpu: 0.8% command: leafpad pid: 29103 mem: 29.6 MiB (0.1%)
4: cpu: 0.6% command: roxterm pid: 29171 mem: 29.0 MiB (0.1%)
5: cpu: 0.4% command: conky pid: 3401 mem: 10.8 MiB (0.0%)
Memory top: 5
1: mem: 80.7 MiB (0.5%) command: apt-notifier.py started by: python pid: 3670 cpu: 0.0%
2: mem: 54.8 MiB (0.3%) command: xorg pid: 2797 cpu: 3.8%
3: mem: 45.5 MiB (0.2%) command: rox pid: 3316 cpu: 0.0%
4: mem: 29.6 MiB (0.1%) command: leafpad pid: 29103 cpu: 0.8%
5: mem: 29.0 MiB (0.1%) command: roxterm pid: 29171 cpu: 0.6%
Info: Processes: 155 Uptime: 1h 18m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8
Shell: bash (sudo) v: 5.0.3 running in: roxterm inxi: 3.0.36

[Member bb73]

#42134,
Thanks,Not really sure what Im doing just tinkering around and watching the dolphin tutorials, this is what I have done so far, see screenshot attachment. I also set up 1gb of swap not really sure if I needed to. I guess the next thing would be re-master, but not sure I know what Im doing there so will leave that till I have watched a few tutorials. I guess the upgrade has saved as showing 1.13gb used on rootfs 🙂

Attachments:

1. 

   screenshot-1.jpg
   

Nota: Isto é apenas uma tradução, adaptação e simplificação do excelente guia disponível, em inglês, em https://www.antixforum.com/forums/topic/step-by-step-guide-to-install-antix-os/#post-4198

*Versões do antiX:
O antiX está disponível em quatro “sabores” tanto para 32 como para 64 bits:

Completo (“full”): instala uma gama completa de aplicações
Base (“base”): Permite ao utilizador escolher o seu próprio conjunto de aplicações.
Núcleo (“Core”): O utilizador terá o controlo completo sobre quais as aplicações a instalar.
Net (“Net”): A edição mínima.

As versões “Core” e “Net” permitem ao utilizador ter controlo total sobre a instalação, dando-lhe a oportunidade de construir o sistema quase do zero. Deve ter conhecimentos de Debian para instalar e configurar as versões Core & Net.

*Requisitos do sistema

A página antiX FAQ dá as seguintes informações sobre os requisitos do sistema.
antiX-core e antiX-net funcionarão com 128MB de RAM mais swap, mas não espere milagres!

192MB de RAM é o mínimo recomendado para o antiX. 256MB de RAM e acima é preferido especialmente para o antiX-full.

O antiX-full precisa de um disco rígido mínimo de 3,8GB. O antiX-base precisa de 2,6GB e o antiX-core precisa de 1,0GB. O antiX-net precisa de 0,7GB.

A maioria dos utilizadores deverá utilizar o antiX-full, uma vez que oferece uma experiência completa de “desktop” (ambiente de trabalho) tanto em computadores antigos como modernos.

Se tiver um desktop (computador de mesa) ou um laptop (computador portatil) muito antigo, com menos de 256MB de RAM (PII, PIII), ou se quiser um desktop com “o básico”, é provavelmente melhor usar o antiX-base.

Live USB/CD
O antiX também pode ser usado como CD de salvamento rápido, ou correr “Live” (“ao vivo”) numa pen USB, com ou sem armazenamento de ficheiros persistentes. Leia mais abaixo, sob o título “Persistência” para obter informações sobre “armazenamento de ficheiros/arquivos persistente”. Para detalhes sobre o primeiro ecrã do sistema Live, ver a secção “O PRIMEIRO ECRÃ DE BOOT do SISTEMA LIVE”.

DOWNLOAD

Descarregue a ‘imagem ISO antiX’ a partir do website: https://antixlinux.com.

Enquanto descarrega a sua versão antiX requerida, certifique-se também de descarregar os ficheiros md5, sha256 e sig correspondentes para verificar a integridade da imagem ISO descarregada. Coloque todos estes ficheiros, incluindo a imagem ISO, na mesma pasta. Isto ajuda a verificar a integridade da imagem ISO descarregada.

Após o descarregamento, verifique a integridade da imagem ISO descarregada, conforme abaixo:

** VERIFICAÇÃO DA INTEGRIDADE DO FICHEIRO ISO (Passo facultativo)

Verifique ou md5sum ou sha256sum.

O procedimento documentado abaixo pode funcionar num sistema Linux. No entanto, se estiver agora num sistema Windows, dei uma ligação abaixo onde o procedimento para verificar a integridade de um ficheiro ISO no Windows é dado.

https://forums.linuxmint.com/viewtopic.php?f=42&t=291093

Verificação da integridade de um ficheiro ISO em qualquer sistema Linux:
Encontre o caminho para a sua pasta de transferências. Se for para a pasta descarregada com a ajuda do gestor de ficheiros/arquivos SpaceFM (ou qualquer gestor de ficheiros/arquivos, dependendo do sistema operativo actual, o seu computador), o caminho para a pasta de transferências é dado na barra de endereço quando abre a pasta respectiva. Se o seu ficheiro/arquivo ISO for descarregado para a pasta ‘Downloads’, o caminho será ‘/home/seu nome de utilizador/Downloads’. Se tiver guardado o seu ficheiro ISO noutro lugar, será diferente.

Por exemplo, os nomes dos ficheiros que foram descarregados são os seguintes; (O seu pode ser diferente).

antiX-19.2.1_x64-base.iso.
antiX-19.2.1_x64-base.iso.md5
antiX-19.2.1_x64-base.iso.sha256

Não se esqueça que a primeira letra, o ‘a’ de ‘antiX’ é uma letra minúscula e a última letra ‘X’ está maiúscula.

Abra um terminal em modo “root” (Menu > Aplicações > Sistema > …) e vá para a pasta onde descarregou a ISO, digitando ‘cd’ seguido do caminho para a sua pasta no terminal, como se mostra abaixo;

cd /caminho para a sua pasta descarregada/antiX-19-2-1-x64-base

(Aqui dei o nome do ficheiro de exemplo. O seu pode ser diferente. Portanto, adapte para o nome do ficheiro que descarregou).

Agora está dentro da pasta que descarregou.

Verificar o md5sum

Verifique o md5sum do ficheiro iso, digitando o comando no Terminal, como se mostra abaixo;

md5sum antiX-19.2.1_x64-base.iso

Não se esqueça de mudar para o nome do ficheiro que descarregou.

Como resposta irá receber um número, como se mostra abaixo (o seu pode ser diferente); (Não feche ainda o terminal).

53ec93c66f0ba7231f5a2aaf2fcb312b antiX-19.2.1_x64-base.iso

Verifique este número com o número incluído dentro do ficheiro antiX-19.2.1_x64-base.iso.md5. Ambos devem idênticos, caso contrário, a imagem que descarregou pode ter sido comprometida ou ter-se corrompido. Se isso acontecer, terá que a descarregar novamente.

Verificação do sha256sum:

A seguir, verifique o sha256sum do ficheiro ISO, como se mostra abaixo;

sha256sum antiX-19.2.1_x64-base.iso

Não se esqueça de mudar para o nome do ficheiro que descarregou.

Receberá um conjunto de números e letras, como se mostra abaixo (o seu pode ser diferente); (Não feche ainda o terminal).

1bdcd8c460bb7b0dd498588c6f459906e06eea24e2048f63815a14c6f54cb959 antiX-19.2.1_x64-base.iso

Verifique este ncódigo com o código dado dentro do ficheiro antiX-19.2.1_x64-base.iso.sha256. Ambos devem ser idênticos, caso contrário, a imagem descarregada pode ter sido comprometida ou ter ficado corrompida e terá que a descarregar novamente, de preferência a partir de um “mirror” diferente.

Minimize o Terminal.
gpg –keyserver hkp://keys.gnupg.net –recv-keys 4A0C4F9C

E depois, no terminal da pasta ISO, aquela que minimizou, escreva este comando;

gpg --verify antiX-19.2.1_x64-base.iso.sig antiX-19.2.1_x64-base.iso

Mais uma vez, não se esqueça de mudar para o nome do ficheiro que descarregou.

O resultado seria semelhante a este;

gpg: Assinatura feita Dom 29 Mar 2020 08:52:05 PM IST
gpg: usando a chave RSA 30AA418A0C723D937B50A986A80582E000067FDD
gpg: Boa assinatura de "anticapitalista <antiX@operamail.com>" (desconhecido)
gpg: AVISO: Esta chave não é certificada com uma assinatura de confiança!
gpg: Não há qualquer indicação de que a assinatura pertença ao proprietário.
Impressão digital da chave primária: 30AAA 418A 0C72 3D93 7B50 A986 A805 82E0 0006 7FDD

Se o procedimento acima falhar, faça isto:

Para verificar a assinatura digite primeiro o comando para importar a chave no terminal;

gpg --keyserver hkp://keys.gnupg.net --recv-keys B9B6375C 0679EE98 892C32F1

E depois no terminal da pasta ISO, aquela que minimizou, escreva este comando;

gpg --verify antiX-19.2.1_x64-base.iso.sig antiX-19.2.1_x64-base.iso

Mais uma vez, não se esqueça de mudar para o nome do ficheiro que descarregou.

O resultado seria semelhante a este;

(ak@ak-RV509 ~)$ gpg --keyserver hkp://keys.gnupg.net --recv-keys B9B6375C 0679EE98 892C32F1
gpg: chave 13C74A22892C32F1: chave pública "Steven Pusser <stevep@mxlinux.org>" importada
gpg: chave 70938C780679EE98: chave pública "Adrian <adrian@mxlinux.org>" importada
gpg: chave 9B68A1E8B9B6375C: chave pública "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>" importada
gpg: Número total processado: 3
gpg: importado: 3
(ak@ak-RV509 ~)$  

Feche este terminal recém-aberto.

Depois escreva o seguinte comando no terminal que minimizou, para verificar a assinatura:

gpg --verify antiX-19.2.1_x64-base.iso.sig

O resultado seria semelhante a este:

(ak@ak-RV509 antiX-19-2-1-x64-base)$ gpg --verify antiX-19.2.1_x64-base.iso.sig
gpg: assumindo dados assinados em 'antiX-19.2.1_x64-base.iso'.
gpg: Assinatura feita Domingo 29 Março 2020 08:52:05 PM IST
gpg: usando a chave RSA 30AA418A0C723D937B50A986A80582E000067FDD
gpg: Boa assinatura de "anticapitalista <antiX@operamail.com>" (desconhecido)
gpg: AVISO: Esta chave não é certificada com uma assinatura de confiança!
gpg: Não há qualquer indicação de que a assinatura pertença ao proprietário.
Impressão digital da chave primária: 30AAA 418A 0C72 3D93 7B50 A986 A805 82E0 0006 7FDD
(ak@ak-RV509 antiX-19-2-1-x64-base)$ 

O aviso nas últimas linhas está relacionado com a confiança que se deposita na chave de assinatura antiX. A imagem ISO continua correcta, e válida de acordo com a chave de assinatura antiX que descarregou.

**CRIAÇÃO DO DISPOSITIVO USB “BOOTÁVEL” (de arranque)

É necessário um mínimo de 2GB de cartão SD ou unidade USB para proceder à instalação. Se deseja ter um dispositivo USB com persistência “ao vivo”, então necessitará de mais.

Pode criar um DVD “bootável”. É o mesmo procedimento para ambos os casos.

Agora crie o USB de arranque com a imagem ISO do antiX-19.2.1-x64-Base imagem ISO como indicado:

Para isso, precisa de um software chamado “USBMaker-git”. Ele está disponível na maioria das distribuições Linux, no instalador de pacotes. Instale-o se ainda não estiver instalado. Este procedimento pode ser feito em muitos softwares de fabrico Live USB que estão disponíveis em muitas distribuições Linux. Basta tentar e verificar qual funciona para si. Ou então pode criar o usb inicializável num sistema operativo antiX, se um estiver acessível a si. Existe um usb de arranque que foi criado pela equipa antiX, e é instalado por defeito no SO anitiX. Inicie-o a partir de Menu > Aplicações > antiX > “Live USB maker”. Se estiver no SO Windows, é sugerido e recomendado por especialistas o software “Rufus” USB.

Após lançar o “criador de disco USB”, siga as instruções simples que se seguem. O processo é semelhante na maioria dos fabricantes de USB. Estou a dar aqui o procedimento sobre o USBMaker-git.

Dispositivo
No topo, o dispositivo é a unidade USB que escolheu para criar o dispositivo de arranque, ou seja, o leitor de cartões e o cartão dentro dele. Para tal, será necessário um cartão sd de 2GB, no mínimo.

Esquema de partição
Deixe o esquema de partição como MBR se o computador que vai instalar for antigo com a configuração da BIOS. Se o computador for novo com a configuração UEFI, então escolhe o esquema GPT. Em seguida, escolha o sistema de ficheiros como FAT32.

Tamanho do cluster – por defeito.

Etiqueta do volume
Dê uma etiqueta de volume do seu agrado, de modo a poder reconhecer o que está dentro do cartão SD.

Imagem ISO
De seguida clicar no botão de 3 pontos. Navegue até à localização da ISO que descarregou. É isso mesmo. Clique em start. O seu USB de arranque será criado.

** DEFINIÇÕES DA BIOS

A seguir tem de configurar o seu computador para arrancar a partir do seu USB de instalação. Para o fazer, tem de entrar na secção de configuração da BIOS do computador.

A maioria dos computadores não precisa desta configuração de BIOS para instalar um sistema operativo a partir de USB. Eles já estão configurados para arrancar a partir de USB primeiro. Portanto, primeiro tente ver se o seu computador inicializaria a partir de USB. Se não, configure então a BIOS para arrancar a partir de USB como primeira prioridade, como mencionado abaixo.

Para configurar a sua BIOS para arrancar a partir de USB, reinicie o seu computador, e imediatamente após ligar o computador, comece a premir, F2, F4 ou F8 ou podem também ser outras teclas. Cada computador tem uma chave diferente.

Uma vez no menu da BIOS, navegue até à secção “Boot” utilizando as teclas do cursor. Leia atentamente as instruções à direita. Definir a prioridade de arranque a partir de “USB” como a opção mais alta ou a primeira opção, depois a unidade de CD/DVD e depois o disco rígido. Guardar as alterações e saia. Será automaticamente inicializado na sua instalação Live USB. Terá um menu de arranque. Seleccione o sistema operativo antiX e prima enter.

**O PRIMEIRO ECRÃ DE ARRANQUE DO SISTEMA "LIVE"

Quando o primeiro ecrã do sistema “Live” surge, encontrará várias opções com as teclas “F” para facilitar o arranque em qualquer hardware. Não há necessidade de se assustar ao ver tantas opções. As coisas são muito fáceis se seguir apenas uma dica, ou seja, se não entender nada, deixe as coisas como estão, excepto fazer algumas coisas básicas sugeridas abaixo. Mesmo que não defina nada aqui, terá a oportunidade quando arrancar para o sistema Live e mesmo depois de instalar. Portanto, não precisa de se preocupar com nada. Pode limitar-se a coisas básicas como linguagem e zona horária. Se precisar de mais detalhes, prima F1. Se achar que são necessárias mais explicações, vá para o link abaixo que explica tudo neste ecrã em detalhe;

https://download.tuxfamily.org/antix/docs-antiX-19/Boot_Menu/antiX-gfxboot.html

Defina a sua língua através da tecla F2.

Para definir o fuso horário, use F3.

Use F6 para definir o ambiente de trabalho. Se estiver confuso, basta deixá-lo como está. Obterá a combinação padrão “ROX-IceWM”. Pode alterá-lo mais tarde.
Se tiver menos de 128MB de RAM, e quiser testar o antiX ao vivo, escolha uma das opções min- via tecla F6.

Pode actualizar a base de dados do sistema (update), actualizar (upgrade) e instalar aplicações durante a sessão em directo, elas serão “transportadas” para a instalação real no disco rígido. Pode configurar a Internet mesmo em modo “Live”, os seus dados (por exemplo, sobre a rede Wi-fi) Serão transportados para a instalação real.

Se desejar criar uma instância “persistente”, veja a secção abaixo. Se não, depois de configurar tudo, para entrar a seguir, no sistema live, seleccione para arrancar na versão antiX que descarregou e criou o USB/CD Live e carregue em enter. (É a primeira escolha e já está seleccionada por defeito).

**Persistência

A persistência é um híbrido entre um LiveCD/USB e uma instalação completa. Uma das belezas de um LiveCD é que permite arrancar o Linux sem tocar em qualquer disco rígido para que possa ter um “test-drive” sem medo de alterar o seu sistema actual. Outra característica de um LiveCD é que, uma vez queimado, é quase impossível que seja infectado com um vírus ou um cavalo de Tróia. Cada vez que o arranca, começa com um sistema limpo e imaculado. A persistência dá-lhe uma forma de se lembrar das coisas entre botas. Para o fazer, necessita de acesso a um dispositivo de leitura-escrita, tipicamente um disco rígido ou uma pen drive USB.

Para detalhes completos sobre persistência visite a seguinte página no site antiX FAQ (em inglês):

https://download.tuxfamily.org/antix/docs-antiX-17/FAQ/persistence.html

**PARTICIONAMENTO DO DISCO RÍGIDO

Esta é a parte mais importante. Se for utilizar todo o disco rígido e este estiver vazio, então não há problema. Se tiver algumas partições nas quais existam dados, terá de ter cuidado. Se cometer o menor erro, os seus dados no disco rígido podem ficar corrompidos ou ser apagados. Portanto, faça uma cópia de segurança do seu HD. Passe por este processo com muita cautela. Tome as medidas apenas quando tiver a certeza suficiente. Recomendo que procure na web e veja alguns tutoriais em vídeo ou leia alguns websites sobre “como utilizar o Gparted para fazer partições”, antes de prosseguir.

Embora seja possível criar partições durante a instalação, é prefirivel criar partições antes da instalação, em vez de o fazer no meio do processo de instalação. Use Gparted para o fazer. Se se sentir à vontade para o fazer durante a instalação, não se preocupe. É um processo guiado. Pode fazer o que preferir.

Os ficheiros do SO Linux são armazenados numa partição chamada como partição raiz (/), que guarda todos os ficheiros do sistema. Deve ser formatado de preferência como ext4 e montado em /.

O SO Linux armazena os ficheiros do utilizador como, Documentos, Downloads, Vídeos, Música, etc, num directório chamado directório /home (a barra ‘/’ é para root e a pasta ‘home’ que alberga a, Documentos, Downloads, Vídeos, Música, etc, é colocada dentro da partição raiz). Todas as definições e configurações do utilizador são também colocadas nesta pasta /home como pastas ocultas.

Deve ser formatada de preferência como “ext4” e montada em “/home”.

Alguns utilizadores preferem manter esta pasta “/home” numa partição separada. Ou pode escolher não ter uma partição separada para home e optar por mantê-la como directória (pasta) na raiz. Tem a opção de o fazer durante o processo de instalação. Pode fazer o que preferir. Se optar por mantê-la como directória na raiz, não deve criar agora a partição “/home”. Na realidade, o SO Linux NÃO precisa de uma partição /home separada. A /home só é necessária no caso de não querer que os ficheiros do utilizador sejam armazenados na partição /root ou se quiser um utilizador acessível a partir de diferentes sistemas instalados (arranque múltiplo). A razão pela qual algumas pessoas preferem ter uma partição separada é, no caso de destruírem o seu sistema e terem de ir para uma reinstalação, não perderão o que está na sua partição “home” separada. Portanto, a escolha é sua. Durante a instalação, pode especificar a /home para estar dentro da raiz ou como uma partição separada.

O SO Linux necessita opcionalmente de uma partição chamada Swap para memória quando a sua RAM ficar toda preenchida. Deve ser formatada como swap. Se estiver com pouca RAM, irá beneficiar de ter uma partição swap. (Poderá não é necessária.)

Escolha cerca de 10 a 15GB de espaço para ‘root’, dependendo do tipo e tamanho das aplicações que vai utilizar. Depois, se estiver a criar uma partição Swap, dê-lhe 1,5 vezes o tamanho da sua RAM (se a sua RAM for 3GB, a sua Swap deverá ser 3×1,5=4,5GB). E mantenha o resto do espaço para “/home”.

Se optar por fazer as partições durante a instalação, o procedimento é quase o mesmo. O Dolphin Oracle fez um vídeo sobre isso.

**INSTALAÇÃO DO SISTEMA OPERATIVO

A maior parte do processo de instalação é automatizado. No entanto, antes de proceder à instalação, é necessário configurar a ligação à Internet.

Iniciar a ligação à Internet

Estabelecer a ligação à Internet Wi-Fi: Utilizar o ícone de Ligação de Internet, as duas setas, na parte inferior direita, junto ao relógio, para a configurar. Clique com o botão direito nas duas setas, e clique com o botão esquerdo do rato em “WiFi” para o ligar. De seguida clique com o botão esquerdo do rato no ícone de Ligação de Internet e mantenha-o premido. Deverá aparecer uma lista das redes WiFi disponíveis. Aguarde alguns segundos para preencher a lista. Mova-se para a que pretende e depois solte o botão esquerdo do seu rato. Deve aparecer o aviso de palavra-passe (“passphrase”). Introduza-a e clique em “aplicar”( Apply). Deverá ver algumas barras verticais amarelas e vermelhas no monitor da rede WiFi à direita, junto ao relógio, e o pequeno x ao lado das setas no ícone do Connection-manager irá desaparecer. Se tiver alguma dificuldade, pode ver este vídeo aqui – https://www.antiXforum.com/forums/topic/wifi-with-connman-antiX-19-2/.

Se tiver uma ligação Ethernet, basta ligar o cabo Ethernet a partir do seu modem, introduzir a palavra-passe de utilizador que lhe foi dada pelo seu fornecedor de serviços de Internet, se for necessário.

Se não conseguir ligar-se nem ao WiFi nem à Ethernet, basta ligar o seu telefone com um cabo de dados USB e escolher as opções de ligação no seu telefone. Os seus dados devem estar ligados. A ligação será fácil. Deve estar ciente de que, a primeira actualização & actualização consumirá cerca de 400 MB de dados mais quaisquer aplicações que instale manualmente.

Actualização da base de dados (update) e actualização do sistema (upgrade)

Agora actualize o sistema com os seguintes comandos, no terminal. Também pode usar o antiX Updater (Menu > Aplicações > antiX > antiX Updater) que faz ambos os passos num único programa GUI.

sudo apt-get update

Carregue em enter e escreva a sua palavra-passe quando lhe for pedido e carregue em enter. A palavra-passe predefinida no antiX Live USB é ‘demo’. [Para acesso root, a palavra-passe é ‘root’. Por favor, não faça o login como root. É totalmente desnecessário]. A sua palavra-passe não será exibida no ecrã. Basta escrevê-la correctamente e pressionar enter cegamente. Após a actualização estar completa, escreva o seguinte no terminal e carregue em enter;

sudo apt-get upgrade

Escolha as partições

No ambiente de trabalho existe um atalho para iniciar o processo de instalação. Faça um único clique sobre ele. Lembre-se, um duplo clique trará uma notificação de erro. Está no ROX-IceWM, pelo que um simples clique é o que precisa para iniciar as aplicações. Contudo, se precisar da opção de duplo clique, pode fazer o seguinte.

Menu > Aplicações > Sistema > Rox Filer > Clique com o botão direito do rato em qualquer espaço vazio dentro do gestor de ficheiros > Opções > Janelas de filtragem > Desactivar “Navegação com o botão direito do rato”.

A seguir, escolha as partições, se já tiver criado as partições. Se não tiver o processo guiado irá levá-lo a cabo.

Durante a instalação, a escolha das partições correctas é um assunto sério. Essas partições são formatadas antes da instalação por parte do instalador. Mesmo se optar por não formatar a partição /home, deve formatar a partição /root. Por isso, tem de escolher as partições correctas. Se escolher outra coisa por engano, os seus dados nessa partição serão apagados.

Definir idioma e fuso horário e nome de utilizador

Durante o processo de instalação, clique nos botões seguintes para configurar a sua hora, data, fuso horário, teclado, nome de utilizador, palavra-passe, etc. Não há necessidade de se apressar, o processo de instalação aguardará até que tenha terminado de o fazer. É tudo. O resto será tratado pelo instalador USB.

Após a instalação, desligue o computador, retire o USB e inicie o computador. Será inicializado no novo sistema operativo antiX.

Below is the thorough step by step guide to install the crispy, nimble, lean and mean antiX Operating system for computers ranging from 30 year olds to the latest. The following guide was documented keeping in mind the installation of antiX-Base-64bit version, but is equally applicable to the installation and setup of both antiX Full and Base instances and for 32 and 64 bit computers. A person having knowledge of Debian and opting to install Core and Net editions, and building up from scratch, would probably not need this guide but still it can be used for reference.

The below guide has been edited to incorporate the suggestions made by experts after scrutiny. There is a section under the heading “CHANGING THE DEFAULT SETTINGS”. It is recommended that the default settings be maintained. If you do not want to change the default settings, you can skip this section and directly go to the next, ‘USER SETTINGS’ section. Still if anybody feels that the default settings need to be customized to fit their needs, they can attempt the changes as given under the section.

Normally you should be able to setup a working antiX system with the help of this guide. Still if you face any difficulties, feel free to discuss them on the forum by creating a new thread mentioning your issue in the topic heading. Please kindly give a link to your new thread here that you have created seeking solution to your issue, and post here briefly describing your issue. Suitable changes can be made to this guide depending upon the discussions in that new thread of yours, so that others who face the same issue can benefit from it. Let us together keep this guide dynamic and evolving.

I personally have created more than 20 threads till now to seek solutions faced while installing antiX and using it and to understanding the working of antiX. Many honorable members of the forum, who have been using antiX for a long time, the moderators of the forum and the antiX team have guided me into learning to install and use antiX and it is the education received from them, that has enabled me to compile this guide. You too can find solutions to any of your issues on the forum. The enthusiastic members of the forum and the antiX team are highly benevolent and would help. Here is the link to antiX forum: https://www.antixforum.com/

Moreover you have the video guides of Dolphin Oracle. They are detailed and highly helpful. Here is the link to the videos:
https://www.youtube.com/user/runwiththedolphin/videos

I thank all the honorable members for suggesting improvements in the guide through their meticulous scrutinizing efforts.

How to Install antiX
***********************

Index

INTRODUCTION
System requirements
Live USB/CD
DOWNLOAD
VERIFICATION OF THE INTEGRITY OF THE ISO FILE
Verifying md5sum
Verifying sha256sum
Open a new terminal.
Verification of signature
CREATING THE BOOTABLE USB
THE FIRST BOOT SCREEN OF THE LIVE SYSTEM
Persistence
PARTITIONING THE HARD DISK
INSTALLATION OF THE OPERATING SYSTEM
Starting Internet
Update and upgrade
Choose the partitions
Setting Language, timezone & Username
SETTING UP THE NEW antiX OS
Package Installer
Synaptic package Manager
CHANGING THE DEFAULT SETTINGS
Desktop right-bottom tray
Desktop left-bottom
Conky disabling
Menu updating – manual
Menu updating – system
USER SETTINGS
Desktop Background/Wallpaper
Screen blanking
Ad blocking
Sound problems
User Accounts
A WORD ON DESKTOPS
A WORD ON FRUGAL INSTALL

INTRODUCTION

The name ‘antiX’ is written with the first alphabet ‘a’ being a small letter and the last alphabet ‘X’ being a capital letter. That is how it has been named and recognized.

antiX is a Linux distribution comparatively lightweight and suitable for older computers, while also providing cutting edge kernel and applications, as well as updates and additions via the apt-get package system and Debian-compatible repositories. Besides the standard LIVE release, other versions of antiX are available (base and core), allowing installations with even lower amounts of RAM, hard drive space, and overall hardware limitations. The goal of antiX is to provide a light, but fully functional and flexible free operating system for both newcomers and experienced users of Linux. antiX is set up using Debian Stable repositories by default. This allows users to keep their system up to date with regular upgrades.

Using apt-get or install and use aptitude (but keep to one) from the command line is recommended.

antiX comes in four flavors for both 32 and 64 bit boxes:

Full: Installs a full range of applications
Base: Allows the user to choose their own application suite.
Core: The user will have complete control over what applications to install.
Net: The minimal edition.

The Core & Net versions enable the user to have total control over the install by giving opportunity to build the system almost from scratch. You must have knowledge of Debian to install and setup Core & Net versions.

Synaptic application installer is available by default on the full version. It can be installed via package-installer available by default on Base version and from the Debian repositories in other versions.

antiX is based on Debian but is totally free of systemd. It comes with a custom kernel, its own custom scripts and repository to enhance user experience. antiX can be used as a rolling release distro ie you should be able to keep your applications up to date by regularly upgrading. If you wish you can enable the Debian testing or unstable repositories and live on the bleeding-edge! For those that prefer stability, keep to the Debian Stable/stretch repositories. For a nice and thorough discussion and understanding on making/not-making your antix the rolling release see this: https://www.antixforum.com/forums/topic/new-to-debian-and-antix-rolling-release-help/

Visit the antiX FAQ page for any further details on the antiX operating system and its working: https://download.tuxfamily.org/antix/docs-antiX-19/FAQ/index.html

Do not forget to check the “Remaster” and “Snapshot” sections on the FAQ page. You will need them very much after installation.

System requirements

The antiX FAQ page gives the following info on system requirements.

antiX-core and antiX-net will run with 128MB RAM plus swap, but don’t expect miracles!

192MB RAM is the recommended minimum for antiX. 256MB RAM and above is preferred especially for antiX-full.

antiX-full needs a 3.8GB minimum hard disk size. antiX-base needs 2.6GB and antiX-core needs 1.0GB. antiX-net needs 0.7GB.

Most users will be happy to use antiX-full as it offers a full desktop experience on legacy and modern computers.

If you have a very old desktop/laptop with less than 256MB RAM (PII, PIII), or you want a desktop with "the basics", it is probably best to use antiX-base.

Live USB/CD
antiX can also be used as a fast-booting rescue CD, or run “live” on a USB stick, with or without persistent file storage. See below under the heading ‘Persistence’ for info on ‘persistent file storage’. For details on Live system first boot screen see section “THE FIRST BOOT SCREEN OF THE LIVE SYSTEM”.

DOWNLOAD

Download the ‘antiX ISO image’ from the website: https://antixlinux.com.

While you download your required antiX version also make sure to download the corresponding md5, sha256 and sig files to check the integrity of the downloaded ISO image. Place all these files including the ISO image in the same folder. It helps to verify the integrity of the downloaded ISO image.

After download verify the integrity of the downloaded ISO image as bellow:

VERIFICATION OF THE INTEGRITY OF THE ISO FILE

Verifying, any one of the md5sum or sha256sum will be enough.

The below documented procedure can work on a Linux system. However if you are on a Windows system now, I have given a link below where the procedure to verify the integrity of an ISO file on windows is given.

https://forums.linuxmint.com/viewtopic.php?f=42&t=291093

Verifying the integrity of an ISO file on any Linux system:
Find the path to your downloaded folder. If you go to the downloaded folder with the help of SpaceFM file manager (or any File manager, depending upon the current Operating System, your computer is installed with.), the path to your downloaded folder is given on the toolbar when you open the downloaded folder. If suppose your ISO file is downloaded to the ‘Downloads’ folder, the path would be ‘/home/your-username/Downloads’. If you have saved your ISO file somewhere else, it would be different.

Let us say, the names of the files that were downloaded are as below; (Yours could be different.)

antiX-19.2.1_x64-base.iso.
antiX-19.2.1_x64-base.iso.md5
antiX-19.2.1_x64-base.iso.sha256

Don’t forget that the first alphabet ‘a’ in ‘antiX’ is small letter and the last letter ‘X’ is in capitals.

Open a root terminal (Menu > Applications > System > Root Terminal.) and go to the folder where you downloaded the ISO by typing ‘cd’ followed by the path to your folder in the terminal, as shown below;

cd /path to your downloaded folder/antiX-19-2-1-x64-base

(Here I have given the example file name. Yours could be different. So change to the name of the file that you have downloaded.)

Now you are inside the downloaded folder.

Verifying md5sum

Verify the md5sum of the iso file, by typing the command in the Terminal as shown below;

md5sum antiX-19.2.1_x64-base.iso

Do not forget to change to the name of the file that you have downloaded.

You will get a number as output, as shown below (yours may be different); (Do not close the terminal yet.)

53ec93c66f0ba7231f5a2aaf2fcb312b antiX-19.2.1_x64-base.iso

Verify this number with the number given inside the antiX-19.2.1_x64-base.iso.md5 file. Both should be the same. Otherwise your downloaded image may have been compromised or got corrupt. So you have to download again.

Verifying sha256sum

Next, verify the sha256sum of the iso file, as shown below;

sha256sum antiX-19.2.1_x64-base.iso

Do not forget to change to the name of the file that you have downloaded.

You will get a number as output, as shown below (yours may be different); (Do not close the terminal yet).

1bdcd8c460bb7b0dd498588c6f459906e06eea24e2048f63815a14c6f54cb959 antiX-19.2.1_x64-base.iso

Verify this number with the number given inside the antiX-19.2.1_x64-base.iso.sha256 file. Both should be the same. Otherwise your downloaded image may have been compromised or got corrupt. So you have to download again, preferably from a different mirror.

Minimize the Terminal.

Now verify the signature as follows.

Verification of signature

To check the signature type the command to import the key in the terminal;

gpg --keyserver hkp://keys.gnupg.net --recv-keys 4A0C4F9C

And then in the terminal of the ISO folder, the one that you have minimized, type this command;

gpg --verify antiX-19.2.1_x64-base.iso.sig antiX-19.2.1_x64-base.iso

Again do not forget to change to the name of the file that you have downloaded.

The result would be similar to this;

gpg: Signature made Sun 29 Mar 2020 08:52:05 PM IST
gpg:                using RSA key 30AA418A0C723D937B50A986A80582E000067FDD
gpg: Good signature from "anticapitalista <antiX@operamail.com>" (unknown)
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 30AA 418A 0C72 3D93 7B50  A986 A805 82E0 0006 7FDD

If the above fails, do this;

To check the signature type the command first to import the key in the terminal;

gpg --keyserver hkp://keys.gnupg.net --recv-keys B9B6375C 0679EE98 892C32F1

And then in the terminal of the ISO folder, the one that you have minimized, type this command;

gpg --verify antiX-19.2.1_x64-base.iso.sig antiX-19.2.1_x64-base.iso

Again do not forget to change to the name of the file that you have downloaded.

The result would be similar to this;

(ak@ak-RV509 ~)$ gpg --keyserver hkp://keys.gnupg.net --recv-keys B9B6375C 0679EE98 892C32F1
gpg: key 13C74A22892C32F1: public key "Steven Pusser <stevep@mxlinux.org>" imported
gpg: key 70938C780679EE98: public key "Adrian <adrian@mxlinux.org>" imported
gpg: key 9B68A1E8B9B6375C: public key "Dolphin Oracle (mxlinux) <dolphinoracle@gmail.com>" imported
gpg: Total number processed: 3
gpg:               imported: 3
(ak@ak-RV509 ~)$  

Close this newly opened terminal, now.

Then type the following command in the terminal you have minimized, to check the signature;

gpg --verify antiX-19.2.1_x64-base.iso.sig

The result would be similar to this;

(ak@ak-RV509 antiX-19-2-1-x64-base)$ gpg --verify antiX-19.2.1_x64-base.iso.sig
gpg: assuming signed data in 'antiX-19.2.1_x64-base.iso'
gpg: Signature made Sunday 29 March 2020 08:52:05 PM IST
gpg:                using RSA key 30AA418A0C723D937B50A986A80582E000067FDD
gpg: Good signature from "anticapitalista <antiX@operamail.com>" (unknown)
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 30AA 418A 0C72 3D93 7B50  A986 A805 82E0 0006 7FDD
(ak@ak-RV509 antiX-19-2-1-x64-base)$ 

The warning in the last few lines is related to the trust that you put in the antiX signing key. The ISO image is still correct, and valid according to the antiX signing key that you downloaded.

CREATING THE BOOTABLE USB

You will need a minimum of 2GB SD card or USB drive for installation purposes. If you are aspiring to have a persistence USB live then you would need more.

You can even create it on a DVD. The same procedure for both.

Now create the bootable USB with the ISO image of antiX-19.2.1-x64-Base ISO image as follows.

For this you need a software called “USBMaker-git”. It is available on most Linux distributions, in the package installer. Install it if it is not already installed. I have verified this. This procedure can be done on many Live USB making software which are available on many Linux distros. Just try and verify which works for you. Or else you can create the bootable usb on an antiX OS, if one is accessible to you. There is a bootable usb maker which has been created by the antiX team, and it is installed by default in anitiX OS. Start it from Menu > Applications > antiX > Live USB maker. If you are on Windows OS, it suggested and recommended by experts that, Rufus USB making software is suitable.

After launching the USB maker, follow the simple instructions as follows. The process is similar on most of the USB makers. I am giving here the procedure on USBMaker-git.

Device
At the top, the device is the USB drive you have chosen to create the bootable device, namely the card reader and card inside it. You will need a minimum of 2GB sd card for this.

Partition scheme
Leave the partition scheme as MBR if the computer you are going to install is old with BIOS setup. If the computer is new with UEFI setup then you choose GPT scheme. Next choose the file system as FAT32.

Cluster size – default.

Volume label
Give a volume label of your liking, such that you can recognize what is inside the SD card.

ISO Image
Next click on the 3 dots button. Browse to the location of the ISO you have downloaded. That’s it. Click start. Your bootable USB will be created.

BIOS SETUP

Next you have to set your computer to boot from your installation USB. To do this you have to enter into BIOS setup section of the computer.

Most computers don’t need this setting up of BIOS to install an OS from USB. They are already setup to boot from USB as the first priority. So first try and see if your computer would boot into your USB. If it doesn’t then set up the BIOS to boot from USB as the first priority as mentioned below.

To setup your BIOS to boot from USB, restart your computer, and immediately after powering on the computer, start pressing, F2 or F4 or F8 or it could be other keys too. Each computer has a different key.

Once you enter BIOS, navigate to Boot section using the arrow keys. Read the instructions on the right thoroughly. There, set the boot priority to boot from USB as the topmost or the first option, then CD/DVD drive and then Hard disk. That’s it. Save and exit. You will be automatically booted into your Live USB installation, now. You will get a boot menu. Select the antiX OS and hit enter.

THE FIRST BOOT SCREEN OF THE LIVE SYSTEM

When the Live system first boot screen opens, you will find several F options to make it easy to boot on any hardware. No need to get startled by seeing so many options. Things are very easy if you follow just one tip and that is, if you don’t understand anything just leave it as it is, except doing some basic things suggested below. Even if you do not set anything here, you will get the opportunity when you boot into the Live system and even after installing. So no need to worry about anything. You can just stick to basic things like language and timezone. If you need more details, press F1. If you think further explanation is necessary, go to the link given below that explains everything on this screen in detail;

https://download.tuxfamily.org/antix/docs-antiX-19/Boot_Menu/antiX-gfxboot.html

Set your language via the F2 key.

To set the timezone use F3.

Use F6 to set the desktop. If you are confused, just leave it as it is. You will get the default ROX-IceWM combo. You can change it later as described in the below sections. Read the section ‘A word on Desktops’. If you have less than 128MB RAM, and want to test antiX live, choose one of the min- options at F6.

You can update, upgrade and install applications during the live session, they will carry over to the actual installation on the Hard disk. You can set the internet in the Live instance. It will be carried over to the actual installation. See the “Starting Internet” section below on how to set the internet. See the “Update & upgrade” sub-section below on how to update & upgrade.

If you want to create a persistence instance see the below section. If not after setting up things, to enter next, into the live system, select to boot into the antiX version you have downloaded and created the Live USB/CD and hit enter. (It is the first choice and is selected already by default.)

Persistence

Persistence is a hybrid between a LiveCD/USB and a full install. One of the beauties of a LiveCD is that it allows you to boot Linux without touching any hard drives so you can have a “test-drive” without fear of altering your current system. Another feature of a LiveCD is that once it is burned, it is close to impossible for it to get infected with a virus or a Trojan horse. Every time you boot it, you start off with a system that is clean and pristine. Persistence gives you a way of remembering things between boots. In order to do so, it needs access to a read-write device, typically either a hard drive or a USB stick.

For complete details on persistence visit the following page on antiX FAQ site. It has dealt with the process thoroughly.

https://download.tuxfamily.org/antix/docs-antiX-17/FAQ/persistence.html

PARTITIONING THE HARD DISK

This is the most serious part. If you are going to use the entire Hard disk and it is empty, then no problem. If you have some partitions on which there is some data, you need to be careful. If you make the smallest mistake your data on the Hard disk can get corrupted or get washed clean. So make a backup of your HD. Go through this process with great caution. Take the steps only when you are sure enough. I recommend that you should search the web and watch some video tutorials or read some websites on ‘how to use Gparted to make partitions’, before proceeding.

Though it is possible to create partitions during installations, I prefer to create partitions before installation leisurely, instead of doing it in the midst of installation process. Use Gparted to do it. If you are comfortable doing it during installation, no worries. It is a guided process. You can do as you prefer.

The Linux OS files are stored on a partition called as the root (/) partition, which holds all the system files. It must be formatted preferably as ext4 and mounted on /.

The Linux OS stores the user files like, Documents, Downloads, Videos, Music etc on a directory called /home directory (the forward slash ‘/’ is for root and the ‘home’ folder which houses the, Documents, Downloads, Videos, Music etc is placed inside the root partition). All the user settings & configurations are also placed in this /home folder as hidden folders.

It must be formatted preferably as ext4 and mounted on /home.

Some users prefer to keep this /home folder on a separate partition. Or you can choose to have no separate partition for home and choose to keep it as a directory in the root. You get an option to do this during the installation process. You can do as you prefer. If you choose to keep it as a directory in the root, you should not create the /home partition now. Actually the Linux OS Does NOT need a separate /home partition. /home is only needed in case you don’t want the user files to be stored in the /root partition or if you want a user accessible from different installed (Multiple boot) systems. The reason some people prefer to have a separate partition is, in case they wreck their system and have to go for a re-installation, they will not loose what is on their separate home partition. So the choice is yours. During installation, you can specify the /home to be inside root or as a separate partition.

The Linux OS optionally needs a partition called Swap for memory when your RAM gets all filled. It must be formatted as swap. If you are tight on RAM, you will benefit from having a swap partition. Or else it is not necessary.

Give about 10 to 15GB space for ‘root’ depending upon the type and size of applications you are going to use. Then, if you are creating a Swap partition, give it 1.5 times the size of your RAM (If your RAM is 3GB, your Swap should be 3×1.5=4.5GB). And keep the rest for /home.

If you choose to do the partitions during installation, almost the same procedure is to be carried out. Dolphin Oracle has made a video on it to get you through. I have given the link above to Dolphin Oracles videos.

INSTALLATION OF THE OPERATING SYSTEM

Most of the installation process is automated. However, before going for installation you must setup the internet connection.

Starting Internet

Setting up the WiFi internet connection: Use the Connection-manager icon, the two arrows, at the right bottom to get it going. Right click the two arrows, and left click WiFi to turn it on. Next left click the Connection-manager icon and hold it down. It should pop up a list of available WiFi networks. Give it a few seconds to fill the list. Move to the one you want and then release the left button of your mouse. It should pop up the password prompt. Type it in and click apply. You should see some yellow and red vertical bars in the WiFi network monitor to the right, and the little x next to the arrows on the Connection-manager icon will disappear. If you face difficulties, you can watch this video here – https://www.antiXforum.com/forums/topic/wifi-with-connman-antiX-19-2/.

If you have an Ethernet connection, just plug in the Ethernet cable from your modem, enter the username password given to you by your internet service provider.

If you cannot connect to either the WiFi or the Ethernet, just tether your phone with a USB data cable and choose the tethering options in your phone. Your data must be ON. It will be easily connected. You must be aware that, the first update & upgrade will consume about 400 MB of data plus any applications that you would manually install.

Update and upgrade

Now update and upgrade with following commands, in the terminal. You can also use antiX Updater (Menu > Applications > antiX > antiX Updater) which does both steps in a single GUI program.

sudo apt-get update

Hit enter and type your password when asked and hit enter. The default password in the antiX Live USB is ‘demo’. [For root access, password is ‘root’. Please do not login as root. It is totally unnecessary.] Your password will not be displayed on the screen. Just type it correctly and hit enter blindly. After the update is complete, type the following in the terminal and hit enter;

sudo apt-get upgrade

Choose the partitions

On the desktop there is a shortcut to start the installation process. Single click on it. Remember, double click will bring error notification. You are on ROX-IceWM, so single click is what you need to launch applications. However, if you need the double click option, you can do the following.

Menu > Applications > System > Rox Filer > Right click on any empty space inside the file manager > Options > Filer windows > Disable “Right-click navigation”.

Next choosing the partitions, if you have already created the partitions. If you haven’t the guided process will take you through.

During the installation, choosing the correct partitions is a serious matter. Those partitions are formatted before installation by the installer. Even if you choose not to format the /home partition, you must format the /root partition. So you have to choose the right partitions. If you choose something else by mistake your data on that partition will be washed off.

Setting Language & timezone & Username

While the installation process is going on, click on the next buttons to set up your time, date, timezone, keyboard, username, password etc. No need to hurry, the installation process will wait till you have finished doing it. That’s it. The rest will be taken care of by the USB installer.

After installation, shut down the computer, remove the USB and start the computer. You will be booted into the new antiX OS.

SETTING UP THE NEW antiX OS

Once you boot into the new OS, the first step is to update and upgrade, if you have not done it in the Live USB stick before installation. Follow the same procedure as given above.

You are automatically connected to the internet using your earlier setup during installation.

Restart. It is always good to restart once after large system wide updates, upgrades or installations. You may not do this for small individual package installations.

Package Installer

Then open the package installer (The shopping bag icon) from the left bottom of the desktop. Select the applications you would like to install. Don’t forget to select “Synaptic” from Package-Management drop-down list. You will need this to install packages from several repositories.

After installation, restart.

Synaptic package Manager

Now open the ‘Synaptic package Manager’ from the Menu > Applications > System

In the package manager go to;

Settings > Preferences > General > Select/enable ‘Consider recommended packages as dependencies’ > Apply & OK.

Next, search and select from the following packages, which you may find necessary for your daily work. The below list shows the most common applications used by the home user. If you need anything else, search and select, ‘mark for installation’. Though by default, antiX-Base and antiX-Full have almost all the necessary packages, I am just giving a hint to get your system ready to do all the tasks a home user would do. Omit if you have already installed from the Package Installer. If you are installing antiX Full, you will find some of the packages mentioned already installed.

Audacity – (To edit audio files.)
Catfish – (This is a good file searching software. There is a default SpaceFM search, if it is OK for you.)
Chromium – (Browser. You have the Firefox-esr by default.)
Gdebi – (To install debian packages.)
GIMP – (For editing images)
Gnome Disks Utility – (You may need it to create mount options for your other external partitions)
Ibus – (This is necessary to do typing in regional languages.) Ensure all the following dependencies are installed. You must configure Ibus by starting Ibus from Preferences > Yes > OK > The IBUS preferences box will open. If it doesn’t you should start by right clicking on the icon in your right tray > Preferences > Input method > Add > Select your language. > Add. You will then have to copy and place your language ‘Fonts’ folder by downloading from the web, inside the /usr/share/fonts/truetype/. And then configure LibreOfficeWriter by going to > Tools → Options → Language settings → Languages Check Enabled for Complex Text Layout(CTL) and Choose your language in Default languages for Documents (CTL).

You may need to install the following ibus dependencies depending upon your language. Verify it from the web.
ibus-m17n
ibus-table-extraphrase
ibus-gtk
ibus-gtk3
ibus-qt4 (Ignore this if it is not available on the repositories.)
ibus-table
ibus-clutter

Kolourpaint – (Like MS paint)
Libreoffice – (MS Office like package)
Media Info gui- (To extract technical information of video files.)
VLC – (Video/Audio player)
Vnstat – (Command line Interface to extract Internet traffic information)
gnome-Screenshot – (To take screenshots. There is a default screenshot app, if it is OK with you.)
Virtualbox – (For creating Virtual machines.)
Zim – (This is a note making software.)

Avidemux – (To edit video files. Install if you do this kind of work.)

There is no Debian package for Avidemux application. There is a thing called AppImage. AppImage is a format for distributing portable software on Linux without needing superuser permissions to install the application. It contains an app and all the files the app needs to run.

You can download the latest Avidemux package here: http://avidemux.sourceforge.net/download.html.

If you want Tor Browser, you can see this (https://www.antiXforum.com/forums/topic/tor-browser-installation-signature-verification-failed/) link for a manual to do it.

These packages are enough for day to day functions. Select ones that you need and click apply. After finishing, restart.

Now that all packages have been installed, you can customize the Desktop and other settings.

CHANGING THE DEFAULT SETTINGS

An important information, before you go for changing the default settings:

It is preferred and recommended that you use the OS as it comes. However, every person has different requirements. The default applications shown in the panel to the left & right bottoms, could be subjectively appropriate for you or not. Like if you often switch between workspaces, having the workspaces on the toolbar really helps. If you do not, it simply holds space that can be given to other applications that you use every now and then. Similarly, other applications displayed on the toolbar. If you feel, it helps to keep some of the most often used applications there and remove the ones you use less often, you can do so by the following method. Here I will take certain examples and change accordingly. The same procedure applies to any application. You can follow that to your liking. However there is a caveat here;

Any change in the default settings, will be overwritten and return to default settings, if in future you install/upgrade/remove any program using the Synaptic, because of the special hook in apt. So whenever you do so, you will have to repeat these changes.

Keep that in mind.

If you do not want any changes to the default system, you skip these steps and directly jump to, USER SETTINGS, below.

Desktop right-bottom tray

If you don’t like the ‘CPU status’ and ‘Memory status’ (There is already Conky on the desktop doing almost the same thing. If you want to disable Conky and keep these, see below.) in the right-bottom tray and the ‘Workspaces switching buttons’ in Left-bottom, you can remove them by doing as below. Workspaces can be accessed with Control+Alt+right/left arrow mark keys alternatively.

Open the ‘Control center’ from the Menu. In the Control-center > Desktop > Edit IceWM settings > Preferences

The text editor will open.

Click on ‘preferences’. (Whatever you edit here, will take effect only after a fresh ‘logon’.)

Search for ‘# Show RAM usage in CPU status tool tip
# CPUStatusShowRamUsage=1 # 0/1’ in the search box given above. Change 1 to 0, like this ‘TaskBarShowCPUStatus=0’.

Search for ‘# Show CPU status on task bar
TaskBarShowCPUStatus=1 # 0/1’ in the search box given above. Change 1 to 0, like this ‘TaskBarShowCPUStatus=0’.

Search for ‘# Show memory usage status on task bar (Linux only)
TaskBarShowMEMStatus=1 # 0/1’ in the search box given above. Change 1 to 0, like this ‘TaskBarShowMEMStatus=0’.

Search for ‘# Show workspace switching buttons on task bar
TaskBarShowWorkspaces=1 # 0/1’ in the search box given above. Change 1 to 0, like this ‘TaskBarShowWorkspaces=0’.

Don’t close the text editor, yet.

Desktop left-bottom

Next if you don’t like the default applications given in the left-bottom. Instead, if you want Terminal, Notes (a note keeping software), Leafpad (Notepad equivalent), Calculator, Screenshot, Firefox, Chromium, ‘SpaceFM-File Manager’ and Unplug Removable Device. To change the current set and bring yours there in place of them, do as below.

In the same the text editor, click on ‘toolbar’. There is a list of apps there. The scheme of the settings is;

prog “app-name-to-be-displayed” path-to-app-icon app-executable

Just add a ‘#’ before those applications which you don’t want in the left-bottom of your desktop. And add any new ones you want to be shown there. I have added some and hashed out some. You can take this as an example and change it according to your requirement. The final edited set looks as below.

### Commonly used applications
prog “Terminal” terminal.png roxterm
prog “Notes” zim.png zim
prog “Leafpad” leafpad.png leafpad
prog “Calculator” galculator.png galculator
prog “Firefox” firefox.png firefox
prog “Chromium” chromium.png chromium
prog “File Manager” spacefm.png spacefm
prog “Unplug Removable Device” /usr/share/icons/papirus-antiX/48×48/devices/drive-removable-media-usb.png unplugdrive.sh
#prog “Software Installer” /usr/share/icons/papirus-antiX/48×48/apps/packageinstaller.png su-to-root -X -c packageinstaller
#prog “File Manager” /usr/share/icons/papirus-antiX/48×48/apps/file-manager.png desktop-defaults-run -fm
#prog “File Manager as root” /usr/share/icons/papirus-antiX/48×48/places/folder-red.png su-to-root -X -c rox
#prog “Web Browser” /usr/share/icons/papirus-antiX/48×48/apps/web-browser.png desktop-defaults-run -b

The path to the app icons need not be shown. The system knows where those are placed. Sometimes the system may fail to locate icons. If that occurs you have to find the icon and show the path to that icon here.

Conky disabling

There is the ‘conky’ (system resource details displayer) placed on the right-top of the desktop. If you want you can keep it. If you want to toggle between on/off in a session but keep it getting launched at startup, you can do so by going to;

Mwnu > Desktop > Conky On/Off

However, if you want to permanently stop it from launching at start up, this is how you do it.

Open ‘control-center’. Session > User Desktop session.

A text editor will open. Click on ‘desktop-session.conf’. Search for LOAD_CONKY=”true”. Change it to false like this;

LOAD_CONKY=”false”.

Conky will not be displayed after a fresh logon.

Now close the editor and the control-center and logoff and logon. All your changes must take effect. If they don’t, you have done something wrong or you need to show the paths. Re-edit and check. You can even copy from the above list given by me here, under ‘### Commonly used applications’, and paste in the toolbar.

Menu updating – system

Now after installation of applications from the Synaptic or from outside the repositories, if any of the apps are not shown in the Menu, do the following. Any change in the default settings you do by this method, will be overwritten and return to default settings, if in future you install/upgrade/remove any program using the Synaptic, because of the special hook in apt. So whenever you do so, you will have to repeat these steps.

Updating the Menu using the Control-center;

Menu > Control-center > Maintenance > Menu editor

In the box that opens;

Applications > Show > A list is opened > Choose the App that you want displayed in the Menu > OK > Refresh > OK > Close control center

Menu updating – manual

If the above mentioned method fails, do the following.

However, before following the below mentioned procedure, it is recommended using the “Refresh Menu” (It’s on the Menu list) or the command “desktop-menu –write-out-global” if your applications was installed manually (after installing with gdebi, for example). If this doesn’t work for you do the following.

Open the ‘Rox filer’ file manager from the Menu > System, inside the /home/your-username/ folder, at the top, click on the ‘eye’ symbol to show hidden files. Open the ‘.icewm’ folder. Open ‘menu-applications’ by right clicking on it and clicking on ‘Edit as root’.

There is the list of applications shown in the Menu in different categories, in alphabetical order. Here too the scheme is as below;

prog “app-name-to-be-displayed” path-to-app-icon app-executable

Add this line under appropriate section.

prog “Application-name” application.png application

Save and close. Re-logon. Now your application will be in the Menu, under the section you added it.

USER SETTINGS

Desktop Background/Wallpaper

If you want to change the wallpaper/background on the desktop and add your own personal background, open ‘Rox filer as root’ from the Menu > Application > System. Go to /usr/share/wallpaper. It contains the default backgrounds. You can choose one among them. Or paste there any wallpaper you want and close it. Then to choose that as your desktop background do the following.

Menu > Control-center > Desktop > Choose wallpaper > In the box that opens > Select picture > Select your picture and open > Apply

Screen blanking

There is the screen blanking setting in antiX. The screen will go blank after your set number of minutes. Do as below to set it.

Menu > Control-center > Session > Set screen blanking > Slide to, say 10 minutes, and click Apply > OK > close the Control-center.

Ad blocking

If you want to block ads do the following.

Menu > Control-center > Network > Adblock > In the box that opens, click OK > In the box that opens, select some/all the options and click OK.

Sound problems

If there is no sound do the following.

Menu > Control-center > Hardware > Adjust mixer > In the box that opens, set as below;

An “MM” means muted, and “OO” means unmuted. Press ‘m’ key on the keyboard to mute/unmute. Note that a bar can be 100% full but still be muted, so do check for this.

See that the AlsaMixer box that has opened has the following settings.

Master – 00 & 100
Headphone – As much as you want.
Speaker – As much as you want.
Mic – MM & 00
Mic booster – 00
Mic booster – 00
S/PDIF – MM
Capture – 40<>40
Auto-Mut – Enabled
Internal – MM & O<>O
Internal – O<>O
Internal – O<>O
Loopback – Disabled
Pre-amp – 11<>11
Pre-amp – 11<>11

Exit from alsamixer with the Esc key.

User Accounts

To create a daily-use user-account do the following;

Menu > Control-center > Maintenance > User manager > In the box that opens go to;

Administration > Add any username and password.

Then go to Copy/sync tab. A file navigator box opens. Close it. In the section under Copy between desktops, your Administrator name and the newly created name is displayed. If you want to just copy whatever changes you have just done on the new system to the new user account select copy. If you want to keep synchronizing any changes you will make in the future too, select sync. Under ‘What to copy/sync’, select ‘Entire home’ to take every change made to the new user account. Apply and close. In the same window you can select/deselect groups, in the Groups management tab. Groups give or take privileges to users.

Restart. Your system is ready. This will get almost all the home users going. Best wishes with your new antiX system.

A WORD ON DESKTOPS

To keep the OS light, the antiX creaters have adopted the strategy of giving the users a ‘File Manager-Window Manager’ combination and a range of varieties also to suit the different liking of the users. You get several different such File managers and Window managers like; ROX filer, SpaceFM, file managers and IceWM, JWM, Fluxbox Window managers and their different combinations with just a click of the mouse. Menu > Desktop > Other desktops will take you to more than 20 options to choose from, to fit your inclinations. The SpaceFM file manager is available by default in Menu > Applications > System.

A WORD ON FRUGAL INSTALL

Frugal install is an interesting option. It is the same like the Live USB but it is on your Hard Disk. It is secure than the regular install, because any changes made are not retained. If you restart the system, everything fresh as before. It is an interesting instance, worth trying.

You can find details of Frugal install in the antiX FAQ page and in the following threads.

https://www.antixforum.com/forums/topic/the-philosophy-behind-my-attachment-with-antix-or-floss/

And in the posts of Olsztyn in the thread below;

https://www.antixforum.com/forums/topic/how-to-create-isolated-underprevileged-but-standard-user-accounts/

Changing to EXTLINUX/SYSLINUX as the bootloader for the frugal install is a very good setup. You can find the details of it in the below thread;

https://www.antixforum.com/forums/topic/booting-antix-frugal-only-from-hdd-without-any-full-installed-os-with-extlinux/

Take a look at these threads. They give a glimpse to the very interesting instance of antiX setup.

Thanks & Regards

Hello, new user of antix here.
After many unsuccessful attempts at reviving computer, I used antix and it was the best alternative OS option for it. As I was setting things up, I discovered that you can change your desktop. I’ve chosen herbstluftwm and it completely changed my desktop to some .txt file, that had commands on it, which allowed me to reboot computer, log off or another similar commands, however I can’t use this environment, and I want to swap to default similar one. Can you please help me with it?

[Member marcelocripe]

Seaken64, how are you?

A colleague challenged me to do an installation test of Raspbery Pi Desktop (2020-02-12-rpd-x86-buster.iso), I challenged him to do an installation test with antiX-19.2_386-full .iso or antiX-19.2_x64-full.iso. I also proposed for him to compare help on the forum https://www.antixforum.com/ and on https://www.raspberrypi.org/forums/

I made two posts on the other forum, the first was deleted and modified by a moderator, there were no answers, I asked for basic information about minimum system requirements and other issues that I have already covered here in other posts.

As he does not participate in this forum, we still do not have his impression of antiX.

Here are the data I managed to capture from the tests I did:

Tests performed on the computer Motherboard: Asus P5V800-MX Rev. 1.04G, Intel (R) Celeron (R) D 2.53 GHz Frequency 2533MHz FSB Speed ​​533Mhz Cache L1 16kB Cache L2 256KB Cache L3 0KB, 1GB Ram DDR 400 Mhz, 40GB HD.

pi @ raspberrypi: ~ $ free {Enter}
Memory: total: 2031844 KB, used: 157692 KB, free: 1174244 KB, shared: 138292, buff / cache: 699908 avaliable: 1582408
Swap: total: 0, used: 0, free: 0

Memory: total: 1010484 KB, used: 153740 KB, free: 135232 KB, shared: 120144, buff / cache: 721512 avaliable: 581556
Swap: total: 0, used: 0, free: 0

pi @ raspberrypi: ~ $ free {Enter}

Memory: total: 1010468 KB, used: 146788 KB, free: 672468 KB, shared: 5328, buff / cache: 191212 avaliable: 719676
Swap: total: 2081784 KB, used: 0, free: 2081784 KB

pi @ raspberrypi: ~ $ htop {Enter}
CPU 1.3% and 3.3%
Mem (Memory) 151MB / 987MB
Swp: 0K / 0K

pi @ raspberrypi: ~ $ df -h {Enter}
System. File Size Used Used Use% Mounted on
/ dev / sdb1 / 36G 5.4G 29G 16% /
Information from the Task Manager, showed 2% CPU usage and memory: 141 MB of 986 MB used.

The Raspbery Pi Desktop takes a long time to start up compared to antiX, as does the installation. The number of programs already installed is much smaller for an ISO of (2020-02-12-rpd-x86-buster.iso) of 2.92 GB, the two ISOs of antiX 19.2 (32 and 64 bits) have about 2.32 GB.

I think he will come to the antiX community after doing some testing.

marcelocripe

Original text in Brazilian Portuguese, translated into English by Google translator.

————–

Seaken64, tudo bem com você?

Um colega me desafiou para eu fazer um teste de instalação do Raspbery Pi Desktop (2020-02-12-rpd-x86-buster.iso), eu o desafiei para que ele fizesse um teste de instalação com o antiX-19.2_386-full.iso ou antiX-19.2_x64-full.iso. Eu propus ainda para ele comparasse a ajuda no fórum https://www.antixforum.com/ e no https://www.raspberrypi.org/forums/

Eu fiz duas postagens no outro fórum, a primeira foi apagada e modificada por um moderador, não houveram respostas, eu pedi informações básicas sobre requisitos mínimos de sistema e sobre outros assuntos que eu já abordei aqui em outras postagens.

Como ele não participa deste fórum, ainda, não termos a impressão dele sobre o antiX.

Seguem os dados que eu consegui capturar dos testes que eu fiz:

Testes realizados no computador Placa mãe: Asus P5V800-MX Rev. 1.04G, Intel (R) Celeron (R) D 2,53 GHz Frequência 2533MHz FSB Speed 533Mhz Cache L1 16kB Cache L2 256KB Cache L3 0KB, 1GB Ram DDR 400 Mhz, 40GB de HD.

pi@raspberrypi:~ $ free {Enter}
Memória: total: 2031844 KB, used: 157692 KB, free: 1174244 KB, shared: 138292, buff/cache: 699908 avaliable: 1582408
Swap: total: 0, used: 0, free: 0

Memória: total: 1010484 KB, used: 153740 KB, free: 135232 KB, shared: 120144, buff/cache: 721512 avaliable: 581556
Swap: total: 0, used: 0, free: 0

pi@raspberrypi:~ $ free {Enter}

Memória: total: 1010468 KB, used: 146788 KB, free: 672468 KB, shared: 5328, buff/cache: 191212 avaliable: 719676
Swap: total: 2081784 KB, used: 0, free: 2081784 KB

pi@raspberrypi:~ $ htop {Enter}
CPU 1,3% e 3,3%
Mem (Memória) 151MB/987MB
Swp (Swap): 0K/0K

pi@raspberrypi:~ $ df -h {Enter}
Sist. Arq. Tam. Usado Dispo. Uso % Montado em
/dev/sdb1/ 36G 5,4G 29G 16% /
Informações do Gerenciador de Tarefas (Task Manager), exibiu Uso de CPU 2% e memória: usados 141 MB de 986 MB.

A inicialização é muito demorada do Raspbery Pi Desktop se comparada ao antiX, bem como a instalação. A quantidade de programas já instalados é bem menor para um a ISO de (2020-02-12-rpd-x86-buster.iso) de 2,92 GB, as duas ISOs do antiX 19.2 (32 e 64 bits) possuem cerca de 2,32 GB.

Eu acho que ele virá para a comunidade antiX após fazer alguns testes.

marcelocripe

Texto original em idioma português do Brasil, traduzido para o inglês por Google tradutor.

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

[Member Red_Fir]

Mint is on its own 120G ssd, Linux Lite and antiX share a 120G ssd ./home and swap are on a 500G hd

[Member Red_Fir]

yes home and swap are shared, mint 19.3, and Linux Lite, and antiX

[Member Retromaniak]

no problem:

System:
Host: retromaniak Kernel: 4.9.212-antix.1-486-smp i686 bits: 32
compiler: gcc v: 8.3.0 Desktop: IceWM 1.6.5
Distro: antiX-19.2.1_386-base Hannie Schaft 29 March 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: Hewlett-Packard product: HP 2133 v: F.05
serial: <filter>
Mobo: Hewlett-Packard model: 3030 v: KBC Version 07.17
serial: <filter> BIOS: Hewlett-Packard v: 68VGU Ver. F.05
date: 08/20/2008
Battery:
ID-1: BAT1 charge: 2.1 Wh condition: 2.2/2.5 Wh (86%)
model: Hewlett-Packard Primary status: Discharging
CPU:
Topology: Single Core model: VIA C7-M bits: 32 type: UP
arch: C7 L2 cache: 128 KiB
flags: nx pae sse sse2 sse3 bogomips: 1596
Speed: 800 MHz min/max: 800/1600 MHz Core speed (MHz): 1: 800
Graphics:
Device-1: VIA CN896/VN896/P4M900 [Chrome 9 HC]
vendor: Hewlett-Packard driver: N/A bus ID: 01:00.0
Display: x11 server: X.Org 1.20.4 driver: vesa
resolution: 640×480~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits)
v: 3.3 Mesa 18.3.6 direct render: Yes
Audio:
Device-1: VIA VT8237A/VT8251 HDA vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus ID: 80:01.0
Sound Server: ALSA v: k4.9.212-antix.1-486-smp
Network:
Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY
vendor: Hewlett-Packard driver: wl v: kernel port: bc00
bus ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Device-2: Broadcom Limited NetXtreme BCM5788 Gigabit Ethernet
driver: tg3 v: 3.137 port: bc00 bus ID: 07:03.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 903.57 GiB used: 3.66 GiB (0.4%)
ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172
size: 903.57 GiB
Partition:
ID-1: / size: 97.93 GiB used: 3.66 GiB (3.7%) fs: ext4
dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap
dev: /dev/sda2
Sensors:
System Temperatures: cpu: 44.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 125 Uptime: 2m Memory: 873.0 MiB
used: 113.0 MiB (12.9%) Init: SysVinit runlevel: 5 Compilers:
gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36

[Member gregorylock]

I’m also very new to postimg.cc I think I can give you larger pictures.

https://i.postimg.cc/syhhYcX6/01-Nvidia-Install.jpg
https://i.postimg.cc/bq3DyVCJ/02-Nvidia-Install.jpg

https://i.postimg.cc/6B94Nxhg/01-Nvidia-Issues.jpg
https://i.postimg.cc/W2zDhmC7/02-Nvidia-Issues.jpg
https://i.postimg.cc/PTbvc511/03-Nvidia-Issues.jpg
https://i.postimg.cc/X46yQCBV/04-Nvidia-Issues.jpg

I forgot to show system specs, after installing the Nvidia Driver.

inxi -Fxz
System:
  Host: antix1 Kernel: 4.9.221-antix.1-amd64-smp x86_64 bits: 64 
  compiler: gcc v: 8.3.0 Desktop: IceWM 1.6.6 
  Distro: antiX-19.2_x64-full Hannie Schaft 27 March 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: Dell product: Vostro 400 v: N/A serial: <filter> 
  Mobo: Dell model: 0GN723 v: ��� serial: <filter> BIOS: Dell v: 1.0.15 
  date: 06/23/2008 
CPU:
  Topology: Dual Core model: Intel Core2 Duo E4600 bits: 64 type: MCP 
  arch: Core Merom rev: D L2 cache: 2048 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 9576 
  Speed: 1200 MHz min/max: 1200/2400 MHz Core speeds (MHz): 1: 1200 2: 1200 
Graphics:
  Device-1: NVIDIA GT218 [GeForce 210] vendor: eVga.com. driver: nvidia 
  v: 340.108 bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: nvidia 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: GeForce 210/PCIe/SSE2 v: 3.3.0 NVIDIA 340.108 
  direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Dell driver: snd_hda_intel 
  v: kernel bus ID: 00:1b.0 
  Device-2: NVIDIA High Definition Audio vendor: eVga.com. 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Sound Server: ALSA v: k4.9.221-antix.1-amd64-smp 
Network:
  Device-1: Intel 82562V-2 10/100 Network vendor: Dell driver: e1000e 
  v: 3.2.6-k port: ff00 bus ID: 00:19.0 
  IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter> 
  Device-2: D-Link System DGE-528T Gigabit Ethernet Adapter driver: r8169 
  v: 2.3LK-NAPI port: de00 bus ID: 02:01.0 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 465.76 GiB used: 4.65 GiB (1.0%) 
  ID-1: /dev/sda vendor: Seagate model: ST9500423AS size: 465.76 GiB 
Partition:
  ID-1: / size: 455.45 GiB used: 4.65 GiB (1.0%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 40.0 C mobo: N/A gpu: nvidia temp: 41 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 40% 
Info:
  Processes: 165 Uptime: 3m Memory: 3.86 GiB used: 270.8 MiB (6.8%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

For those who might be interested, I have just completed my ‘initial’ basic build of antiX19 with dwm (tiler) as my window manager (wm); I have also completed a fair amount of testing and tweaking.

The setup is significantly different from a standard antiX build. The following items have been removed entirely:

--IceWM
--fluxbox
--jwm
--hlwm
--slim
--roxterm
--rox-filer
--etc....

The following have been added/ augmented for use:

--dwm
--st-simple terminal
--slstatus
--rofi
--zenity
--thunar
--lightdm
--flatpak
--numerous console apps

I have also swapped out a bunch of apps and replaced them with others.

In order to sync my antiX setup with an arch setup I have, I used flatpak for thunderbird, skype, zoom, and firefox. (That way I don’t have to deal with old Debian versions of those apps).

I’ll create a more detailed write-up on the setup in the near term (when I get around to it in my Covid enforced ‘free-time’.)

• This topic was modified 2 years, 8 months ago by manyroads.
• This topic was modified 2 years, 8 months ago by manyroads.

Pax vobiscum,
Mark Rabideau - http://many-roads.com
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
dwm & i3wm ~Reg. Linux User #449130
20 Jan 2021 ~ "End of an Error"

[Moderator Brian Masinick]

Over time the resource consumption of the various tools and application, and even the size of the kernel increase.
A decade ago I could run antiX with IceWM and use around 60 MB of memory, even less than that at start up time.
Now if I can stay under 100 MB or even close, I’m happy. Larger systems use 300-400 MB before even running any applications.

So to me that means it is likely that the size of the system and the footprint it consumes is larger.
If it’s too taxing, try an older release and only update what you need to use and see if it helps.

ystem:    Host: lucrece Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.212-antix.1-486-smp 
           root=UUID=a6640781-22bf-469e-bee1-24e4492dd40f ro vga=791 quiet 
           Desktop: IceWM 1.6.6 wm: JWM 2.3.7 dm: SLiM 1.3.6 
           Distro: antiX-19.2.1_386-base Hannie Schaft 29 March 2020 
           base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ECS model: P4S5MG/GL+ v: 1.0 serial: <filter> 
           BIOS: American Megatrends v: 07.00T date: 04/02/01 
Memory:    RAM: total: 969.1 MiB used: 186.9 MiB (19.3%) 
           RAM Report: permissions: Unable to run dmidecode. Root privileges required. 
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. 
CPU:       Topology: Single Core model: Intel Pentium 4 bits: 32 type: MCP 
           arch: Netburst Northwood family: F (15) model-id: 2 stepping: 4 microcode: 1E 
           L2 cache: 512 KiB bogomips: 3984 
           Speed: 1992 MHz min/max: N/A Core speed (MHz): 1: 1992 
           Flags: acpi bts clflush cmov cx8 de dts fpu fxsr ht mca mce mmx msr mtrr pae pat pebs 
           pge pse pse36 sep ss sse sse2 tm tsc vme 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf status: Vulnerable 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown status: Vulnerable 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Silicon Integrated Systems [SiS] 65x/M650/740 PCI/AGP VGA Display Adapter 
           driver: N/A bus ID: 01:00.0 chip ID: 1039:6325 
           Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1280x1024~N/A 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 compat-v: 3.1 
           direct render: Yes 
Audio:     Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound 
           vendor: C-Media CMI9739 on ECS K7S series driver: snd_intel8x0 v: kernel 
           bus ID: 00:02.7 chip ID: 1039:7012 
           Sound Server: ALSA v: k4.9.212-antix.1-486-smp 
Network:   Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet driver: sis900 
           v: kernel port: d400 bus ID: 00:04.0 chip ID: 1039:0900 
           IF: eth0 state: down mac: <filter> 
           Device-2: 3Com 3c905B 100BaseTX [Cyclone] driver: 3c59x v: kernel port: d000 
           bus ID: 00:09.0 chip ID: 10b7:9055 
           IF: eth1 state: down mac: <filter> 
           Device-3: Belkin F6D4050 N150 Enhanced Wireless Network Adapter v1000 [Ralink RT3070] 
           type: USB driver: rt2800usb bus ID: 2-3:2 chip ID: 050d:935a serial: <filter> 
           IF: wlan0 state: down mac: <filter> 
           WAN IP: No WAN IP data found. Connected to the web? SSL issues? 
Drives:    Local Storage: total: 57.27 GiB used: 2.73 GiB (4.8%) 
           ID-1: /dev/sda vendor: Maxtor model: 6Y060L0 size: 57.27 GiB block size: 
           physical: 512 B logical: 512 B speed: <unknown> serial: <filter> rev: 1VW0 scheme: MBR 
           Floppy-1: /dev/fd0 
           Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H50N rev: 1.00 
           dev-links: cdrom,cdrw,dvd,dvdrw 
           Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram 
           state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / raw size: 55.24 GiB size: 54.12 GiB (97.98%) used: 2.73 GiB (5.0%) fs: ext4 
           dev: /dev/sda1 label: rootantiX19 uuid: a6640781-22bf-469e-bee1-24e4492dd40f 
           ID-2: swap-1 size: 2.00 GiB used: 4 KiB (0.0%) fs: swap swappiness: 10 (default 60) 
           cache pressure: 50 (default 100) dev: /dev/sda2 label: swapantiX 
           uuid: cfe19436-0a18-41df-9f37-d117675722cb 
Unmounted: Message: No unmounted partitions found. 
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s 
           chip ID: 1d6b:0002 
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
           chip ID: 1d6b:0002 
           Device-1: 2-3:2 
           info: Belkin F6D4050 N150 Enhanced Wireless Network Adapter v1000 [Ralink RT3070] 
           type: Network driver: rt2800usb interfaces: 1 rev: 2.0 speed: 480 Mb/s 
           chip ID: 050d:935a serial: <filter> 
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Device-2: 3-1:2 info: IBM Rapid Access IIIe Keyboard type: Keyboard,Mouse 
           driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s chip ID: 04b3:300a 
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Device-3: 4-1:2 info: Holtek Optical Mouse type: Mouse driver: hid-generic,usbhid 
           interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 04d9:0499 
           Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
           Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s 
           chip ID: 1d6b:0001 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http: //mirrors.rit.edu/mxlinux/mx-packages/antix/buster buster main nonfree nosystemd
           Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
           1: deb http: //deb.debian.org/debian buster-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http: //ftp.ca.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http: //ftp.ca.debian.org/debian/ buster main contrib non-free
           2: deb http: //security.debian.org/ buster/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/onion.list 
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes: CPU top: 5 
           1: cpu: 26.5% command: xorg pid: 2305 mem: 53.4 MiB (5.5%) 
           2: cpu: 4.5% command: perl pid: 15338 mem: 14.8 MiB (1.5%) 
           3: cpu: 3.5% command: yad pid: 15361 mem: 9.07 MiB (0.9%) 
           4: cpu: 0.7% command: apt-get pid: 5778 mem: 50.8 MiB (5.2%) 
           5: cpu: 0.6% command: [ksoftirqd/0] pid: 3 mem: 0.00 MiB (0.0%) 
           Memory top: 5 
           1: mem: 53.4 MiB (5.5%) command: xorg pid: 2305 cpu: 26.5% 
           2: mem: 50.8 MiB (5.2%) command: apt-get pid: 5778 cpu: 0.7% 
           3: mem: 33.1 MiB (3.4%) command: connman-ui-gtk pid: 4704 cpu: 0.1% 
           4: mem: 26.5 MiB (2.7%) command: x-terminal-emulator pid: 4978 cpu: 0.5% 
           5: mem: 15.6 MiB (1.6%) command: ceni started by: perl pid: 4538 cpu: 0.0% 
Info:      Processes: 140 Uptime: 52m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: 
           gcc: 8.3.0 alt: 8 Client: shell wrapper inxi: 3.0.36 

Edit: Pasted his full info text in the wrong post. My bad. I will leave it alone though. I meant to put it the post above yours Brian.

• This reply was modified 2 years, 8 months ago by rokytnji.
• This reply was modified 2 years, 8 months ago by rokytnji.

--
Brian Masinick

[Moderator Brian Masinick]

Anonymous wrote:

anilkagi, liveboot has been the focus of my interest. Your howto skips past, glosses over, the liveboot experience.

When reading a howto, the user has a goal. Chunking the howto into sections, even if just delineated by ======== lines or however, should help the user feel a sense of accomplishment as they “work their way through” performing the steps (and reading about the optional steps) within a given section, toward achieving the goal.

Excuse my pedantic stumbling (it’s just my nature), but I sensed a disconnect between the title “guide to install” and the content discussing housekeep-y tweaks like editing the desktop menu entries and suppressing the conky autostart. These details seem out of scope for a goal of “installing”. That’s why I mentioned my decision to defer making suggestions “regarding desktop setup/customization”. Similarly, the topic of BIOS setup would probably be best presented as “list of curated doc/tutorial links” within this installation howto.

Rufus, across years, has always worked successfully when I tested. (you asked)
A separate howto for using it, although short, (forum search will find it within my past posts) is beyond the scope of this installation howto.

In assisting with revisions, IMO our attention should focus on achieving correctness/accuracy, e.g. catching sticking points like “needs” (outdated? optional, but unnecessary) within the statement “The Linux OS needs a seperate partition or a directory called /home partition”.

With regard to being particular and accurate, to the best of my knowledge the only required partitions (within the distribution) are the root (/, rather than /root) and swap. Other file systems may be desirable, but directories such as /home and /data do not require their own separate filesystem. That is a matter of either personal preference or corporate standardization. If you are using UEFI and GPT for boot management and file system infrastructure, then a /boot filesystem containing at least a EFI directory is also mandatory, but it only needs to be CREATED if it does not already exist. If a previous installation or another system exists, the /boot infrastructure may already be present.

--
Brian Masinick