Search Results for 'ppa'

[Member DaveW]

rokytnji – Well… That’s basically where I expected this would lead… and also the way I’ve been dealing with it. My only reason for using the 5.8 kernel, is that wireguard is already part of the kernel. So, when I need that, that’s the go to kernel. Otherwise, for now, 4.9 is best. I may try some other kernels, too. Thanks for sharing your experience.

andyprough – Thank you also for sharing your experience. It looks like tlp is already installed (cli version, no GUI) and apparently running in the default mode. However, I suppose, it is not active during the boot process (where the problem usually shows up). Perhaps it might help prevent a crash, after the system is up. I’ll keep that in mind. Thanks!

[Member roland]

roland@antix1:~/Desktop
$ sudo dmesg | grep -i “ath9k\|0cf3:9271”
[sudo] password for roland:
Sorry, try again.
[sudo] password for roland:
[ 13.280651] usb 3-1.4: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw requested
[ 13.281375] usbcore: registered new interface driver ath9k_htc
[ 13.601771] usb 3-1.4: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.dev.0.fw, size: 51008
[ 13.864495] ath9k_htc 3-1.4:1.0: ath9k_htc: HTC initialized with 33 credits
[ 14.483269] ath9k_htc 3-1.4:1.0: ath9k_htc: FW Version: 1.4
[ 14.483273] ath9k_htc 3-1.4:1.0: FW RMW support: On
roland@antix1:~/Desktop
$
I now have no significant wifi troubles on this PC and the install has become stable. There is just one small annoyance, Ceni does not automatically run after a cold boot, I have to run it manually typing in the network key and using the paste option each time, after choosing the network from the list presented. Should I shift networking to another runlevel, at present it is in ‘S’? Which runlevel is recommended? The messages Ceni returns about shortage of buffer space and failing to send 300b packets do not seem to affect its ability to connect.

I have now installed 19.3 on another PC which I use intending to gain experience with Connman, but after using the wifi switch as suggested Connman simply failed to do anything after I entered the network name and key. What does ‘tethering’ refer to? No apparent attempt was made by Connman to make a connection although I could see my wlan in the list. I quickly switched to Ceni, which on this PC starts and runs autonomously and makes the connection seamlessly.

Once again thanks in advance for all suggestions and contributions, they are all most welcome.

[Forum Admin SamK]

christophe wrote:

I think your experience is very valid. You apparently guide a large antiX user group.

ModdIt wrote:

I would appreciate it if user improvements in progress become available to a wider range of users in one form or another..

This is where the existing capabilities inherent in antiX come to your aid. There is no need to wait, those scripts/ideas can already be implemented today.

By design antiX is extensively configurable to cater for local circumstances. A standard version of antiX can be modified by removing unwanted progs, adding wanted progs, scripts, guides etc. That modified version can then be made available/distributed to local users to install and run from disk/DVD/Live. That can be achieved using standard antiX tools, which have been provided specifically for that purpose.

When viewed from that perspective, the process fulfils parts of the antiX philosophy:
• Put the choices into the hands of the user by enabling antiX to be fine tuned to suit their personal/local desires.
• Encourage the user to learn Linux and understand what they are doing.

The following is a pertinent example of modifying standard antiX oneself. It demonstrates the the principle but does not indicate whether the extra step is taken of making it available to others.

manyroads wrote:

…what I have read regarding Intro help brings something to mind I do for myself…It’s drop dead simple to do…

https://www.antixforum.com/forums/topic/ideas-for-improvements-in-future-releases/page/3/#post-46620

Afterthought
The way of working taken by manyroads is a good model. He produces work for his own reasons/benefit. When complete he shares his work so others may employ it if they so choose. This approach to working is a good fit with antiX. Thanks manyroads.

[Member ModdIt]

Christophe wrote: You apparently guide a large antiX user group.

I would sooner say I assisted installs with quite a number of persons.
Not taking things out of others hands and Encouragement is the most
important part. It is an intense learning experience for all.

