having problems with the sda2 partition, so this may not be OS related, but two of five installations displayed crazy swap usage (8gb doing routine install things), and two (one of which may have been a crazy swapper--went through five slackos, a precise, and an april all while breaking my own stuff
, so not sure. it was all very distracting...) used up their 12 gig first run save-space allotment. one of those installations took (on it now), though i lost the dropbox it synced. a gripe, not a bug:
what's the easiest way to regain the control the new jwm configuration scripts have taken away? other than the mouse two button, i'd like to be able to get rid of them and all their interference with my configuration choices, reverting to an earlier jwm (how to?--ditching jwmconfig trashed an installation--it wouldn't reboot.) if need be. seems like it should be a user choice to override the developers' choices, especially where there's no harm to be found.
a request, not a gripe:
anyone know of a working megasync package for it? i tried two debs and slackware64 package. i'd try another search of the ppm, but it says it's running, so it's going to exit now, which'd make it just as unavailable (if it's running, it's also well hidden).
any tips for dual monitor support? i got lxrandr to partially work (it will allow you to change the settings, ask if you want to keep them, then ignore your input).
resetting jwm configurations through the gui appears to have broken radky's pup clock set (worked before a switch, then wouldn't even after the switch back).
i recall most slackos and precises as defaulting to a pop up giving you the choice to install when a txz is clicked--is this missing or have i broken something (it worked earlier...but was that in an april or precise...). anyway, i can't get txz packages to install without first unpacking them and then converting them to pet (using don570's newest right click utility, which isn't labeled as 64 bit--the april64 version didn't install correctly).
thanks in advance.
____
played around some more with the jwm configuration gui(s) and found that it undoes many changes for no reason and could use a few additions once things get ironed out: edit labels ("applications," "menu," and "bookmarks" all waste space in my eyes), add your own menu buttons (not just the two), actually allow you to move around the dock, pager, and tasklist (strategy seems to be offer and recommend against a non-option?), pick the starting spot for the trays--some aspects of the new thing are really nice and some don't work well and some don't appear to work at all.
---
on the positive side, this is the first 64 bit pup i've used in which xdotool works correctly (2._ .rpm--slackware and ppm (it was working for me at the time) versions didn't work. need to double check, but i think the redhat version is the one i used (xdotool 2.20110530.1 x86_64 rpm).
Our way or the HiWay. Good to see China keeps'em in line..