-
Search Results
-
In reply to: System Requirements for antiX and other Debians
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 freeSakura 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 MBAfter installing on HD:
$ free {Enter}
XTerm Terminal
Memory: total: 1991712 KB of RAM, 72264 KB in use and 1866784 KB freeSakura 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.https://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 card64bit 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 cardAfter 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)
https://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 2 years, 9 months ago by marcelocripe.
In reply to: System Requirements for antiX and other Debians
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 livresSakura 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 MBApó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 livresSakura 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.https://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 somSlax 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 somApó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)
https://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 2 years, 9 months ago by marcelocripe.
- This reply was modified 2 years, 9 months ago by marcelocripe.
Anonymous
a GUI application (GTK3) for configuring and customizing JWM:
https://codeberg.org/JWMKit/JWM_Kit/
(just pointing it out, cannot recommend it as I haven’t tested it)JWM Kit is a new set of software design to simplify usage of JWM (Joe’s Window Manager). In order to maximize personal customization JWM Kit focus on providing a graphical interface for editing menus, trays, groups, etc. No part of the kit is designed to run in the background. It only runs when the user starts it, and properly quits when “closed”, or for notifications will close when timed out in a few seconds.
# JWM Kit is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License, version 2, # as published by the Free Software Foundation.I discovered it mentioned (by its author) here:
Announcing JWM Kit Live [updated iso download]
a devuan-based liveboot ISO showcasing the JWMKit is availableIn reply to: Unable to set resolution to FullHD
caprea
A suggestion what you should try to do first is to install another kernel. My box with nvidia card boots with vesa with the 4.9 kernel and with nouveau with the 4.19 kernel. But it is also a more modern gtx 960 card, so it makes more sense. But it is worth a try.
Or try a live-stick with the 4.19-kernel.
antiX-19.2-4.19_kernel_x64-full.isoGordo
I’m booting live antiX-19.2.1_x64-base.iso directly from HDD (via grub), just
for familiarization purposes before doing an install.Noticed the following peculiar behavior, 100% reproducible on my setup.
Wondering if anyone else can reproduce and perhaps diagnose. Summary:* With kernel ‘hostname’ parameter unspecified, bootup and shutdown behavior
is normal.* However, if ‘hostname’ parameter is explicitly supplied on the kernel
commandline as any value other than the default (“antiX1”), then
both bootup and shutdown times become abut 10-15 seconds longer.Steps to reproduce:
Case 1:
* Boot from HDD iso with kernel ‘hostname’ parameter unspecified. Note
elapsed time until full desktop appears (including icons at left side).
* As soon as desktop comes up, start a ROXterm and do “sudo reboot”.
* Observe nearly instantaneous bash prompt, followed quickly (1-2 seconds)
by X shutdown and then the usual sequence of shutdown console messages.Case 2:
* Boot from HDD iso with kernel hostname=foo.
* Observe that it takes about 10 – 15 seconds longer to reach full
desktop state than in Case 1. (In particular, the icons along the
left side are delayed by “many” seconds.)
* As soon as full desktop comes up, start a ROXterm and do “sudo reboot”.
* Observe delay of about 10 – 15 seconds until bash prompt seen, then
followed by X shutdown and usual console shutdown messages.My guess is that hostname != “antiX1” results in some sort of persistence-
related squashfs activity, which fails and times out because squashfs is
read-only on the live iso image.Anyone able to reproduce this?
rayluo
Hi there,
I’ve been using LiveUSB without any persistence. My USB disk is relatively small (4 GB), with 1 GB already consumed by the boot iso itself. But since I store very few files in ~/Live-usb-storage, I never pay attention to its disk consumption, and things still work well. Today I encountered a “No space left on device” error when copying for example a 50 MB file into it, but then the following disk space check suggests I am supposed to have still 2+ GB available. How come?
$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sdb2 3.8G 1.6G 2.2G 42% /live/boot-dev /dev/loop0 1013M 1013M 0 100% /live/linux tmpfs 1.6G 2.2M 1.6G 1% /live/aufs-ram overlay 1.6G 2.2M 1.6G 1% / tmpfs 10M 0 10M 0% /media tmpfs 201M 1.1M 200M 1% /run tmpfs 10M 6.3M 3.8M 63% /live tmpfs 1003M 4.0K 1003M 1% /tmp devtmpfs 1001M 4.0K 1001M 1% /dev tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 453M 588K 452M 1% /dev/shm tmpfs 1003M 0 1003M 0% /sys/fs/cgroup tmpfs 201M 0 201M 0% /run/user/1000 /dev/sdb1 201M 512 201M 1% /media/USB-DATA /dev/sdb3 49M 4.2M 45M 9% /media/LIVE-UEFI /dev/sdc1 3.3G 3.2G 106M 97% /media/demo/DELL_PRO_64In the first line of the above screen output, /dev/sdb2 is my USB disk. Those numbers are the same as GParted’s output (except rounding errors), although GParted also mention my sdb2 is also mounted to another 2 more mount points: /home/demo/Live-usb-storage and /root/Live-usb-storage (which shouldn’t matter here, should it?)
And, my ~/Live-usb-storage currently contains only 513M data, which still matches the “Used” stat from “df -h” (because 1GB boot iso + 513M user data ~= 1.6G used).
$ du -h -s Live-usb-storage/ 513M Live-usb-storage/Where else should I look into to figure this out?
UPDATE: Ah, it seems I run out of inodes. Now trying to figure out why that happens, and how to fix it…
$ df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdb2 40320 40320 0 100% /live/boot-dev /dev/loop0 159441 159441 0 100% /live/linux tmpfs 218859 1269 217590 1% /live/aufs-ram overlay 218859 1269 217590 1% / tmpfs 218859 10 218849 1% /media tmpfs 218859 645 218214 1% /run tmpfs 218859 851 218008 1% /live tmpfs 218859 17 218842 1% /tmp devtmpfs 217462 526 216936 1% /dev tmpfs 218859 2 218857 1% /run/lock tmpfs 218859 90 218769 1% /dev/shm tmpfs 218859 3 218856 1% /sys/fs/cgroup tmpfs 218859 5 218854 1% /run/user/1000 /dev/sdb1 0 0 0 - /media/USB-DATA /dev/sdb3 0 0 0 - /media/LIVE-UEFI /dev/sdc1 173252 36 173216 1% /media/demo/DELL_PRO_64 /dev/sda5 0 0 0 - /media/DATAUPDATE 2: From what I found online, number of inodes are decided when the file system was created, and you can not change it afterwards. The default number would be disk size in KB / 16 KB. In my case, the 40320 inodes were supposed to be created for a 660MB disk (which would have been right), but my disk has 4GB. So, I don’t know whether this is considered a bug in the LiveUSB maker. Meanwhile, my workaround is to delete some less useful files from this LiveUSB disk in order to save some inodes.
In reply to: [SOLVED] MultBootUSB not working with antiX19
Brian Masinick
https://www.funkyspacemonkey.com/how-to-create-a-multi-iso-bootable-flash-drive
shows the basics to running Ventoy.Debian, antiX, and MX Linux are included in the list of supported distros, so that is a good start for me!
--
Brian MasinickIn reply to: [SOLVED] MultBootUSB not working with antiX19
BobC
I found that there are some distros that do work on Exfat which is what ventoy creates as it’s default.
And some distros that don’t work on Exfat. And of the ones that don’t work on Exfat, some of them do work on Ext2.
The most common problem is that it is able to find the .iso and pop up it’s boot options, but then when it tries to boot, it can’t find something that it expected to find, and the boot fails.
On my machines I have troubles with mounting the ventoy partition. Automount causes troble. Adding to fstab causes trouble. Basically everything is trouble. It has to do with something else that I have installed, I think.
In reply to: [SOLVED] MultBootUSB not working with antiX19
I couldn’t get anything to work. I spent too many hours/days trying. I had a few successful boots with Ventoy, but can’t seem to figure out why things worked vs what didn’t. The Exfmt is a nightmare for antiX. Automount can’t be left on. NTFS is trouble for many. So you end up with no easy way to mount the drive. Automount needs to be off. Nothing can mount the drive. But the worst problem is that no matter what format, most of the time you can’t boot from the ISO, even though usually the boot screen comes up. It always has problems finding the pieces of the OS itself half way through booting, and ends up on an initramfs error where it can’t find the medium. I tried Ext2, Ext4 and NTFS as well as Exfat.
That’s enough. I’m too exhausted from brain drain at work anyway.
It was a nice idea, but not ready for prime time.
olsztyn
I would like to create user accounts (for my different daily uses), which are; Underprivileged, isolated and standard.
By this I mean, when one is logged in to such an account, one cannot bring any systemic changes. The user can’t install software, can’t access the system except making subjective configurations for the desktop and application use. But one can access all the standard applications and not the system. The account is so isolated from other user accounts that even if a Trojan happens to get into one underprivileged account it cannot access anything or any data from other accounts and cannot access the system.
I am following this thread with great interest as this is something I was thinking of in the past. As originally described this would be great to have from theoretical perspective but IMHO appears to be quite challenging to accomplish in practice.
However from your later post I infer that the purpose of such distinction of entitlements is to actual use in practice rather than theoretical project, just to have dedicated setups for use such as work/banking/… etc., with their own security setups and entitlements, antiX is a unique OS that makes this easy to accomplish and to some degree I am actually using such concept in practice:
Namely:
Rather than looking at such task from a complicated and challenging setup of user entitlement, their lock-downs and application access, I have simply created separate Live USB keys:
– Separate keys for banking, system maintenance, multimedia, etc.
– Such keys are encrypted with their password. Separate passwords can be used e.g. for banking key than for multimedia, but in my case I am just one real user so I made the same password for all.
– Such separate live systems are configured to their requirements, so e.g. banking key has all the security configured to the max, such as firewall, browser security restrictions, etc.
– Once all applications and security/privacy setups are finalized for each USB key according to their requirements these USB keys are then set to have no persistence for banking key or to have some home persistence for typical work key. No persistence means no chance for rogue code or virus to make any permanent change. Should this unlikely happen during session – just reboot.The reason I mentioned that antiX is a unique OS that make such task easy to accomplish in practice is that:
– antiX has all the needed tools already included and easy to use.
– Memory requirements are very low – USB keys can be used an any laptop
– Boots very fast from USB. Hard drives are optional.
– Mostly operates from memory so writes to USB are minimalJust my two cents added to this interesting subject…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
I received the Email notification today that:
"------------------------------------------------------------------------ The Debian Project https://www.debian.org/ Updated Debian 10: 10.5 released press@debian.org August 1st, 2020 https://www.debian.org/News/2020/20200801 ------------------------------------------------------------------------ The Debian project is pleased to announce the fifth update of its stable distribution Debian 10 (codename "buster"). This point release mainly adds corrections for security issues, along with a few adjustments for serious problems. Security advisories have already been published separately and are referenced where available. This point release also addresses Debian Security Advisory: DSA-4735-1 grub2 -- security update [1] which covers multiple CVE issues regarding the GRUB2 UEFI SecureBoot 'BootHole' vulnerability [2]. 1: https://www.debian.org/security/2020/dsa-4735 2: https://www.debian.org/security/2020-GRUB-UEFI-SecureBoot/ Please note that the point release does not constitute a new version of Debian 10 but only updates some of the packages included. There is no need to throw away old "buster" media. After installation, packages can be upgraded to the current versions using an up-to-date Debian mirror. Those who frequently install updates from security.debian.org won't have to update many packages, and most such updates are included in the point release. New installation images will be available soon at the regular locations. Upgrading an existing installation to this revision can be achieved by pointing the package management system at one of Debian's many HTTP mirrors. A comprehensive list of mirrors is available at: https://www.debian.org/mirror/list Miscellaneous Bugfixes ---------------------- This stable update adds a few important corrections to the following packages: +---------------------------+------------------------------------------+ | Package | Reason | +---------------------------+------------------------------------------+ | appstream-glib [3] | Fix build failures in 2020 and later | | | | | asunder [4] | Use gnudb instead of freedb by default | | | | | b43-fwcutter [5] | Ensure removal succeeds under non- | | | English locales; do not fail removal if | | | some files no longer exist; fix missing | | | dependencies on pciutils and ca- | | | certificates | | | | | balsa [6] | Provide server identity when validating | | | certificates, allowing successful | | | validation when using the glib- | | | networking patch for CVE-2020-13645 | | | | | base-files [7] | Update for the point release | | | | | batik [8] | Fix server-side request forgery via | | | xlink:href attributes [CVE-2019-17566] | | | | | borgbackup [9] | Fix index corruption bug leading to data | | | loss | | | | | bundler [10] | Update required version of ruby- | | | molinillo | | | | | c-icap-modules [11] | Add support for ClamAV 0.102 | | | | | cacti [12] | Fix issue where UNIX timestamps after | | | September 13th 2020 were rejected as | | | graph start / end; fix remote code | | | execution [CVE-2020-7237], cross-site | | | scripting [CVE-2020-7106], CSRF issue | | | [CVE-2020-13231]; disabling a user | | | account does not immediately invalidate | | | permissions [CVE-2020-13230] | | | | | calamares-settings- | Enable displaymanager module, fixing | | debian [13] | autologin options; use xdg-user-dir to | | | specify Desktop directory | | | | | clamav [14] | New upstream release; security fixes | | | [CVE-2020-3327 CVE-2020-3341 CVE-2020- | | | 3350 CVE-2020-3327 CVE-2020-3481] | | | | | cloud-init [15] | New upstream release | | | | | commons- | Prevent object creation when loading | | configuration2 [16] | YAML files [CVE-2020-1953] | | | | | confget [17] | Fix the Python module's handling of | | | values containing "=" | | | | | dbus [18] | New upstream stable release; prevent a | | | denial of service issue [CVE-2020- | | | 12049]; prevent use-after-free if two | | | usernames share a uid | | | | | debian-edu-config [19] | Fix loss of dynamically allocated IPv4 | | | address | | | | | debian-installer [20] | Update Linux ABI to 4.19.0-10 | | | | | debian-installer-netboot- | Rebuild against proposed-updates | | images [21] | | | | | | debian-ports-archive- | Increase the expiration date of the 2020 | | keyring [22] | key (84C573CD4E1AFD6C) by one year; add | | | Debian Ports Archive Automatic Signing | | | Key (2021); move the 2018 key (ID: | | | 06AED62430CB581C) to the removed keyring | | | | | debian-security- | Update support status of several | | support [23] | packages | | | | | dpdk [24] | New upstream release | | | | | exiv2 [25] | Adjust overly restrictive security patch | | | [CVE-2018-10958 and CVE-2018-10999]; fix | | | denial of service issue [CVE-2018-16336] | | | | | fdroidserver [26] | Fix Litecoin address validation | | | | | file-roller [27] | Security fix [CVE-2020-11736] | | | | | freerdp2 [28] | Fix smartcard logins; security fixes | | | [CVE-2020-11521 CVE-2020-11522 CVE-2020- | | | 11523 CVE-2020-11524 CVE-2020-11525 | | | CVE-2020-11526] | | | | | fwupd [29] | New upstream release; fix possible | | | signature verification issue [CVE-2020- | | | 10759]; use rotated Debian signing keys | | | | | fwupd-amd64-signed [30] | New upstream release; fix possible | | | signature verification issue [CVE-2020- | | | 10759]; use rotated Debian signing keys | | | | | fwupd-arm64-signed [31] | New upstream release; fix possible | | | signature verification issue [CVE-2020- | | | 10759]; use rotated Debian signing keys | | | | | fwupd-armhf-signed [32] | New upstream release; fix possible | | | signature verification issue [CVE-2020- | | | 10759]; use rotated Debian signing keys | | | | | fwupd-i386-signed [33] | New upstream release; fix possible | | | signature verification issue [CVE-2020- | | | 10759]; use rotated Debian signing keys | | | | | fwupdate [34] | Use rotated Debian signing keys | | | | | fwupdate-amd64- | Use rotated Debian signing keys | | signed [35] | | | | | | fwupdate-arm64- | Use rotated Debian signing keys | | signed [36] | | | | | | fwupdate-armhf- | Use rotated Debian signing keys | | signed [37] | | | | | | fwupdate-i386-signed [38] | Use rotated Debian signing keys | | | | | gist [39] | Avoid deprecated authorization API | | | | | glib-networking [40] | Return bad identity error if identity is | | | unset [CVE-2020-13645]; break balsa | | | older than 2.5.6-2+deb10u1 as the fix | | | for CVE-2020-13645 breaks balsa's | | | certificate verification | | | | | gnutls28 [41] | Fix TL1.2 resumption errors; fix memory | | | leak; handle zero length session | | | tickets, fixing connection errors on | | | TLS1.2 sessions to some big hosting | | | providers; fix verification error with | | | alternate chains | | | | | intel-microcode [42] | Downgrade some microcodes to previously | | | issued versions, working around hangs on | | | boot on Skylake-U/Y and Skylake Xeon E3 | | | | | jackson-databind [43] | Fix multiple security issues affecting | | | BeanDeserializerFactory [CVE-2020-9548 | | | CVE-2020-9547 CVE-2020-9546 CVE-2020- | | | 8840 CVE-2020-14195 CVE-2020-14062 | | | CVE-2020-14061 CVE-2020-14060 CVE-2020- | | | 11620 CVE-2020-11619 CVE-2020-11113 | | | CVE-2020-11112 CVE-2020-11111 CVE-2020- | | | 10969 CVE-2020-10968 CVE-2020-10673 | | | CVE-2020-10672 CVE-2019-20330 CVE-2019- | | | 17531 and CVE-2019-17267] | | | | | jameica [44] | Add mckoisqldb to classpath, allowing | | | use of SynTAX plugin | | | | | jigdo [45] | Fix HTTPS support in jigdo-lite and | | | jigdo-mirror | | | | | ksh [46] | Fix environment variable restriction | | | issue [CVE-2019-14868] | | | | | lemonldap-ng [47] | Fix nginx configuration regression | | | introduced by the fix for CVE-2019-19791 | | | | | libapache-mod-jk [48] | Rename Apache configuration file so it | | | can be automatically enabled and | | | disabled | | | | | libclamunrar [49] | New upstream stable release; add an | | | unversioned meta-package | | | | | libembperl-perl [50] | Handle error pages from Apache >= 2.4.40 | | | | | libexif [51] | Security fixes [CVE-2020-12767 CVE-2020- | | | 0093 CVE-2020-13112 CVE-2020-13113 | | | CVE-2020-13114]; fix buffer overflow | | | [CVE-2020-0182] and integer overflow | | | [CVE-2020-0198] | | | | | libinput [52] | Quirks: add trackpoint integration | | | attribute | | | | | libntlm [53] | Fix buffer overflow [CVE-2019-17455] | | | | | libpam-radius-auth [54] | Fix buffer overflow in password field | | | [CVE-2015-9542] | | | | | libunwind [55] | Fix segfaults on mips; manually enable C | | | ++ exception support only on i386 and | | | amd64 | | | | | libyang [56] | Fix cache corruption crash, CVE-2019- | | | 19333, CVE-2019-19334 | | | | | linux [57] | New upstream stable release | | | | | linux-latest [58] | Update for 4.19.0-10 kernel ABI | | | | | linux-signed-amd64 [59] | New upstream stable release | | | | | linux-signed-arm64 [60] | New upstream stable release | | | | | linux-signed-i386 [61] | New upstream stable release | | | | | lirc [62] | Fix conffile management | | | | | mailutils [63] | maidag: drop setuid privileges for all | | | delivery operations but mda [CVE-2019- | | | 18862] | | | | | mariadb-10.3 [64] | New upstream stable release; security | | | fixes [CVE-2020-2752 CVE-2020-2760 | | | CVE-2020-2812 CVE-2020-2814 CVE-2020- | | | 13249]; fix regression in RocksDB ZSTD | | | detection | | | | | mod-gnutls [65] | Fix a possible segfault on failed TLS | | | handshake; fix test failures | | | | | multipath-tools [66] | kpartx: use correct path to partx in | | | udev rule | | | | | mutt [67] | Don't check IMAP PREAUTH encryption if | | | $tunnel is in use | | | | | mydumper [68] | Link against libm | | | | | nfs-utils [69] | statd: take user-id from /var/lib/nfs/sm | | | [CVE-2019-3689]; don't make /var/lib/nfs | | | owned by statd | | | | | nginx [70] | Fix error page request smuggling | | | vulnerability [CVE-2019-20372] | | | | | nmap [71] | Update default key size to 2048 bits | | | | | node-dot-prop [72] | Fix regression introduced in CVE-2020- | | | 8116 fix | | | | | node-handlebars [73] | Disallow calling "helperMissing" and | | | "blockHelperMissing" directly | | | [CVE-2019-19919] | | | | | node-minimist [74] | Fix prototype pollution [CVE-2020-7598] | | | | | nvidia-graphics- | New upstream stable release; security | | drivers [75] | fixes [CVE-2020-5963 CVE-2020-5967] | | | | | nvidia-graphics-drivers- | New upstream stable release; security | | legacy-390xx [76] | fixes [CVE-2020-5963 CVE-2020-5967] | | | | | openstack-debian- | Install resolvconf if installing cloud- | | images [77] | init | | | | | pagekite [78] | Avoid issues with expiry of shipped SSL | | | certificates by using those from the ca- | | | certificates package | | | | | pdfchain [79] | Fix crash at startup | | | | | perl [80] | Fix multiple regular expression related | | | security issues [CVE-2020-10543 | | | CVE-2020-10878 CVE-2020-12723] | | | | | php-horde [81] | Fix cross-site scripting vulnerability | | | [CVE-2020-8035] | | | | | php-horde-gollem [82] | Fix cross-site scripting vulnerability | | | in breadcrumb output [CVE-2020-8034] | | | | | pillow [83] | Fix multiple out-of-bounds read issues | | | [CVE-2020-11538 CVE-2020-10378 CVE-2020- | | | 10177] | | | | | policyd-rate-limit [84] | Fix issues in accounting due to socket | | | reuse | | | | | postfix [85] | New upstream stable release; fix | | | segfault in the tlsproxy client role | | | when the server role was disabled; fix | | | "maillog_file_rotate_suffix default | | | value used the minute instead of the | | | month" ; fix several TLS related issues; | | | README.Debian fixes | | | | | python-markdown2 [86] | Fix cross-site scripting issue | | | [CVE-2020-11888] | | | | | python3.7 [87] | Avoid infinite loop when reading | | | specially crafted TAR files using the | | | tarfile module [CVE-2019-20907]; resolve | | | hash collisions for IPv4Interface and | | | IPv6Interface [CVE-2020-14422]; fix | | | denial of service issue in | | | urllib.request.AbstractBasicAuthHandler | | | [CVE-2020-8492] | | | | | qdirstat [88] | Fix saving of user-configured MIME | | | categories | | | | | raspi3-firmware [89] | Fix typo that could lead to unbootable | | | systems | | | | | resource-agents [90] | IPsrcaddr: make "proto" optional to | | | fix regression when used without | | | NetworkManager | | | | | ruby-json [91] | Fix unsafe object creation vulnerability | | | [CVE-2020-10663] | | | | | shim [92] | Use rotated Debian signing keys | | | | | shim-helpers-amd64- | Use rotated Debian signing keys | | signed [93] | | | | | | shim-helpers-arm64- | Use rotated Debian signing keys | | signed [94] | | | | | | shim-helpers-i386- | Use rotated Debian signing keys | | signed [95] | | | | | | speedtest-cli [96] | Pass correct headers to fix upload speed | | | test | | | | | ssvnc [97] | Fix out-of-bounds write [CVE-2018- | | | 20020], infinite loop [CVE-2018-20021], | | | improper initialisation [CVE-2018- | | | 20022], potential denial-of-service | | | [CVE-2018-20024] | | | | | storebackup [98] | Fix possible privilege escalation | | | vulnerability [CVE-2020-7040] | | | | | suricata [99] | Fix dropping privileges in nflog runmode | | | | | tigervnc [100] | Don't use libunwind on armel, armhf or | | | arm64 | | | | | transmission [101] | Fix possible denial of service issue | | | [CVE-2018-10756] | | | | | wav2cdr [102] | Use C99 fixed-size integer types to fix | | | runtime assertion on 64bit architectures | | | other than amd64 and alpha | | | | | zipios++ [103] | Security fix [CVE-2019-13453] | | | | +---------------------------+------------------------------------------+ 3: https://packages.debian.org/src:appstream-glib 4: https://packages.debian.org/src:asunder 5: https://packages.debian.org/src:b43-fwcutter 6: https://packages.debian.org/src:balsa 7: https://packages.debian.org/src:base-files 8: https://packages.debian.org/src:batik 9: https://packages.debian.org/src:borgbackup 10: https://packages.debian.org/src:bundler 11: https://packages.debian.org/src:c-icap-modules 12: https://packages.debian.org/src:cacti 13: https://packages.debian.org/src:calamares-settings-debian 14: https://packages.debian.org/src:clamav 15: https://packages.debian.org/src:cloud-init 16: https://packages.debian.org/src:commons-configuration2 17: https://packages.debian.org/src:confget 18: https://packages.debian.org/src:dbus 19: https://packages.debian.org/src:debian-edu-config 20: https://packages.debian.org/src:debian-installer 21: https://packages.debian.org/src:debian-installer-netboot-images 22: https://packages.debian.org/src:debian-ports-archive-keyring 23: https://packages.debian.org/src:debian-security-support 24: https://packages.debian.org/src:dpdk 25: https://packages.debian.org/src:exiv2 26: https://packages.debian.org/src:fdroidserver 27: https://packages.debian.org/src:file-roller 28: https://packages.debian.org/src:freerdp2 29: https://packages.debian.org/src:fwupd 30: https://packages.debian.org/src:fwupd-amd64-signed 31: https://packages.debian.org/src:fwupd-arm64-signed 32: https://packages.debian.org/src:fwupd-armhf-signed 33: https://packages.debian.org/src:fwupd-i386-signed 34: https://packages.debian.org/src:fwupdate 35: https://packages.debian.org/src:fwupdate-amd64-signed 36: https://packages.debian.org/src:fwupdate-arm64-signed 37: https://packages.debian.org/src:fwupdate-armhf-signed 38: https://packages.debian.org/src:fwupdate-i386-signed 39: https://packages.debian.org/src:gist 40: https://packages.debian.org/src:glib-networking 41: https://packages.debian.org/src:gnutls28 42: https://packages.debian.org/src:intel-microcode 43: https://packages.debian.org/src:jackson-databind 44: https://packages.debian.org/src:jameica 45: https://packages.debian.org/src:jigdo 46: https://packages.debian.org/src:ksh 47: https://packages.debian.org/src:lemonldap-ng 48: https://packages.debian.org/src:libapache-mod-jk 49: https://packages.debian.org/src:libclamunrar 50: https://packages.debian.org/src:libembperl-perl 51: https://packages.debian.org/src:libexif 52: https://packages.debian.org/src:libinput 53: https://packages.debian.org/src:libntlm 54: https://packages.debian.org/src:libpam-radius-auth 55: https://packages.debian.org/src:libunwind 56: https://packages.debian.org/src:libyang 57: https://packages.debian.org/src:linux 58: https://packages.debian.org/src:linux-latest 59: https://packages.debian.org/src:linux-signed-amd64 60: https://packages.debian.org/src:linux-signed-arm64 61: https://packages.debian.org/src:linux-signed-i386 62: https://packages.debian.org/src:lirc 63: https://packages.debian.org/src:mailutils 64: https://packages.debian.org/src:mariadb-10.3 65: https://packages.debian.org/src:mod-gnutls 66: https://packages.debian.org/src:multipath-tools 67: https://packages.debian.org/src:mutt 68: https://packages.debian.org/src:mydumper 69: https://packages.debian.org/src:nfs-utils 70: https://packages.debian.org/src:nginx 71: https://packages.debian.org/src:nmap 72: https://packages.debian.org/src:node-dot-prop 73: https://packages.debian.org/src:node-handlebars 74: https://packages.debian.org/src:node-minimist 75: https://packages.debian.org/src:nvidia-graphics-drivers 76: https://packages.debian.org/src:nvidia-graphics-drivers-legacy-390xx 77: https://packages.debian.org/src:openstack-debian-images 78: https://packages.debian.org/src:pagekite 79: https://packages.debian.org/src:pdfchain 80: https://packages.debian.org/src:perl 81: https://packages.debian.org/src:php-horde 82: https://packages.debian.org/src:php-horde-gollem 83: https://packages.debian.org/src:pillow 84: https://packages.debian.org/src:policyd-rate-limit 85: https://packages.debian.org/src:postfix 86: https://packages.debian.org/src:python-markdown2 87: https://packages.debian.org/src:python3.7 88: https://packages.debian.org/src:qdirstat 89: https://packages.debian.org/src:raspi3-firmware 90: https://packages.debian.org/src:resource-agents 91: https://packages.debian.org/src:ruby-json 92: https://packages.debian.org/src:shim 93: https://packages.debian.org/src:shim-helpers-amd64-signed 94: https://packages.debian.org/src:shim-helpers-arm64-signed 95: https://packages.debian.org/src:shim-helpers-i386-signed 96: https://packages.debian.org/src:speedtest-cli 97: https://packages.debian.org/src:ssvnc 98: https://packages.debian.org/src:storebackup 99: https://packages.debian.org/src:suricata 100: https://packages.debian.org/src:tigervnc 101: https://packages.debian.org/src:transmission 102: https://packages.debian.org/src:wav2cdr 103: https://packages.debian.org/src:zipios++ Security Updates ---------------- This revision adds the following security updates to the stable release. The Security Team has already released an advisory for each of these updates: +----------------+-----------------------------+ | Advisory ID | Package | +----------------+-----------------------------+ | DSA-4626 [104] | php7.3 [105] | | | | | DSA-4674 [106] | roundcube [107] | | | | | DSA-4675 [108] | graphicsmagick [109] | | | | | DSA-4676 [110] | salt [111] | | | | | DSA-4677 [112] | wordpress [113] | | | | | DSA-4678 [114] | firefox-esr [115] | | | | | DSA-4679 [116] | keystone [117] | | | | | DSA-4680 [118] | tomcat9 [119] | | | | | DSA-4681 [120] | webkit2gtk [121] | | | | | DSA-4682 [122] | squid [123] | | | | | DSA-4683 [124] | thunderbird [125] | | | | | DSA-4684 [126] | libreswan [127] | | | | | DSA-4685 [128] | apt [129] | | | | | DSA-4686 [130] | apache-log4j1.2 [131] | | | | | DSA-4687 [132] | exim4 [133] | | | | | DSA-4688 [134] | dpdk [135] | | | | | DSA-4689 [136] | bind9 [137] | | | | | DSA-4690 [138] | dovecot [139] | | | | | DSA-4691 [140] | pdns-recursor [141] | | | | | DSA-4692 [142] | netqmail [143] | | | | | DSA-4694 [144] | unbound [145] | | | | | DSA-4695 [146] | firefox-esr [147] | | | | | DSA-4696 [148] | nodejs [149] | | | | | DSA-4697 [150] | gnutls28 [151] | | | | | DSA-4699 [152] | linux-signed-amd64 [153] | | | | | DSA-4699 [154] | linux-signed-arm64 [155] | | | | | DSA-4699 [156] | linux-signed-i386 [157] | | | | | DSA-4699 [158] | linux [159] | | | | | DSA-4700 [160] | roundcube [161] | | | | | DSA-4701 [162] | intel-microcode [163] | | | | | DSA-4702 [164] | thunderbird [165] | | | | | DSA-4704 [166] | vlc [167] | | | | | DSA-4705 [168] | python-django [169] | | | | | DSA-4707 [170] | mutt [171] | | | | | DSA-4708 [172] | neomutt [173] | | | | | DSA-4709 [174] | wordpress [175] | | | | | DSA-4710 [176] | trafficserver [177] | | | | | DSA-4711 [178] | coturn [179] | | | | | DSA-4712 [180] | imagemagick [181] | | | | | DSA-4713 [182] | firefox-esr [183] | | | | | DSA-4714 [184] | chromium [185] | | | | | DSA-4716 [186] | docker.io [187] | | | | | DSA-4718 [188] | thunderbird [189] | | | | | DSA-4719 [190] | php7.3 [191] | | | | | DSA-4720 [192] | roundcube [193] | | | | | DSA-4721 [194] | ruby2.5 [195] | | | | | DSA-4722 [196] | ffmpeg [197] | | | | | DSA-4723 [198] | xen [199] | | | | | DSA-4724 [200] | webkit2gtk [201] | | | | | DSA-4725 [202] | evolution-data-server [203] | | | | | DSA-4726 [204] | nss [205] | | | | | DSA-4727 [206] | tomcat9 [207] | | | | | DSA-4728 [208] | qemu [209] | | | | | DSA-4729 [210] | libopenmpt [211] | | | | | DSA-4730 [212] | ruby-sanitize [213] | | | | | DSA-4731 [214] | redis [215] | | | | | DSA-4732 [216] | squid [217] | | | | | DSA-4733 [218] | qemu [219] | | | | | DSA-4735 [220] | grub-efi-amd64-signed [221] | | | | | DSA-4735 [222] | grub-efi-arm64-signed [223] | | | | | DSA-4735 [224] | grub-efi-ia32-signed [225] | | | | | DSA-4735 [226] | grub2 [227] | | | | +----------------+-----------------------------+ 104: https://www.debian.org/security/2020/dsa-4626 105: https://packages.debian.org/src:php7.3 106: https://www.debian.org/security/2020/dsa-4674 107: https://packages.debian.org/src:roundcube 108: https://www.debian.org/security/2020/dsa-4675 109: https://packages.debian.org/src:graphicsmagick 110: https://www.debian.org/security/2020/dsa-4676 111: https://packages.debian.org/src:salt 112: https://www.debian.org/security/2020/dsa-4677 113: https://packages.debian.org/src:wordpress 114: https://www.debian.org/security/2020/dsa-4678 115: https://packages.debian.org/src:firefox-esr 116: https://www.debian.org/security/2020/dsa-4679 117: https://packages.debian.org/src:keystone 118: https://www.debian.org/security/2020/dsa-4680 119: https://packages.debian.org/src:tomcat9 120: https://www.debian.org/security/2020/dsa-4681 121: https://packages.debian.org/src:webkit2gtk 122: https://www.debian.org/security/2020/dsa-4682 123: https://packages.debian.org/src:squid 124: https://www.debian.org/security/2020/dsa-4683 125: https://packages.debian.org/src:thunderbird 126: https://www.debian.org/security/2020/dsa-4684 127: https://packages.debian.org/src:libreswan 128: https://www.debian.org/security/2020/dsa-4685 129: https://packages.debian.org/src:apt 130: https://www.debian.org/security/2020/dsa-4686 131: https://packages.debian.org/src:apache-log4j1.2 132: https://www.debian.org/security/2020/dsa-4687 133: https://packages.debian.org/src:exim4 134: https://www.debian.org/security/2020/dsa-4688 135: https://packages.debian.org/src:dpdk 136: https://www.debian.org/security/2020/dsa-4689 137: https://packages.debian.org/src:bind9 138: https://www.debian.org/security/2020/dsa-4690 139: https://packages.debian.org/src:dovecot 140: https://www.debian.org/security/2020/dsa-4691 141: https://packages.debian.org/src:pdns-recursor 142: https://www.debian.org/security/2020/dsa-4692 143: https://packages.debian.org/src:netqmail 144: https://www.debian.org/security/2020/dsa-4694 145: https://packages.debian.org/src:unbound 146: https://www.debian.org/security/2020/dsa-4695 147: https://packages.debian.org/src:firefox-esr 148: https://www.debian.org/security/2020/dsa-4696 149: https://packages.debian.org/src:nodejs 150: https://www.debian.org/security/2020/dsa-4697 151: https://packages.debian.org/src:gnutls28 152: https://www.debian.org/security/2020/dsa-4699 153: https://packages.debian.org/src:linux-signed-amd64 154: https://www.debian.org/security/2020/dsa-4699 155: https://packages.debian.org/src:linux-signed-arm64 156: https://www.debian.org/security/2020/dsa-4699 157: https://packages.debian.org/src:linux-signed-i386 158: https://www.debian.org/security/2020/dsa-4699 159: https://packages.debian.org/src:linux 160: https://www.debian.org/security/2020/dsa-4700 161: https://packages.debian.org/src:roundcube 162: https://www.debian.org/security/2020/dsa-4701 163: https://packages.debian.org/src:intel-microcode 164: https://www.debian.org/security/2020/dsa-4702 165: https://packages.debian.org/src:thunderbird 166: https://www.debian.org/security/2020/dsa-4704 167: https://packages.debian.org/src:vlc 168: https://www.debian.org/security/2020/dsa-4705 169: https://packages.debian.org/src:python-django 170: https://www.debian.org/security/2020/dsa-4707 171: https://packages.debian.org/src:mutt 172: https://www.debian.org/security/2020/dsa-4708 173: https://packages.debian.org/src:neomutt 174: https://www.debian.org/security/2020/dsa-4709 175: https://packages.debian.org/src:wordpress 176: https://www.debian.org/security/2020/dsa-4710 177: https://packages.debian.org/src:trafficserver 178: https://www.debian.org/security/2020/dsa-4711 179: https://packages.debian.org/src:coturn 180: https://www.debian.org/security/2020/dsa-4712 181: https://packages.debian.org/src:imagemagick 182: https://www.debian.org/security/2020/dsa-4713 183: https://packages.debian.org/src:firefox-esr 184: https://www.debian.org/security/2020/dsa-4714 185: https://packages.debian.org/src:chromium 186: https://www.debian.org/security/2020/dsa-4716 187: https://packages.debian.org/src:docker.io 188: https://www.debian.org/security/2020/dsa-4718 189: https://packages.debian.org/src:thunderbird 190: https://www.debian.org/security/2020/dsa-4719 191: https://packages.debian.org/src:php7.3 192: https://www.debian.org/security/2020/dsa-4720 193: https://packages.debian.org/src:roundcube 194: https://www.debian.org/security/2020/dsa-4721 195: https://packages.debian.org/src:ruby2.5 196: https://www.debian.org/security/2020/dsa-4722 197: https://packages.debian.org/src:ffmpeg 198: https://www.debian.org/security/2020/dsa-4723 199: https://packages.debian.org/src:xen 200: https://www.debian.org/security/2020/dsa-4724 201: https://packages.debian.org/src:webkit2gtk 202: https://www.debian.org/security/2020/dsa-4725 203: https://packages.debian.org/src:evolution-data-server 204: https://www.debian.org/security/2020/dsa-4726 205: https://packages.debian.org/src:nss 206: https://www.debian.org/security/2020/dsa-4727 207: https://packages.debian.org/src:tomcat9 208: https://www.debian.org/security/2020/dsa-4728 209: https://packages.debian.org/src:qemu 210: https://www.debian.org/security/2020/dsa-4729 211: https://packages.debian.org/src:libopenmpt 212: https://www.debian.org/security/2020/dsa-4730 213: https://packages.debian.org/src:ruby-sanitize 214: https://www.debian.org/security/2020/dsa-4731 215: https://packages.debian.org/src:redis 216: https://www.debian.org/security/2020/dsa-4732 217: https://packages.debian.org/src:squid 218: https://www.debian.org/security/2020/dsa-4733 219: https://packages.debian.org/src:qemu 220: https://www.debian.org/security/2020/dsa-4735 221: https://packages.debian.org/src:grub-efi-amd64-signed 222: https://www.debian.org/security/2020/dsa-4735 223: https://packages.debian.org/src:grub-efi-arm64-signed 224: https://www.debian.org/security/2020/dsa-4735 225: https://packages.debian.org/src:grub-efi-ia32-signed 226: https://www.debian.org/security/2020/dsa-4735 227: https://packages.debian.org/src:grub2 Removed packages ---------------- The following packages were removed due to circumstances beyond our control: +--------------------------------+------------------------------------+ | Package | Reason | +--------------------------------+------------------------------------+ | golang-github-unknwon- | Security issues; unmaintained | | cae [228] | | | | | | janus [229] | Not supportable in stable | | | | | mathematica-fonts [230] | Relies on unavailable download | | | location | | | | | matrix-synapse [231] | Security issues; unsupportable | | | | | selenium-firefoxdriver [232] | Incompatible with newer Firefox | | | ESR versions | | | | +--------------------------------+------------------------------------+ 228: https://packages.debian.org/src:golang-github-unknwon-cae 229: https://packages.debian.org/src:janus 230: https://packages.debian.org/src:mathematica-fonts 231: https://packages.debian.org/src:matrix-synapse 232: https://packages.debian.org/src:selenium-firefoxdriver Debian Installer ---------------- The installer has been updated to include the fixes incorporated into stable by the point release. URLs ---- The complete lists of packages that have changed with this revision: http://ftp.debian.org/debian/dists/buster/ChangeLog The current stable distribution: http://ftp.debian.org/debian/dists/stable/ Proposed updates to the stable distribution: http://ftp.debian.org/debian/dists/proposed-updates stable distribution information (release notes, errata etc.): https://www.debian.org/releases/stable/ Security announcements and information: https://www.debian.org/security/ About Debian ------------ The Debian Project is an association of Free Software developers who volunteer their time and effort in order to produce the completely free operating system Debian. Contact Information ------------------- For further information, please visit the Debian web pages at https://www.debian.org/, send mail to <press@debian.org>, or contact the stable release team at <debian-release@lists.debian.org>."--
Brian MasinickBrian Masinick
A third one that shows what was going on for a little while – Warren Woodford, the MEPIS founder, switched from Debian to Ubuntu repositories for a while, hoping to get easy to use, stable software. After a while with that “experiment, MEPIS – and antiX along with it, went back to using Debian software. (I used both, and didn’t have any problems with it, but this small window of time were among the “most unstable” of the MEPIS and antiX history that I can think of or remember):
https://web.archive.org/web/20071005225440/http://antix.mepis.org/index.php/Main_Page
archived article:
Welcome to antiX.
News
27 September 2007More places to get antiX-M7-rc1 and antiX-beta2-r1 xdelta patch, thanks to MEPIS mirrors.
ftp://ftp.ibiblio.org/pub/linux/distributions/mepis/testing/
ftp://carroll.aset.psu.edu/pub/linux/distributions/mepis/testing/
md5sum: c164ed3bbf959a39777c63625ac83c80 antiX-M7-rc1.iso
Post comments, bugs on the antiX forum
20 September 2007
antiX-M7-rc1 (288MB) available from here: http://www.gigasize.com/get.php?d=och28h6opdf
md5sum: c164ed3bbf959a39777c63625ac83c80 antiX-M7-rc1.iso
antiX-beta2-r1 xdelta patch (77MB) available here: http://www.gigasize.com/get.php?d=qhghq8llopd
12 September 2007
antiX forum now available.
The one at MepisLovers is still open.
05 September 2007
If you have recently downloaded antiX-M7-beta2 and you want to install some kde app, you will find you cannot due to dependency problems. This is because antiX temporarily got ahead with gcc and cpp from Debian testing.
Easiest solution and an upgrade: Install aptitude from synaptic or
apt-get install aptitude (it will also upgrade apt and synaptic)
then
aptitude update
aptitude dist-upgrade
and agree to the first solution offerred.You will then have a fully dist-upgraded antiX (to Mepis beta3) and you will be able to install kde apps.
Alternatively, after installing aptitude,
aptitude update
aptitude install libavahi-qt3-1
Oraptitude update
aptitude install libssp0
You will not need to use (I hope) aptitude again.Edit: It isn’t really a bug as such, but a feature to exclude kde 🙂
04 September 2007 antiX-M7-beta2 also now available from the MEPIS mirrors.
eg: download antiX-M7-beta2 here
For a list of changes from antiX-Spartacus and antiX-M7.
30 August 2007. antiX-M7-beta2 is available for testing.
This version has a few more applications installed, has been dist-upgraded to include all the recent changes in Debian Etch and Mepis7-beta2. A few extra wallpapers have been added and some files removed. antiX-M7-beta2 is 299MB.
At the moment get it from here: http://tomlinux.ca/testing using the following passwords.
user=antiXtester password=fluxbox
md5sum: f2b6466da0ac8ba17a4e282262074158
For those with antiX-M7-beta1.iso, you can use xdelta to add the patch_beta1-beta2.delta http://tomlinux.ca/testing/patch_beta1-beta2.delta It is 82MB.
Post comments, queries antiX forum on MepisLovers.
22 August 2007. antiX-M7-beta1 is available for testing.
This version is pretty rusty, has similar issues as Mepis7-beta1, but I’d like people to test it out and let me know what they think.
It is not yet available on the Mepis mirrors, I need some feedback before it gets uploaded.
antiX-M7-beta1 is about 280MB and is best installed to hard-disk, rather than used as a livecd (at the moment). Minimum 128MB RAM is recommended, though installed it should work well with 64MB RAM plus swap.
md5sum=5e38db8c554aa5f3171dfa930f8ac3c2 antiX-M7-beta1.iso
Edit: user=demo password=demo You cannot login as root! If you need to use root in a terminal, password=root
To exit from the login screen user=reboot password=root To shut down user=halt password=root
antiX-M7-beta1 is no longer available, antiX-M7-beta2 will be available for testing very soon.
03 August 2007. Work is starting on antiX-Mepis7. This will be based on MEPIS7 ie Debian Etch. Being based on the Debian repos will give developers and users much more flexibility.
09 July 2007. antiX goes final! With great pleasure, after a lot of hard work, I am pleased to announce that antiX final, code named Spartacus, is now available for download. (See link below and extra mirrors provided by MEPIS)
About antiX
antiX is a fast, lightweight and easy to install linux live CD distribution based on MEPIS for Intel-AMD x86 compatible systems. antiX offers users the “Magic of Mepis” in an environment suitable for old computers. So don’t throw away that old computer yet! 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. It should run on most computers, ranging from 64MB old PII 266 systems with pre-configured 128MB RAM to the latest powerful boxes. 128MB RAM is recommended for antiX. antiX can also be used as a fast-booting rescue cd.antiX-M7 will not run (yet) on older processors such as Pentium II (it seems that PII is ok), AMD K5, and AMD K6 as it uses an up to date i686 kernel. antiX-Spartacus should.
--
Brian MasinickWhat If I delete all these and keep only the following list
In that case, the snapshot operation would never reach completion.
Consider:
sys/*
proc/*
^——— these filepaths represent “virtual filesystems”, and their content (at least /sys/, I reckon) is generated dynamically, on-the-fly. Attempting to traverse and read the content of each subdirectory therein during snapshot operation will recursively (endlessly) generate further virtual subdirectories…home/snapshot/
^——— copies of any previously-generated ISO files output from snapshot operations reside here.
They are huge, and copies of ’em would needlessly be packed into the new snapshot ISO file.re: “# Do NOT edit this entry block unless you know what you are doing”
The pattern (filepath) conveyed within each line of the default excludes list(s) for a good, sound, reason.
Various reasons. The 3 most common are: inclusion would cause recursion; inclusion would render the resulting image unbootable; inclusion would needlessly bloat the size of the produced ISO (contents of /tmp/ for instance)var/cache/apt/archives/*.deb
Maybe you have only a few, or a cumulatively small set of, deb files onhand and _do_ wish to preserve them within the snapshot, in order to avoid re-downloading them? (Will be later booting the system on a machine without internet access, for instance, and those /archives/ debfiles are packages which you tried, then uninstalled on THIS system but did not delete because you expect you’ll want to have them onhand when performing customizations to the system, later, on another machine.)home/*/.cache/mozilla/firefox/*/thumbnails/*
home/*/.mozilla/firefox/*/Cache/*
Someone who has bandwidth-metered internet access may indeed wish to preserve copies of browser-cached files, but the DEFAULT represents the likelihood that one’s preference would be to “avoid needless bloat” (size of generated ISO, and time necessary to perform the snapshot operation ~~ compressing myriad extra files into it).etc/X11/xorg.conf.d/20-nvidia.conf
Need to consider: If on THIS machine you have installed a vendor-specific driver, and you neglect to exclude it from the snapshot…
later you would be unable to boot the snapshotted system on a machine containing an AMD graphics card, eh.In reply to: Bento Openbox antiX online!
melodie
Hi PPC,
first thanks very much for your feedback!
About the Applications menu button:
– the image is located in /usr/share/bento/lxpanel.
– The font used for this edition has for name “It wasn’t me”.
When you do a right-click on the applications button you can access to a menu “parameters of the menu”. And from there you can browse the files and choose another one: there is an image with just the cat head for example.
Also, you can create your own icon menu, using Gimp. Make a copy of the actuel menu image in a folder in your home, open it with Gimp, then use the “file create a new image” (choose transparent as an option) then you get a new image having the same size as the initial file, and you can work on a new version.
If you create a menu for portuguese and provide it to me, I can add it to the files in the system when rebuilding the next update (which is about to happen), or in the following one.
Applications near the Cat menu : you have to first install your language from the repos, (ie: using Synaptic package manager?) then if needed, do a right-click on one of the fast lauchers, open the first entry on the top of this right-click menu, and then remove and add whatever applications you want to the quick launchers near the applications menu.
Outdated icons : yes they are. I keep them for two reasons, there is a large choice of colors in this theme, it works a treat, and it is very complete, I don’t see icons missing in the menus. You have not tried that perhaps, but seeking for a new icon theme, installing theme, testing, takes looots of time.
On the other hand, if you want other sets, some are available in the repos, some are available at https://www.gnome-look.org, https://www.xfce-look.org, https://www.box-look.org, https://store.kde.org. Browser, download, install, test…
SpaceFM : just get it from the repos (ie : using Synaptic package manager).
The Bento Openbox editions are meant for end users, SpaceFM is a geek application, the simple users I know would not know how to use it. I don’t use it either, except when I boot a Parted Magic distribution ( https://partedmagic.com/) to detect things failing in a computer.
antiX:
“does not have the boot animation, displays the full text into (that may seem weird to some users)”
Package installer would be a great of easily build up the system to have almost anything most regular users could need…
boot animation uses computer resources, the intention with Bento antiX is to keep it as small and light on resource as possible. Some users will find it weird the first time, and the second time they will have gotten used to it (provided they get a good user experience during the session).
Package installer : I didn’t understand what you are talking about. Isn’t Synaptic not a tool good enough to install packages?
“You included some usefull scripts, but did not make them available in the menu, and also included scripts like Icewm Toolbar Icon Manager and fast menu editor that do nothing in your Desktop… ”
The scripts are small and don’t do harm to the size of the ISO, but so many launchers in the applications menu can confuse the simple end users. The more advanced antiX users who are used to them can easily restore them. I think all you have to do is dive into ~/.local/share/applications (hence, in your home) and remove the entry files (they contain an instruction to be kept hidden).
Icewm Toolbar Icon Manager : menu files for icewm, jwm and one more which originate from the official antiX edition will be removed in the next edition.
fast menu editor : which one are you talking about? Is it one for the lxpanel menu editor? Where is that? Or is it “obmenu” in the openbox right click menu on the desktop?
Next editions coming soon! Also I intend to remix a 64bits edition. Haven’t I seen one related to UEFI somewhere? Do you know if there is one?
Best regards,
Mélodie
macondo
HOWTO: Basic Ratpoison Configuration
This is a basic configuration, I haven’t learned all the tricks to it but i do
know what works for me smile.Ratpoison (rp) is not for everybody, eye-candy, icons, title/taskbar are absent. It’s
all business, uses every pixel of space and uses 1 MB of RAM. Apps are maximized
by default. If you spend time comparing desktops with your buddies to see which is
prettier, stop reading, this is not for you.Gamers, devs, and all sort of miscreants love rp.
#apt-get install ratpoison dmenuBIND KEY
The way it works is: you press a ‘bind’ key plus another letter you
assign to a package you want to launch.The default keybind (or bind key) is C-t (Control + letter t) but to me, it’s
cumbersome and painful on the wrist or fingers. If you google you’ll find tons
of material on ‘.ratpoisonrc’ or ‘ratpoison configuration’.Other examples of bind keys are: C-z, C-a, C-d …etc
I found this article by Dion Moult which explains how to change the bind key to
the Caps Lock (the key next to your left pinky finger). It’s a very good
article, you should read it. It explains how to make the Caps Lock key your bind
key.https://thinkmoult.com/ratpoison-an-efficient-and-minimalist-wm.html
IMHO, the easiest way to configure rp is from another wm/DE you’re using at the moment.
Create the file .xmodmaprc in your /home:
$ touch .xmodmaprcOnce created, enter it with favorite editor:
$ nano .xmodmaprc
And paste this:
remove lock = Caps_Lock keycode 66 = F13Put xmodmaprc in your .xinitrc:
$ nano .xinitrc
Paste this:
xmodmap .xmodmaprc
LAUNCHING RP
You can launch rp from your .xinitrc, here is mine:Example:
#!/bin/sh setxkbmap -option terminate:ctrl_alt_bksp xsetroot -solid black xrdb -merge .Xdefaults unclutter -idle 2 & numlockx & xmodmap .xmodmaprc exec ratpoisonsave/exit/reboot
CONFIGURATION FILE
It’s called .ratpoisonrc, so you create it:$ touch .ratpoisonrcThen you enter it:
$ nano .ratpoisonrc
You’ll notice is blank, then paste and post something like this:
Here’s my .ratpoisonrc:alias term exec lxterminal escape F13 unbind k bind j focusdown bind h focusleft bind k focusup bind l focusright bind J exchangedown bind H exchangeleft bind K exchangeup bind L exchangeright exec /usr/bin/rpws init 2 -k exec rpws 1 exec /usr/bin/rpws init 6 -k bind F1 exec rpws 1 bind F2 exec rpws 2 exec xsetroot -solid black -cursor_name left_ptr bind semicolon colon set winname class set fgcolor yellow set bgcolor black set bargravity sw defborder 0 defpadding 0 0 0 0 defbarpadding 0 0 definekey top M-Tab next bind space exec lxterminal definekey top F2 exec xfe bind f exec firefox bind b exec brave-browser-stable definekey top F4 kill definekey top F7 exec mirage definekey top F8 exec hexchat definekey top F9 exec geany definekey top Print exec lxterminal -e scrot -cd 10 SOUND definekey top C-Down exec amixer -q set Master 5- unmute && ratpoison -c "echo Master Vol Down" definekey top C-Up exec amixer -q set Master 5+ unmute && ratpoison -c "echo Master Vol Up" bind d exec dmenu_run bind r restart bind w windows bind Escape abort bind q only bind b banish rudeness 12 #Run box (sudo and apps launching) definekey top C-space execsave/exit/reboot
—
HOW DOES IT WORK?To launch a terminal: press bind key (caps lock) and the spacebar, a white small square will
appear , and the xterm (or whatever terminal you
specify in .ratpoisonrc) will appear. Ditto for all the other apps.You want to abort in the middle of an operation? Bind key + Escape.
Close an app? F4
Want to know what windows you got open? bind + w
Want to go to one of them? bind + the window #
Want to launch dmenu? bind + d
After every change ‘restart rp’ with: bind + r
What time/date is it? bind + a
Snapshot? press the key Print.
You miss fbrun? Control key + Space bar
If you want to split the screen horizontally: bind + s
Vertically? Bind + S
Go back to normal? Bind + q
alt-tab as usual OR tap the bind key twicePlay with it, it’s addictive.
Happy trails,
macondoPS: Contrary to common wisdom, you CAN use your mouse as in any other wm.
- This topic was modified 2 years, 9 months ago by macondo.
- This topic was modified 2 years, 9 months ago by macondo.
antiX Core 64 Bit Runit IceWM
"Sometimes a man finds his destiny on the road he took to avoid it."
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
