You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hacks for Linux kernel glitches on the HP Elitebook Folio G1
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
This commit message template helps you write great commit messages and enforce it across teams.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a quick walkthrough about how you might calculate equidistant launches for a kOS-driven satellite network.
Note: It's unlikely that this will work perfectly. Tiny variations in how KSP handles air resistance, computing physics, etc, means that you'll still want to perform some minor corrections once these things get to orbit. This is the epitome of "sensitivity to initial conditions"
Starting Assumptions
Let's assume that we want to get four satellites equally spaced from launch. For convenience, we'll also assume that the orbital period is 360 seconds (you can get the real orbital period you're looking for using SHIP:OBT:PERIOD on the first craft you launch. This just makes the calculations simpler). Since we want them evenly spaced out, Satellite 2 should be 90° behind Satellite 1 in its orbit, with the same orbital period.
I use this script to backup my QEMU/KVM/libVirt virtual machines. The script requires KVM 2.1+ since it uses the live blockcommit mode. This means the data in the snapshot disk is rolled back into the original instead of the other way around. Script does NOT handle spaces in paths.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Progress Bars - An animated progress bar widget for Dashing.
Progress Bar Widget
Description
A widget made for Dashing. This widget shows multiple animated progress bars and reacts dynamically to new information being passed in. Anything with a current state and with a projected max/goal state can easily be represented with this widget. Some sample ideas would be to show progress, completion, capacity, load, fundraising, and much more.
Features
Animating progress bars - Both the number and bar will grow or shrink based on new data that is being passed to it.
Responsive Design - Allows the widget to be resized to any height or width and still fit appropriately. The progress bars will split up all available space amongst each other, squeezing in when additional progress bars fill the widget.