I long for a Pizzeria meetup with Linux kids, friends and classmates of my daughter.

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

[Moderator christophe]

Not my experience

I think your experience is very valid. You apparently guide a large antiX user group.

anticapitalista wrote:

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

Now he has to sift through the suggestions & see what fits best for his vision for the OS.

confirmed antiX frugaler, since 2019

[Member fladd]

Okay, the reason for the first bug is in the following comment above where you set the TerminalCommand in the preferences (line 649):

# Terminal emulator must accept -e option.

The command “desktop-defaults-run -t”, when given the “-e” option, will apparently translate to running “desktop-defaults-run -e”, which opens Claws Mail.

Hence, you have to explicitly set a terminal emulator as TerminalCommand! You cannot use this desktop-defaults-run thingy there, as this does not work.

That still leaves us with the second bug, namely that completion does not work. Any ideas on that?

[Moderator BobC]

Thanks for everyone’s input and help.

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

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

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

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

[Anonymous]

As you can see, you need root authority to run it.

Use of the command doesn’t require elevated permissions.
Apparently the mount, or the file(s) slated for comparison, were readable only by root.

how can I check it if its written by live-usb-maker in non-dd mode?

The live-usb-maker tool diligently calls “sync” after its write operations.
A quick check (search in page: sync) https://github.com/BitJam/live-usb-maker/blob/master/live-usb-maker finds sync is mentioned 16 times throughout the script.

Also, @masinick “I usually clear a USB drive before writing new content“:
refer to the clear_partition() and clear_filesystem() functions within live-usb-maker ~~ it attends to this detail.
The in-app menu of live-usb-maker additionally provides on-demand access to the “clear_partition” operation.

> how can I check

If you paste the following into your conkyrc…

${execi 5 iostat -dp | tail -n +3 | grep -v loop | awk '{ printf "%-7s %7s %8s\n", $1, $5, $6}'}

…it will (per “5” in my example above) provide updated output every 5secs, ala

Device: kB_read  kB_wrtn
sda        4207        0
sda1       3635        0
sdb     1773573      119
sdb1    1773033      119
sdc      824743     4341
sdc1     824215     4341

providing visual confirmation of kb_wrtn value changes as they occur

I know how to check it if its written by dd, but how can I check it if its written by live-usb-maker in non-dd mode?

Aw, i missed or misread the gist of your question ~~ in non-dd mode
but I’m not gonna erase the bit I’ve already typed here.

What is “it”? I guess you mean iso file.
Skimming through the live-usb-maker code (itza bash script, plus external sourced scripts)
As far as I can tell, unless one has requested “clone” mode, an iso file will be handled the via copy_files_spec routine, @L2297, which invokes “cp” command (not “dd”)

And could these checks either be done optionally or by default automatically by the program at the end as part of the process instead of me trying to figure it out?

AFAIK, the checks are an intrinsic part of live-usb-maker’s operation.
In fact, as I recall, someone had requested a way to bypass the checks, b/c checking huge files, on old/slow hardware was painfully slow… and BitJam responded by adding an option ––force=nomd5 to accommodate that request.

[Member PPC]

Hi all! After some family time, that I mostly spent off line, I would like to chip in:

Skiddo is right- there’s no single way to make any OS easily understandable and configured by every single user, even more for people coming from the “Closed Windows” world. Terms vary so greatly that confusion when using a new OS is almost certain, even for tech minded people…
That said, I have to say that Windows has the “de facto” monopoly on desktop computer users- basically speaking- if you find a random person on the street that uses a computer, he/she knows only about the existence of MS Windows- so the little or more advanced knowledge that person has on computing is gear towards getting stuff done in windows.

