246 karma · joined July 10, 2015
Was repair attempted it or was it just thrown away? Things can look cooked, but they're often easily repairable. Far too often, most consumers are completely clueless, choosing instead to fix it by going to the store and filling the landfill needlessly because they don't care about wasting resources.
With perfect security hygiene, more things are attainable.
But an even more perfect crime is hedging both sides of an option with phony identities, with different amounts, different enough times, different brokerages, different IP addresses, etc.
Feel free to try it out and report back.
PS: Startups, code a valuable add-on for SnapChat and be sure to engage them early to avoid crossed-signals. That's how to make a few million in short-order (just be sure that the "golden handcuffs" terms are minimal).
WTTW: Such folks are better off calling McKinsey, they will send a 7'5" Brit ex-physicist whom speaks English and Mandarin and knows the secret handshakes of how .cn works.
Btw: Here's a capacitor lifetime calculator with equations.
http://www.illinoiscapacitor.com/tech-center/life-calculator...
Note: Electrolytic capacitors dry out, frequently rendering power supplies and other electronics unusable in a decade or three but they're easily replaced w/ soldiering.
TL;DR: Resflash has some really useful features for real-world embedded use-cases.
Having done embedded development (industrial packet radios), having an embedded firmward loader and fail-safe ROM are definitely major pluses for less brickable products. The having two versions is a similar approach.
Also handy is a dev board w/ actual hardware watchdog and some industrial NVRAM.
To me, it's just as easy/fast and more powerful to use RoR/Sinatra or Django/Flask from the get-go and for limiting longer-term tech-debt (migrating from one to the other).
0. Use backup agents for local boxes to make a compressed, encrypted backup to the NAS/SAN on some host-unique temporary dir on the same volume as the offsite dir.
1. Test restores of backups to throwaway VMs before blessing them as good for offsite storage. Fail any backups that fail this test. (Very important for checking backup jobs and restore automation processes. An untested backup == not a backup.)
2. Use mv to move the compressed backup from host-unique dir into the offsite dir.
3. Continuously replicate the offsite dir to offsite providers.
4. Prune old jobs as needed, which then replicates. (Be sure to set provider-specific previous backup retentions appropriately, to avoid error replication issues.)
5. Sleep at night.
A best practice is to ask the next new person to keep notes of obvious questions/unclear details to put in an internal, secure wiki. The issue, as founders, we often don't think about what is obvious to us when we deployed an app and all the server tweaks necessary to get it going, for teaching someone else or replicating what was done. Then, they learn some things and put them into the wiki. Rinse-later-repeat until there's few/no questions as the team grows.
It's continual DR/BCP housekeeping: architecture diagrams, instance inventory/config and other critical info (contact / escalation info) updated so that it's run-over-by-a-bus and EC2-burns-down (almost) resilient.
As you scale, having someone put server config all in Chef or Puppet (cfg management stored in git) will also help reduce deployment pain at the expense of initial setup pain. Initially, a wiki page containing a giant shell script for each server box kind is usually a faster hack.
The end.
SpiderOak uses end-to-end encryption, but I wouldn't trust it completely https://spideroak.com/opendownload
rsync.net is also pretty usable, but I wouldn't trust there is any in-flight or at-rest security http://www.rsync.net/
Tahoe LAFS provider https://leastauthority.com/ (it's possible to run your own Tahoe LAFS servers on cloud/colo boxes on several providers)
The best-practice mitigation to allow backups on less secure providers is encrypt locally (end-to-end encryption effectively) and distribute restore keys to a decent quorum of managers/founders/supervisors.
Having done offsite LTO tape vaulting and formal disaster recovery / business continuity planning at the organization level, it's a whole lot cheaper, easier and more flexible to use multiple cloud providers for most real use-cases (apart from multiple PiB datasets).
Speaking of usability, here's a patch to libfetch to ignore crusty ftp server non-RFC spurious responses https://gist.github.com/steakknife/b4772a5deb6afc8851e0 (I have absolute zero idea how to contribute code/patches to FreeBSD or it's not obvious/easy from docs.)
s/on/for/ That's what I meant. ;)
FreeBSD ip-172-x-x-x 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 19:31:38 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
Woohoo!Afterwards, folks may want to rebuild outdated ports to avoid stale shared libs from the previous release using something like:
(cd /usr/ports && make update && portmaster -a)
# or: -aBg saves new packages for re/installation on other boxes
Finally, check ports for any unpatched security issues (should be 0): pkg audit -F
EDIT: only rebuild outdated portsIt's possible to run a NetBSD Xen dom0 (host system) on bare metal, under VMware or Xen HVM: it takes a few patches, building a kernel and config tweaks to get going but it works stably. [0] (There's no XAPI (the Xen remote management API) support however, so XenServer tools and other 3rd-party XAPI integrations probably won't work. FYI: XAPI server-side is coded in OCaml; don't ask how I know that. ;) [1])
For most people w/ baremetal or rented colo that just want a turn-key supportable hypervisor, I would advise using Citrix XenServer (commercial official Xen, free download, it seems be more stable than XCP and includes XAPI) or VMware ESXi (free download, very stable, $$$ quickly). After that, you can run whatever OS/es you like. (IIRC a ton of AWS boxes run heavily-modified Xen open-source 3.3.x.)
For desktop/laptop dev: VirtualBox, VMware Fusion/Workstation or qemu.
References:
0. https://wiki.netbsd.org/ports/xen/howto/
1. https://github.com/xapi-project/xen-api
EDIT: pronouns
freebsd-update fetch install && freebsd-update -r 10.2-RELEASE upgrade
EDIT: Updates to 10.1-RELASE-p17 (currently) before upgrading