System Requirements for antiX and other Debians

Forum Forums General Tips and Tricks System Requirements for antiX and other Debians

  • This topic has 24 replies, 8 voices, and was last updated Sep 17-2:53 pm by Brian Masinick.
Viewing 15 posts - 1 through 15 (of 24 total)
  • Author
    Posts
  • #40100
    Member
    seaken64

      This a continuation of a discussion we started over here (we got off topic):

      https://www.antixforum.com/forums/topic/still-using-antix-16-in-2020/page/3/#post-40082

      @marcelocripe,

      Here is my recommendations for system requirements for antiX, MX, MX-Fluxbox, Q4OS and Debian. My tests were all done in 32-bit on old P-3 and P-4 equipment.

      Seaken64

      System Requirements for Linux on Old Computers

      Here I will make a comparison of the officially documented “system requirements”, when provided, and my system specifications as I have them on the actual hardware.

      The antiX system requirements say at least 256MB RAM for the FULL version with 5GB hard disk space. On my computers this seems to be a reasonable minimum. But with only 256MB RAM you can only run a simple browser like NetSurf or Dillo, maybe SeaMonkey or Palemoon-nonsse2 will work for simple pages. My installs are between 3.6GB and 4.9GB of hard disk space. That leaves no room for data. I suggest at least 512MB of RAM and a 6GB hard drive or an 8GB USB.

      The MX system requirements say at least 1GB RAM and 6GB hard drive space and recommends 2GB RAM and 20GB hard drive space. I can run MX 32-bit in 512MB RAM if I use the MX-Fluxbox desktop. The hard drive space is under 5GB on my P-III machine. When running the full XFCE system I agree that 1GB is the minimum and 2GB would be better. And MX uses over 8.5GB on my P4 machine. For standard MX I recommend 2GB of RAM and a 20GB hard drive or 16GB USB. For MX-Fluxbox I recommend 1GB of RAM and 20GB HD or 16GB USB.

      Q4OS system requirements say at least 128MB RAM and 3GB storage for the TDE desktop. Recommended is 1GB RAM and 5GB of storage. On my P-III it needs at least 256MB and runs slower than antiX in 512MB. The installation uses over 5GB of storage. On my P-4 it needs at least 512MB and uses over 8GB of storage. For Q4OS Trinity (the TDE version) I recommend at least 512MB of RAM and it runs better with 1GB or more. I recommend at least an 8GB hard drive but it is better with 15GB or more.

      Debian system requirements say a minimum of 256MB RAM and 10GB drive space. They recommend 1GB of RAM and 10GB hard drive. On my P-III Debian uses at least 256MB of RAM and up to 6.5 GB of storage when installed with the XFCE desktop. It runs okay in 512MB as long as I limit the browser to SeaMonkey. I recommend at least 512MB of RAM and 1GB would be better. I recommend at least 10GB of storage and 15GB would be better.

      I will use the Pentium-III 1.0Ghz with 512MB and the P-4 3.2Ghz w/ 3GB.

      P-III Coppermine 1.0 Ghz, 512M
      p3—–
      antiX-17.4 32-bit, Kernel=4.10.5-antix.1-486-smp i686, Debian=9 (Stretch)
      15GB HD Partition, 4.87G used, 1GB Swap Partition
      IceWM Window Manager, “rox-icewm” desktop, antiX Adblock activated
      Memory used reported in Conkey
      Initial Idle Memory – 78M
      Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 240M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 185M
      PaleMoon-nonsse2 Loaded, with NoScript, one tab on antiX forum – 158M
      Netsurf, open to antiX forum – 108M
      LibreOffice Writer loaded, all browsers closed, single document – 150M

      p3—–
      antix-19.1 32-bit, Kernel=4.9.200-antix.1-486-smp i686, Debian=10 (Buster)
      15GB HD Partition, 3.61G used, 1GB Swap Partition
      IceWM Window Manager, “icewm” desktop, antiX Adblock activated
      Memory used reported in Conkey
      Initial Idle Memory – 70M
      Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 248M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 171M
      PaleMoon-nonsse2 Loaded, NoScript NOT installed, one tab on antiX forum – 150M
      Note: PM w/o NoScript = CPU 100% on antiX Forum, CPU 82% on MX Forum
      Netsurf, open to antiX forum – 110M
      SMTube, 360p mp4 video playing in mpv, all browsers closed – 195M, CPU=70%

      p3—–
      Q4OS Trinity 32-bit, Kernel=4.9.0-12-686-pae i686, Debian=9 (Stretch)
      15GB HD Partition, 5.1G used, 1GB Swap Partition
      Trinity Desktop Environment (TDE – KDE Plasma 3), “Q4OS_Default” theme
      Memory used reported in “htop”
      Initial Idle Memory – 136M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 255M
      PaleMoon-nonsse2 Loaded, NoScript NOT installed, one tab on antiX forum – unusable
      Note: PM w/o NoScript = CPU 100% on antiX Forum, unusable. Install NoScript.
      PaleMoon-nonsse2 Loaded, NoScript activated, one tab on antiX forum – 210M
      Midori, open to antiX forum – 248M CPU=100%
      Konqueror, open to antiX forum – 209M
      Netsurf, open to antiX forum – 170M
      SMTube, 360p mp4 video playing in mpv, all browsers closed – 228M, CPU=70%
      LibreOffice Writer loaded, all browsers closed, single document – 242M

      p3—–
      MX-Fluxbox 19.2 32-bit, Kernel=4.19.0-6-686-pae i686, Debian=10 (Buster)
      (Note – might be better off installing 4.9 kernel)
      15GB HD Partition, 3.61G used, 1GB Swap Partition
      XFCE Desktop Environment, “Fluxbox” desktop
      Memory used reported in “htop”
      Initial Idle Memory – 93M
      Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 310M
      Note: ESR version is not installed by default. Used MXPI to install.
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 222M
      Note: SeaMonkey must be installed from archive file downloaded from website.
      PaleMoon-nonsse2 Loaded, with NoScript active, one tab on antiX forum – 191M
      Note – installed PM from .deb file using gdebi. MX-17 repository.
      Netsurf, open to antiX forum – 150M
      LibreOffice Writer loaded, all browsers closed, single document – 228M

      SMTube, 360p mp4 video playing in VNC, all browsers closed – 189M, CPU=100%
      Note – mpv not installed. Installed mplayer and mpv from MXPI. Didn’t work. Maybe need non-SSE2 version. Check antiX repos. Installed SMPlayer. SMPlayer starts but video does not play. Maybe related to youtube-dl? Installed youtube-dl. Didn’t help.

      p3—–
      Debian 9 (Stretch) 32-bit, Kernel=4.9.0-12-686-pae i686
      13GB HD Partition, 6.3G used, 1GB Swap Partition
      XFCE Desktop Environment, “IceWM” desktop
      Memory used reported in “htop”
      Initial Idle Memory – 80M
      Firefox ESR Loaded, with NoScript active, one tab on antiX forum – 401M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 227M

      p3—–
      Debian 10 (Buster) 32-bit, Kernel=4.19.0-8-686-pae i686
      13GB HD Partition, 4.14G used, 1GB Swap Partition
      XFCE Desktop Environment, “IceWM” desktop
      Memory used reported in “htop”
      Initial Idle Memory – 90M
      Firefox ESR Loaded, could not install NoScript. CPU=100% hung up.
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 215M

      P-4 Prescott HT 3.2 Ghz, 3Gb
      p4—–
      MX-19.2 32-bit, Kernel=4.19.0-6-686-pae i686, Debian=10 (Buster)
      23GB HD Partition, 8.56G used, 3GB Swap Partition
      XFCE Desktop Environment, “XFCE” desktop
      Memory used reported in Conkey
      Initial Idle Memory – 429M
      Firefox Loaded, one tab on antiX forum – 726M
      Falkon Loaded, one tab on antiX forum – 681M
      PaleMoon Loaded, one tab on antiX forum – 674M
      Vivaldi Loaded, one tab on antiX forum- 667M
      SlimJet Loaded, one tab on antiX forum – 629M
      Chromium Loaded, one tab on antiX forum – 583M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 571M
      LibreOffice Writer loaded, all browsers closed, single document – 660M

      p4—–
      MX-Fluxbox 19.2 32-bit, Kernel=4.19.0-6-686-pae i686, Debian=10 (Buster)
      23GB HD Partition, 8.56G used, 3GB Swap Partition
      XFCE Desktop Environment, “Fluxbox” desktop
      Memory used reported in “htop”
      Initial Idle Memory – 237M
      Firefox Loaded, one tab on antiX forum – 446M
      Falkon Loaded, one tab on antiX forum – 404M
      PaleMoon Loaded, one tab on antiX forum – 403M
      Vivaldi Loaded, one tab on antiX forum- 427M
      SlimJet Loaded, one tab on antiX forum – 392M
      Chromium Loaded, one tab on antiX forum – 362M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 405M
      LibreOffice Writer loaded, all browsers closed, single document – 332M

      p4—–
      antix-19.1 32-bit, Kernel=4.9.193-antix.1-486-smp i686, Debian=10 (Buster)
      Frugal install on 8GB HD Partition, 2.44G used, 3GB Swap Partition
      IceWM Window Manager, “space-icewm” desktop, antiX Adblock activated
      Memory used reported in Conkey
      Initial Idle Memory – 73M
      Firefox ESR Loaded, one tab on antiX forum – 285M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 200M
      Chromium Loaded – one tab on antiX forum – 230M
      SMTube, 360p mp4 video playing in mpv, all browsers closed – 192M, CPU=16%
      LibreOffice Writer loaded, all browsers closed, single document – 140M
      SeaMonkey open one tab, SMTube video playing, Writer document – 375M, CPU=42%

      p4—–
      Q4OS Trinity 32-bit, Kernel=4.9.0-13-686-pae i686, Debian=9 (Stretch)
      12GB HD Partition, 8G used, 3GB Swap Partition
      Trinity Desktop Environment (TDE – KDE Plasma 3), “Debonaire” theme
      Memory used reported in “htop”
      Initial Idle Memory – 160M
      SeaMonkey Loaded, with NoScript active, one tab on antiX forum – 284M
      Chromium, open to antiX forum – 321M
      Konqueror, open to antiX forum – 274M
      SMTube, 360p mp4 video playing in VLC, all browsers closed – 302M, CPU=16%
      LibreOffice Writer loaded, all browsers closed, single document – 327M
      SeaMonkey open one tab, SMTube video playing, Writer document – 408M, CPU=17%

      #40107
      Member
      cyrilus31

        What’s striking is that PrePrescott CPUs (my laptop has a northwood p4, same boat) are struggling with web browsing. It’s hard to open a tab and using libreoffice at the same time, or viewing a video. Ram is not a matter once you have a minimum of 512Mo, but these processors are too old to run modern browsers.
        In any case, you made a great job seaken ! Very helpful.

        • This reply was modified 3 years, 8 months ago by cyrilus31.
        • This reply was modified 3 years, 8 months ago by cyrilus31.
        #40111
        Member
        ModdIt

          @ seaken64, many thanks for the comparison list, it takes away illusions for some but is a help in explaining why.

          BTW. just saw this: downloadram.net

          Download more RAM for free and instantly from our website. Free upgrade 1GB RAM – 2GB RAM – 4GB RAM – 8GB RAM – 16GB RAM.
          Watching the RAM modules materialise from empty air space would be fun !.

          @ crilus31
          Maybe someone will correct me: The lightest way to watch video seems to be searching with MPVST and using MPV as player.
          I really like this method as search is really easy, playlist generation too.
          SM tube is too heavy for my wimpy EEPC although it is pretty modern in comparison to P4 machines.

          Browsers: agree not easy, ripping all the rubbish out of latest firefox has made it pretty usable though,

          I use it for sites which only work with fox, chrome or Edge. quite a few.
          Still fighting with Badwolf for debian based system.

          #40117
          Moderator
          christophe

            Wow! Very interesting seeing the comparisons. Thanks for all the work involved in testing & documenting it for us.

            confirmed antiX frugaler, since 2019

            #40120
            Moderator
            Brian Masinick

              @seaken64: Thank you very much for providing these statistics.

              “Just For Fun”, I snagged another image of antiX 16 x64 Full and put it on an old USB drive to check it out on my Dell Inspiron 5558 laptop. I knew it would still work because I got this laptop around 2015, so antiX 16 (original) was released midway through 2016, with updates through early 2017 before antiX 17 was released.

              By Default it comes with Firefox ESR and dillo as browsers, but you can use the metapackage installer (now simply called Package Installer) to add more Web Browsers.

              I’m pleasantly surprised at how many useful things we have added between antiX 16 and antiX 19.2! I guess the many changes creep up on us. In any case, this release may work for a few of those OLDER systems that we’ve been discussing recently.

              --
              Brian Masinick

              #40130
              Member
              marcelocripe

                Seaken64,

                Infelizmente eu vou ficar devendo, eu não consegui tantas informações detalhadas quanto as suas. A minhas ficam limitadas pelo comando $ free {Enter}, $ htop {Enter}, ou de algum gerenciador de tarefas.

                Tiny Core Plus (CorePlus-current.iso ou Tiny Core Plus 11.0)

                Antes da instalação no HD:
                Terminal, com o comando “free”, memória total 964532 KB de memória RAM, 89060 KB em uso e 797756 KB livres.

                Após a instalação no HD:
                Terminal, com o comando “free”, memória total 964532 KB, 50988 KB em uso e 866016 KB livres.

                Programas já instalados no Tiny Core Plus 11.0 e 11.1
                Menu Wbar: Exit, Editor, ControlPanel, Apps, RunProgram, MountTool, Terminal, eZremaster, Wifi.

                No Tiny Core Plus 11.0 e 11.1 o Vídeo padrão é o xvesa.tcz, o Áudio por padrão não está disponível na ISO, Placa de rede LAN e WiFi são inicializadas por padrão na inicialização do sistema operacional.

                Puppy Linux BionicPup 32 (bionicpup32-8.0-uefi.iso)
                Antes da instalação no HD:
                Com o “Task Manager”, dos 1607 MB, 126 MB estão em uso e 5% de CPU.

                Após a instalação no HD:
                $ free {Enter}
                Memória: total: 1646012 KB, 76468 KB em uso e 1408204 MB livres.
                Com o Task Manager,dos 1607 MB, 92 MB estão em uso e 16% de CPU.

                SliTaz (slitaz-rolling-core64.iso versão 20-05-2020)

                Antes da instalação no HD:
                $ free {Enter}
                XTerm Terminal
                Memória: total: 2088424 KB de memória RAM, 101276 KB em uso e 1701092 KB livres

                Sakura Terminal
                Memória: total: 2048424 KB de memória RAM, 101608 KB em uso e 1700716 KB livres.

                Gerenciador de tarefas LXTask 0.1.9:
                Exibe uso da CPU entre 0% e 2%, consumo de memória 93 MB de 2000 MB

                Após a instalação no HD:
                $ free {Enter}
                XTerm Terminal
                Memória: total: 1991712 KB de memória RAM, 72264 KB em uso e 1866784 KB livres

                Sakura Terminal
                Memória: total: 1991712 KB de memória RAM, 72996 KB em uso e 1864176 KB livres.

                Gerenciador de tarefas LXTask 0.1.9:
                Exibe uso da CPU entre 1% e 3%, consumo de memória 66 MB de 1945 MB.

                http://www.slax.org/introduction.php

                Requisitos de sistema para executar o Slax

                Slax 32bit
                Processador: CPU i686 ou mais recente, todos os processadores Intel e AMD funcionarão
                Memória: 128 MB de RAM para a área de trabalho, 512 MB de RAM para executar o navegador da Web
                Periféricos: Para inicializar a partir de unidade de CD ou USB ou HD
                Opcionalmente: placa de rede, placa de som

                Slax 64bit
                Processador: CPU x86_64, como AMD Athlon 64, Opteron, Sempron, Intel Core 2 / i3 / i5 / i7 e outros
                Memória: 128 MB de RAM para a área de trabalho, 512 MB de RAM para executar o navegador da Web
                Periféricos: Para inicializar a partir de unidade de CD ou USB ou HD
                Opcionalmente: placa de rede, placa de som

                Após a instalação no HD:

                Slax Linux (slax-64bit-9.11.0.iso):
                Utilizando o comando free no terminal o consumo de memória RAM foi de cerca de 134 MB ou utilizando o gerenciador de tarefas o consumo de memória RAM foi de cerca 155 MB.

                Slax Linux (slax-32bit-9.11.0.iso)
                Utilizando o comando free no terminal o consumo de memória RAM foi de cerca de 97912 KB (97,91 MB) ou utilizando o gerenciador de tarefas o consumo de memória RAM foi de cerca 109 MB.

                Void (void-live-x86_64-20191109-lxde.iso)

                -Antes da instalação, executando o Void Linux via pendrive:
                [anon@void-live:~] $ free {Enter}
                Memória: total: 2028996, used: 116344, free: 1306088 KB , shared: 23368, buff/cache: 606564, avaliable: 1743776 (valores em KB).

                -Após a instalação do Void Linux no HD:
                Memória: total: 2029456, usada: 121328, livre: 1727560 KB , compartilhada: 26048, buff/cache: 180568, disponível: 1741848 (valores em KB), Swap: total: 2096476, usada: 0, livre: 2096476.

                antiX (antiX-19.2_x64-full.iso)

                Antes da instalação no HD:
                Informações exibidas pelo Conky antes da instalação: Resolução 1366×768, dpi 96, Automount enable, CPU variando entre 2% e 4 %, Frequencia variando entre 800 e 1600, RAM 174M Usada / 1,56GB Total (para vídeo onboard -Via VT8237R Plus) ou RAM 144M Usada / 1,96GB Total (para vídeo offboard – nVidia GeForce MX 4000 Version 4.18.20.36.00 64 MB), Swap 0 / 5GB, Disco (Pendrive) 2,59M / 1,23 GB.

                Com o Terminal, comando demo@antixl:~ $ free {Enter}, memória total: 1641436 KB de memória RAM, 171304 KB em uso e 900160 KB livres, shared 11502.

                Após a instalação no HD:
                Informações exibidas pelo Conky, Resolução 1366×768, dpi 96, Automount enable, CPU variando entre 2% e 4 %, Frequencia variando entre 800 e 1600, RAM 172M Usada / 1,56GB Total, Swap 0 / 4GB, Disco (HD) 3,24G / 224 GB.

                Terminal, o comando Usuario@antixl:~ $ free {Enter}, memória total: 1641436 KB de memória RAM, 175864 KB estão em uso e 1230832 KB estão livres, shared 2092, Swap 4194300.

                Eu não sei desabilitar o Conky da inicialização do antiX, eu acredito que possa diminuir ainda mais o consumo de memória. Você sabe em qual arquivo de configuração onde podemos retirar o Conky? O ideal seria que o Conky fosse carregado na memória se o usuário o abrisse, ao invés de ser carregado por padrão.

                antiX Linux (antiX-17.4.1_x64-full.iso)

                Antes da instalação no HD:
                Informações exibidas pelo Conky, Resolução 1280×1024, dpi 96, Automount enable, CPU variando entre 52% e 54 %, Frequencia variando 2528, RAM 114M Usada / 1,89GB Total (para vídeo onboard), Swap 0 / 0B, Disco (Pendrive) 1,87M / 1,49 GB.
                Terminal, com o comando demo@antixl:~ $ free {Enter}, memória total: 1985696 KB de memória RAM, 113592 KB estão em uso e 1511040 KB estão livres, shared 8876, buff/cache 361064 avaliable 1725964.

                Após a instalação no HD:
                Informações exibidas pelo Conky, Resolução 1024×768, dpi 96, Automount enable, CPU variando entre 51% e 53 %, Frequencia variando entre 2528, RAM 131M Usada / 1,96GB Total, Swap 0 / 2GB, Disco (HD) 2,83G / 34.5 GB.
                Terminal, com o comando Usuario@antixl:~ $ free {Enter}, memória total: 1985708 KB de memória RAM, 138836 KB estão em uso e 1681044 KB estão livres, shared 1712, buff/cache 165828 avaliable 1710044, Swap 2096124.

                antiX Linux (antiX-16.3_x64-full.iso)

                Antes da instalação no HD:
                Informações exibidas pelo Conky, Resolução 1024×768, dpi 96, Automount enable, CPU variando entre 2% e 4 %, Frequencia variando 2528, RAM 103M Usada / 1,89GB Total (para vídeo onboard), Swap 0 / 0B, Disco (Pendrive) 2,43M / 1,49 GB.
                Terminal, com o comando demo@antixl:~ $ free {Enter}, memória total: 1985244 KB de memória RAM, 454408 KB estão em uso e 1530836 KB estão livres, shared 7324, buffers 68448 cached 268368 -/+ buffers/cache 117592 used e 1867652 free.

                Após a instalação no HD:
                Informações exibidas pelo Conky, Resolução 1024×768, dpi 96, Automount enable, CPU variando entre 3% e 5%, Frequencia variando entre 2528, RAM 118M Usada / 1,89GB Total, Swap 0 / 2GB, Disco (HD) 2,44G / 28.9 GB.
                Terminal, com o comando Usuario@antix:~ $ free {Enter}, memória total: 1985244 KB de memória RAM, 282176 KB estão em uso e 1703068 KB estão livres, shared 1012, buffers 20100 cached 126868 +/- buffers/cached 135208 free 1850036, Swap 2097148 total 0 used 2097148 free.

                GoboLinux (GoboLinux-017-x86_64.iso)

                http://gobolinux.org/release_notes_017.html
                Hardware requirements
                Processor
                GoboLinux is compiled to run on x86-64-class systems. You shouldn’t have problems to run it on any modern x86 machine, including Macs. This release contains 64-bit binaries.

                Memory
                To load the Live CD environment, 128 MB of RAM is the recommended minimum for a text-mode system, 512 MB is the recommended minimum to load the graphic Awesome desktop; 1 GB is recommended for a comfortable Live-boot experience.

                Once the system is installed in the hard disk, memory requirements vary greatly depending on the kind of applications executed, but the values stated above related to the Live CD experience serve as a good guideline.

                Antes da instalação no HD:
                $ free {Enter}
                Memória: total: 2026848 KB, usada: 115776 KB, livre: 1360880 KB, compartilhada: 110308 KB, buff/cache: 550192 KB, disponível: 1648868 KB, swap: total: 0 KB, usada: 0, livre: 0 KB.

                No Menu, System Tools, Htop, exibe valores de consumo de memória dos 1.93G de memória RAM, 192MB estão em uso, exibe uso da CPU entre 1.3% e 2%

                Após a instalação no HD:
                $ free {Enter}
                Memória: total: 2026860 KB, usada: 102568 KB, livre: 1664500 KB, compartilhada: 69260 KB, buff/cache: 259792 KB, disponível: 1710960, swap: total: 2097148 KB, usada: 0, livre: 2097148 KB.

                Htop, exibe valores de consumo de memória, dos 1.93G de memória RAM, 147MB estão em uso, exibe uso da CPU entre 0% e 1.3%.

                marcelocripe

                • This reply was modified 3 years, 8 months ago by marcelocripe.
                • This reply was modified 3 years, 8 months ago by marcelocripe.
                #40131
                Member
                marcelocripe

                  Seaken64,

                  Unfortunately I will be in debt, I didn’t get as much detailed information as yours. Mine are limited by the command $ free {Enter}, $ htop {Enter}, or some task manager.

                  Tiny Core Plus (CorePlus-current.iso or Tiny Core Plus 11.0)

                  Before installing to HD:
                  Terminal, with the command “free”, total memory 964532 KB of RAM, 89060 KB in use and 797756 KB free.

                  After installing on HD:
                  Terminal, with the command “free”, total memory 964532 KB, 50988 KB in use and 866016 KB free.

                  Programs already installed on Tiny Core Plus 11.0 and 11.1
                  Wbar menu: Exit, Editor, ControlPanel, Apps, RunProgram, MountTool, Terminal, eZremaster, Wifi.

                  In Tiny Core Plus 11.0 and 11.1 the default Video is xvesa.tcz, Audio by default is not available at ISO, LAN and WiFi network cards are initialized by default at the startup of the operating system.

                  Puppy Linux BionicPup 32 (bionicpup32-8.0-uefi.iso)
                  Before installing to HD:
                  With the “Task Manager”, of the 1607 MB, 126 MB are in use and 5% CPU.

                  After installing on HD:
                  $ free {Enter}
                  Memory: total: 1646012 KB, 76468 KB in use and 1408204 MB free.
                  With the Task Manager, of the 1607 MB, 92 MB are in use and 16% CPU.

                  SliTaz (slitaz-rolling-core64.iso version 20-05-2020)

                  Before installing to HD:
                  $ free {Enter}
                  XTerm Terminal
                  Memory: total: 2088424 KB of RAM, 101276 KB in use and 1701092 KB free

                  Sakura Terminal
                  Memory: total: 2048424 KB of RAM, 101608 KB in use and 1700716 KB free.

                  Task manager LXTask 0.1.9:
                  Displays CPU usage between 0% and 2%, memory consumption 93 MB of 2000 MB

                  After installing on HD:
                  $ free {Enter}
                  XTerm Terminal
                  Memory: total: 1991712 KB of RAM, 72264 KB in use and 1866784 KB free

                  Sakura Terminal
                  Memory: total: 1991712 KB of RAM, 72996 KB in use and 1864176 KB free.

                  Task manager LXTask 0.1.9:
                  Displays CPU usage between 1% and 3%, memory consumption 66 MB of 1945 MB.

                  http://www.slax.org/introduction.php

                  System requirements for running Slax

                  32bit Slax
                  Processor: i686 CPU or later, all Intel and AMD processors will work
                  Memory: 128 MB of RAM for the desktop, 512 MB of RAM to run the web browser
                  Peripherals: To boot from CD or USB or HD drive
                  Optionally: network card, sound card

                  64bit Slax
                  Processor: x86_64 CPU, such as AMD Athlon 64, Opteron, Sempron, Intel Core 2 / i3 / i5 / i7 and others
                  Memory: 128 MB of RAM for the desktop, 512 MB of RAM to run the web browser
                  Peripherals: To boot from CD or USB or HD drive
                  Optionally: network card, sound card

                  After installing on HD:

                  Slax Linux (slax-64bit-9.11.0.iso):
                  Using the free command on the terminal the consumption of RAM was about 134 MB or using the task manager the consumption of RAM was about 155 MB.

                  Slax Linux (slax-32bit-9.11.0.iso)
                  Using the free command on the terminal the RAM memory consumption was about 97912 KB (97.91 MB) or using the task manager the RAM memory consumption was about 109 MB.

                  Void (void-live-x86_64-20191109-lxde.iso)

                  -Before installation, running Void Linux via pendrive:
                  [anon @ void-live: ~] $ free {Enter}
                  Memory: total: 2028996, used: 116344, free: 1306088 KB, shared: 23368, buff / cache: 606564, avaliable: 1743776 (values ​​in KB).

                  -After installing Void Linux on the HD:
                  Memory: total: 2029456, used: 121328, free: 1727560 KB, shared: 26048, buff / cache: 180568, available: 1741848 (values ​​in KB), Swap: total: 2096476, used: 0, free: 2096476.

                  antiX (antiX-19.2_x64-full.iso)

                  Before installing to HD:
                  Information displayed by Conky before installation: Resolution 1366×768, dpi 96, Automount enable, CPU varying between 2% and 4%, Frequency varying between 800 and 1600, RAM 174M Used / 1.56GB Total (for onboard video – Via VT8237R Plus) or Used 144M RAM / 1.96GB Total (for offboard video – nVidia GeForce MX 4000 Version 4.18.20.36.00 64 MB), Swap 0 / 5GB, Disk (Pendrive) 2.59M / 1.23 GB.

                  With Terminal, command demo @ antixl: ~ $ free {Enter}, total memory: 1641436 KB of RAM, 171304 KB in use and 900160 KB free, shared 11502.

                  After installing on HD:
                  Information displayed by Conky, Resolution 1366×768, dpi 96, Automount enable, CPU varying between 2% and 4%, Frequency varying between 800 and 1600, RAM 172M Used / 1.56GB Total, Swap 0 / 4GB, Disk (HD) 3, 24G / 224 GB.

                  Terminal, the command Usuario @ antixl: ~ $ free {Enter}, total memory: 1641436 KB of RAM, 175864 KB are in use and 1230832 KB are free, shared 2092, Swap 4194300.

                  I do not know how to disable Conky from antiX startup, I believe it can reduce memory consumption even more. Do you know in which configuration file we can get Conky from? Ideally, Conky would be loaded into memory if the user opened it, instead of being loaded by default.

                  antiX Linux (antiX-17.4.1_x64-full.iso)

                  Before installing to HD:
                  Information displayed by Conky, 1280×1024 resolution, 96 dpi, Automount enable, CPU ranging from 52% to 54%, Frequency ranging from 2528, Used RAM 114M / 1.89GB Total (for onboard video), Swap 0 / 0B, Disk (Pendrive) 1.87M / 1.49 GB.
                  Terminal, with the command demo @ antixl: ~ $ free {Enter}, total memory: 1985696 KB of RAM, 113592 KB are in use and 1511040 KB are free, shared 8876, buff / cache 361064 avaliable 1725964.

                  After installing on HD:
                  Information displayed by Conky, Resolution 1024×768, dpi 96, Automount enable, CPU varying between 51% and 53%, Frequency varying between 2528, 131M RAM Used / 1.96GB Total, Swap 0 / 2GB, Disk (HD) 2,83G / 34.5 GB.
                  Terminal, with the command Usuario @ antixl: ~ $ free {Enter}, total memory: 1985708 KB of RAM, 138836 KB are in use and 1681044 KB are free, shared 1712, buff / cache 165828 avaliable 1710044, Swap 2096124.

                  antiX Linux (antiX-16.3_x64-full.iso)

                  Before installing to HD:
                  Information displayed by Conky, 1024×768 resolution, 96 dpi, Automount enable, CPU ranging from 2% to 4%, Frequency ranging from 2528, RAM 103M Used / 1.89GB Total (for onboard video), Swap 0 / 0B, Disk (Pendrive) 2.43M / 1.49 GB.
                  Terminal, with the command demo @ antixl: ~ $ free {Enter}, total memory: 1985244 KB of RAM, 454408 KB are in use and 1530836 KB are free, shared 7324, buffers 68448 cached 268368 – / + buffers / cache 117592 used and 1867652 free.

                  After installing on HD:
                  Information displayed by Conky, Resolution 1024×768, dpi 96, Automount enable, CPU varying between 3% and 5%, Frequency varying between 2528, 118M RAM Used / 1.89GB Total, Swap 0 / 2GB, Disk (HD) 2.44G / 28.9 GB.
                  Terminal, with the command Usuario @ antix: ~ $ free {Enter}, total memory: 1985244 KB of RAM, 282176 KB are in use and 1703068 KB are free, shared 1012, buffers 20100 cached 126868 +/- buffers / cached 135208 free 1850036, Swap 2097148 total 0 used 2097148 free.

                  GoboLinux (GoboLinux-017-x86_64.iso)

                  http://gobolinux.org/release_notes_017.html
                  Hardware requirements
                  Processor
                  GoboLinux is compiled to run on x86-64-class systems. You shouldn’t have problems to run it on any modern x86 machine, including Macs. This release contains 64-bit binaries.

                  Memory
                  To load the Live CD environment, 128 MB of RAM is the recommended minimum for a text-mode system, 512 MB is the recommended minimum to load the graphic Awesome desktop; 1 GB is recommended for a comfortable Live-boot experience.

                  Once the system is installed in the hard disk, memory requirements vary greatly depending on the kind of applications executed, but the values ​​stated above related to the Live CD experience serves as a good guideline.

                  Before installing to HD:
                  $ free {Enter}
                  Memory: total: 2026848 KB, used: 115776 KB, free: 1360880 KB, shared: 110308 KB, buff / cache: 550192 KB, available: 1648868 KB, swap: total: 0 KB, used: 0, free: 0 KB.

                  In the Menu, System Tools, Htop, displays memory consumption values ​​of 1.93G of RAM, 192MB are in use, displays CPU usage between 1.3% and 2%

                  After installing on HD:
                  $ free {Enter}
                  Memory: total: 2026860 KB, used: 102568 KB, free: 1664500 KB, shared: 69260 KB, buff / cache: 259792 KB, available: 1710960, swap: total: 2097148 KB, used: 0, free: 2097148 KB.

                  Htop, displays memory consumption values, of the 1.93G of RAM, 147MB are in use, displays CPU usage between 0% and 1.3%.

                  marcelocripe

                  • This reply was modified 3 years, 8 months ago by marcelocripe.
                  #40135
                  Member
                  marcelocripe

                    Removed by marcelocripe on 08-18-2020, due to duplicate postage.
                    Removido por marcelocripe no dia 18-08-2020, devido a postagem duplicada.

                    • This reply was modified 3 years, 8 months ago by anticapitalista.
                    • This reply was modified 3 years, 8 months ago by marcelocripe.
                    #40136
                    Member
                    seaken64

                      @marcelocripe,

                      this is just my opinion, you can take it or leave it. I think there is a lot to be said about usability out of the box. I was always impressed with Puppy because it had everything ready to use upon bootup. Once you get the network running you just click on the icons to start using the apps. But when it came to updates and customizing I found it difficult. It was not standard enough for me. I had a similar experience with Vector Linux. It was nicely setup and usable. But I could never figure out how to install packages that were not in the repositories.

                      Then I found antiX and Debian. antiX was also very usable out of the box and the setup was very familiar to me as an old Windows user. But now, when I tried to install software I could do it! The apt system of Debian was just easier for me. I found antiX both usable out of the box and easy to update and upgrade.

                      I have used plain Debian, SparkyLinux, SliTaz, Slax, Ubuntu, Xubuntu, Kubuntu, Lubuntu, LXLE, PepperMint, Slackware, CentOS, openSUSE, and Redhat/Fedora. They are all interesting. But only a few of these even come close to being usable on an old computer like a Pentium-4 or a Core2. For my old computers antiX is by far the easiest for me to actually use since I am not a programmer or developer. It just works and comes ready to use browsers, office software, file managers, and music and video – out of the box. And updates and upgrades are easy.

                      Some people have had good results using the Core version of antiX or the NET version of Debian and building their own setup. Same for Tiny Core or SliTaz or Arch, gentoo, etc. But if you are not a programmer or developer, and just want a usable system that runs on old equipment then it is really hard to find a better solution than antiX or MX.

                      You may find that Debian will work best for your installing packages from CD or DVD repos. Maybe you can get such a setup working in antiX since antiX is a very close cousin to Debian.

                      I enjoyed your list. But you still have to install software to make those system useful. It will be interesting to me if you find a better software system than Debian/antiX/MX.

                      Seaken64

                      #40137
                      Moderator
                      Brian Masinick

                        @seaken64:

                        You stated very clearly exactly what I also believe.

                        I love Debian when I want something pretty close to what I plan to use; MX Linux and antiX meet my needs.

                        1. The initial software is good and well suited for the desktop (MX Linux).
                        2. The software is efficient and well suited for old or less powerful software. (antiX)

                        Either one of these distributions are usable for a wide range of computer systems and applications.

                        • This reply was modified 3 years, 8 months ago by Brian Masinick.
                        • This reply was modified 3 years, 8 months ago by Brian Masinick. Reason: Typos
                        • This reply was modified 3 years, 8 months ago by Brian Masinick.

                        --
                        Brian Masinick

                        #40138
                        Member
                        seaken64

                          What’s striking is that PrePrescott CPUs (my laptop has a northwood p4, same boat) are struggling with web browsing. It’s hard to open a tab and using libreoffice at the same time, or viewing a video. Ram is not a matter once you have a minimum of 512Mo, but these processors are too old to run modern browsers.
                          In any case, you made a great job seaken ! Very helpful.

                          Yes, that is true. You really have to be careful what sites you go to or the CPU will peg at 100% and hang up. I have found that SeaMonkey with NoScript gives me a pretty good result. I am also going to try using Moddit’s tips on setting up Firefox.

                          If you’re on a P-III or P-4, or Athlon XP, you need to be satisfied with doing one thing at a time. And only one to three tabs open at once. This is not a problem for me since I have been computing like that since the beginning with 16-bit computers running DOS, or even 8-bit CP/M.

                          I do notice a difference with multi-threading. My Prescott P4 here is HyperThread and at 3.2Ghz. It does a pretty good job of multitasking. Especially as compared to my P-III or single thread P4’s.

                          Seaken64

                          • This reply was modified 3 years, 8 months ago by seaken64.
                          #40141
                          Member
                          seaken64

                            @ seaken64, many thanks for the comparison list, it takes away illusions for some but is a help in explaining why.

                            BTW. just saw this: downloadram.net

                            Download more RAM for free and instantly from our website. Free upgrade 1GB RAM – 2GB RAM – 4GB RAM – 8GB RAM – 16GB RAM.
                            Watching the RAM modules materialise from empty air space would be fun !.

                            @ crilus31
                            Maybe someone will correct me: The lightest way to watch video seems to be searching with MPVST and using MPV as player.
                            I really like this method as search is really easy, playlist generation too.
                            SM tube is too heavy for my wimpy EEPC although it is pretty modern in comparison to P4 machines.

                            Browsers: agree not easy, ripping all the rubbish out of latest firefox has made it pretty usable though,

                            I use it for sites which only work with fox, chrome or Edge. quite a few.
                            Still fighting with Badwolf for debian based system.

                            Hi Moddit, I think you are referring to MPSYT, MPS-YouTube in the antiX menu. It is a command line app and yes, it is very good. I also like to use youtube-dl. I use youtube-dl on a P-III with 256MB RAM to watch YouTube! Pretty amazing. And if SMTube doesn’t work try “Streamlight” in the gui.

                            I am going to go back and review your instruction on setting up Firefox now that I’ve found that Firefox ESR works on my non-SSE2 computers. Maybe I can add a modified Firefox ESR to my list of browsers that can be used on these ancient boxes.

                            Seaken64

                            #40142
                            Member
                            seaken64

                              Wow! Very interesting seeing the comparisons. Thanks for all the work involved in testing & documenting it for us.

                              I hope it helps. As marcel has told us there are still a lot of old computers that need to be kept alive. Maybe this will assist the admins of those types of systems.

                              And yes, it took some work. I spent yesterday doing the tests. But it is my hobby so it was fun.

                              Seaken64

                              #40143
                              Member
                              seaken64

                                @seaken64: Thank you very much for providing these statistics.

                                “Just For Fun”, I snagged another image of antiX 16 x64 Full and put it on an old USB drive to check it out on my Dell Inspiron 5558 laptop. I knew it would still work because I got this laptop around 2015, so antiX 16 (original) was released midway through 2016, with updates through early 2017 before antiX 17 was released.

                                By Default it comes with Firefox ESR and dillo as browsers, but you can use the metapackage installer (now simply called Package Installer) to add more Web Browsers.

                                I’m pleasantly surprised at how many useful things we have added between antiX 16 and antiX 19.2! I guess the many changes creep up on us. In any case, this release may work for a few of those OLDER systems that we’ve been discussing recently.

                                It’s fun isn’t it? You’re just missing that old 32-bit hardware! That’s cheating with a Core i5! 🙂

                                Seaken64

                                #40144
                                Member
                                seaken64

                                  @marcelocripe

                                  I do not know how to disable Conky from antiX startup, I believe it can reduce memory consumption even more. Do you know in which configuration file we can get Conky from? Ideally, Conky would be loaded into memory if the user opened it, instead of being loaded by default.

                                  You can edit the startup files from the Control Centre/Session/User Desktop-Session/desktop-session.conf

                                  Seaken64

                                  • This reply was modified 3 years, 8 months ago by seaken64.
                                Viewing 15 posts - 1 through 15 (of 24 total)
                                • You must be logged in to reply to this topic.