Taking that into consideration, I even themed the tint2 toolbar to work much like Windows 10 – even if you boot in min-fluxbox – you get most of the stuff you have on W10 interface, for about 100Mb of RAM – It began as a personal configuration that I decided to share here in the forum with, what it seemed moderated success, that appealed to some people- the toolbar and even, to a small extent – the menu, follow most of what an average Windows users expects- some stuff is done even better than in Windows 10, some stuff not as well, other stuff is just plain different. Linux is not Windows and it’s not meant to be. But some Linux developers tend to ignore what a normal user expects and invent new terminalogy for normal stuff that’s been around for decades- making getting used to that interface a pain- my main example- _Bohdi OS- it’s a great OS an Ubuntu derived distro (that allows using PPA’s most of the on line tutorials for Ubuntu, etc) – much more eye catching than antiX- it provides eye candy, a wonderful app to search for apps and files at the same time, etc- all that using about the same system resources as antiX… It has some annoying bugs, like all systems, but, worst than that- if a newbie thinks it’s hard to get the hang of antiX – Bohdi simply insists on calling features but what seem to be names randomly generated -I know, this is a thing in Linux, even, to some small extent here in antiX

Icons are a modern OS user’s paradigm- I always have a start menu (because, well, it’s been there since the dawn of time, or, at least my first windows version), a “search” icon [app-select is a god send, but rofi is a bit faster on slow machines and can also be configures to perform file searches), a “browser icon” [firefox-esr], a folder icon [space-fm or even a sanely configured rox-filler], a “store” icon [app installer] and an antiX updater icon is probably all that most Windows users need to comfortably use antiX for most common tasks.
An easy way to automagicaly connect to wi-fi networks [connman has yet to fail me on that account] and HIDPI screens [unfortunately I don’t have that “problem”] would be greatly appreciated for common users/users with more modern hardware. Bob seems to be working hard on testing that – it that works, out of the box, behind the scenes and with no resources over heat, even better…
All previous suggestions couple with am welcome screen- easy to read by Windows users or non techie users[possibly pinned to the desktop] and auto starting for the first time (and with the possibility to disable that auto-start] would not cost any system resources, would help newbies, while only costing a couple if extra clicks [disabling the welcome screen] for advanced users…

Note: we think we should try to keep app’s names easy to understand and related to the task at hand- do you want to select an app? “app-select”, is a nice name, you want to edit a picture? WTF is a “GIMP”? You want to run a Windows application? Why drink “WINE”?… etc…

P.

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

I have performed a full update of Live antiX using Synaptic and after reboot the first thing I noticed was the boot screens change from full screen to just top left corner (small font) and back as the booting process progresses with dots representing stage of boot, as apparently screen resolution was determined. This video happens to be 1440×900 Nuveau default driver. I will test on other laptops with different resolutions and screens as well.
This was happening in the past but eventually got fixed and the boot screen was uniform in showing boot progress.
I do not think this this catch much attention but if someone has any hints what to exclude from update so as to not cause this fault, such hint will be greatly appreciated.
My antiX was 19.2 Hannie Schaft fully updated about three weeks ago, which update was fine and without negative artifacts.
I am not at a loss as I have multiple backup copies of perfectly working antiX Live, as performing any updates entails for me extensive testing before I migrate to updated release.
Any hints greatly appreciated…
Thanks and Regards.

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

[Member roland]

Bad news this morning, I gave it a 100gb SD to HD copy to be getting on with, to simulate hard work, and immediately the wlan and freezing problems returned.

Ceni reported ‘unable to write a 300b packet to wlan – no buffer space’ several times during the linkup phase to the selected network, it did get there after 3 or 4 such holdups. Again this is with the interim Usb wlan adapter which I will replace as soon as the Pci-e wireless lan adapter arrives. I have never liked Usb adapters for some reason. Should I abandon Ceni and try either Wicd or Connman?

Anything I tried to do has been punctuated by mouse pointer freezes, every 15 or 20 seconds, and lasting 30 to 60 seconds but quite variable, and always clearing itself after waiting. Conky shows the background jobs and networking to be running apparently normally in the background, and the folder copies I set running eventually completed as expected.

