- This topic has 324 replies, 28 voices, and was last updated May 12-8:19 am by Robin.
-
Posts
-
marcelocripe
demo@antix1:~
$ inxi -G
Graphics:
Device-1: Intel 82G33/G31 Express Integrated Graphics driver: i915 v: kernel
Display: server: X.Org v: 1.21.1.7 driver: X: loaded: intel dri: i915
gpu: i915 resolution: 1024×768~60Hz
API: OpenGL v: 2.1 Mesa 22.3.6 renderer: i915 (: G33)
demo@antix1:~
$
anticapitalista
Today’s upgrade will bring in libelogind0 (pulled by new Xorg).
systemd/elogind-free versions are ready – they just need to be added to the repos.dave has added the latest antiX version to the repos (thanks).
Depending on which repos you are using,you should see the antiX versions showing up soon.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Brian Masinick
Today’s upgrade will bring in libelogind0 (pulled by new Xorg).
systemd/elogind-free versions are ready – they just need to be added to the repos.dave has added the latest antiX version to the repos (thanks).
Depending on which repos you are using,you should see the antiX versions showing up soon.Thanks; I’ll keep an eye out and check the processes and services the next time I update antiX 23 Beta 1.
--
Brian Masinickolsztyn
Thanks; I’ll keep an eye out and check the processes and services the next time I update antiX 23 Beta 1.
I saw those Debian versions of Xorg but I simply did not include them in the update process. In general, whenever there is an updated Debian version of any component, overriding antiX version I do not include these components as part of update.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
Thanks; I’ll keep an eye out and check the processes and services the next time I update antiX 23 Beta 1.
I saw those Debian versions of Xorg but I simply did not include them in the update process. In general, whenever there is an updated Debian version of any component, overriding antiX version I do not include these components as part of update.
If I happen to get the wrong versions, I’ll simply replace them; this is a test system and it’s working quite well, but I also have multiple instances and copies of our stable (and test) versions, so I’m not afraid to test, experiment, mess up, and redo if necessary. Hopefully our updated version(s) will simply replace any other instances; if not, I’ll deal with them accordingly.
By the way, I *did* have a situation not that long ago where a Debian version of something crept in; anticapitalista spotted it and mentioned it to me; it wasn’t very difficult at all to correct, but it was easy to miss when not looking closely enough at which versions of key processes were running.
--
Brian MasinickBrian Masinick
I’m pretty sure I just picked up the fix, but in case I missed something, what follows is the memory report followed by a process list.
If I’ve overlooked anything, let me know, thanks!sudo ps_mem.py Private + Shared = RAM used Program 112.0 KiB + 26.5 KiB = 138.5 KiB runit 128.0 KiB + 39.5 KiB = 167.5 KiB runsvdir 144.0 KiB + 46.5 KiB = 190.5 KiB seatd 416.0 KiB + 146.5 KiB = 562.5 KiB dbus-launch 368.0 KiB + 306.5 KiB = 674.5 KiB icewm-session 364.0 KiB + 337.5 KiB = 701.5 KiB udevil 472.0 KiB + 394.5 KiB = 866.5 KiB getty (3) 632.0 KiB + 427.5 KiB = 1.0 MiB devmon 720.0 KiB + 441.0 KiB = 1.1 MiB dbus-daemon (2) 816.0 KiB + 420.5 KiB = 1.2 MiB desktop-session 920.0 KiB + 356.0 KiB = 1.2 MiB runsv (10) 888.0 KiB + 829.0 KiB = 1.7 MiB sudo (2) 1.6 MiB + 496.5 KiB = 2.1 MiB udevd 1.9 MiB + 473.5 KiB = 2.3 MiB bash 2.2 MiB + 726.5 KiB = 2.9 MiB conky 3.6 MiB + 321.5 KiB = 4.0 MiB connmand 3.4 MiB + 636.5 KiB = 4.0 MiB cupsd 4.7 MiB + 1.5 MiB = 6.2 MiB slimski 3.3 MiB + 3.3 MiB = 6.6 MiB volumeicon 6.9 MiB + 564.5 KiB = 7.5 MiB wpa_supplicant 5.4 MiB + 2.5 MiB = 7.9 MiB icewm 12.5 MiB + 5.2 MiB = 17.7 MiB roxterm 23.0 MiB + 3.8 MiB = 26.8 MiB zzzfm 105.1 MiB + 1.6 MiB = 106.7 MiB Xorg --------------------------------- 204.2 MiB ================================= [antixBeta-hp-14-fq-1025]/home/masinick: > ps ax PID TTY STAT TIME COMMAND 1 ? Ss 0:00 runit 2 ? S 0:00 [kthreadd] 3 ? I< 0:00 [rcu_gp] 4 ? I< 0:00 [slub_flushwq] 5 ? I< 0:00 [netns] 6 ? I 0:00 [kworker/0:0-pm] 7 ? I< 0:00 [kworker/0:0H-events_highpri] 8 ? I 0:00 [kworker/u24:0-events_unbound] 9 ? I< 0:00 [mm_percpu_wq] 10 ? I 0:00 [rcu_tasks_kthread] 11 ? I 0:00 [rcu_tasks_rude_kthread] 12 ? I 0:00 [rcu_tasks_trace_kthread] 13 ? S 0:00 [ksoftirqd/0] 14 ? I 0:00 [rcu_preempt] 15 ? S 0:00 [rcub/0] 16 ? S 0:00 [rcu_exp_gp_kthread_worker] 17 ? S 0:00 [rcu_exp_par_gp_kthread_worker] 18 ? S 0:00 [migration/0] 19 ? S 0:00 [cpuhp/0] 20 ? S 0:00 [cpuhp/1] 21 ? S 0:00 [migration/1] 22 ? S 0:00 [ksoftirqd/1] 23 ? I 0:00 [kworker/1:0-events] 24 ? I< 0:00 [kworker/1:0H-events_highpri] 25 ? I 0:00 [kworker/0:1-mm_percpu_wq] 26 ? S 0:00 [cpuhp/2] 27 ? S 0:00 [migration/2] 28 ? S 0:00 [ksoftirqd/2] 29 ? I 0:00 [kworker/2:0-events] 30 ? I< 0:00 [kworker/2:0H-events_highpri] 31 ? S 0:00 [cpuhp/3] 32 ? S 0:00 [migration/3] 33 ? S 0:00 [ksoftirqd/3] 34 ? I 0:00 [kworker/3:0-events] 35 ? I< 0:00 [kworker/3:0H-events_highpri] 36 ? S 0:00 [cpuhp/4] 37 ? S 0:00 [migration/4] 38 ? S 0:00 [ksoftirqd/4] 39 ? I 0:00 [kworker/4:0-events] 40 ? I< 0:00 [kworker/4:0H-events_highpri] 41 ? S 0:00 [cpuhp/5] 42 ? S 0:00 [migration/5] 43 ? S 0:00 [ksoftirqd/5] 44 ? I 0:00 [kworker/5:0-events] 45 ? I< 0:00 [kworker/5:0H-events_highpri] 46 ? S 0:00 [cpuhp/6] 47 ? S 0:00 [migration/6] 48 ? S 0:00 [ksoftirqd/6] 49 ? I 0:00 [kworker/6:0-events] 50 ? I< 0:00 [kworker/6:0H-events_highpri] 51 ? S 0:00 [cpuhp/7] 52 ? S 0:00 [migration/7] 53 ? S 0:00 [ksoftirqd/7] 54 ? I 0:00 [kworker/7:0-events] 55 ? I< 0:00 [kworker/7:0H-events_highpri] 56 ? S 0:00 [cpuhp/8] 57 ? S 0:00 [migration/8] 58 ? S 0:00 [ksoftirqd/8] 59 ? I 0:00 [kworker/8:0-events] 60 ? I< 0:00 [kworker/8:0H-events_highpri] 61 ? S 0:00 [cpuhp/9] 62 ? S 0:00 [migration/9] 63 ? S 0:00 [ksoftirqd/9] 64 ? I 0:00 [kworker/9:0-events] 65 ? I< 0:00 [kworker/9:0H-events_highpri] 66 ? S 0:00 [cpuhp/10] 67 ? S 0:00 [migration/10] 68 ? S 0:00 [ksoftirqd/10] 69 ? I 0:00 [kworker/10:0-mm_percpu_wq] 70 ? I< 0:00 [kworker/10:0H-kblockd] 71 ? S 0:00 [cpuhp/11] 72 ? S 0:00 [migration/11] 73 ? S 0:00 [ksoftirqd/11] 74 ? I 0:00 [kworker/11:0-events] 75 ? I< 0:00 [kworker/11:0H-events_highpri] 77 ? I 0:00 [kworker/u24:1-events_unbound] 78 ? I 0:00 [kworker/u24:2-events_power_efficient] 79 ? I 0:00 [kworker/u24:3-events_unbound] 80 ? I 0:00 [kworker/u24:4-flush-259:0] 81 ? I 0:00 [kworker/u24:5-nvme-wq] 82 ? I 0:00 [kworker/u24:6-events_unbound] 83 ? I 0:00 [kworker/u24:7-events_unbound] 84 ? I 0:00 [kworker/u24:8-events_unbound] 85 ? I 0:00 [kworker/u24:9-events_unbound] 86 ? I 0:00 [kworker/u24:10-events_unbound] 87 ? I 0:00 [kworker/u24:11] 88 ? S 0:00 [kdevtmpfs] 89 ? I< 0:00 [inet_frag_wq] 90 ? S 0:00 [oom_reaper] 91 ? I< 0:00 [writeback] 92 ? S 0:00 [kcompactd0] 93 ? SN 0:00 [ksmd] 94 ? SN 0:00 [khugepaged] 95 ? I< 0:00 [kintegrityd] 96 ? I< 0:00 [kblockd] 97 ? I< 0:00 [blkcg_punt_bio] 98 ? I< 0:00 [ata_sff] 99 ? I< 0:00 [edac-poller] 100 ? I< 0:00 [devfreq_wq] 101 ? S 0:00 [watchdogd] 102 ? I 0:00 [kworker/4:1-events] 103 ? I< 0:00 [kworker/4:1H-kblockd] 104 ? S 0:00 [irq/25-AMD-Vi] 105 ? I 0:00 [kworker/2:1-events] 106 ? S 0:00 [kswapd0] 107 ? I< 0:00 [kthrotld] 108 ? I 0:00 [kworker/3:1-events] 109 ? I 0:00 [kworker/1:1-mm_percpu_wq] 110 ? I 0:00 [kworker/5:1-mm_percpu_wq] 111 ? I 0:00 [kworker/6:1-events_freezable] 112 ? I 0:00 [kworker/7:1-events] 113 ? I 0:00 [kworker/8:1-events] 114 ? I 0:00 [kworker/9:1-mm_percpu_wq] 115 ? I 0:00 [kworker/10:1-pm] 116 ? I 0:00 [kworker/11:1-mm_percpu_wq] 117 ? I< 0:00 [acpi_thermal_pm] 118 ? S 0:00 [xenbus_probe] 119 ? I< 0:00 [amd_iommu_v2] 120 ? I< 0:00 [nvme-wq] 121 ? I< 0:00 [nvme-reset-wq] 122 ? I< 0:00 [nvme-delete-wq] 123 ? I< 0:00 [nvme-auth-wq] 124 ? I< 0:00 [mld] 125 ? I< 0:00 [ipv6_addrconf] 126 ? I< 0:00 [kworker/2:1H-kblockd] 128 ? I< 0:00 [kworker/10:1H-kblockd] 134 ? I< 0:00 [kstrp] 135 ? I< 0:00 [zswap1] 136 ? I< 0:00 [zswap1] 137 ? I< 0:00 [zswap-shrink] 138 ? I< 0:00 [kworker/u25:0-rtw89_tx_wq] 139 ? I< 0:00 [charger_manager] 140 ? S 0:00 [irq/26-ACPI:Event] 141 ? S 0:00 [irq/27-ACPI:Event] 142 ? S 0:00 [irq/28-ACPI:Event] 143 ? S 0:00 [irq/29-ACPI:Event] 144 ? S 0:00 [irq/30-ACPI:Event] 145 ? S 0:00 [irq/31-ACPI:Event] 146 ? S 0:00 [irq/32-ACPI:Event] 176 ? I< 0:00 [kworker/0:1H-kblockd] 184 ? I< 0:00 [kworker/6:1H-kblockd] 189 ? I< 0:00 [kworker/8:1H-kblockd] 191 ? I< 0:00 [kworker/3:1H-kblockd] 193 ? I< 0:00 [kworker/5:1H-kblockd] 194 ? I< 0:00 [kworker/1:1H-kblockd] 196 ? I< 0:00 [kworker/9:1H-kblockd] 205 ? I< 0:00 [kworker/7:1H-kblockd] 206 ? I< 0:00 [kworker/11:1H-kblockd] 217 ? I 0:00 [kworker/2:2-events] 218 ? I 0:00 [kworker/4:2-mm_percpu_wq] 219 ? I< 0:00 [cryptd] 220 ? S 0:00 [irq/68-SYNA32AC:00] 221 ? I 0:00 [kworker/0:2-events] 222 ? I 0:00 [kworker/7:2-events] 223 ? I 0:00 [kworker/0:3-events] 224 ? I 0:00 [kworker/0:4-events] 263 ? S 0:00 [jbd2/nvme0n1p5-8] 264 ? I< 0:00 [ext4-rsv-conver] 280 ? I 0:00 [kworker/3:2] 509 ? I< 0:00 [tpm_dev_wq] 604 ? I< 0:00 [cfg80211] 605 ? I 0:00 [kworker/10:2-events] 607 ? I 0:00 [kworker/10:3] 611 ? I 0:00 [kworker/7:3] 616 ? S 0:00 [irq/77-rtw89_pci] 745 ? I< 0:00 [kworker/u25:1-rtw89_tx_wq] 746 ? I< 0:00 [kworker/u25:2-hci0] 752 ? I< 0:00 [amdgpu-reset-de] 753 ? I< 0:00 [amdgpu_dm_hpd_r] 754 ? I< 0:00 [amdgpu_dm_hpd_r] 755 ? I< 0:00 [dm_vblank_contr] 756 ? S 0:00 [card0-crtc0] 757 ? S 0:00 [card0-crtc1] 758 ? S 0:00 [card0-crtc2] 759 ? S 0:00 [card0-crtc3] 760 ? S 0:00 [gfx_low] 761 ? S 0:00 [gfx_high] 762 ? S 0:00 [comp_1.0.0] 763 ? S 0:00 [comp_1.1.0] 764 ? S 0:00 [comp_1.2.0] 765 ? S 0:00 [comp_1.3.0] 766 ? S 0:00 [comp_1.0.1] 767 ? S 0:00 [comp_1.1.1] 768 ? S 0:00 [comp_1.2.1] 769 ? S 0:00 [comp_1.3.1] 770 ? S 0:00 [sdma0] 771 ? S 0:00 [vcn_dec] 772 ? S 0:00 [vcn_enc0] 773 ? S 0:00 [vcn_enc1] 774 ? S 0:00 [jpeg_dec] 1765 ? Ss 0:00 runsvdir -P /etc/service log: .................................................. 1777 ? Ss 0:00 runsv getty-tty2 1778 ? Ss 0:00 runsv dbus 1779 ? Ss 0:00 runsv getty-tty3 1780 ? Ss 0:00 runsv slimski 1781 ? Ss 0:00 runsv udevd 1782 ? Ss 0:00 runsv connman 1783 ? Ss 0:00 runsv seatd 1784 ? Ss 0:00 runsv cups 1785 ? Ss 0:00 runsv getty-tty1 1786 ? Ss 0:00 runsv ufw 1787 ? S 0:00 /usr/sbin/cupsd -f 1788 tty2 Ss+ 0:00 getty 38400 tty2 linux 1789 ? S 0:00 /usr/sbin/seatd 1790 tty1 Ss+ 0:00 getty 38400 tty1 linux 1791 tty3 Ss+ 0:00 getty 38400 tty3 linux 1792 ? S 0:00 /sbin/udevd 1793 ? S 0:00 /usr/bin/slimski 1794 ? S 0:00 /usr/sbin/connmand -n --nodnsproxy 1796 ? S 0:00 dbus-daemon --system --nofork --nopidfile 1832 tty4 Ssl+ 0:01 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/slimski.auth 1833 ? I 0:00 [kworker/2:3] 1851 ? S 0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant 1859 ? Ss 0:00 /bin/bash /usr/local/bin/desktop-session zzz-icewm 1931 ? S 0:00 /usr/bin/icewm-session 1936 ? Ss 0:00 /usr/bin/icewm --notify 1941 ? S 0:00 roxterm 1945 ? S 0:00 dbus-launch --autolaunch 2caebd418eb2ab95fccc74f26419ad32 --binary-syntax --clos 1946 ? Ss 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --sess 1965 pts/0 Ss 0:00 /bin/bash 1973 ? S 0:00 zzzfm --desktop 2044 ? S 0:00 volumeicon 2051 ? Sl 0:00 conky 2132 ? S 0:00 /bin/bash /usr/bin/devmon --exec-on-drive desktop-defaults-run -fm "%d" --exec-o 2187 ? S 0:00 /usr/bin/udevil --monitor 5002 ? I< 0:00 [xfsalloc] 5003 ? I< 0:00 [xfs_mru_cache] 5006 ? S 0:00 [jfsIO] 5007 ? S 0:00 [jfsCommit] 5008 ? S 0:00 [jfsCommit] 5009 ? S 0:00 [jfsCommit] 5010 ? S 0:00 [jfsCommit] 5011 ? S 0:00 [jfsCommit] 5012 ? S 0:00 [jfsCommit] 5013 ? S 0:00 [jfsCommit] 5014 ? S 0:00 [jfsCommit] 5015 ? S 0:00 [jfsCommit] 5016 ? S 0:00 [jfsCommit] 5017 ? S 0:00 [jfsCommit] 5018 ? S 0:00 [jfsCommit] 5019 ? S 0:00 [jfsSync] 17850 pts/0 R+ 0:00 ps ax--
Brian MasinickBrian Masinick
PS: I didn’t get a close look, but I think an update yesterday or two days ago did bring in the elogin ( libelogind0 package ) but today’s update with the correction did get it back out, and in the meantime I believe libelogind0 was NOT running; best as I can see, it is not running now, unless my eyes failed to spot it.
--
Brian MasinickPS: I didn’t get a close look, but I think an update yesterday or two days ago did bring in the elogin ( libelogind0 package ) but today’s update with the correction did get it back out
Yes, indeed.
Whether it is testing, Beta or Stable, vulnerability of antiX is that many components are modified by anticapitalista and his team from the Debian components. If such Debian components get updated anticapitalista’s team needs to modify the new version accordingly. If someone does across the board update in that window of time before the corresponding antiX-specific version gets published, such user will introduce certain malfunction, instability or at least inconsistency into his/her’s so called ‘stable’ system. So issues are certain to happen after indiscriminate updates. This is one reason I never do updates across the board.
One important principle:
– Never overlay antiX-specific component with Debian one. Wait until anticapitalista/team has a chance to update.
Taking some basic precautions can make even SID system more stable than the so called ‘stable’ system vulnerable to indiscriminate updates…- This reply was modified 1 month, 1 week ago by olsztyn.
- This reply was modified 1 month, 1 week ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersBrian Masinick
I don’t worry about doing everything “correctly” at all times because:
1) I have both “stable” and “development test” versions of antiX.
2) I have many additional distributions available.
3) I have multiple hardware units on which to test and
4) I have multiple media back ups.So if I totally break something, it gives me an opportunity to learn something
and it’s not difficult at all to reinstall it.My work is generally network-based, with off the network backups, and plenty
of redundancy. No single source of error will eliminate my access.Only a 100% network outage will disrupt access but it won’t permanently break
anything.That doesn’t mean that I’m usually careless; I’m not, but on
occasion I will deliberately do things the wrong way in order
to better understand how to recover. I only do that when I have
time to get over it or use something else (and this is always covered).--
Brian Masinick
iznit
Here’s a suggestion: provide a default alias so that “deb-installer” will launch if someone attempts to launch “gdebi”
iznit
I believe libelogind0 was NOT running; best as I can see, it is not running now
It is a library package. Contains zero executable files, only *.so files
Brian Masinick
I spent some time this afternoon with antiX 23 Beta 1 on an aging Lenovo X201 laptop and the experience was good.
Only one issue: Wi-Fi went out this afternoon.
Rebooted and the problem did not reappear.
We have a Wifi provider update coming next week. I have a sneaky feeling that they’ve been testing it intermittently for the past couple of weeks because the wireless network signal drops fairly frequently, which is a recent thing. It dawned on me that the problem might be testing of the new WiFi here.
--
Brian Masinick
ile
i use rgbpaint for some simple jobs, so i tested it on the version beta. oops, strange rgbpaint screenshot desktop. odd enough to call it fun testing.
Attachments:
Wallon
Dear All,
I discovered that I had different keyboards with antix 19/21/22 and antix 23.
I checked the system keyboard configuration. It is exactly the same.
Keys = 105 international
Keyboard = be_Belge without variant.But when using AltGr + another key, I don’t have the same symbols on the keyboard keys.
This makes it very difficult for me to do the translations on Transifex. It creates confusion between antiX versions.
Has Debian changed anything?
Best regards,
WallonJust to report:
Testing of antiX 23 Beta is complete on my hardware, including a bunch of laptops:
– Thinkpad X61 – Core2Duo
– Thinkpad T410 – i5
– Thinkpad X220 – i7All seems fine, including printing, reliability of network and SMB Shares access.
I have moved all day-to-day use of my laptops to antiX 23. No issues.
Screenshot of my current day-to day antiX 23 on Core2Duo Thinkpad X61 from about 2007, with dark theme:- This reply was modified 1 month ago by olsztyn.
Attachments:
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
