But when using it on one of my test-sites, it turned out the site looks pretty much broken. Apparently WordPress doesn’t yet use protocol relative URLs, so CSS, JS etc. may still have a http:// prefix, causing some browsers not to load that content over an insecure channel. Furthermore, trying to access the WordPress dashboard results in an infinite loop, since the request from Cloudflare to your server is still HTTP and handled accordingly by WordPress.
The quick way to fix this is to simply add a few lines to woud wp-config.php
After wet-tumbling my first batch of brass the first thing that came to my mind was that scene from Despicable Me: It’s so fluffy shiny I’m gonna die!
So I went ahead and did my already dry-tumbled “clean” brass over again, leaving my with piles of oh so shiny brass. But… how much? Well, counting brass kinda sucks when you’re talking thousands per caliber, so better put it on a scale and do the math.
Here’s a handy breakdown for future reference:
grains per case
grams per case
cases per lb
cases per kg
lb per 1000
kg per 1000
.40 S&W / 10mm / .357 Sig.
* the bigger the cartridge, the bigger the margin of error of course
If you are for gun control, then you are not against guns, because the guns will be needed to disarm people. So it’s not that you are anti-gun. You’ll need the police’s guns to take away other people’s guns. So you are very pro-gun, you just believe that only the Government (which is, of course, so reliable, honest, moral and virtuous) should be allowed to have guns. There is no such thing as gun control. There is only centralizing gun ownership in the hands of a small, political elite and their minions
A quick tip for anyone experiencing somewhat finicky buttons on a Vortex Sparc (Gen. 1): Chances are your unit isn’t defective, it’s just time to replace your CR2354 battery.
Apparently the red-dot will continue working until the very last moment, when your cell is completely out of juice – but the controls won’t. Sometimes they work, sometime they won’t. Turning the red dot on and off seemingly takes forever and occasionally won’t work at all. Even though the dot itself was as bright as it gets, turns out my battery was almost out of power. Replaced it with a new one – everything is back to working again like it’s supposed to.
Kind of a hilarious bug, really… I recently installed another Ubuntu 14.04 server running inside a KVM with a rather fast storage backend, therefore the system apparently boots just a tiny bit faster than my other images have in the past. Problem is, apparently that slows down the boot process as init thinks something must be crashing and decides to respawn it for good measure…
[2.311174]input:ImExPS/2Generic Explorer Mouse as/devices/platform/i8042/serio1/input/input3
[2.811553]init:plymouth-upstart-bridge main process(191)terminated with status1
[2.812789]init:plymouth-upstart-bridge main process ended,respawning
[2.874117]init:plymouth-upstart-bridge main process(210)terminated with status1
[2.875167]init:plymouth-upstart-bridge main process ended,respawning
[2.904155]init:plymouth-upstart-bridge main process(217)terminated with status1
[2.905289]init:plymouth-upstart-bridge main process ended,respawning
[2.928618]init:plymouth-upstart-bridge main process(221)terminated with status1
[2.929713]init:plymouth-upstart-bridge main process ended,respawning
Yep, that’s right – 47 seconds waiting and idling, doing nothing when the image could have booted in a fraction of that time.
To fix it, simply add a sleep 2 to your /etc/init/plymouth-upstart-bridge.conf
stop on(stopping plymouth
Init won’t freak out anymore and starts the image as it’s supposed to:
[1.225045]random:lvm urandom read with16bits of entropy available
[1.370262]EXT4-fs(dm-0):mounted filesystem with ordered data mode.Opts:(null)