At times a left mouse button press is not immediately accepted and acted upon, a second press usually gets it going.

Any suggestions most welcome and will be carefully considered, and thanks for all previous contributions.

[Member seaken64]

I’ve been reading this thread with interest. Unfortunately, I don’t think I grasp everything. I understand that Marcelocripe has some old machines that don’t work well with the standard antiX-19 and that Xecure has been trying to provide an alternate iso that may work better on those machines. One approach was to replace the Xorg package with the package from antiX-16, is that correct? I’ve never quite got a handle on how all of this works, but will an older Xorg package continue to work with other programs that may require a dependency on the current Xorg files? Maybe a desktop environment or video editor, or something like that?

For what it is worth, I have one laptop that use the VIA Graphics. So far, I have been able to use this machine in antiX-16, antiX-17, and antiX-19 with no problems. It always uses the OpenChrome driver for Xorg and I am able to use the default screen size of 1280×768. I’ve had no video problems with the apps that I use, such as SMTube or Streamlight, or mpv, or VLC, etc. Apparently marcelocripe has different chips and get different results. I have another system that uses an Intel integrated graphics chip that was not supported and I had to get help from BitJam and others on this forum to set it up with the GUI. So I understand that sometimes the video does not get setup correctly from the standard iso download. But if I recall I only had to force an install of an alternate driver module. Apparently this is not always the case and no driver will solve the problem. In these cases is it a combination of the kernel, Xorg, and drivers? Is it that the driver files have not been maintained to support the newer Xorg and/or kernel?

I also have a keen interest in keeping old computers alive and out of the trash. I hope I can learn how all of these parts of the puzzle fit together so I can contribute to efforts such as those on display here in this forum. If marcelocripe and xecure are successful in getting marcelocripes computers working with antiX-19 it will go a long way toward all of us learning how to massage linux to our own goals. I only have this one laptop that uses the VIA graphics but if my testing will help I will do what I can.

I downloaded the legacy-bet1 iso file that xecure provided and booted it on this Gateway MX3210 laptop, which uses the VIA graphics chipset. It booted to the GUI with no problem and inxi shows the OpenChrome driver for Xorg. But the WiFi does not work. I compared the inxi to the previously installed antiX-19.1 which has been fully upgraded as of today. The graphics driver is the same with the correct resolution for this laptop on both. I’ll paste the inxi output below.

Also, it seems to me that a working WiFi is at least as important as a working graphics. Maybe this beta1 test is only focused on the graphics for now? and the WiFi will be working later?

Thank you all for you hard work. This has always been one of my favorite things about antiX. antiX developers and users appreciate that an old piece of equipment still has some value, even if only to a small handful of the world’s computer users.

Seaken64

Here’s the inxi outputs. The first is the beta1 test on a LiveUSB, the second is my installed and current antiX-19 on the hard drive.

$ inxi -Fxz
System:
  Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.9.2 
  Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Portable System: Gateway product: MX3210 v: 73.03 serial: <filter> 
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <filter> BIOS: Phoenix 
  v: 73.03 date: 01/06/2006 
Battery:
  ID-1: BAT0 charge: 20.9 Wh condition: 21.1/48.8 Wh (43%) 
  model: Gateway W32044L status: Charging 
CPU:
  Topology: Single Core model: Intel Celeron M bits: 32 type: MCP 
  arch: M Dothan rev: 8 L2 cache: 1024 KiB 
  flags: pae sse sse2 bogomips: 2793 
  Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
  vendor: Gateway driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.16.4 driver: openchrome 
  unloaded: fbdev,modesetting,vesa resolution: 1280x768~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
Network:
  Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  driver: N/A bus ID: 00:0e.0 
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine 
  v: N/A port: 1800 bus ID: 00:12.0 
  IF: eth0 state: down mac: <filter> 
Drives:
  Local Storage: total: 44.72 GiB used: 789.2 MiB (1.7%) 
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB 
  ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive 
  size: 7.46 GiB 
