kbknapp

44 ms·

31.
by kbknapp 3y ago
At least on Fedora I've always found the RPMs either lagged pretty far behind version wise (at least the COPR repos, I can't remember if I tried the OpenSUSE ones or not? But I generally try not to use OpenSUSE RPMs due to differe
32.
by kbknapp 3y ago
The fact that my M2 has an effectively double size battery from my Fedora based Thinkpad (M2 has a 100Wh battery, while the Thinkpad has a 57Wh) means it just needs to be not terribly less efficient than x86 Fedora laptop for me to be happy
33.
by kbknapp 4y ago
Last I looked Session[0] does not and was created for just that purpose but without sacrificing much in the way if UX. 0: https://getsession.org/
34.
by kbknapp 4y ago
In Rust the edge cases are often more apparent because you're often forced to at least acknowledge them. So while you do have to put thought into handling them, you don't have to spend much thought finding or worrying about missin
35.
by kbknapp 5y ago
Setting KDEWM to something other than KWin no longer works in Fedora as of 35 (and other "leading edge" Plasma distros like OpenSUSE are quickly approaching this turning point as well). There are several spots in the Plasma code b
36.
by kbknapp 5y ago
A real attacker would try to minimize all those constraints by being collocated with the target as close as possible such as in the same datacenter or same rack if possible.
37.
by kbknapp 5y ago
I wonder if they're talking about competing with all of systemd or not? The suite that is systemd is pretty massive, in an unironic way. I personally think one of the tragedies of systemd is how all the related tooling and components
38.
by kbknapp 6y ago
The lack of a CVE does not imply the lack of a security vulnerability.
39.
by kbknapp 6y ago
Not the parent, but I've also been using KDE in a multi-monitor setup for years (I have a 1440p primary monitor, and two vertical 1080p monitors to the sides). In my experience, applications open on the primary monitor, or on the monit
40.
by kbknapp 6y ago
Same! Unfortunately we have a system is more or less tethered to use of LXD. While other workloads have moved to CentOS or Red Hat systems, LXD is supremely broken on those systems (or any distro that uses SELinux). It's extremely frus
41.
Way Cooler Post Mortem(way-cooler.org)
2 points by kbknapp 7y ago|0 comments
42.
by kbknapp 7y ago
To be clear, I'm not say you personally. I don't know you, or anything about your work so I'm speaking in purely a general sense about a position that you were representing. I don't think all upstream contributions are
43.
by kbknapp 7y ago
How about using some of that revenue to pay the project maintainer to incorporate the patch upstream and make a release? I've seen this very often in my personal experience that a company says exactly like you're saying now, &quot
44.
by kbknapp 7y ago
I think you're missing the point from the previous poster about (perceived) competition. Unless your challenge literally stops at, "make X appear onscreen" with no regard for quality, testing, etc. Giving unchecked/unver
45.
by kbknapp 7y ago
> They presented three design challenge options to pick from, with a weeks notice and advised that we should spend no more that 3–5 hours on the task (wink, wink) I know this self-selects for people willing to do extra work for no extra
46.
by kbknapp 7y ago
Those are just the protocols. They should also list the client application they're forking as well. What they're doing is like forking nginx selling you a webserver, then when people ask what it's based on they reply with &#x
47.
by kbknapp 8y ago
> if you are making git commits through your toaster you got other issues. This made me snort out some coffee on a Monday. Thank you! I think your point is also a good one I don't see represented often, portability for portability&#
48.
by kbknapp 8y ago
It's pretty good, I'd recommend it. I haven't finished the book yet, but what I've read thus far has been good. Something I'd wish I'd known (although it wouldn't have changed my decisions to purchase) is