- This topic has 20 replies, 5 voices, and was last updated Dec 15-4:34 am by Ninho.
-
Posts
-
Ninho
Hi ! Setting-up/fixing new AntiX-16 on old, low memory system (specs in sig at end of this post). Please remind me of how we prevent Conky auto-loading along with the Destop startup (run level 5) ? Shutting it down from theat the Desktop doesn’t “stick”, it’s regenerated during the next booting sequence. And I can’t find how to exterminate the critter either from Control pannel nor any of the configuration files I’ve examined. I know the key is hidden somewhere since I did nuke Conky on the other computer, but HOW…?
—
Ninho
System: Host: AntiX-Dell Kernel: 4.4.10-antix.1-486-smp i686 bits: 32
Desktop: IceWM 1.3.8
Distro: antiX-16_386-full Berta Cáceres 26 June 2016
Machine: Device: unknown System: Dell product: XPS-Z serial: N/A
Mobo: Intel model: D815EEA v: AAA10383-402 serial: N/A
BIOS: Intel v: A11 date: 06/11/2002
CPU: Single core Pentium III (Coppermine) (-UP-) cache: 256 KB
speed: 797 MHz (max)
Graphics: Card: Advanced Micro Devices [AMD/ATI] R100 [Radeon 7200 / All-In-Wonder Radeon]
Display Server: X.Org 1.16.4 driver: vesa
Resolution: 1024×768@0.00hz
OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.5, 128 bits)
version: 3.0 Mesa 10.3.2
Audio: Card Ensoniq ES1371 / Creative Labs CT2518 [AudioPCI-97]
driver: snd_ens1371
Sound: ALSA v: k4.4.10-antix.1-486-smp
Network: Card: D-Link System RTL8139 Ethernet driver: 8139too
IF: eth0 state: unknown speed: 100 Mbps duplex: full
mac: 00:0d:88:2f:67:f7
Drives: HDD Total Size: 120.0GB (2.6% used)
ID-1: /dev/sda model: ST3120026A size: 120.0GB
Partition: ID-1: / size: 19G used: 2.9G (17%) fs: ext3 dev: /dev/sda7
caprea
Try ~/.desktop-session/desktop-session-conf edit as root “Session load conky” from LOAD_CONKY=”true” to LOAD_CONKY=”false”
@Caprea : thanks !
@Skidoo : the FAQ is a good starting point but… many tips and accumulated knowledge got lost in the migration from the old site and forum, unfortunately.
Anonymous
“the FAQ is a good starting point but…”
But? The doc linked to FAQ https://download.tuxfamily.org/antix/docs-antiX-17/FAQ/index.html
(which is unchanged vs the antiX16 FAQ) states:2.Control Centre–} Session–} User Desktop Session
click on startup tab and comment # entries you do not want to use3.Control Centre–} Session–} User Desktop Session
click on desktop-session.conf and […]^—— my “Tip” was sincere, not a sarcastic RTFM (but) the FAQ does contain apropos guidance.
many tips and accumulated knowledge got lost in the migration from the old site and forum, unfortunately
subforum: Announcements
topic: “antiX oldforums archive (you can browse online, or clone, or download a copy)”
https://www.antixforum.com/forums/topic/antix-oldforums-archive-you-can-browse-online-or-clone-or-download-a-copy/Please remind me
Okay, here ya go. Hopefully, revisiting your archived posts will jog your memories (works for me)
using-the-hosts-file-t6040
acceder-a-worgroup-t6627-s30
live-usb-no-load-hangs-before-done-drawing-graphic-t6655
solved-install-swap-partition-t6661
fix-screen-resolution-persistently-t6663
browse-ntfs-partitions-in-rox-filer-t6664
superblock-last-write-time-in-the-future-fsck-on-e-t6666
antixtousb-help-t6671
packages-vs-meta-t6677
solved-droopy-antix-shell-script-works-but-not-wit-t6678
mouse-sensitivity-icewm-t6680
cwd-in-usdpath-really-t6684
a-trashcan-for-the-antix-desktop-t6689
1to1-voice-software-compatibility-t6691
dyndns-software-at-antix-with-autoupdate-t6693
solved-how-to-modify-the-blanking-delay-t6698
making-desktop-or-menu-shortcuts-to-launch-apps-ro-t6701
antix-icewm-desktop-background-black-or-solid-colo-t6711
exctract-original-file-from-the-compressed-linuxfs-t6719
zramfs-for-swap-t6721
kernel-headers-t6725
switching-antix-kernels-how-to-and-caveats-t6737aha, the FAQ in question was under the “antiX-17” section, wichi explains why I hadn’t found it. Glad to learn that the old forum has thus been successfully turned into browsable archives!
Thanks, @Skidoo ! Re-reading old posts – not just mine – may trigger my fading memories.
Have good time – and no, I’m not the sarcastic type, ever ;=)@Mod : it appears you edited/uncluttered this thread so the point get lost where I reported
having activated the task bar CPU & Memory load monitor, by setting :
” TaskBarShowCPUStatus=1 ”
…in the ICEWM config ( ~/.icewm/preferences)/Re-entered for future references..
In turn this raises a new question : mouse-hovering over the CPU-indicator shows a 5 line-report, of which the last two (ACPI temp, CPU freq) are meaningless on this sytem. Is there a way to remove the display of the lines in question ?
caprea
maroc
mouse-hovering over the CPU-indicator shows a 5 line-report, of which the last two (ACPI temp, CPU freq) are meaningless on this sytem. Is there a way to remove the display of the lines in question ?
Get rid of the two meaningless lines by adding
CPUStatusShowAcpiTemp=0 CPUStatusShowCpuFreq=0to your ~/.icewm/preferences.
- This reply was modified 5 years, 4 months ago by maroc.
@Caprea : woot…I can’t seem to find my way along the corners of this forum !
Too many sections, perhaps : what do you all think ?@Maroc : oh, nice tip ! Thank you, merci, choukran… !
cyrilus31
Arg too late 🙂
However I still can’t find why TaskBarShowMEMStatus does not work prio antiX 17still can’t find why TaskBarShowMEMStatus does not work prio antiX 17
Same here.
FWIW, antiX16 used the icewm version packaged by debian.
I checked: debian changelog for package “icewm”
doesn’t mention the bug being known to debian’s package maintainer, nor fixed in the latest packaged-by-debian version.antiX17 ships a version of icewm which is newer than the current “debian stable” version (and newer than the current “debian testing” version, AFAICT).
Ours is probably ( @anticapitalista can confirm this detail ) sourced from icewm fork at github
I quickly skimmed the open+closed issue tickets there & still haven’t found this bug mentioned.by adding
CPUStatusShowAcpiTemp=0
CPUStatusShowCpuFreq=0to your ~/.icewm/preferences.
I’m collecting notes toward creating a “frequently observed pitfalls” Hints-n-Tips topic, and reading this reminded me how I’ve often encountered “WTF?” results after having edited a config file, due to:
• neglecting to notice a particular var=value declaration line already exists, and winding up with that existing line re-declaring and stomping the value I intended to change.^—- dealing with some config files is often “even more confusing, rub salt in my eye whydontcha”.
For instance: ~/.fluxbox/init
After having manually edited the file (and confirming that your change is recognized, AND is retained across restarts), later, in the indeterminate future…
…when you perform “Reconfigure” via fluxbox menu, the app silently “performs housekeeping” and rewrites the config file
( strips commented lines, strips redundant/redeclaration lines {— only the bottommost of a redundant pair of lines is preserved )…can’t find why TaskBarShowMEMStatus does not work prio antiX 17
Përhaps does the WM rely on an external executable to grab that “MEMStatus” – that might be accidentally missing for aX-16 ? But what do I know :=)
Which begs asking the question : the CPUStatus (not the MemStatus), while mouse hovering, shows
CPU Load as four figures (like e.g 0.19 0.53 0.71 241). What gives ? I kind of guess the last figure could be number of processes (user? total?) as for the other 3, not even a guess :=)—
Ninho
now expermeting with zram on the low-spec system. Not that I am a believer in snake-oil remedies, but, who knows…@Skidoo :
collecting notes toward creating a “frequently observed pitfalls” Hints-n-Tips topic
Regarding pitfalls, might be interesting to review/discuss the nonstandard and rather extravagant looking value for vm.swappiness=1 adopted by antiX – at least in -16 Berta Caceres.
Was this choice discussed ? Of course it doesn’t matter if running from CD live (where, I believe, no swap at all is used by default anyway), but it might hurt once a swap file or partition is in place, on systems with little RAM, by all-but preventing the swap to play its role. Or am I mistaken ?
On my own systems with swapping I have reset the “swappiness” value to 60.
- You must be logged in to reply to this topic.
