It has no support for rrdcached flush, AVERAGE CF is hardcoded , and I cannot seem to get it to not connect lines through gaps where there were no measurements.
I don't think there's a tiling wm that puts mouse first. I think years ago there was some work on KDE to add some tiling behaviour, but I don't know if it was merged and buried in settings somewhere, or it was a plugin, or a patch. I only remember some demonstration video from years ago.
I'm pretty sure there's also Openbox setup with tiling behavior.
I use dwm with some patches, and some customizations that allow for more mouse use.
For instance mouse wheel on the tagbar cycles through tags, mouse wheel on window title cycles through windows, middle click on window title makes currently selected window master, control + mouse wheel on the window title pushes selected window around, mouse wheel on status text increases or decreases sound volume, middle click on status text kills selected window, ctrl + mouse-wheel-up sends selected window to that particular tag, etc etc etc...
So yeah, it's doable in dwm. It's not "mouse first" but most used actions are also doable with mouse, in addition to the keyboard.
It's not too hard, spend an afternoon, or two and you can get it working that way.
Once their system upgrade crashed my Mongo instance and only support they could provide was telling me I should have had backups. They were right but I had to move out.
I still remember this problem. To my best knowledge nobody else has ever had data loss after a clean shutdown and no hardware problems.
It sounded to me like it could have been the same problem as this person encountered:
https://stackoverflow.com/questions/10560834/to-what-extent-... . Based on their data
loss after a clean shutdown of mongodb in order to perform a backup, I think the only way we could have possibly saved the data is if we hibernated the system instead of doing a clean shutdown. But I don't know how well mongodb handles sudden time jumps. In general, since time jumps can be an issue, we typically perform shutdowns if a service needs to be stopped for whatever reason.
I hope you ended up with a hosted mongodb service or an MSP with an expertise specifically with mongodb, as mongo seems like it can be very tricky to administer properly if it's not the one thing you do.
Well, the tagline on their front page does read "We don't assume you're stupid.".
I'm not calling you stupid, I think everyone has failed to backup something important at one point or another, just saying that the sentiment behind the business seems to be "services provided with minimum hand-holding"
If you search for my name there, you will find at least discussions about file modes and also why I claim that processes are a failed abstraction (it was really another user who pointed that out).
Yes, the nag text was removed, but at least xscreensaver gets updates, which was the whole point.
> patches/packages/xscreensaver-5.34-i486-1_slack14.1.txz: Upgraded.
I promised jwz that I'd keep this updated in -stable when I removed (against
his wishes) the nag screen that complains if a year has passed since that
version was released. So, here's the latest one.
Personally I don't get the point of screesavers at all, since we have monitors that can be sent sleep/standby mode when they're not used.
So? Large majority code running in any distro was developed by third parties. This means nothing. It's a part of Slackware.
It was announced in Tue Sep 16 11:20:30 PDT 2003 that it's a part of 'extra' repository. So, not installed by default, but it's there.
Announcent on Fri Nov 21 13:51:57 CST 2008 says it was moved from extra/ to ap/, meaning installed by default on all except the most stripped down installs.
Also, there's nothing special in using third party tools as package managers, they all use slackwares pkg tools under the hood.
Think (apt<->slackpkg, dpkg -i <-> installpkg, dpkg -r <-> removepkg, etc etc etc).
That looks like low hanging fruit.