- This topic has 9 replies, 8 voices, and was last updated Mar 31-10:31 pm by caprea.
-
Posts
-
olsztyn
From my perspective and the various hardware I have been testing antiX 23 Beta the only significant issue I had was initially missing system-config-printer. However this was quickly resolved by installation of the existing antiX version and then updating to the latest 1.5.18 one, thanks anticapitalista, who developed and to @Caprea, who pointed to the location.
Other than that antiX 23 Beta works fine in all my testing and has become my primary day-to-day system I am running after putting in place all my individual customizations.
What are the remaining significant issues encountered in antiX 23, not counting:
– Perfecting various translation details
– Various IceWM options, such as various inconsistent behavior of Trashcan, menu or toolbar options, disappearing Conky, etc., etc…Disclaimer: The examples above may be considered very significant to some users. I just wanted to separate issues resulting from antiX desktop customizations from core antiX system and desktop issues…
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersXunzi_23
Reading in antiX-23-beta1-runit-full (64bit) for testing
The thread started by anticapitalistaShould provide enlightenment.
PPC
For now the only thing I noticed was that I have to solve the problem of 2 zzzfm toolbar icons using the same keys and wingrid uses, in jwm and fluxbox…
What “inconsistent behavior of Trashcan”? I do have to try to implement a check for lack of diskspace when using the Trashcan (I almost forgot about that).
Since I rarely use Conky, I did not notice any problem with it, it always appears if I summon it…
There are some programs that do not install using Package Manager (not an antiX problem, but changes from the creators of those pieces of software).
P.
Thank you PPC!
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
anticapitalista
The biggest remaining ‘issue’ is to set up our antiX bookworm repos.
Once that is done, Repo Manager should work properly.
We also need to fix the various non-free packages in the Package Installer (not high priority at the moment).Some other changes (same for MX Linux):
* Installer will support swapfile creation. The autoinstall option will set up a swapfile rather than a swap partition by default.
* Live system and installer will create home folders with permissions defined by /etc/adduser.conf, or 0700 by default. Currently we use 755, but 0700 is the debian default.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
dolphin_oracle
* Live system and installer will create home folders with permissions defined by /etc/adduser.conf, or 0700 by default. Currently we use 755, but 0700 is the debian default.
On that change, I’m having trouble forking the live intrd gitlab repo for some reason. But I’ll get the change to you once I figure out what I’m doing wrong with gitlab.
blur13
“The autoinstall option will set up a swapfile rather than a swap partition by default”
Why? I’m not knowledgeable in this area so I’d be curious to learn the motivation for this. One advantage of a swap partition, that I’ve noticed, is that it can be shared among several Linux installations.
* Live system and installer will create home folders with permissions defined by /etc/adduser.conf, or 0700 by default. Currently we use 755, but 0700 is the debian default.
Great change. Thank you… Although strictly speaking this would be considered an enhancement.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
Brian Masinick
“The autoinstall option will set up a swapfile rather than a swap partition by default”
Why? I’m not knowledgeable in this area so I’d be curious to learn the motivation for this. One advantage of a swap partition, that I’ve noticed, is that it can be shared among several Linux installations.
I multi-boot too. I can’t remember the last time that any of my systems, even the “old ones”, have actually used swap.
The last time any of my systems used swap was when I had a 256 MB Dell Dimension 4100 desktop. Running KDE, I could run out of swap with just a browser and one other app; switching between processes would cause a swap and then the running process (ONLY) would be in usable memory because the size of the apps grew and used all of it. Even if it was 512 MB, same thing. Swap did work quite nicely, though swapping tasks in and out consumed time. Hopefully most of us don’t actually use swap often.The other “purpose” for swap is for suspend and hibernate actions. Ever since the small memory Dell, everything since has run 100% in memory for ALL processes; only activating a suspend or hibernate used swap; I hardly suspend or hibernate, so as far as I’m concerned, I don’t care where (or if) we have swap; those with very limited resources will definitely care.
If a swapfile can activate only if needed, it could in theory use available space.
“It’s easier to grow or shrink a swap file than a swap partition in many cases, so a swap file offers flexibility there. You can also move a swap file to a different disk, so it can be placed away from disks that typically see intense I/O operations, which can be a benefit for performance.”
Jul 18, 2022 https://kodekloud.com/community/t/swap-file-vs-swap-partition-when-to-use-what-any-disadvantages-or-advantage/146383--
Brian Masinick
caprea
When someone multiboots, they do not use the autoinstall option.
- You must be logged in to reply to this topic.
