Forum › Forums › antiX-development › Development › antiX-23-alpha1-runit-full (64bit) for testing
Tagged: <!-- comment
- This topic has 436 replies, 24 voices, and was last updated Mar 21-8:50 pm by Brian Masinick.
-
AuthorPosts
-
February 4, 2023 at 12:07 am #98808Moderator
Brian Masinick
::Do the *default* antiX 4.19/5.10 kernels on antiX-23 alpha (live or installed) show any marked differences from antiX-22 or earlier?
I’m certain and if I understand your tests correctly that a 6 series kernel on *any* antiX will have higher RAM usage. – please confirm – thanksBoth the 5 and 6 series kernels on antiX 22 used fewer resources than any of the scenarios I ran with either the 4 or 5 series kernels for antiX 23 so the overhead is not coming from the kernels, it’s coming from the method used in the Alpha build.
The xanmod1 6.1.9 kernel I used on antiX 22 unexpectedly used fewer resources on the Dell than it did on either of the test kernels.
--
Brian MasinickFebruary 4, 2023 at 4:18 am #98810Memberolsztyn
::We are indeed using more memory in this version – straight from boot, on my Dell I’m using
$ free -h
total used free shared buff/cache available
Mem: 7.7Gi 457Mi 6.9Gi 52Mi 611Mi 7.3Gi
Swap: 8.0Gi 0B 8.0Gi
demo@antix1:~I want to confirm Brian’s observation on much higher (almost 290M more) memory used reported by ‘free -h’ on freshly booted antiX 23 vs. antiX 22 runit.
I do not know what this really means for using ‘free -h’ as memory footprint measurement however and why it shows that much higher under antiX 23, because measuring footprint using Lxtask both antiX 22 and antiX 23 are very much comparable, where antiX 23 appears just slightly higher, by just a few Mb than antiX 22.
Just to note, a similarly much higher memory footprint is reported by ‘free -h’ on antiX/Bookworm/SID than on antiX 22. So I am not sure if so much higher memory footprint reported by ‘free -h’ is to be taken for the face value.
My testing is on Thinkpad T410, i5, 6Mb. Tested with kernel 5.10.What I do notice – an additional process at-spi-bus-launcher seems to be running by default in antiX 23, which takes over 7Mb. I am not sure yet of the purpose of this process in antiX 23, especially because I do not see this process running in antiX/Bookworm.SID.
Aside from my above memory footprint observation:
– antiX 23 seems a head turner now, with the new wallpaper. Excellent. Huge initial impression.
– JWM default theme seems nicer than before, I think.
– No issues in operation so far…- This reply was modified 3 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersFebruary 4, 2023 at 10:32 am #98822MemberXunzi_23
::Sorry unable to join the party, not yet anyway.
green screen on both old and new kernel, never seen that before,
normal is only happens the antiX latest version. I use Kernel: 5.18.0-4-amd64 arch: x86_64 from debian,
the legacy kernel has booted fine up to this time.
The ISO sha256 sum is checked, usb stick was booting stable version until I rewrote this morning.
Stick was formatted after getting greenout. No errors from antiX usb write utility.
Screen messages and system Info attached.System runs fine, no high temeratures or other reported issues.
February 4, 2023 at 10:36 am #98826MemberPPC
::On my home computer- Ram after booting into zzz-icewm:
Conky: 178M/3.81G
“free -h” in the terminal: 381Mi
Task manager: 160/3.90CPU: 0% when idle
1% running zzzfm and firefox-esr showing only the forum (RAM: conky: 605; free -h: 874Mi; task-manager: 587MBI tested opening several .odt documents and one .pdf file using zzzfm- it worked perfectly and lightning fast, even in live mode… Writer launches in less than 3 seconds!
Edit: I’m using wi-fi via an USB dongle: no network problems to report, for now.
Edit2: I installed Ft10 on it- it runs fine, but, for some reason a few menu entries come up twice (the second one without icon and does not run anything: “Bluetooth” and “Add items to menu”, “app-select” and “adsl/ppp…”)
P.- This reply was modified 3 months ago by PPC.
- This reply was modified 3 months ago by PPC.
February 4, 2023 at 12:43 pm #98836Membercalciumsodium
::A comparison of memory at baseline of antiX21 and antiX23 a1 on the same computer. I tried to make both systems as similar to each other as possible: wallpaper, startup, etc.
For antiX21:
$ free -h total used free shared buff/cache available Mem: 2.4Gi 145Mi 2.0Gi 66Mi 240Mi 2.1Gi Swap: 2.0Gi 0B 2.0Gi jakersfan@antix1:~ $ inxi -b System: Host: antix1 Kernel: 6.1-8.1-liquorix-amd64 x86_64 bits: 64 Desktop: IceWM 2.8.0 Distro: antiX-21_x64-base Grup Yorum 31 October 2021For antiX23a1:
$ free -h total used free shared buff/cache available Mem: 2.4Gi 379Mi 1.9Gi 69Mi 310Mi 2.0Gi Swap: 2.0Gi 0B 2.0Gi jakersfan@antix1:~ $ inxi -b System: Host: antix1 Kernel: 6.1.9-2-liquorix-amd64 arch: x86_64 bits: 64 Desktop: IceWM v: 3.3.1 Distro: antiX-23-runit_x64-full Grup Yorum 3 February 2023The difference is about 234 Mb of used ram at baseline.
February 4, 2023 at 12:48 pm #98837Forum Admin
anticapitalista
::Posting output of
sudo ps_mem.pywould help to see what is taking up all that extra RAM.
I suspect Xorg.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
February 4, 2023 at 12:56 pm #98838MemberPPC
::sudo ps_mem.py
In my OS, this reports:
sudo ps_mem.py Private + Shared = RAM used Program 112.0 KiB + 21.5 KiB = 133.5 KiB runit 128.0 KiB + 24.5 KiB = 152.5 KiB runsvdir 148.0 KiB + 29.5 KiB = 177.5 KiB svlogd 148.0 KiB + 34.5 KiB = 182.5 KiB seatd 372.0 KiB + 113.5 KiB = 485.5 KiB dbus-launch 356.0 KiB + 298.5 KiB = 654.5 KiB udevil 364.0 KiB + 291.5 KiB = 655.5 KiB icewm-session 800.0 KiB + 432.5 KiB = 1.2 MiB desktop-session 824.0 KiB + 431.5 KiB = 1.2 MiB devmon 1.1 MiB + 355.0 KiB = 1.4 MiB runsv (12) 968.0 KiB + 584.5 KiB = 1.5 MiB getty (7) 904.0 KiB + 672.5 KiB = 1.5 MiB dbus-daemon (3) 1.0 MiB + 812.0 KiB = 1.8 MiB sudo (2) 1.6 MiB + 462.5 KiB = 2.0 MiB bash 1.4 MiB + 800.5 KiB = 2.2 MiB at-spi-bus-launcher 1.8 MiB + 653.5 KiB = 2.4 MiB udevd 2.2 MiB + 672.5 KiB = 2.8 MiB conky 3.6 MiB + 259.5 KiB = 3.9 MiB connmand 2.5 MiB + 2.4 MiB = 4.8 MiB fbxkb 3.3 MiB + 2.9 MiB = 6.2 MiB volumeicon 4.8 MiB + 1.4 MiB = 6.3 MiB slimski 5.3 MiB + 2.3 MiB = 7.6 MiB icewm 7.2 MiB + 645.5 KiB = 7.8 MiB wpa_supplicant 11.1 MiB + 4.5 MiB = 15.6 MiB zzzfm 12.2 MiB + 4.8 MiB = 17.0 MiB roxterm 82.5 MiB + 2.0 MiB = 84.5 MiB Xorg --------------------------------- 174.3 MiBI think that “free -h” is reporting the wrong value, for some reason???
February 4, 2023 at 1:14 pm #98844Member
marcelocripe
::Hello.
Olá.ISO: antiX-23-alpha1-runit_x64-full.iso
System:
Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc
v: 12.2.0 Desktop: IceWM v: 3.3.1
Distro: antiX-23-runit_x64-full Grup Yorum 3 February 2023
base: Debian GNU/Linux bookworm/sid
Machine:
Type: Laptop System: Hewlett-Packard product: HP G42 NoteBook PC
v: 049D110000202710000010000 serial: <superuser required>
Mobo: Hewlett-Packard model: 1484 v: 77.36 serial: <superuser required>
BIOS: Hewlett-Packard v: F.31 date: 10/18/2010
Battery:
ID-1: BAT0 charge: 27.3 Wh (96.5%) condition: 28.3/47.5 Wh (59.6%)
volts: 12.4 min: 10.8 model: Hewlett-Packard Primary status: N/A
CPU:
Info: dual core model: Pentium T4500 bits: 64 type: MCP
arch: Penryn Yorkfield rev: A cache: L1: 128 KiB L2: 1024 KiB
Speed (MHz): avg: 2255 high: 2256 min/max: 1200/2300 cores: 1: 2256
2: 2255 bogomips: 9177
Flags: ht lm nx pae sse sse2 sse3 ssse3
Graphics:
Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen5 bus-ID: 00:02.0
Device-2: Suyin HP Webcam-101 type: USB driver: uvcvideo bus-ID: 2-4:3
Display: server: X.Org v: 1.21.1.6 driver: X: loaded: intel gpu: i915
resolution: 1366×768~60Hz
OpenGL: renderer: Mesa Mobile Intel GM45 Express (CTG) v: 2.1 Mesa 22.3.3
direct render: Yes
Audio:
Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Sound Server-1: ALSA v: k5.10.142-antix.2-amd64-smp running: yes
Network:
Device-1: Realtek RTL8191SEvA Wireless LAN vendor: Hewlett-Packard
driver: rtl8192se v: kernel port: 3000 bus-ID: 02:00.0
IF: wlan0 state: down mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus-ID: 03:00.0
IF: eth0 state: down mac: <filter>
Info:
Processes: 141 Uptime: 3m Memory: 3.74 GiB used: 448.4 MiB (11.7%)
Init: runit runlevel: 2 Compilers: gcc: 12.2.0 Packages: 1625 Shell: Bash
v: 5.2.15 inxi: 3.3.19demo@antix1:~
$ free -m
total usada livre compart. buff/cache disponível
Mem.: 3832 420 3118 53 562 3412
Swap: 0 0 0
demo@antix1:~
$Conky displayed 181MB of RAM with no other windows open.
O Conky exibia 181 MB de memória RAM sem nenhuma outra janela aberta.February 4, 2023 at 1:19 pm #98846Membercalciumsodium
::Here are my updated numbers with conky + free -h + ps_mem.py:
antiX 21: Conky at baseline 165 Mb of RAM.
$ free -h total used free shared buff/cache available Mem: 2.4Gi 172Mi 2.0Gi 66Mi 240Mi 2.0Gi Swap: 2.0Gi 0B 2.0Gi jakersfan@antix1:~ $ sudo ps_mem.py [sudo] password for jakersfan: Private + Shared = RAM used Program 184.0 KiB + 43.5 KiB = 227.5 KiB acpid 196.0 KiB + 47.5 KiB = 243.5 KiB anacron 212.0 KiB + 37.5 KiB = 249.5 KiB gpm 216.0 KiB + 61.5 KiB = 277.5 KiB init 312.0 KiB + 80.5 KiB = 392.5 KiB cron 364.0 KiB + 142.5 KiB = 506.5 KiB dbus-launch 472.0 KiB + 36.5 KiB = 508.5 KiB rpc.idmapd 440.0 KiB + 119.5 KiB = 559.5 KiB rpc.statd 512.0 KiB + 170.5 KiB = 682.5 KiB rpcbind 364.0 KiB + 340.5 KiB = 704.5 KiB udevil 352.0 KiB + 354.5 KiB = 706.5 KiB icewm-session 640.0 KiB + 440.5 KiB = 1.1 MiB devmon 804.0 KiB + 433.5 KiB = 1.2 MiB desktop-session 724.0 KiB + 583.5 KiB = 1.3 MiB redshift 856.0 KiB + 536.0 KiB = 1.4 MiB getty (6) 748.0 KiB + 672.0 KiB = 1.4 MiB dbus-daemon (2) 1.6 MiB + 40.5 KiB = 1.7 MiB smartd 1.4 MiB + 319.5 KiB = 1.7 MiB ntpd 1.7 MiB + 88.5 KiB = 1.7 MiB elogind-daemon 1.5 MiB + 337.5 KiB = 1.9 MiB connmand 1.4 MiB + 471.5 KiB = 1.9 MiB bash 1.8 MiB + 53.5 KiB = 1.9 MiB rsyslogd 1.4 MiB + 511.5 KiB = 1.9 MiB sudo 2.6 MiB + 447.5 KiB = 3.0 MiB udevd 3.2 MiB + 27.5 KiB = 3.2 MiB haveged 3.8 MiB + 955.5 KiB = 4.7 MiB conky 4.9 MiB + 617.5 KiB = 5.5 MiB wpa_supplicant 5.3 MiB + 2.6 MiB = 7.8 MiB icewm 4.4 MiB + 3.5 MiB = 7.9 MiB volumeicon 7.4 MiB + 1.0 MiB = 8.4 MiB slimski 9.8 MiB + 5.3 MiB = 15.1 MiB roxterm 17.3 MiB + 1.6 MiB = 18.9 MiB Xorg 21.8 MiB + 3.8 MiB = 25.7 MiB rox --------------------------------- 124.2 MiB ================================= jakersfan@antix1:~ $ inxi -b System: Host: antix1 Kernel: 6.1-8.1-liquorix-amd64 x86_64 bits: 64 Desktop: IceWM 2.8.0 Distro: antiX-21_x64-base Grup Yorum 31 October 2021antiX 23 a1: Conky at baseline 182 Mb of RAM.
$ free -h total used free shared buff/cache available Mem: 2.4Gi 356Mi 2.0Gi 65Mi 306Mi 2.1Gi Swap: 2.0Gi 0B 2.0Gi jakersfan@antix1:~ $ sudo ps_mem.py [sudo] password for jakersfan: Private + Shared = RAM used Program 112.0 KiB + 20.5 KiB = 132.5 KiB runit 132.0 KiB + 25.5 KiB = 157.5 KiB runsvdir 148.0 KiB + 34.5 KiB = 182.5 KiB svlogd 148.0 KiB + 36.5 KiB = 184.5 KiB seatd 328.0 KiB + 147.5 KiB = 475.5 KiB dbus-launch 364.0 KiB + 284.5 KiB = 648.5 KiB icewm-session 364.0 KiB + 319.5 KiB = 683.5 KiB udevil 644.0 KiB + 419.5 KiB = 1.0 MiB devmon 692.0 KiB + 447.0 KiB = 1.1 MiB dbus-daemon (2) 808.0 KiB + 425.5 KiB = 1.2 MiB desktop-session 740.0 KiB + 508.5 KiB = 1.2 MiB redshift 1.1 MiB + 379.0 KiB = 1.5 MiB runsv (12) 952.0 KiB + 609.5 KiB = 1.5 MiB getty (7) 944.0 KiB + 815.0 KiB = 1.7 MiB sudo (2) 1.5 MiB + 463.5 KiB = 2.0 MiB bash 1.7 MiB + 649.5 KiB = 2.4 MiB udevd 2.2 MiB + 602.5 KiB = 2.8 MiB conky 3.6 MiB + 291.5 KiB = 3.9 MiB connmand 6.9 MiB + 638.5 KiB = 7.6 MiB wpa_supplicant 5.9 MiB + 2.4 MiB = 8.2 MiB icewm 5.1 MiB + 3.3 MiB = 8.5 MiB volumeicon 7.4 MiB + 1.5 MiB = 8.9 MiB slimski 11.4 MiB + 5.4 MiB = 16.8 MiB roxterm 22.4 MiB + 4.1 MiB = 26.5 MiB rox 61.4 MiB + 1.9 MiB = 63.3 MiB Xorg --------------------------------- 162.5 MiB ================================= jakersfan@antix1:~ $ inxi -b System: Host: antix1 Kernel: 6.1.9-2-liquorix-amd64 arch: x86_64 bits: 64 Desktop: IceWM v: 3.3.1 Distro: antiX-23-runit_x64-full Grup Yorum 3 February 2023The RAM difference in Conky and ps_mem.py are not as dramatic as in the free -h method.
February 4, 2023 at 1:26 pm #98847Forum Admin
anticapitalista
::So Xorg RAM used accounts for the difference. (almost 45MB more!)
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
February 4, 2023 at 1:43 pm #98849Moderator
Brian Masinick
::Good finding. Regardless of the memory consumption my Dell Inspiron 5558 has plentiful memory and the Alpha build, even with the minor issues is a first rate Alpha build.
I challenge anyone to find more reliable builds than those in our family of distributions. Both antiX and MX Linux have a long history of reliable software and the first builds are quite usable.
I will check ps_mem.py next time I run the image. Meanwhile I trust the data and the explanation just provided. It makes sense to me.
--
Brian MasinickFebruary 4, 2023 at 3:01 pm #98852MemberXunzi_23
::Was now able to run on a T420, same stick, no problems at all with either kernel.
Will have to switch to rox as my preference.Really like the look with new wallpaper, now need some flash icons to match :-).
No way found to boot the beta on my desktop setup, as always freezing or crashing
with the reported green screen. Everything unresponsive so unsure what happens.
Busy but can try some boot codes from BitJam tomorrow and hope to get some sensible
output for fault finding..Will try and test on another couple of desktop setups tomorrow, recently I ran in to
same green screen crash on one of those. Similar setup to mine, I5 and Nvidia card
gigabyte board.- This reply was modified 3 months ago by Xunzi_23.
February 4, 2023 at 3:07 pm #98854Member
marcelocripe
::The ISO boot “antiX-23-alpha1-runit_x64-full.iso” took place on a USB device prepared with Ventoy, this is just a live boot.
The F1 option is now next to the F2 option in the antiX ISO boot and this is great, before the F1 option was not visible.
Now I want to make some suggestions:
1 – Place the “Unplug Removable Device” icon (original text in English to avoid any misunderstanding) at the far left, as it was always further to the left in previous editions of antiX. Please, don’t answer me so I can use “IceWM Toolbar Icon Manager” to organize it as I’m suggesting.
My suggestion:
prog “Unplug Removable Device” /usr/share/icons/papirus-antix/48×48/devices/drive-removable-media-usb.png unplugdrive.sh
prog “antiX Updater” /usr/share/icons/papirus-antix/48×48/categories/software-sources.png /usr/local/bin/yad-updater
prog “Software Installer” /usr/share/icons/papirus-antix/48×48/apps/packageinstaller.png su-to-root -X -c packageinstaller
prog “File Manager” /usr/share/icons/papirus-antix/48×48/apps/file-manager.png desktop-defaults-run -fm
prog “Web Browser” /usr/share/icons/papirus-antix/48×48/apps/web-browser.png desktop-defaults-run -b
prog “IceWM Toolbar Icon Manager” /usr/share/icons/papirus-antix/48×48/categories/icewm_editor.png /usr/local/bin/icewm-toolbar-icon-manager.sh2 – I thank you for correcting the “pt_BR” identifier in the “/usr/share/antiX/localisation” folder.
3 – The file “refresh-menu.desktop.desktop” continues with the entry like this “Exec=desktop-menu –write-out-global”, by chance it should be with “sudo desktop-menu –write-out-global ” for the menu to work?
4 – Now I’m going to look at the menus and compare with antiX 21/22.
“antiX” submenu: All menus are translated to “pt_BR”, except “locale-antix-user.desktop” and “locale-antix-system.desktop”. Please use the translated .desktop files on GitLab (https://gitlab.com/antix-contribs/antix-desktop-files/-/tree/main/.desktop).
“Accessories” submenu: They will only be 100% translated to “pt_BR” when all our translated .desktop files are used by the creators of the respective programs. I’ve already found out that this will be impossible, because many developers don’t care about translations or have refused to use our translations. For example, the creators of Firejail, Celluloid, MPV, DeSmuMe, etc. If any of the programs that are in the antiX full ISO are maintained by the antiX development team and are on this list of menus that need to be translated, please use our translations.
“Development” submenu: Only Geany needs to be translated.
“Graphics” submenu: It remains to be translated to “pt_BR” – “Gtkam Digital Camera Browser”, “Mirage” and “LibreOffice Draw” (the latter is an “impossible mission”).
“Internet” submenu: Still need to be translated to “pt_BR” – “Ceni”, “Claws Mail”, “Dillo”, “Firefox ESR”, “HexChat”, “Links 2”, “Modem Manager GUI”, “Sakis3G” and “Transmission”.
“Games” submenu: Still need to be translated to “pt_BR” – “DOSBox Emulator” and “Mahjongg”.
Submenu “Multimídia”: Need to be translated to “pt_BR” – “Asunder CD Ripper”, “Celluloid” (I already explained the reason above), “SMTube”, “WinFF” (this project is unfortunately abandoned and therefore will never be merged with our translations) and “XMMS”.
“Preferences” submenu: Still need to be translated to “pt_BR” – “Bluetooth Manager”, “Screenlight” and “User Language”. The “blueman-manager.desktop” and “User Language” files are an old version and it is not the file that was used in antiX 22, please compare with our GitLab file or the file used in antiX 22.
“System” submenu: It remains to be translated to “pt_BR” – “Firetools” (I already explained the reason above), “Modem Manager GUI” and “ROXTerm”.5 – I missed having a “trash.desktop”, without it the zzzFM right-click menu won’t have the translations. Trash-related translations could be in the “trash.desktop” file.
6 – On the zzzFM right-click menu, I suggest changing the position of the “Delete (Shitf + Delete)” option to be below the “Send to Trash” option (this menu is not translated to “pt_US”) . I believe it is safer to have the “Send to Trash (Delete)” option below the Rename option (F2).
Rename (F2)
Send to Trash (Delete)
Delete (Shift+Delete)As soon as possible, I will boot the ISO “antiX-23-alpha1-runit_x64-full.iso” on computers older than the one I posted in my previous message.
– – – – –
A inicialização da ISO “antiX-23-alpha1-runit_x64-full.iso” ocorreu em um dispositivo USB preparado com o Ventoy, trata-se apenas uma inicialização ao vivo.
A opção F1 agora está ao lado da opção F2 na inicialização da ISO do antiX e isso é muito bom, antes a opção F1 não estava visível.
Agora eu pretendo apresentar algumas sugestões:
1 – Posicionar o ícone do “Unplug Removable Device” (texto original em Inglês para evitar qualquer mal entendido) na extremidade da esquerda, pois ele sempre esteve mais a esquerda nas edições anteriores do antiX. Por favor, não me respondam para eu utilizar o “IceWM Toolbar Icon Manager” para deixar organizado como eu estou sugerindo.
A minha sugestão:
prog “Unplug Removable Device” /usr/share/icons/papirus-antix/48×48/devices/drive-removable-media-usb.png unplugdrive.sh
prog “antiX Updater” /usr/share/icons/papirus-antix/48×48/categories/software-sources.png /usr/local/bin/yad-updater
prog “Software Installer” /usr/share/icons/papirus-antix/48×48/apps/packageinstaller.png su-to-root -X -c packageinstaller
prog “File Manager” /usr/share/icons/papirus-antix/48×48/apps/file-manager.png desktop-defaults-run -fm
prog “Web Browser” /usr/share/icons/papirus-antix/48×48/apps/web-browser.png desktop-defaults-run -b
prog “IceWM Toolbar Icon Manager” /usr/share/icons/papirus-antix/48×48/categories/icewm_editor.png /usr/local/bin/icewm-toolbar-icon-manager.sh2 – Eu agradeço por você corrigir o identificador “pt_BR” na pasta “/usr/share/antiX/localisation”.
3 – O arquivo “refresh-menu.desktop.desktop” continua com a entrada assim “Exec=desktop-menu –write-out-global”, por acaso deveria ser com “sudo desktop-menu –write-out-global” para o menu funcionar?
4 – Agora eu vou olhar para os menus e comparar com o antiX 21/22.
Submenu “antiX”: Todos os menus estão traduzidos para “pt_BR”, exceto “locale-antix-user.desktop” e “locale-antix-system.desktop”. Por favor, utilize os arquivos .desktop traduzidos no GitLab (https://gitlab.com/antix-contribs/antix-desktop-files/-/tree/main/.desktop).
Submenu “Acessórios”: Só ficarão 100% traduzidos para “pt_BR” quando todos os nossos arquivos .desktop traduzidos forem utilizados pelos criadores dos respectivos programas. Eu já descobri que isso será impossível, porque vários desenvolvedores não dão a mínima para as traduções ou se recusaram a utilizar as nossas traduções. Por exemplo, os criadores do Firejail, Celluloid, MPV, DeSmuMe, etc. Se algum dos programas que estão na ISO full do antiX for mantido pela equipe de desenvolvimento do antiX estiver neste relação dos menus que faltam ser traduzidos, por favor, utilize as nossas traduções.
Submenu “Desenvolvimento”: Só falta o Geany ser traduzido.
Submenu “Gráficos”: Faltam ser traduzidos para “pt_BR” – “Gtkam Digital Camera Browser”, “Mirage” e “LibreOffice Draw” (este último trata-se de uma “missão impossível”).
Submenu “Internet”: Faltam ser traduzidos para “pt_BR” – “Ceni”, “Claws Mail”, “Dillo”, “Firefox ESR”, “HexChat”, “Links 2”, “Modem Manager GUI”, “Sakis3G” e “Transmission”.
Submenu “Jogos”: Faltam ser traduzidos para “pt_BR” – “DOSBox Emulator” e “Mahjongg”.
Submenu “Multimídia”: Faltam ser traduzidos para “pt_BR” – “Asunder CD Ripper”, “Celluloid” (eu já expliquei acima o motivo), “SMTube”, “WinFF” (este projeto infelizmente está abandonado e por isso nunca será mesclado com as nossas traduções) e “XMMS”.
Submenu “Preferências”: Faltam ser traduzidos para “pt_BR” – “Bluetooth Manager”, “Screenlight” e “User Language”. Os arquivos “blueman-manager.desktop” e “User Language” são uma versão antiga e não é o arquivo que foi utilizado no antiX 22, por favor, compare com o nosso arquivo do GitLab ou com o arquivo utilizado no antiX 22.
Submenu “Sistema”: Faltam ser traduzidos para “pt_BR” – “Firetools” (eu já expliquei acima o motivo), “Modem Manager GUI” e “ROXTerm”.5 – Eu senti falta de ter um “trash.desktop”, sem ele o menu do clique com o botão direito do zzzFM não terá as traduções. As traduções relacionadas a Lixeira poderiam estar no arquivo “trash.desktop”.
6 – Sobre o menu do clique com o botão direito do zzzFM, eu sugiro alterar a posição da opção “Excluir (Shitf + Delete)” para ficar abaixo da opção “Send to Trash” (este menu não está traduzido para “pt_BR”). Eu acredito ser mais seguro a opção “Send to Trash (Delete)” ficar abaixo da opção Renomear (F2).
Renamear (F2)
Send to Trash (Delete)
Excluir (Shitf + Delete)Assim que for possível, eu irei inicializar a ISO “antiX-23-alpha1-runit_x64-full.iso” em computadores mais antigos que este que eu postei na minha mensagem anterior.
February 4, 2023 at 3:14 pm #98856Member
marcelocripe
::I just verified that zzzFM was unable to mount the hard disk partition with user “demo”. The partition is of type ext4 and has antiX 22 installed. Normally we can mount ext4 partitions with the regular user without the need for root. This appears to be a problem.
– – – – –
Eu acabei de verificar que o zzzFM não conseguiu montar a partição do disco rígido com o usuário “demo”. A partição é do tipo ext4 e possui o antiX 22 instalado. Normalmente nós conseguimos montar as partições ext4 com o usuário comum sem a necessidade do root. Isso parece ser um problema.
February 4, 2023 at 3:19 pm #98857Member
marcelocripe
::About the kernel, my suggestion is not to use the terms “Modern Kernel” or “Legacy Kernel”, I think it’s better to display the kernel version number. The concept “Legacy” or “Modern” is very relative and is not consistent, the number still presents the accuracy of the information.
As for the version that will be used, I don’t have enough technical knowledge to make suggestions about it.– – – – –
Sobre o kernel, a minha sugestão não é utilizar o termos “Kernel Moderno” ou “Kernel Legado”, eu acho melhor que seja exibido o número da versão do kernel. O conceito “Legado” ou “Moderno” é muito relativo e não é consistente, o número ainda apresenta a exatidão na informação.
Quanto a versão que será utilziada, eu não tenho conhecimentos técnicos suficientes para apresentar sugestões a respeito disso. -
AuthorPosts
- You must be logged in to reply to this topic.