Partition:
  ID-1: / size: 364.0 MiB used: 2.2 MiB (0.6%) fs: overlay source: ERR-102 
  ID-2: swap-1 size: 896.0 MiB used: 52 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 114 Uptime: 4m Memory: 479.1 MiB used: 98.2 MiB (20.5%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

$ inxi -Fxz
System:
  Host: 3210antix19 Kernel: 4.9.200-antix.1-486-smp i686 bits: 32 
  compiler: gcc v: 8.3.0 Desktop: IceWM 1.9.2 
  Distro: antiX-19.1_386-base Marielle Franco 23 December 2019 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Portable System: Gateway product: MX3210 v: 73.03 serial: <filter> 
  Mobo: Gateway model: N/A v: Rev1.73.03 serial: <filter> BIOS: Phoenix 
  v: 73.03 date: 01/06/2006 
Battery:
  ID-1: BAT0 charge: 20.9 Wh condition: 21.1/48.8 Wh (43%) 
  model: Gateway W32044L status: Charging 
CPU:
  Topology: Single Core model: Intel Celeron M bits: 32 type: MCP 
  arch: M Dothan rev: 8 L2 cache: 1024 KiB 
  flags: pae sse sse2 bogomips: 2793 
  Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:
  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] 
  vendor: Gateway driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.4 driver: openchrome 
  unloaded: fbdev,modesetting,vesa resolution: 1280x768~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Gateway 
  driver: snd_via82xx v: kernel bus ID: 00:11.5 
  Sound Server: ALSA v: k4.9.200-antix.1-486-smp 
Network:
  Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN 
  driver: b43-pci-bridge v: N/A bus ID: 00:0e.0 
  Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Gateway driver: via-rhine 
  v: N/A port: 1800 bus ID: 00:12.0 
  IF: eth0 state: down mac: <filter> 
  IF-ID-1: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 44.72 GiB used: 4.69 GiB (10.5%) 
  ID-1: /dev/sda vendor: Hitachi model: HTS424040M9AT00 size: 37.26 GiB 
  ID-2: /dev/sdb type: USB vendor: Lexar model: USB Flash Drive 
  size: 7.46 GiB 
