riveravaldez writes:
On 9/5/21, Linux-Fan <Ma_Sys.ma@web.de> wrote: > riveravaldez writes: > >> I have this `phwmon.py`[1] which I use with fluxbox to have a couple >> of system monitors at hand. It depends on some python2 packages, so >> stopped working some time ago. > > Any specific reason for preferring `phwmon.py` over a tool like `conky`? Hi, Linux-Fan, thanks a lot for your answers. `conky` is great, but you have to see the desktop to see `conky`, and I tend to work with maximized windows. Monitors like `phwmon.py` or the ones that come by default with IceWM for instance are permanently visible in the sys-tray/taskbar (no matter you're using fluxbox, openbox+tint2, etc.). That's the only reason: minimal and visible.
That makes sense. In case you still want to try conky, there might be means to make it appear as a dedicated panel that is not overlapped by maximized windows, although I did not test that back when I was using Fluxbox (now on i3). See e.g.
https://superuser.com/questions/565784/can-conky-remain-always-visible-alongside-other-windows https://forum.salixos.org/viewtopic.php?t=1166 [...]
> There are differences: Whenever you install packages, you may not notice > that they are only avaliable in old releases because the output of > `apt-cache search` and similar tools will include old packages. Also, > running a release with stable+oldstable in sources.list is less common than > the other case: stable in sources.list and some oldstable packages leftover> from upgrades. In case bugs are fixed in the oldstable package, you will > get them automatically if you have them in sources.list.> > My personal choice would be to install the packages without adding the > oldstable repositories as to be reminded that they are obsolete and are > likely to stop working in the future. Thanks again. Very informative and educational. When you say 'as to be reminded that they are obsolete', how/when/where the system will remind me this?, will it be?
There is no automatism for this that I am aware of. There are tools like `deborphan` and `aptitude search ~o` that may tell you about them. The release notes recommend proactively removing obsolete packages:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#for-next
> Be aware that libraries like `python-psutil` may not work with newer > kernels. Here (on oldstable with a backported kernel 5.10) the script would > > not run due to excess fields reported by the kernel for disk statistics:
[...]
Yes, indeed. I didn't mentioned it but I had to "fix" that as seen in: https://gitlab.com/o9000/phwmon/-/issues/3#note_374558691 Essentially, convert: `elif flen == 14 or flen == 18:` to `elif flen == 14 or flen == 18 or flen == 20:` In /usr/lib/python2.7/dist-packages/psutil/_pslinux.py Supposedly shouldn't be problematic, but I'm not sure. Any comment on this?
It's pretty much how I would go about it for a short-term solution. Any upgrade/reinstallation of the respective python package may revert your change. I would not mind that too much, given that there will not be any "unexpected" upgrades to the package while its repositories are not enabled in sources.list :)
[...]
> PS: If you are interested in my thoughts on status bars, see here: > https://masysma.lima-city.de/32/i3bar.xhtml Thanks a lot, LF! I'm checking it right now. Very interesting.
You're welcome. If anything is unclear/wrong there, feel free to tell me directly via e-mail :)
HTH Linux-Fan öö
Attachment:
pgpU1e0Rz61PS.pgp
Description: PGP signature