Standard Braking Distance
(Geschwindigkeit / 10) * (Geschwindigkeit / 10)
Evasive (Emergency) Braking Distance
((Geschwindigkeit / 10) * (Geschwindigkeit / 10)) / 2
After my dad died, I wanted to be able to have access any of his online accounts going forward. My dad was a Safari user and used iCloud Keychain to sync his credentials across his devices. I don’t want to have to keep an OS X user account around just to access his accounts, so I wanted to export his credentials to a portable file.
This is the process I used to create a CSV file of his credentials in the format “example.com,user,pass”. This portable format would be pretty easy to import into 1Password or Safari in the future.
The way I went about this isn’t great; it opens up more opportunities for apps to control one’s Mac through Accessibility APIs, it writes plaintext passwords to disk, and it could use some cleaning up. A better approach might leverage the
security command line tool that ships with OS X. That said, I found this method to be a fun illustration of what’s possible us
|# Author: Erik Kristensen|
|# Email: firstname.lastname@example.org|
|# License: MIT|
|# Nagios Usage: check_nrpe!check_docker_container!_container_id_|
|# Usage: ./check_docker_container.sh _container_id_|
|# Depending on your docker configuration, root might be required. If your nrpe user has rights|
|# to talk to the docker daemon, then root is not required. This is why root privileges are not|
I'm hunting for the best solution on how to handle keeping large sets of DB records "sorted" in a performant manner.
Most of us have work on projects at some point where we have needed to have ordered lists of objects. Whether it be a to-do list sorted by priority, or a list of documents that a user can sort in whatever order they want.
A traditional approach for this on a Rails project is to use something like the
acts_as_list gem, or something similar. These systems typically add some sort of "postion" or "sort order" column to each record, which is then used when querying out the records in a traditional
order by position SQL query.
This approach seems to work fine for smaller datasets, but can be hard to manage on large data sets with hundreds (or thousands) of records needing to be sorted. Changing the sort position of even a single object will require updating every single record in the database that is in the same sort group. This requires potentially thousands of wri
|These two files should help you to import passwords from mac OS X keychains to 1password.|
|1) You have some experience with scripting/are a power-user. These scripts worked for me|
|but they haven't been extensively tested and if they don't work, you're on your own!|
|Please read this whole document before starting this process. If any of it seems|
|incomprehensible/frightening/over your head please do not use these scripts. You will|
|probably do something Very Bad and I wouldn't want that.|
|2) You have ruby 1.9.2 installed on your machine. This comes as standard with Lion, previous|
|versions of OS X may have earlier versions of ruby, which *may* work, but then again, they|