Partition:
  ID-1: / size: 7.65 GiB used: 3.92 GiB (51.2%) fs: ext4 dev: /dev/sda7 
  ID-2: swap-1 size: 896.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 128 Uptime: 2m Memory: 477.3 MiB used: 90.6 MiB (19.0%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36 

[Member Xecure]

Anonymous wrote:

did an experiment and
apparently it is a problem only with buster version of xorg. this
is a sid/bullseye core build up and it works in 16 bit and 24 bit
with no icon disappearing problem.

This means that (probably) building an iso for testing with the new xorg version instead of trying to hold the old xorg package from jessie is a better path.
Then this will probably be the last iso I build, as this will become a fruitless endeavor if newer xorg versions fix the issues with SIS and VIA video cards.

It is good news for the future of old machines. Less work for reviving them. This was going to be the next beta2 iso (740MB, autologin, semifix to virtualbox video, removed the firmware, included some of skidoo’s suggestions, added synaptic, could not get a good way to setup xorg.conf automatically that worked, so this will not be included), but I will next try to build an iso with bullseyes repos to see if it will boot for marcelocripe.

Thanks for all the tests, linuxdaddy. It lead to a possible better path than keeping an alternative separate version with low support.

Thank you everyone for participating. This was a learning experience for me.

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

[Anonymous]

provide (and we already have) the tools that allows for the creation of spin-off works

a “Community Edition”, or multiple variations, is long overdue (years overdue).
The gitlab.com/antix-contribs group repository is in place, has been sitting idle for the past year.
The build-iso tool has been (published, documented and) available for several years.

decide on key base components and make sure that the menu and access to them is consistent, clean and clear.

Can 3 people even find agreement in what are the “key base components”?
rox-filer? In the absence of the gtk2 library stack, it’s dead.
lxappearance: It’s largely unable to deal with gtk3 personalizations, and no capabilities-ehnanced followon version is on the horizon (lxde team has migrated to Qt-based theming).
spacefm: someone during the past week expressed an interest in submitting improved localizations. Good luck figuring out how to contact “upstream” for that (stevep@mx “maintains” a package, but afaik no project repository exists to accept pull requests)

The “key base components”, after we fuss over making “access to them” consistent… we’re saddled with the fact that their BEHAVIOR is not consistent. rox “Desktop” directory and spaceFM “Desktop” differ, as does the behavior when interacting with desktop items. Some of the pre-installed programs would abide “delete means ‘move to Trash'” if a trash directory is available, others would hard unlink regardless, and yet other programs will silently create a Trash directory, as needed, if such does not already exist. Some of the pre-installed programs will (do) abide the antixCC user-assigned “preferred applications”, others do not.

I don’t see either MX Linux or antiX catering primarily to a Windows based user base

Unsure the meaning of “see” in that comment.
Do not foresee, vs do not realize//recognize?

Last year I initiated a topic regarding this apparent schism
(lean-n-mean, vs magicky-userfriendly and PRETTY!)

Also last year (hmm, well, it seems like just last year), I opined:
“BobC is a programmer, he just doesn’t realize it yet.”

Recognition of SIGs (special interest groups) and issuance of “community respins” seems like a healthy way to move forward. Seeing the word “didactic” here several times recently, prompted me to (re)visit an online dictionary. My off-the-cuff definition would have been along the lines of “Teach a man to fish, vs feed a man a fish” ~~ and I have worried that antiX’ identity is indeed drifting. “Fried or baked fish? Ya want breading, or batter? Okay, and do ya want fries with that?”

Our twice-banned provocateur (“Queen of the Galactic School of Design”) has made a spate of posts to distrowatch weekly during the past few weeks. His/her/their description of MX Linux is scathing ~~ “[they are] design barbarians“. My point in mentioning this is to underscore the fact that pandering to “customers” (consumers) is a losing proposition; while consuming their free meal, they inevitably “find a bone”.

Linux BBQ was (waaaaay) too bent on remaining lean-n-mean. Defunct. (despite its solid “identity”)
CrunchyLabs, what is its identity? The userbase seems like a happy band of lean-ish supplicants, yet the forum contains a sprinkling of “didactic” topics and user contribs. A year ago I stopped posting at MX forum after the mods repeatedly beat me up and took my lunch money, but I still read, and… hey HEY lookit ’em go! SIGs (special interest groups) and issuance of “community respins”…

[Moderator Brian Masinick]

I truly believe that the great features of our distribution are:

1. It works very well on both new and old hardware but it specifically intends to be “lean and mean” – or another way to say the same thing is that it is efficient in the use of resources so that it runs very well across a very broad range of hardware.

2. The primary intention is to create a system that works particularly well on old hardware, much of which has been abandoned by many other operating systems.

3. While not explicitly supported in other ways, antiX is also extremely customizable; in other words, the experienced user can make a custom configuration that works perfectly for them.

4. antiX recognizes the prominent availability of small portable USB ‘sticks’ that allow the capability to put the contents into your pocket or keychain, carry it with you and run it, either on your own portable device or run it on another system.

We may not be the only ones with some of these technologies, but the combination antiX offers is a fresh, current, relevant technology that works on systems all around the world. It is unique in the sense that nobody else offers quite the same approach as we do, and it is freely available to use and modify for personal use as you see fit (according to the license provided).

Despite different preferences that various people in our community have, it is readily apparent that antiX works extremely well for an extensive group of people.

Sincere thanks to everyone, beginning with anticapitalista, and extending to developers, community members, newcomers, people with ideas, and more. We won’t always agree on everything, and yet this distribution works great for a very diverse community. Thanks again to all who participate!

--
Brian Masinick