-
Search Results
-
In reply to: Looking for Linux for test labtop
melodie
You can test hardware very easily with the Linux distributions. antiX is also wonderful because easy to use out of the box, light and provides the application having for name “Snapshot” which allows you to rebuild your own version.
In order to put up a USB stick you can install Ventoy on a usb stick then add iso images of live distributions. https://ventoy.net is quite easy to get the hang on it, and antiX is among the distributions known to boot from it.
What you might want to do is do one post per question, and solve one question at a time, to ease the learning curve. This is how I started, almost 20 years ago (once I passed the period of overwhelming and someone told me I needed to take it one problem at a time).
Then you will be able to diagnostic hardware using free software, to know what the best course of action is with a given machine, know which distribution will fit it best, how to help users, how to teach them how to use their computer with a Linux distribution and how to maintain it.Â
Linux in pictures:
http://www.delafond.org/roman_photos/index_en.htmlđ
In reply to: comment installer antix/bento
melodie
Comme dâhabitude vous tourner autour du pot
Bonjour @Jibelit.
Je vous invite Ă modĂ©rer vos propos et Ă user de respect envers moi-mĂȘme et autrui en gĂ©nĂ©ral. Personne ne vous doit rien. Comme quelqu’un d’autre sur ce forum vous l’a dit, nous contribuons bĂ©nĂ©volement, donc gratuitement.
mais Melodie je me suis trompé sur
Vous avez voulu Ă©changer avec moi par mail, et j’ai pris sur mon temps personnel pour vous rĂ©pondre en privĂ©. (Je me demande encore pourquoi). Je vous ai demandĂ© *dĂšs ma premiĂšre rĂ©ponse* de me donner prĂ©cisĂ©ment le nom du fichier que vous avez employĂ© pour l’installation : j’attends encore !
et comment faire lâinstallation de Bento antiX full sauf avec cet ennui des respins pour que cette version soit installĂ© correctement et en plus avec la perte de mes 3 OSs installĂ©s dans ce disque dur de 1 To de ma tour MĂ©dion !
Vous avez peut-ĂȘtre l’habitude de blĂąmer les autres pour vos erreurs ? On n’installe pas une distribution qu’on ne connaĂźt pas sur la machine principale. On utilise Virtualbox !
Cherchez une documentation à propos de Virtualbox et dorénavant faites vos tests en machine virtuelle au lieu de mettre la faute de vos erreurs sur les autres.
Jâai du refaire en entier les partitions avec gparted et Boot-repair pour de nouveau installer Bento openbox et Studio-ubuntu
MĂȘme rĂ©ponse que ci-dessus : faites vos tests en machine virtuelle.
Les screenshot que jâai joint concerne lâinstalle de Bento openbox qui a Ă©tĂ© rĂ©ussieâŠJe ne joue pas sur les mots ni avec ce qui sâensuitâŠ( ce qui bien sur nâa rien a voir avec lâĂ©chec de bento antiX)
Jâai dans ce site eu trois rĂ©ponses des membres MoDDIt , Wallon et anticapilista tous on imaginĂ©s que je jetais un trouble de savoir comment installer la Bento Antix plus vos rĂ©ponses, OUI mais en M.P.Quand vous commencerez par parler poliment et Ă poser des questions claires, cela Ă©vitera de douter de vos intentions et permettra de comprendre oĂč sont vos blocages.
Je nâai toujours pas de rĂ©ponse positives pour faire cette installation de bento antiX ?? lors du test faut-il taper âdemoâ ou ârootâ pour tenter cette installe? mystĂšre âŠ
Je viens de refaire une installation en machine virtuelle de bento-antiX-full-x86_64-full-20220122.iso et je n’ai eu besoin d’aucun mot de passe.
je nâai pas encore de rĂ©ponses positives! A la rĂ©ponse de MoDDIt il mâa expliquĂ© ceci :
âAllez-y doucement, lâinstallateur dâantiX est quelque peu diffĂ©rent de beaucoup dâautresâ
Jâai Ă©tĂ© surpris, bien sur et câest normal !Il existe de nombreuses familles de distributions et elles ont toutes leurs particularitĂ©s, mĂȘme si l’arborescence des rĂ©pertoires et les droits et permissions sur les fichiers utilisent des stratĂ©gies identiques. Vous ne devriez pas *jouer* avec votre ordinateur principal.
Pour la 3Úme fois dans ce post je vous le répÚte : utilisez Virtualbox !!!
Tant que je ne saurais pas comment rĂ©aliser une installe correcte de Bento-AntiX qui a Ă©tĂ© crĂ©Ă© par vous et dâautres membres de ce site dâAntix, est-ce que ça me gĂȘne dâavoir de telles diffĂ©rences entre tel ou tel O.S libres..Je rĂ©ponds oui âŠ
La distribution s’Ă©crit antiX avec le X en majuscule et le a en minuscule. Si le fondateur et la communautĂ© ici ont dĂ©cidĂ© que son nom s’Ă©crit ainsi, Ă©crivez-le ainsi. C’est une question de respect.
Et quand vous aurez compris comment l’installer vous pourrez Ă votre tour la reconstruire, grĂące au programme “Snapshot” qui est dans les menus. (Je dis ça comme ça⊠)
Votre post fait dans le forum ubuntu fr a Ă©tĂ© pour moi intĂ©ressant a cause du terme âbentoâcar je connais de mot japonais qui en fait est un boitier et son couvercle sert dâavoir dans chaque petit compartiment de la nourriture nipponne⊠qui peut ĂȘtre fait et prĂ©parĂ© soit chez soi soit dans un magasin Japonais a Paris ou ailleurs .. Je suis depuis 47 ans macrobiotique qui bien sur nâa rien a voir avec les OSs libres, quoique ??
Ce nom de code est la contribution d’un utilisateur : openbox est le gestionnaire de fenĂȘtres utilisĂ©, un bento est un plateau dĂ©jeuner dans lequel on ne met que de bonnes choses et qui est composĂ© comme on le souhaite.
Cela fait de cet environnement openbox un systĂšme qui est facile Ă personnaliser.
Je n’ai pas le temps d’Ă©crire une documentation complĂšte pour l’instant et ça risque de prendre encore du temps.
Par contre en ayant fait Ă l’instant une installation en machine virtuelle, et Virtualbox permettant de prendre des captures d’Ă©crans au fil des actions, j’ai fait des captures d’Ă©crans Ă partir du dĂ©but de l’installation sur un volume virtuel que j’ai scindĂ© en plusieurs partitions dans une partition Ă©tendue un peu comme ce que vous avez montrĂ© dans vos photos.
Vous les trouverez ici :
https://linuxvillage.org/Downloads/Captures/et vous pouvez télécharger tout le dossier avec cette archive zippée:
https://linuxvillage.org/Downloads/Captures.zipVous verrez alors que vous pouvez lancer Gparted directement depuis l’installeur une fois que vous ĂȘtes sur la fenĂȘtre du partitionnement personnalisĂ©.
Si avec ça vous n’y arrivez pas, (en machine virtuelle !!!) alors j’abandonne.
In reply to: (bug ?) the kernel symlinks don't update
Brian Masinick
BTW a fresh antiX-21 iso (full, base, core and net), uses the *new* way â no need for usrmerge.
Same with the antiX-21 sid isos.If upgrading from antiX-19 (or earlier) to antiX-21, DO NOT use usrmerge. It will break your install.
GOOD tip!
I was running antiX 21 on a system that is probably more than ten years old, but the software is something I’ve installed in the past couple of months. I dusted off the system that was in the corner, plugged it in, booted it up, updated the software and it ran well – maybe not as FAST as this current generation laptop, which is currently using EndeavourOS, but once logged in and actually doing stuff on the Web, you’d barely notice the difference; only time I could tell was when I’d invoke a new image; yeah, then the old computer was slower, but not at all unusable on antiX 21; it was a pleasant experience!
--
Brian MasinickBrian Masinick
From an Email I received early this afternoon:
Laura Arjona Reina
To:debian-announce@lists.debian.org————————————————————————
The Debian Project https://www.debian.org/
Updated Debian 11: 11.3 released press@debian.org
March 26th, 2022 https://www.debian.org/News/2022/20220326
————————————————————————The Debian project is pleased to announce the third update of its stable
distribution Debian 11 (codename “bullseye”). 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.Please note that the point release does not constitute a new version of
Debian 11 but only updates some of the packages included. There is no
need to throw away old “bullseye” 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 |
+————————–+——————————————+
| apache-log4j1.2 [1] | Resolve security issues [CVE-2021-4104 |
| | CVE-2022-23302 CVE-2022-23305 CVE-2022- |
| | 23307], by removing support for the |
| | JMSSink, JDBCAppender, JMSAppender and |
| | Apache Chainsaw modules |
| | |
| apache-log4j2 [2] | Fix remote code execution issue |
| | [CVE-2021-44832] |
| | |
| apache2 [3] | New upstream release; fix crash due to |
| | random memory read [CVE-2022-22719]; fix |
| | HTTP request smuggling issue [CVE-2022- |
| | 22720]; fix out-of-bounds write issues |
| | [CVE-2022-22721 CVE-2022-23943] |
| | |
| atftp [4] | Fix information leak issue [CVE-2021- |
| | 46671] |
| | |
| base-files [5] | Update for the 11.3 point release |
| | |
| bible-kjv [6] | Fix off-by-one-error in search |
| | |
| chrony [7] | Allow reading the chronyd configuration |
| | file that timemaster(8) generates |
| | |
| cinnamon [8] | Fix crash when adding an online account |
| | with login |
| | |
| clamav [9] | New upstream stable release; fix denial |
| | of service issue [CVE-2022-20698] |
| | |
| cups-filters [10] | Apparmor: allow reading from Debian |
| | Edu’s cups-browsed configuration file |
| | |
| dask.distributed [11] | Fix undesired listening of workers on |
| | public interfaces [CVE-2021-42343]; fix |
| | compatibility with Python 3.9 |
| | |
| debian-installer [12] | Rebuild against proposed-updates; update |
| | Linux kernel ABI to 5.10.0-13 |
| | |
| debian-installer- | Rebuild against proposed-updates |
| netboot-images [13] | |
| | |
| debian-ports-archive- | Add “Debian Ports Archive Automatic |
| keyring [14] | Signing Key (2023)” ; move the |
| | 2021 signing key to the removed keyring |
| | |
| django-allauth [15] | Fix OpenID support |
| | |
| djbdns [16] | Raise the axfrdns, dnscache, and tinydns |
| | data limit |
| | |
| dpdk [17] | New upstream stable release |
| | |
| e2guardian [18] | Fix missing SSL certificate validation |
| | issue [CVE-2021-44273] |
| | |
| epiphany-browser [19] | Work around a bug in GLib, fixing a UI |
| | process crash |
| | |
| espeak-ng [20] | Drop spurious 50ms delay while |
| | processing events |
| | |
| espeakup [21] | debian/espeakup.service: Protect |
| | espeakup from system overloads |
| | |
| fcitx5-chinese- | fcitx5-table: add missing dependencies |
| addons [22] | on fcitx5-module-pinyinhelper and |
| | fcitx5-module-punctuation |
| | |
| flac [23] | Fix out-of-bounds write issue [CVE-2021- |
| | 0561] |
| | |
| freerdp2 [24] | Disable additional debug logging |
| | |
| galera-3 [25] | New upstream release |
| | |
| galera-4 [26] | New upstream release |
| | |
| gbonds [27] | Use Treasury API for redemption data |
| | |
| glewlwyd [28] | Fix possible privilege escalation |
| | |
| glibc [29] | Fix bad conversion from ISO-2022-JP-3 |
| | with iconv [CVE-2021-43396]; fix buffer |
| | overflow issues [CVE-2022-23218 |
| | CVE-2022-23219]; fix use-after-free |
| | issue [CVE-2021-33574]; stop replacing |
| | older versions of /etc/nsswitch.conf; |
| | simplify the check for supported kernel |
| | versions, as 2.x kernels are no longer |
| | supported; support installation on |
| | kernels with a release number greater |
| | than 255 |
| | |
| glx-alternatives [30] | After initial setup of the diversions, |
| | install a minimal alternative to the |
| | diverted files so that libraries are not |
| | missing until glx-alternative-mesa |
| | processes its triggers |
| | |
| gnupg2 [31] | scd: Fix CCID driver for SCM SPR332/ |
| | SPR532; avoid network interaction in |
| | generator, which can lead to hangs |
| | |
| gnuplot [32] | Fix division by zero [CVE-2021-44917] |
| | |
| golang-1.15 [33] | Fix IsOnCurve for big.Int values that |
| | are not valid coordinates [CVE-2022- |
| | 23806]; math/big: prevent large memory |
| | consumption in Rat.SetString [CVE-2022- |
| | 23772]; cmd/go: prevent branches from |
| | materializing into versions [CVE-2022- |
| | 23773]; fix stack exhaustion compiling |
| | deeply nested expressions [CVE-2022- |
| | 24921] |
| | |
| golang-github- | Update seccomp support to enable use of |
| containers-common [34] | newer kernel versions |
| | |
| golang-github- | Update seccomp support to enable use of |
| opencontainers- | newer kernel versions |
| specs [35] | |
| | |
| gtk+3.0 [36] | Fix missing search results when using |
| | NFS; prevent Wayland clipboard handling |
| | from locking up in certain corner cases; |
| | improve printing to mDNS-discovered |
| | printers |
| | |
| heartbeat [37] | Fix creation of /run/heartbeat on |
| | systems using systemd |
| | |
| htmldoc [38] | Fix out-of-bounds read issue [CVE-2022- |
| | 0534] |
| | |
| installation-guide [39] | Update documentation and translations |
| | |
| intel-microcode [40] | Update included microcode; mitigate some |
| | security issues [CVE-2020-8694 CVE-2020- |
| | 8695 CVE-2021-0127 CVE-2021-0145 |
| | CVE-2021-0146 CVE-2021-33120] |
| | |
| ldap2zone [41] | Use “mktemp” rather than the |
| | deprecated “tempfile” , avoiding |
| | warnings |
| | |
| lemonldap-ng [42] | Fix auth process in password-testing |
| | plugins [CVE-2021-40874] |
| | |
| libarchive [43] | Fix extracting hardlinks to symlinks; |
| | fix handling of symlink ACLs [CVE-2021- |
| | 23177]; never follow symlinks when |
| | setting file flags [CVE-2021-31566] |
| | |
| libdatetime-timezone- | Update included data |
| perl [44] | |
| | |
| libgdal-grass [45] | Rebuild against grass 7.8.5-1+deb11u1 |
| | |
| libpod [46] | Update seccomp support to enable use of |
| | newer kernel versions |
| | |
| libxml2 [47] | Fix use-after-free issue [CVE-2022- |
| | 23308] |
| | |
| linux [48] | New upstream stable release; [rt] Update |
| | to 5.10.106-rt64; increase ABI to 13 |
| | |
| linux-signed-amd64 [49] | New upstream stable release; [rt] Update |
| | to 5.10.106-rt64; increase ABI to 13 |
| | |
| linux-signed-arm64 [50] | New upstream stable release; [rt] Update |
| | to 5.10.106-rt64; increase ABI to 13 |
| | |
| linux-signed-i386 [51] | New upstream stable release; [rt] Update |
| | to 5.10.106-rt64; increase ABI to 13 |
| | |
| mariadb-10.5 [52] | New upstream release; security fixes |
| | [CVE-2021-35604 CVE-2021-46659 CVE-2021- |
| | 46661 CVE-2021-46662 CVE-2021-46663 |
| | CVE-2021-46664 CVE-2021-46665 CVE-2021- |
| | 46667 CVE-2021-46668 CVE-2022-24048 |
| | CVE-2022-24050 CVE-2022-24051 CVE-2022- |
| | 24052] |
| | |
| mpich [53] | Add Breaks: on older versions of |
| | libmpich1.0-dev, resolving some upgrade |
| | issues |
| | |
| mujs [54] | Fix buffer overflow issue [CVE-2021- |
| | 45005] |
| | |
| mutter [55] | Backport various fixes from upstream’s |
| | stable branch |
| | |
| node-cached-path- | Fix prototype pollution issue [CVE-2021- |
| relative [56] | 23518] |
| | |
| node-fetch [57] | Don’t forward secure headers to third |
| | party domains [CVE-2022-0235] |
| | |
| node-follow- | Don’t send Cookie header across domains |
| redirects [58] | [CVE-2022-0155]; don’t send confidential |
| | headers across schemes [CVE-2022-0536] |
| | |
| node-markdown-it [59] | Fix regular expression-based denial of |
| | service issue [CVE-2022-21670] |
| | |
| node-nth-check [60] | Fix regular expression-based denial of |
| | service issue [CVE-2021-3803] |
| | |
| node-prismjs [61] | Escape markup in command line output |
| | [CVE-2022-23647]; update minified files |
| | to ensure that Regular Expression Denial |
| | of Service issue is resolved [CVE-2021- |
| | 3801] |
| | |
| node-trim-newlines [62] | Fix regular expression-based denial of |
| | service issue [CVE-2021-33623] |
| | |
| nvidia-cuda-toolkit [63] | cuda-gdb: Disable non-functional python |
| | support causing segmentation faults; use |
| | a snapshot of openjdk-8-jre (8u312-b07- |
| | 1) |
| | |
| nvidia-graphics-drivers- | New upstream release; fix denial of |
| tesla-450 [64] | service issues [CVE-2022-21813 CVE-2022- |
| | 21814]; nvidia-kernel-support: Provide / |
| | etc/modprobe.d/nvidia-options.conf as a |
| | template |
| | |
| nvidia-modprobe [65] | New upstream release |
| | |
| openboard [66] | Fix application icon |
| | |
| openssl [67] | New upstream release; fix armv8 pointer |
| | authentication |
| | |
| openvswitch [68] | Fix use-after-free issue [CVE-2021- |
| | 36980]; fix installation of libofproto |
| | |
| ostree [69] | Fix compatibility with eCryptFS; avoid |
| | infinite recursion when recovering from |
| | certain errors; mark commits as partial |
| | before downloading; fix an assertion |
| | failure when using a backport or local |
| | build of GLib >= 2.71; fix the ability |
| | to fetch OSTree content from paths |
| | containing non-URI characters (such as |
| | backslashes) or non-ASCII |
| | |
| pdb2pqr [70] | Fix compatibility of propka with Python |
| | 3.8 or above |
| | |
| php-crypt-gpg [71] | Prevent additional options being passed |
| | to GPG [CVE-2022-24953] |
| | |
| php-laravel- | Fix cross-site scripting issue |
| framework [72] | [CVE-2021-43808], missing blocking of |
| | executable content upload [CVE-2021- |
| | 43617] |
| | |
| phpliteadmin [73] | Fix cross-site scripting issue |
| | [CVE-2021-46709] |
| | |
| prips [74] | Fix infinite wrapping if a range reaches |
| | 255.255.255.255; fix CIDR output with |
| | addresses that differ in their first bit |
| | |
| pypy3 [75] | Fix build failures by removing |
| | extraneous #endif from import.h |
| | |
| python-django [76] | Fix denial of service issue [CVE-2021- |
| | 45115], information disclosure issue |
| | [CVE-2021-45116], directory traversal |
| | issue [CVE-2021-45452]; fix a traceback |
| | around the handling of RequestSite/ |
| | get_current_site() due to a circular |
| | import |
| | |
| python-pip [77] | Avoid a race-condition when using zip- |
| | imported dependencies |
| | |
| rust-cbindgen [78] | New upstream stable release to support |
| | builds of newer firefox-esr and |
| | thunderbird versions |
| | |
| s390-dasd [79] | Stop passing deprecated -f option to |
| | dasdfmt |
| | |
| schleuder [80] | Migrate boolean values to integers, if |
| | the ActiveRecord SQLite3 connection |
| | adapter is in use, restoring |
| | functionality |
| | |
| sphinx-bootstrap- | Fix search functionality |
| theme [81] | |
| | |
| spip [82] | Fix several cross-site scripting issues |
| | |
| symfony [83] | Fix CVE injection issue [CVE-2021-41270] |
| | |
| systemd [84] | Fix uncontrolled recursion in systemd- |
| | tmpfiles [CVE-2021-3997]; demote |
| | systemd-timesyncd from Depends to |
| | Recommends, removing a dependency cycle; |
| | fix failure to bind mount a directory |
| | into a container using machinectl; fix |
| | regression in udev resulting in long |
| | delays when processing partitions with |
| | the same label; fix a regression when |
| | using systemd-networkd in an |
| | unprivileged LXD container |
| | |
| sysvinit [85] | Fix parsing of “shutdown +0” ; clarify |
| | that when called with a “time” |
| | shutdown will not exit |
| | |
| tasksel [86] | Install CUPS for all *-desktop tasks, as |
| | task-print-service no longer exists |
| | |
| usb.ids [87] | Update included data |
| | |
| weechat [88] | Fix denial of service issue [CVE-2021- |
| | 40516] |
| | |
| wolfssl [89] | Fix several issues related to OCSP- |
| | handling [CVE-2021-3336 CVE-2021-37155 |
| | CVE-2021-38597] and TLS1.3 support |
| | [CVE-2021-44718 CVE-2022-25638 CVE-2022- |
| | 25640] |
| | |
| xserver-xorg-video- | Fix SIGILL crash on non-SSE2 CPUs |
| intel [90] | |
| | |
| xterm [91] | Fix buffer overflow issue [CVE-2022- |
| | 24130] |
| | |
| zziplib [92] | Fix denial of service issue [CVE-2020- |
| | 18442] |
| | |
+————————–+——————————————+1: https://packages.debian.org/src:apache-log4j1.2
2: https://packages.debian.org/src:apache-log4j2
3: https://packages.debian.org/src:apache2
4: https://packages.debian.org/src:atftp
5: https://packages.debian.org/src:base-files
6: https://packages.debian.org/src:bible-kjv
7: https://packages.debian.org/src:chrony
8: https://packages.debian.org/src:cinnamon
9: https://packages.debian.org/src:clamav
10: https://packages.debian.org/src:cups-filters
11: https://packages.debian.org/src:dask.distributed
12: https://packages.debian.org/src:debian-installer
13: https://packages.debian.org/src:debian-installer-netboot-images
14: https://packages.debian.org/src:debian-ports-archive-keyring
15: https://packages.debian.org/src:django-allauth
16: https://packages.debian.org/src:djbdns
17: https://packages.debian.org/src:dpdk
18: https://packages.debian.org/src:e2guardian
19: https://packages.debian.org/src:epiphany-browser
20: https://packages.debian.org/src:espeak-ng
21: https://packages.debian.org/src:espeakup
22: https://packages.debian.org/src:fcitx5-chinese-addons
23: https://packages.debian.org/src:flac
24: https://packages.debian.org/src:freerdp2
25: https://packages.debian.org/src:galera-3
26: https://packages.debian.org/src:galera-4
27: https://packages.debian.org/src:gbonds
28: https://packages.debian.org/src:glewlwyd
29: https://packages.debian.org/src:glibc
30: https://packages.debian.org/src:glx-alternatives
31: https://packages.debian.org/src:gnupg2
32: https://packages.debian.org/src:gnuplot
33: https://packages.debian.org/src:golang-1.15
34: https://packages.debian.org/src:golang-github-containers-common
35: https://packages.debian.org/src:golang-github-opencontainers-specs
36: https://packages.debian.org/src:gtk+3.0
37: https://packages.debian.org/src:heartbeat
38: https://packages.debian.org/src:htmldoc
39: https://packages.debian.org/src:installation-guide
40: https://packages.debian.org/src:intel-microcode
41: https://packages.debian.org/src:ldap2zone
42: https://packages.debian.org/src:lemonldap-ng
43: https://packages.debian.org/src:libarchive
44: https://packages.debian.org/src:libdatetime-timezone-perl
45: https://packages.debian.org/src:libgdal-grass
46: https://packages.debian.org/src:libpod
47: https://packages.debian.org/src:libxml2
48: https://packages.debian.org/src:linux
49: https://packages.debian.org/src:linux-signed-amd64
50: https://packages.debian.org/src:linux-signed-arm64
51: https://packages.debian.org/src:linux-signed-i386
52: https://packages.debian.org/src:mariadb-10.5
53: https://packages.debian.org/src:mpich
54: https://packages.debian.org/src:mujs
55: https://packages.debian.org/src:mutter
56: https://packages.debian.org/src:node-cached-path-relative
57: https://packages.debian.org/src:node-fetch
58: https://packages.debian.org/src:node-follow-redirects
59: https://packages.debian.org/src:node-markdown-it
60: https://packages.debian.org/src:node-nth-check
61: https://packages.debian.org/src:node-prismjs
62: https://packages.debian.org/src:node-trim-newlines
63: https://packages.debian.org/src:nvidia-cuda-toolkit
64: https://packages.debian.org/src:nvidia-graphics-drivers-tesla-450
65: https://packages.debian.org/src:nvidia-modprobe
66: https://packages.debian.org/src:openboard
67: https://packages.debian.org/src:openssl
68: https://packages.debian.org/src:openvswitch
69: https://packages.debian.org/src:ostree
70: https://packages.debian.org/src:pdb2pqr
71: https://packages.debian.org/src:php-crypt-gpg
72: https://packages.debian.org/src:php-laravel-framework
73: https://packages.debian.org/src:phpliteadmin
74: https://packages.debian.org/src:prips
75: https://packages.debian.org/src:pypy3
76: https://packages.debian.org/src:python-django
77: https://packages.debian.org/src:python-pip
78: https://packages.debian.org/src:rust-cbindgen
79: https://packages.debian.org/src:s390-dasd
80: https://packages.debian.org/src:schleuder
81: https://packages.debian.org/src:sphinx-bootstrap-theme
82: https://packages.debian.org/src:spip
83: https://packages.debian.org/src:symfony
84: https://packages.debian.org/src:systemd
85: https://packages.debian.org/src:sysvinit
86: https://packages.debian.org/src:tasksel
87: https://packages.debian.org/src:usb.ids
88: https://packages.debian.org/src:weechat
89: https://packages.debian.org/src:wolfssl
90: https://packages.debian.org/src:xserver-xorg-video-intel
91: https://packages.debian.org/src:xterm
92: https://packages.debian.org/src:zziplibSecurity 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-5000 [93] | openjdk-11 [94] |
| | |
| DSA-5001 [95] | redis [96] |
| | |
| DSA-5012 [97] | openjdk-17 [98] |
| | |
| DSA-5021 [99] | mediawiki [100] |
| | |
| DSA-5023 [101] | modsecurity-apache [102] |
| | |
| DSA-5024 [103] | apache-log4j2 [104] |
| | |
| DSA-5025 [105] | tang [106] |
| | |
| DSA-5027 [107] | xorg-server [108] |
| | |
| DSA-5028 [109] | spip [110] |
| | |
| DSA-5029 [111] | sogo [112] |
| | |
| DSA-5030 [113] | webkit2gtk [114] |
| | |
| DSA-5031 [115] | wpewebkit [116] |
| | |
| DSA-5033 [117] | fort-validator [118] |
| | |
| DSA-5035 [119] | apache2 [120] |
| | |
| DSA-5037 [121] | roundcube [122] |
| | |
| DSA-5038 [123] | ghostscript [124] |
| | |
| DSA-5039 [125] | wordpress [126] |
| | |
| DSA-5040 [127] | lighttpd [128] |
| | |
| DSA-5041 [129] | cfrpki [130] |
| | |
| DSA-5042 [131] | epiphany-browser [132] |
| | |
| DSA-5043 [133] | lxml [134] |
| | |
| DSA-5046 [135] | chromium [136] |
| | |
| DSA-5047 [137] | prosody [138] |
| | |
| DSA-5048 [139] | libreswan [140] |
| | |
| DSA-5049 [141] | flatpak-builder [142] |
| | |
| DSA-5049 [143] | flatpak [144] |
| | |
| DSA-5050 [145] | linux-signed-amd64 [146] |
| | |
| DSA-5050 [147] | linux-signed-arm64 [148] |
| | |
| DSA-5050 [149] | linux-signed-i386 [150] |
| | |
| DSA-5050 [151] | linux [152] |
| | |
| DSA-5051 [153] | aide [154] |
| | |
| DSA-5052 [155] | usbview [156] |
| | |
| DSA-5053 [157] | pillow [158] |
| | |
| DSA-5054 [159] | chromium [160] |
| | |
| DSA-5055 [161] | util-linux [162] |
| | |
| DSA-5056 [163] | strongswan [164] |
| | |
| DSA-5057 [165] | openjdk-11 [166] |
| | |
| DSA-5058 [167] | openjdk-17 [168] |
| | |
| DSA-5059 [169] | policykit-1 [170] |
| | |
| DSA-5060 [171] | webkit2gtk [172] |
| | |
| DSA-5061 [173] | wpewebkit [174] |
| | |
| DSA-5062 [175] | nss [176] |
| | |
| DSA-5063 [177] | uriparser [178] |
| | |
| DSA-5064 [179] | python-nbxmpp [180] |
| | |
| DSA-5065 [181] | ipython [182] |
| | |
| DSA-5067 [183] | ruby2.7 [184] |
| | |
| DSA-5068 [185] | chromium [186] |
| | |
| DSA-5070 [187] | cryptsetup [188] |
| | |
| DSA-5071 [189] | samba [190] |
| | |
| DSA-5072 [191] | debian-edu-config [192] |
| | |
| DSA-5073 [193] | expat [194] |
| | |
| DSA-5075 [195] | minetest [196] |
| | |
| DSA-5076 [197] | h2database [198] |
| | |
| DSA-5077 [199] | librecad [200] |
| | |
| DSA-5078 [201] | zsh [202] |
| | |
| DSA-5079 [203] | chromium [204] |
| | |
| DSA-5080 [205] | snapd [206] |
| | |
| DSA-5081 [207] | redis [208] |
| | |
| DSA-5082 [209] | php7.4 [210] |
| | |
| DSA-5083 [211] | webkit2gtk [212] |
| | |
| DSA-5084 [213] | wpewebkit [214] |
| | |
| DSA-5085 [215] | expat [216] |
| | |
| DSA-5087 [217] | cyrus-sasl2 [218] |
| | |
| DSA-5088 [219] | varnish [220] |
| | |
| DSA-5089 [221] | chromium [222] |
| | |
| DSA-5091 [223] | containerd [224] |
| | |
| DSA-5092 [225] | linux-signed-amd64 [226] |
| | |
| DSA-5092 [227] | linux-signed-arm64 [228] |
| | |
| DSA-5092 [229] | linux-signed-i386 [230] |
| | |
| DSA-5092 [231] | linux [232] |
| | |
| DSA-5093 [233] | spip [234] |
| | |
| DSA-5095 [235] | linux-signed-amd64 [236] |
| | |
| DSA-5095 [237] | linux-signed-arm64 [238] |
| | |
| DSA-5095 [239] | linux-signed-i386 [240] |
| | |
| DSA-5095 [241] | linux [242] |
| | |
| DSA-5098 [243] | tryton-server [244] |
| | |
| DSA-5099 [245] | tryton-proteus [246] |
| | |
| DSA-5100 [247] | nbd [248] |
| | |
| DSA-5101 [249] | libphp-adodb [250] |
| | |
| DSA-5102 [251] | haproxy [252] |
| | |
| DSA-5103 [253] | openssl [254] |
| | |
| DSA-5104 [255] | chromium [256] |
| | |
| DSA-5105 [257] | bind9 [258] |
| | |
+—————-+————————–+93: https://www.debian.org/security/2021/dsa-5000
94: https://packages.debian.org/src:openjdk-11
95: https://www.debian.org/security/2021/dsa-5001
96: https://packages.debian.org/src:redis
97: https://www.debian.org/security/2021/dsa-5012
98: https://packages.debian.org/src:openjdk-17
99: https://www.debian.org/security/2021/dsa-5021
100: https://packages.debian.org/src:mediawiki
101: https://www.debian.org/security/2021/dsa-5023
102: https://packages.debian.org/src:modsecurity-apache
103: https://www.debian.org/security/2021/dsa-5024
104: https://packages.debian.org/src:apache-log4j2
105: https://www.debian.org/security/2021/dsa-5025
106: https://packages.debian.org/src:tang
107: https://www.debian.org/security/2021/dsa-5027
108: https://packages.debian.org/src:xorg-server
109: https://www.debian.org/security/2021/dsa-5028
110: https://packages.debian.org/src:spip
111: https://www.debian.org/security/2021/dsa-5029
112: https://packages.debian.org/src:sogo
113: https://www.debian.org/security/2021/dsa-5030
114: https://packages.debian.org/src:webkit2gtk
115: https://www.debian.org/security/2021/dsa-5031
116: https://packages.debian.org/src:wpewebkit
117: https://www.debian.org/security/2021/dsa-5033
118: https://packages.debian.org/src:fort-validator
119: https://www.debian.org/security/2022/dsa-5035
120: https://packages.debian.org/src:apache2
121: https://www.debian.org/security/2022/dsa-5037
122: https://packages.debian.org/src:roundcube
123: https://www.debian.org/security/2022/dsa-5038
124: https://packages.debian.org/src:ghostscript
125: https://www.debian.org/security/2022/dsa-5039
126: https://packages.debian.org/src:wordpress
127: https://www.debian.org/security/2022/dsa-5040
128: https://packages.debian.org/src:lighttpd
129: https://www.debian.org/security/2022/dsa-5041
130: https://packages.debian.org/src:cfrpki
131: https://www.debian.org/security/2022/dsa-5042
132: https://packages.debian.org/src:epiphany-browser
133: https://www.debian.org/security/2022/dsa-5043
134: https://packages.debian.org/src:lxml
135: https://www.debian.org/security/2022/dsa-5046
136: https://packages.debian.org/src:chromium
137: https://www.debian.org/security/2022/dsa-5047
138: https://packages.debian.org/src:prosody
139: https://www.debian.org/security/2022/dsa-5048
140: https://packages.debian.org/src:libreswan
141: https://www.debian.org/security/2022/dsa-5049
142: https://packages.debian.org/src:flatpak-builder
143: https://www.debian.org/security/2022/dsa-5049
144: https://packages.debian.org/src:flatpak
145: https://www.debian.org/security/2022/dsa-5050
146: https://packages.debian.org/src:linux-signed-amd64
147: https://www.debian.org/security/2022/dsa-5050
148: https://packages.debian.org/src:linux-signed-arm64
149: https://www.debian.org/security/2022/dsa-5050
150: https://packages.debian.org/src:linux-signed-i386
151: https://www.debian.org/security/2022/dsa-5050
152: https://packages.debian.org/src:linux
153: https://www.debian.org/security/2022/dsa-5051
154: https://packages.debian.org/src:aide
155: https://www.debian.org/security/2022/dsa-5052
156: https://packages.debian.org/src:usbview
157: https://www.debian.org/security/2022/dsa-5053
158: https://packages.debian.org/src:pillow
159: https://www.debian.org/security/2022/dsa-5054
160: https://packages.debian.org/src:chromium
161: https://www.debian.org/security/2022/dsa-5055
162: https://packages.debian.org/src:util-linux
163: https://www.debian.org/security/2022/dsa-5056
164: https://packages.debian.org/src:strongswan
165: https://www.debian.org/security/2022/dsa-5057
166: https://packages.debian.org/src:openjdk-11
167: https://www.debian.org/security/2022/dsa-5058
168: https://packages.debian.org/src:openjdk-17
169: https://www.debian.org/security/2022/dsa-5059
170: https://packages.debian.org/src:policykit-1
171: https://www.debian.org/security/2022/dsa-5060
172: https://packages.debian.org/src:webkit2gtk
173: https://www.debian.org/security/2022/dsa-5061
174: https://packages.debian.org/src:wpewebkit
175: https://www.debian.org/security/2022/dsa-5062
176: https://packages.debian.org/src:nss
177: https://www.debian.org/security/2022/dsa-5063
178: https://packages.debian.org/src:uriparser
179: https://www.debian.org/security/2022/dsa-5064
180: https://packages.debian.org/src:python-nbxmpp
181: https://www.debian.org/security/2022/dsa-5065
182: https://packages.debian.org/src:ipython
183: https://www.debian.org/security/2022/dsa-5067
184: https://packages.debian.org/src:ruby2.7
185: https://www.debian.org/security/2022/dsa-5068
186: https://packages.debian.org/src:chromium
187: https://www.debian.org/security/2022/dsa-5070
188: https://packages.debian.org/src:cryptsetup
189: https://www.debian.org/security/2022/dsa-5071
190: https://packages.debian.org/src:samba
191: https://www.debian.org/security/2022/dsa-5072
192: https://packages.debian.org/src:debian-edu-config
193: https://www.debian.org/security/2022/dsa-5073
194: https://packages.debian.org/src:expat
195: https://www.debian.org/security/2022/dsa-5075
196: https://packages.debian.org/src:minetest
197: https://www.debian.org/security/2022/dsa-5076
198: https://packages.debian.org/src:h2database
199: https://www.debian.org/security/2022/dsa-5077
200: https://packages.debian.org/src:librecad
201: https://www.debian.org/security/2022/dsa-5078
202: https://packages.debian.org/src:zsh
203: https://www.debian.org/security/2022/dsa-5079
204: https://packages.debian.org/src:chromium
205: https://www.debian.org/security/2022/dsa-5080
206: https://packages.debian.org/src:snapd
207: https://www.debian.org/security/2022/dsa-5081
208: https://packages.debian.org/src:redis
209: https://www.debian.org/security/2022/dsa-5082
210: https://packages.debian.org/src:php7.4
211: https://www.debian.org/security/2022/dsa-5083
212: https://packages.debian.org/src:webkit2gtk
213: https://www.debian.org/security/2022/dsa-5084
214: https://packages.debian.org/src:wpewebkit
215: https://www.debian.org/security/2022/dsa-5085
216: https://packages.debian.org/src:expat
217: https://www.debian.org/security/2022/dsa-5087
218: https://packages.debian.org/src:cyrus-sasl2
219: https://www.debian.org/security/2022/dsa-5088
220: https://packages.debian.org/src:varnish
221: https://www.debian.org/security/2022/dsa-5089
222: https://packages.debian.org/src:chromium
223: https://www.debian.org/security/2022/dsa-5091
224: https://packages.debian.org/src:containerd
225: https://www.debian.org/security/2022/dsa-5092
226: https://packages.debian.org/src:linux-signed-amd64
227: https://www.debian.org/security/2022/dsa-5092
228: https://packages.debian.org/src:linux-signed-arm64
229: https://www.debian.org/security/2022/dsa-5092
230: https://packages.debian.org/src:linux-signed-i386
231: https://www.debian.org/security/2022/dsa-5092
232: https://packages.debian.org/src:linux
233: https://www.debian.org/security/2022/dsa-5093
234: https://packages.debian.org/src:spip
235: https://www.debian.org/security/2022/dsa-5095
236: https://packages.debian.org/src:linux-signed-amd64
237: https://www.debian.org/security/2022/dsa-5095
238: https://packages.debian.org/src:linux-signed-arm64
239: https://www.debian.org/security/2022/dsa-5095
240: https://packages.debian.org/src:linux-signed-i386
241: https://www.debian.org/security/2022/dsa-5095
242: https://packages.debian.org/src:linux
243: https://www.debian.org/security/2022/dsa-5098
244: https://packages.debian.org/src:tryton-server
245: https://www.debian.org/security/2022/dsa-5099
246: https://packages.debian.org/src:tryton-proteus
247: https://www.debian.org/security/2022/dsa-5100
248: https://packages.debian.org/src:nbd
249: https://www.debian.org/security/2022/dsa-5101
250: https://packages.debian.org/src:libphp-adodb
251: https://www.debian.org/security/2022/dsa-5102
252: https://packages.debian.org/src:haproxy
253: https://www.debian.org/security/2022/dsa-5103
254: https://packages.debian.org/src:openssl
255: https://www.debian.org/security/2022/dsa-5104
256: https://packages.debian.org/src:chromium
257: https://www.debian.org/security/2022/dsa-5105
258: https://packages.debian.org/src:bind9Removed packages
—————-The following packages were removed due to circumstances beyond our
control:+—————————-+——————+
| Package | Reason |
+—————————-+——————+
| angular-maven-plugin [259] | No longer useful |
| | |
| minify-maven-plugin [260] | No longer useful |
| | |
+—————————-+——————+259: https://packages.debian.org/src:angular-maven-plugin
260: https://packages.debian.org/src:minify-maven-pluginDebian 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:
https://deb.debian.org/debian/dists/bullseye/ChangeLog
The current stable distribution:
https://deb.debian.org/debian/dists/stable/
Proposed updates to the stable distribution:
https://deb.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
stable release team at--
Brian MasinickIn reply to: Core, installed KDE, how to automatically start it?
christophe
OK. đ
So, I installed it into a virtualbox VM. I have to say that it did work perfectly.
This is what I did:1. Used the antiX-21 core x64 ISO. I booted up into a fresh virtualbox VM, 11 GB vdi for hard disk. I logged in as root. First thing I did was to run:
apt updatefollowed byapt full-upgrade2. I partitioned the virtual hdd — 10 GB ext & 1 GB swap. (Maybe there’s an easier way to do it, but (for some reason) the console font was HUGE.I couldn’t see the screen well – it was cut off on both sides. Maybe just my old computer. Anyway, I couldn’t figure out what to do, except to reach way back in my memory how to run ‘fdisk /dev/sda’. After it was partitioned & written to disk, I ran ‘mkfs.ext4 /dev/sda1’, to format it. Again, let me just say, that maybe there’s an easier way. But it did the job.)
3. Then I ran the cli-installer. That went easily, as expected. (At the point in the installation where it asks, I took care to adjust the console font to terminusbold at 8×14, and that fixed it to a viewable size.)
4. Once the installer completed, I rebooted. After login, I ran:
sudo apt install --install-recommends kde-standard virtualbox-guest-dkms virtualbox-guest-x11 virtualbox-guest-utils5. Once that concluded, I ran
sudo reboot6. When the VM came back up, it went straight to the SDDM login screen. (Ta-Daaa!) I was able to log in.
So that’s the reason I tried to give as much detail as possible. Because it was basically the same as the video.
EDIT: If you think the problem stems from partitioning/formatting the virtual hdd prior to installing, I’ve figured out the easier (“intended”) way to do it. đ
If you have questions, please ask.
- This reply was modified 1 year, 1 month ago by christophe. Reason: minor clarification
- This reply was modified 1 year, 1 month ago by christophe.
Attachments:
confirmed antiX frugaler, since 2019
PPC
How to test (and possibly install) antiX Linux, if you are a Windows user:
This is not the ideal place to present this how-to, because if you are reading this, you probably already are using antiX, but here it goes (you can show this text to someone that is curious about Linux or thinking about installing antiX, or that guy that is still running Windows XP on a laptop from the Stone Age)
**Some general notions:
-What is Linux?
Linux (technically, you should say GNU Linux) is used to refer to any Operating System that runs the Linux Kernel.-What is an Operating System?
An Operating System (OS for short) is the software that runs you computer and allows you to interface with it. Picture this: your computer is just a piece of hardware, like your TV. Without the Software to tell your hardware what to do, it’s useless, like a TV not plugged to anything. In this analogy, the Operating System is like the TV programming that you can see – you can only use a TV when it’s connected to something (cable, an antenna, a box, a console, etc). Just like you can only use a Computer when it has an Operating System.-Is Linux just like Windows?
They both are O.S.. You know of lots of O.S. already, even if you think you don’t- you know Windows (probably only Windows 10 and 11, if you are young, but there are lots of versions). Mac’s use their own O.S. – MacOS. Mobile devices use their own O.S.- android devices (phones, tablets, smart TV’s and smart TV boxes, even some e-book readers, like the Kindle Fire) use Android, Iphones and Ipads use IOS, old Nokia phones used Symbian OS, etc…
Linux is an OS, just like Windows is, but it has a few differences:
I mentioned Windows 10 and 11, and each one of these systems has Home and Pro versions- that makes 4 different Windows versions, right? But Microsoft still has Windows 8 (with Home and Pro versions). That’s 6 versions. You probably don’t know that each of those Windows also offers an Enterprise edition- so there are 9 different Windows versions (there are more than that, but there’s no need to get into more details).Linux? Linux has hundreds of Versions. Yes. I’m not exaggerating- many hundreds of versions. Each of those versions is called a Linux Distribution (Distro for short)
There are a few Linux “families”, from which many Distros derive from. One of the most used “families” is Debian. But there’s also Arch, Suse, Red Hat, and more.
You probably never heard about Debian. But if you ever heard about Linux, you probably heard about Ubuntu, or Linux Mint or MX Linux. Those “Distros” are based in Debian. In fact Ubuntu is based in Debian and Mint is based in Ubuntu. And there are Distros based in Mint…And while each Windows version (8, 10 and 11) has it’s own User Interface (UI), Linux has many possible interfaces.
There are Desktop Environments (DE) – that include most of what the user perceives as the OS- the window management system, the toolbar, the menu system, the notification system, the video compositor, the log-in manager, the application “store”, etc. Some examples of the most used DE’s are KDE, Gnome and XFCE… But there are also OS that don’t waste system resources running a complete DE, but use only (floating) Window Managers (WM) – different programs that draw and manage the windows of everything the user sees in the OS. Some examples of floating Window Managers are Fluxbox, IceWM, JWM (antiX includes all three of them) and Openbox. Another option are Tilling Window Managers (like Herbstluftwm, that antiX also includes)- that usually open windows either in full screen or in some predefined or manually selected size (ex: half screen, a quarter of the screen, etc), to maximize the usage of screen real-state, and usually are keyboard driven…
DE’s and WM’s are flexible and can be configured to look just like anything – they can be made to resemble (or “clone”) Windows 98, Windows XP, Windows 10, Windows 11, different versions of MacOS, Android, some mix of those interfaces or something completely new and never seen before…
That’s why almost no two Linux distros look exactly the same…
Programs are installed in the different Linux “families” (not the exact term)- Debian, Arch, Red Hat, Void Linux, using different Packaging… Debian (and Ubuntu and antiX) for example, packages software in .deb packages. Windows packages software in .msi packages…
Packages in one file format usually can’t be installed in a Distro that uses a different packaging system (ex: a .rpm package can’t be installed in a Debian system, like antiX).
There are also some universal file packages- like appimages, flatpaks and snaps (snaps are not compatible with antiX), meant to run in almost every possible Linux System… Appimages are the Linux equivalent of portable applications, in Windows (one single compressed and self extracting file that includes almost everything the application needs to run).So… Is Linux just like Windows?… it can be, or it can be something completely different…
Also despite applications made for a system not being compatible with a different system, Linux has software that allows it to run many applications made exclusively for Windows – WINE and Proton (that is derived from WINE and meant to run Windows only games in Linux). Currently Proton allows Linux users to play thousands of games made for Windows. Wine allows some Windows only applications (even including versions of MS Office and Photoshop) to run in Linux, although sometimes not perfectly…
Almost 100% of DOS software can run in Linux using an emulator called DosBox ( included, out of the box in antiX Full).-Why are there so many Linux Distributions?
Because Linux is not just free (hell, Windows 10 and 11 are usually “free”, you can use unlicensed- and limited versions- for private use and MS will do nothing against you, even if you are not exactly complying with their User License Agreement)… Linux is Open Source – that means that it’s code is publicly available- that you can do what you want with it (according to different Open Source Licenses), copy it, change it, adapt it to do what you want, usually the only drawback is that the end result of those changes has to also use the same Open Source licenses.
So, when someone needed an OS to manage a Server, a Linux Distro was created for that…
Do you need an OS that is meant to be just a media player, to stream audio and video? a Linux Distro was made for that…
So you need an OS that is free and looks just like Windows 98? A Linux Distro was made for that too…
And you want an OS that looks just like Windows 10 or 11? You guessed it, there are Linux Distros that do that…
And you want a MacOS clone? There are Linux Distros like that…
Do you want to use your computer mainly for gaming, like a Console- just turn on the computer and access your games? There are Linux Distros for that…
Are you Russian? Or Chinese? Or Korean? Or Portuguese?… and want an OS tailored for your particular language and needs? Those Linux Distros already exist!
Are you an “Anna Montana” fan and want an OS just around that? Someone created one such Linux Distro…
Do you have a computer that is old and want to keep it working? Someone made a Linux Distro like that. Several, in fact. One of them, and the best, in my particular opinion, is antiX Linux. antiX is a GNU Linux Operating System based on Debian (antiX 21 is based on Debian 11)--Why use antiX?
antiX was made to keep very old computers still useful. Even computers that are 20 years old (or even more) can be used to navigate web pages, stream YouTube videos, listen to music, view videos, read e-books or pdf’s, use office suites (that are extremely compatible with Ms Office), write/read e-mails, use instant messaging services, play casual games, play vintage DOS and Windows games, etc…
And if extremely old computers can run antiX, most extremely modern computer can too. Picture this: you can have a computer with a single core CPU, and less than 1gb of RAM that allows you to navigate the Web using a modern browser, have a word processor open and listen to radio/mp3 files, and have a File Manager running, and a Solitaire card game running and still have free RAM. Modern Windows OS need more than 1gb of RAM just to simply run the system itself…
And if you can run all that with a single CPU and less than 1 gb of RAM, if you are running antiX on a system with more than 1 CPU and more than 1gb of RAM, those resources are free to be used to perform any task you need.
Linux is not really magic, not even antiX – it can’t make a 20 years old computer play the latest Tomb Raider game in full HD, at 60 frames per second… That requires simply more processing power than that device has. But you can use antiX on a computer that is over 10 years old and use the modern Web. Do you know what runs on the modern web? Streaming Games Platforms, like Google Stadia and Xbox. If your computer has resources enough to run those webpages, then you *can* play the latest Tomb Raider, almost like you were using a latest generation gaming console.
You can use antiX for work- if you work on-line (using on-line office suites, etc)- you can use probably the crappiest 64bits computer with at least 1gb of RAM (if your computer has more than 1 CPU core and more than 1 gb of RAM, it’s a safe bet that you can run anything the modern Web throws at you, at least at the time I’m writing this), and most existing Linux applications.
You can use streaming video services like Netflix (if your computer is running a 64bits antiX version, because Google, that provides the software that allows browser to access DRM streaming video has blocked 32bits Linux OS from using it, on the latest upgrade).
If your computer has enough resources you can even play thousands of Windows only games- some running better than in Windows it self.
If you need a particular piece of software that can run on Linux, then you have no need to use any other OS.
Also, because the Linux source code is Open Source – any bugs or frailties it may have, tend to be patched faster than in closed sources OS- there are thousands of programmers looking at (“inspecting”) the Linux source code- some are criminals, looking for something they can exploit… but for every criminal there are many honest persons that report and problem and help fix it. Also, in an Open Source OS, people do know what the system is doing… How can you know, for example, if your system is logging every single character you type, or sending every single web site you visit to a server somewhere? Well, on a closed source system, you never know (unless someone with inside knowledge or gathering info from indirect means, like monitoring network connections, warns the public), but on the Open Source world, someone, sooner rather than later, catches on to what the code is doing and rings the alarm in no time – so Open Source software tends not only to have more Security but also to be more Privacy respecting. Even if a particular Open Source application does not respect your privacy, someone will pick up it’s source code and create a new, more privacy respecting version of the same application… (a new version of an application, based on it’s source code but with a different name is called a “fork“, and it happens all the time, in the Open Source World, and for many reasons, some as trivial as just changing the application name that you just don’t like)-Who should not use antiX
If you are perfectly happy with the OS you are running (Windows or any other Linux Distro), stick to it.
If a particular piece of hardware (a printer, a scanner, a card reader, etc) only has drivers (software that allows a device to work with a computer) for your current OS, stick to it. You can’t demand that “Linux has to make xyz work” – There is no single magic “Linux” developer that does that because manufacturers of devices are responsible for the creation of the drivers they need – since they alone know exactly how the hardware they produce works. [HP printers, for example, work great in Linux. Nvidia, on the other hand, refuses to make their drivers open source and the drivers they currently make available for Linux are inferior to those available for Windows]
If you need a particular piece of software that is not (yet) available under Linux: like MS Excel Macros, Adobe Photoshop, CAD or accounting software, certain games etc – don’t use Linux, or, at the very least, have a dual boot system (more on that below). More advanced users, and with powerful enough computers can run a virtual MS Windows version inside Linux – but that usually is much slower than running Windows directly. There are free and open source alternatives for most commercial applications.
But “alternatives” are not the same as the “real deal” – if you spent years learning to be proficient in Photoshop, it probably won’t be efficient relearning how to do your work in Gimp, even that allows you to save software subscription fees…–“It sounds great! How do I try antiX Linux?” you may ask…
Well most Linux Distros (antiX included) allow you do to something that you probably are not used to- they can run without even being installed!
It may seem strange, but that’s true. You can “boot” (this means to starting running the system) your computer from a CD-ROM, DVD-ROM, pen-drive or external hard-drive, that has the antiX system saved in a particular way that allows you computer to start from it, and run the system. It behaves just like the real installed system (but it may run way slower if you are running it from CD/DVD or very slow USB devices) – this is called a “live” system.
There is a special way to save the antiX system to USB devices (pen-drives and external hard drives) that allows you to save any changes that you do- you can create documents, install applications, etc, just like in a “installed system”. This is called “persistence” (the changes you make persist even across reboots, even if you plug your pen-drive on a different computer, etc).Once you are running an antiX live system, you have the option to install it to your hard drive.
To do all that you do need to follow some steps that may require that you understand some principles and can perform some actions. There is no single Manual that says- just do this…
**1- Downloading antiX:
1.1- Please note that this tutorial assumes that you are a Windows user (probably a Windows 10 user). Open your web browser and navigate to the antix download page: https://antixlinux.com/download/ and pick the server nearest to you (so you can download the needed files faster)
1.2- You’ll see a simple web page that lists lots of files. You need to select which file you want to download – currently the latest version is antiX 21, so pick one that starts with “antiX-21″… If you have a very old computer, that is 32bits, you’ll have to select a file that has “_386” on the name. Most users can select the 64bits version (that has “x64” on the file name). Each version of antiX comes in a few flavours- “Full” includes most of the stuff you may need- select that one if you intend to install/test antiX using a DVD-ROM or an USB pen drive.
The file you want to download has the “.iso” extension, that is about 1.4Gb
Example – download the file “https://ftp.di.uminho.pt/pub/mxlinux/ISOs/ANTIX/Final/antiX-21/antiX-21_x64-full.iso”
Wait until the file is downloaded, it may take a while on a slow network connection.Checking the integrity of the .iso file– The other (tiny) files that have similar names to the iso are meant to confirm if the .iso file you downloaded is not corrupted- If you don’t know how to do this (fully optional) step , you can read how to check the integrity of the .iso file you downloaded here: https://antixlinuxfan.miraheze.org/wiki/How_to_install#Verification_of_the_integrity_of_the_ISO_file
Please note that probably most failed OS installations are due to trying to install from corrupted .iso’s!!!**2- “Burning” antiX to a bootable media:
Note: If you are using an extremely old computer, it may not support booting directly from an USB device, only from CD/DVD. On the other side, more modern devices don’t even come with an optical drive!
2.1- You’ll have to save the .iso file you downloaded to a blank CD_ROM/DVD-ROM or pen drive. This process is called “burn” – the expression comes from the CD-ROM days (before USB pen-drives)- info was “burned” into the reflective surface of the disk using a laser. Sometimes the same expression is still used, even when saving iso images to USB pen-drives…
This is were things may begin to differ from user to user…
2.1.1- If you are “burning” the iso file to a CD-ROM/DVD-ROM – insert your disk in the CD/DVD recorder and open the software you use to “burn” disks. Select the option to burn an iso file and select the antiX .iso file you downloaded. Wait for iso file to be saved to the disk…
2.1.2– If you are “burning” the iso file to an USB pen-drive/external disk – insert the device you want to use. WARNING – this process ERASES ALL INFORMATION ON THE USB DEVICE!!! – and use an application that “burns” isos to pen-drive. In Windows you can use, for example Etcher (available here: https://www.etchersoft.com/download/#). You have to make sure you have Etcher or a similar application installed and open it. Select the option to burn your antiX .iso file to the USB device and wait until the process is finished.
NOTE: Even if you don’t have a computer with a working OS, you can download the .iso and create a USB bootable pendrive using an android device – there’s a short, but very nice tutorial on how to do that here (by Moddit): https://www.antixforum.com/forums/topic/create-live-media-with-smartphone-successful/#post-79573**3: Booting into antiX live media
This step differs even more from user to user, depending on the computer that is being used. You may have to configure the computer to boot (to start running the system) from the optical disk/pendrive where you burned antiX…
3.1- Exit your system, completely shutting it down. In Windows 10 you have to hold down the SHIFT key on your keyboard and click the âShut downâ option in the Windows Start Menu (or on the log in screen)
3.2- Boot your computer.
3.2.1- In case your computer is already configured to boot from the media that you saved the antiX iso to, it will display the antiX boot screen. If that happens, jump to step 4.
3.2.2.- If you just see the regular Windows boot screen, you’ll have to let Windows boot and exit it again, repeating step 3.1.
Boot your computer and again and see if the boot screen, that shows up for some moments before the Windows screen says something about about pressing a key to enter the “boot menu/device/etc”. If it does, press that key, before the Windows Screen pops up, and select to boot from the media here you burned the antiX iso in (the optical disk or USB device). If you are successful, the computer will display the antiX boot screen. If that happens, jump to step 4.
3.2.3- If when your computer boots it does not display any indication on how to select “boot menu/device/etc” it will probably tell you to press a certain key to configure the device’s motherboard options.
Once you enter the motherboard options menu, be very careful – don’t change anything unless it’s about “boot devices” “boot order” or something similar – take notes about that the default setting is (or take a picture with your phone).
Change the boot order so the computer first tries to boot from the optical drive or the USB device (if you burned antiX to a DVD select the DVD as the first boot device, if you burned antiX to a pen-drive, select the USB device related entry first). Make sure that after the second boot device is your hard drive. Select the option to save the changes you just made (again, the way to do that depends on your computer’s brand and model) and reboot.NOTE: The keys regularly used to enter the boot option/boot configuration are F8, F10, F12, etc- you can search for that info on your computer’s user manual or on-line.
**4: Running antiX in live mode and possibly installing it:
By default, the system boots in English. If you wish to use some other language, press the F2 key and, using the keyboard, select your language.
antiX 21 has 2 Kernels to boot from- a Legacy kernel (for older devices) and a Modern Kernel (for newer devices). The first boot screen allows you to choose which kernel you want antiX to use. Usually go with the default option, then you’ll reach the second, and main, boot screen, with more options- if you don’t want to change any setting (don’t do it unless you really have to), or after you select your language (if don’t want to use English), press enter on the first option on the menu (“Normal Boot”), to start loading antiX.
P.S.- There’s a Youtube video that shows the boot and install process: https://youtu.be/5z-SYlouQZM?t=10 (you only need to see the video from the 10 seconds mark until the 5 minutes mark. Yes, just 5 minutes to boot antiX for the first time, take a look at the menu, install it and reboot the computer to the newly installed antiX 21 OS – it probably will take you longer to read the rest of this tutorial than to view the relevant part of that video…)
4.1- Loading antiX – when loading antiX from a “live” media, the boot process is different from when you are using an “installed” antiX system. In the “live” boot, you get to see some text roll by and then a simple GUI that shows one line on the middle of the screen that tells you what is happening.4.2- Using antiX “live” – after some moments, you’ll see the antiX desktop – it’s similar to Windows – it has a toolbar on the bottom, with a clock on the right side, you see a wallpaper, and desktop icons. If you are using the default settings, there is also a menu button on the left side of the toolbar, that you can click to access the menu. It’s, in the default antiX settings, a Category driven menu, that has a few generic entries – like Web browser, etc, and then all applications are organized into categories, inside de “Applications” menu entry.
You can configure your Wi-Fi network (if need be) and test the web browser (the compass looking icon, on the toolbar).
If you are using an USB antiX bootable media and you burned the iso in such a way that it can store changes, you can save files to a special folder on the “demo” user folder.
If you want to use real persistence, you’ll have to configure that option (there are how-to’s on that, on the forum and the antiX wiki)4.3- Installing antiX – You can, at any point, when using antiX in Live mode, install antiX to your hard drive.
To start installing antiX click the “Install” icon available in the default antiX desktop (it looks like a CD with an arrow pointing down). You can also start the installer using the antiX Menu > Control Centre > Disks Tab > Install antiX Linux.
If you choose to install antiX, first you’ll have to confirm (or change) the keyboard settings. Then you are given the choice to which disk you want to install to (only if you have more than one hard drive) and to do a “Regular install using the entire disk” or “Customize the disk layout”.
This last option allows you to keep your current system -Windows and all your existing files and documents and install antiX side by side. If you do that, it’s called “Dual booting“- every time you reboot your computer you can select if you want to use antiX or Windows. But that process is relatively complex. Don’t do it without making sure to backup every important file you have in your computer!!!
WARNING 1: if you select the option to install to the entire hard drive your hard drive will be formatted and everything that’s on it erased! (I’m simplifying for all you Windows users, but take this warning seriously)
WARNING 2: If you want to run antiX side by side with Windows and/or keep the files you currently have on your hard disk and you don’t know how to create or manage disk partitions, ask the help of some computer savvy person- run antiX live all you want but don’t try to install it if you have stuff you want to keep from your old system and don’t have backups.
After this selection regarding the hard drive partitions, the installer is extremely easy to use – just answer the questions you are asked.
[Note: when answering the following questions, the install process will continue. If you are a slow typist there’s a good chance that, when you answered every thing, the installation is done or very close to being done…]
Select your “Computer name” and “Computer Domain” (choose any names you want)
Select your username and password,
You’ll be asked if you want to “Auto-login” – if you don’t choose this option, you’ll have to enter your password each time you turn on your computer.
You will also be asked if you want to setup a “Root (administrator) account”– if this is enabled, you’ll be asked to enter your root password every time you want to do any major change to your computer – like installing or removing software or changing some important setting- it’s a very nice security feature.
Basically the installer asks the same simple questions, that you are used to if you ever installed Windows or bought a computer with Windows pre-installed and had to set the system up.
Save live desktop changes: If you choose this option, you can keep all the changes you made in the Live session (the language selection, any package you installed, the Wi-Fi configuration, etc).
You can also keep using the Live session after you install antiX to your hard drive or select the option “Automatically reboot the system when the installer is closed”**5- Exiting Live mode
5- If you don’t want to run antiX in live mode (either because you installed it to your hard drive OR you want to use Windows, remember to remove the media you are using to boot into antiX live (the USB device or the optical disk) before rebooting your computer:
5.1- If you are using a pen-drive – shut down your computer using the exit menu options. Once the computer is completely off, you can remove the USB device and reboot your computer.
5.2- If you are using an optical disk (CD-ROM or DVD-ROM)- shutdown antiX and usually the optical disk is ejected. (If it’s not ejected, for some reason, when rebooting the computer, eject the optical disk, so it can boot into the internal drive).If you did a dual boot installation, when you boot your computer, you’ll be able to select if you want to run antiX or Windows.
If you did a full disk install, you’ll only have several options to boot antiX
If you did not install antiX, when you boot your computer (and don’t have the antiX live boot media inserted in your computer), you’ll run Windows.Note: some motherboards (I have one of those), when you press the key to select the boot device, require you to set the boot order back to first try to boot from the hard drive, once you want to reboot from the hard drive…
P.
- This topic was modified 1 year, 1 month ago by PPC.
- This topic was modified 1 year, 1 month ago by PPC.
- This topic was modified 1 year, 1 month ago by PPC.
In reply to: comment installer “bento” antix remix 20.04
ModdIt
Bonjour jibelit,
Désolé de lire que vous avez des problÚmes avec le respin antiX.
Pour toute question, veuillez continuer Ă poster dans la section respins.Allez-y doucement, l’installateur d’antiX est quelque peu diffĂ©rent de beaucoup d’autres.
Vous demandez comment faire une clé USB pour antiX. Il y a plusieurs façons, si vous avez un smartphone, utilisez
un adaptateur USB OTG et écrire une clé avec une application appelée ISO to USB. à partir de Windows Etcher est probablement le plus fiable. Depuis un autre linux, vous pouvez utiliser dd, et enfin, mais pas
Enfin, depuis antiX ou MX, utilisez live USB Maker.Une fois que vous avez une clé antiX vivante, vous pouvez la démarrer et utiliser grub boot repair qui
qui, avec un peu de chance, vous permettra de retrouver un systĂšme entiĂšrement fonctionnel.N’oubliez pas non plus que vous utilisez un respin non pris en charge, avec lequel la plupart des membres du forum ont peu ou pas d’expĂ©rience.
Pour une aide détaillée, il est préférable de contacter le créateur du respin.Traduit avec http://www.DeepL.com/Translator (version gratuite)
- This reply was modified 1 year, 1 month ago by ModdIt.
Does the live usb stick start WITH persistence by default or without persistence by default
To use persistence you have to specificaly set it up. A small amount of data is always saved for user convenience even
when persistence options are not used, major changes will be lost on shutdown unless a remaster is performed..I make a stick using antix tool or other method.
Select boot device on the computer.Set my language and timezone on the antix boot screen
Boot antix, set your fastest repo using the controll center tool, do sudo apt full-upgrade,
update the kernel as older versions are vunerable. If you are on a device with low memory
you may need to do the kernel and system updates in stages.
Do a personal remaster, that will incorporate the changes in to the usb stick.
Reboot, just select antix, no need to keep setting language.
Customise antiX desktop. Make a backup ISO Snapshot at this stage using antiX tool.
Put it where you have safe space.For safe easy recovery I write the snapshot to a separate USB stick and ensure it will boot,
then keep it safe, it is my personal antiX.Boot with the first stick and make experiments with that, add extra software and test it. If
you do not wish to keep changes just shutdown without a remaster. If you are unsure or wish
to keep changes do a personal remaster.To revert you still have your personal antiX boot stick and the ISO snapshot.
- This reply was modified 1 year, 1 month ago by ModdIt.
- This reply was modified 1 year, 1 month ago by ModdIt.
silverrahul
“You can also make a USB Live stick start without setting up persistence, as long as
you have sufficient RAM and swap memory available”How do i do that? Does the live usb stick start WITH persistence by default or without persistence by default? I had downloaded the antix 21 live usb iso from the antix website and flashed it into my pendrive .
Do, i just boot using the same pen drive if i want to start live usb without persistence ?
- This reply was modified 1 year, 1 month ago by silverrahul.
I am writing this post from a live USB stick created using an android phone.
I downloaded antiX 21 full to phone storage using Bromite Browser,
which I had Installed through F Droid.
Checked the ISO, sha256 using Hash Droid app installed from F Droid
Wrote the Fully featured antiX bootable USB stick using an app
called ISO 2 USB. Downloaded from APK PureSet language and booted in to a fully featured antiX live experience.
Only extra needed, a USB C to OTG adapter.
My phone: Huawei 9XPro, a non google device with android 9.Depending on device USB B or C OTG adapter will be required along
with the USB Stick for installation.Pls do remember to delete the ISO from phone if your space is limited.
Hi silverrahul.
after making so many changes, major desktops pull in many depends
the sanest way to get back to a normal antiX installation is to reinstall from your
personal backup or ISO image.When you want to try out anything which makes major changes to your system may I
recommend to use a live USB stick. It makes reverting really easy. Just rewrite
from your personal backup or a sha256 checked download.You can also make a USB Live stick start without setting up persistence, as long as
you have sufficient RAM and swap memory available, fully update, make changes,
experiments and at any time reboot without doing a live remaster. Next start you
have your personal environment back to the way you booted it.While using a non persistent stick you can at any time remaster keeping your changes
and user environment. In contrast to using persistence to save changes the remaster
will boot and shutdown faster. Save data to live usb storage or another stick.Please do use the fantastic tools antiX provides, they are very useful, efficient
and well thought out.In reply to: Moved: KNOPPIX
PDP-8
Big props to Klaus for what is still essentially a one-man show! 9.1 public is the latest, although I look forward to 9.2 public. Basically thanks to a dev that could easily just close his door long ago.
Hard to believe, but there can be lurkers / newcomers that don’t know the basics if they haven’t kept up over the years …
1) It is primarily meant to be a live-usb / cd /dvd boot. You *can* install to a hard drive, but that is not it’s main purpose, nor is it designed as such.
2) It is not meant to be updated. You grab the latest release (approximately once a year) if you want the latest. SMALL updates and additions ok, but wholesale upgrading with the usual debian apt update / upgrade tools will break it. Knoppix, in order to support both old and new, is a mix of stable, testing, and experimental sources. So don’t treat it like a rolling distro! đ
3) If you burn the Knoppix iso, at first boot it will automatically resize the partition to fill your usb stick for persistence of user files.
4) BUT – for best results, you don’t want to stop there! Ideally, after kicking the tires, you should use the live-usb-installer to create another specially formatted usb stick – it performs better and is more robust!
5) When using the live usb maker in Knoppix, you now have a variety of options to choose from (encryption, size and so forth), and uses the ReiserFS file system instead of the existing typical fat32.
6) Not *everything* boots properly. In that case, one should peruse the “cheatcodes” file and apply kernel options if necessary. One of my machines demands that I use a “knoppix64 acpi=noirq” for instance to be stable. Since the Knoppix stick is really nomadic, getting comfortable with the cheatcode options improves your sysadmins skills. đ
While once it used systemd for many releases, it hasn’t done so for the past few, and is back to a variety of custom hand-written scripts.
The Reiserfs filesystem is very hardy and self-healing. That means that when an unskilled user just yanks out the drive before the system is shut down cleanly, it can recover gracefully, many times without having to use fsck or other filesystem repair utils.
NOte: The Reiserfs and it’s controversy has already been covered for decades, so no need to repeat it here! Please. Such an old topic that it is troll-food. Nuff said.
Still useful, and I thank Klaus for still keeping it going after all this time.
- This reply was modified 1 year, 1 month ago by PDP-8.
In reply to: Copy n Paste install method works
Then you’ll love this – unsupported but worth a try – with nothing but a stock Chromebook:
(Not FOR the Chromebook, but merely using it as a burning tool with default tools it has, for a separate target machine in the corner … hint – it’s a glorified dd)
Download the AntiX iso.
Rename the iso file so that the suffix is “.img”
Use the Chromebook recovery tool, but instead of going online, use the cog icon to get to to the tools to point to the locally downloaded antix and renamed img suffix file.
Create the “recovery” stick. Which won’t boot your Chromebook, but will boot your other target x86/X86_64 machine you have stashed for your project.
Admittedly this would be a rare environment, but these days, it is quite possible that someone may only have a chromebook and could get them out of a jam if that’s all they have to burn.
In reply to: antiX-development
Brian Masinick
I just wrote a post about Mozilla and Firefox releases, and in that post, I spent a lot of time talking about testing.
At the conclusion I dropped a hint about testing antiX, so I’m putting out that big HINT again here:
We really appreciate it when people test antiX, whether it’s a development build or a released version of antiX. When we develop, we understand that not everyone has the time, skills, or interest in testing software. Still, downloading test software and using it occasionally, even if it’s not as part of your day to day system, can still help us. Those who have the skills to keep multiple versions of systems handy, so that they can “take risks” and use test software as “daily drivers”, going back to more stable software only when the test software fails in use cases that are crucial for your personal work – this REALLY helps!
So with the understanding that not everyone can do this, if we can even get 10-20% of our user base to test every so often, and whether it’s testing of our entire distribution or testing of a few of your favorite applications, every little bit helps.
If you find a problem – and if you can contribute – here are some ways.
1) Keep a listing of your system configuration – usually the command inxi -Fxz provides helpful information about your system; you can save the output of the command by storing the output in a file by doing something like this:
inxi -Fxz > ~/inxi-output.txt2) Tell us what you were doing when you found a problem and how to reproduce it:
Example: I downloaded https://sourceforge.net/projects/antix-linux/files/Final/antiX-sid/antiX-21-sid_x64-core.iso/download and verified the checksums at antiX-21-sid_x64-core.iso.sha256
After downloading and verifying this build, I used the Live USB Maker to create a USB drive containing the image, then booted the software from USB in Frugal mode.
Next, I ran _____ (fill in the blank) and found that when I started _________ app, the following behavior happened: _____ (describe what you found, and what you had expected to happen.
This kind of report, even if not formal, is very useful for developers and maintainers. If it concerns a tool or component that antiX develops, the antiX team can work on changes. If it concerns an application that we offer but do not author, it is best to send a similar report to the developers who write and maintain the tool. They may have specific report guidelines, but if you have most of the information outlined above, it’ll generally be helpful.
Anything the community can contribute at any time in the life cycle of our software, whether early testing or production testing is still valued and helpful. I hope that we’ll get new people contributing; even here, people come and go, so new faces and additional community help is always appreciated; Thank you to those who already contribute; we have developers, writers, documentation experts, forum helpers, and every day users, all who are valued; every little bit helps!
--
Brian MasinickSamK
I tried smb4k and had mixed but encouraging results. I may go back to that at some point, though it seems like a 100-kiloton flyswatter.
Yes, I agree.
A lot of work goes into making antiX light on CPU/RAM/disk-space to make it possible to run on modern and elderly systems. Partnering lightweight apps with appropriate methods of working are integral parts of getting the most from this distro. There are many ways of finding and mounting remote shares. It is a step away from the antiX philosophy to use an app that consumes more CPU or RAM or disk space when lighter ways of doing it are available in the distro. For example Connectshares only uses CPU/RAM at the time of actually mounting and unmounting shares, it does not run continuously, nor require something that does. Findshares is similar in that respect and has a tiny disk footprint of circa 20k, whereas other methods can be many MB in size, to do a similar job.
User choice is part of the antiX philosopy and the lightweight items in antiX do not preclude a user from employing a more heavyweight alternative. Share mounting methods that tie a user to a particular file manager are, in effect, a restriction of user choice in favour of that file manager. Connectshares gives access to CIFS shares and NFS exports without requiring the use of a particular a file manager. It works with any file manager of the user’s choice, or no file manager at all. Share access is available directly from any app, whether or not that app is network capable. It places the choice in the hands of the user.
I also use Thunar, and tend to be kind of opinionated about file managers. Iâm not a big fan of the Pcmanfm / Zzzfm family, or of Roxfiler, for that matter.
A few years ago a comparison of Connectshares and Thunar was produced in the former antiX forum, most of it is still OK.
Comparison Connectshares v Thunar
Below it is reproduced for current users who may not have seen it.REPRINT
Many people regularly use network shares at their workplace, university or school. Because Windows is commonly used on their workstation, they are familiar with its way of working. The concept of mounting network shares tends to cause new and even experienced users of Linux some consternation.In Windows, network shares are typically accessed in one of two ways. The first is by using the network browsing functions of your file browser. The other is by mapping a network share to a drive letter. In newer Windows editions, network browsing is also built into the standard âFile Openâ dialog inside your apps.
In Linux, we also have the ability to access network shares. Depending on your particular flavor of Linux, you may be also able to browse shares, and you will most certainly be able to set up your shares to be mounted, similar to the Windows mapping function. However, depending on the flavor of Linux you use, the shares may not be browseable from standard âFile Openâ dialog inside your apps.
Because user choice is a fundamental concept in antiX, it ships with various file browsers installed. When any of these is used together with Connectshares, you can work with network shares in a simple and familiar way.
Connectshares is an easy to use share mounting automation tool, designed with simplicity in mind. It can be set up by a standard user and without the need of deep technical knowledge. Normally, you will set it up once only, and there is a step-by-step user guide to walk you through the process (see antiX FAQ).
It can mount your shares either at boot up or on demand, as you see fit. Your shares will be available to any application, whether the app is network-enabled or not. You can disconnect on demand as well if you wish. You can also choose whether to automatically provide your username and password to access password protected shares.
The table below compares the way network shares are handled in antiX via Connectshares, with its cousin MX via Thunar. It’s not intended to show one is any better than the other. It provides information to help you make a choice that suits your way of working and level of skill. One of the benefits of using Linux is that, in the end, it’s your choice that matters.
Notes
Table based on antiX 13.2 and MX-14 beta2
dolphin_oracle and SamK are joint authors of this post and tableAttachments:
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
