borjaburgos

Orchard '512MB'
========================================================================
   BYTE UNIX Benchmarks (Version 5.1.3)

   System: 782883e0916d: GNU/Linux
   OS: GNU/Linux -- 3.8.0-19-generic -- #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013
   Machine: x86_64 (x86_64)
   Language: en_US.utf8 (charmap="ANSI_X3.4-1968", collate="ANSI_X3.4-1968")
   CPU 0: QEMU Virtual CPU version 1.0 (4000.0 bogomips)
          x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel virtualization

borjaburgos

# DOCKER-VERSION 1.2.0

FROM node

EXPOSE 80

ADD package.json /tmp/package.json

RUN cd /tmp && npm install --production

borjaburgos

Keybase proof

I hereby claim:

• I am borjaburgos on github.
• I am borjaburgos (https://keybase.io/borjaburgos) on keybase.
• I have a public key whose fingerprint is 2B88 BFC5 83A9 240D CB07 15D9 2B6E AE27 EB91 96BB

To claim this, I am signing this object:

borjaburgos

###Pikachu A
proxmark3> hf mfu info

--- Tag Information ---------
-------------------------------------------------------------
      TYPE : NTAG 215 504bytes (NT2H1511G0DU)
       UID : 04 a6 16 72 61 3e 80
    UID[0] : 04, NXP Semiconductors Germany
      BCC0 : 3C, Ok
      BCC1 : AD, Ok

borjaburgos

lb:
  image: 'tutum/haproxy:latest'
  autorestart: always
  links:
    - web-green
  ports:
    - '80:80'
  roles:
    - global
  deployment_strategy: high_availability

borjaburgos

# The load-balancer, gets deployed anywhere
lb:
  image: 'tutum/haproxy:latest'
  links:
    - wordpress
  ports:
    - '80:80'
  restart: always
  roles:
    - global

borjaburgos

Anonymous UUID:       BD25E58F-813B-6792-8048-64E027789ECF

Mon Jun  6 18:42:27 2016

*** Panic Report ***
panic(cpu 6 caller 0xffffff7f90fbbbd5): "GPU Panic: [<None>] 5 0 a0 d9 9 8 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0x103e00000 0xffffff92000a3000 0x0e7150a2, D0, P3/4\n"@/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.12.8/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 6), Frame : Return Address
0xffffff81f99e3510 : 0xffffff800dedab12 
0xffffff81f99e3590 : 0xffffff7f90fbbbd5 
0xffffff81f99e3670 : 0xffffff7f8ed3c1e0 

borjaburgos

I (30) boot: ESP-IDF v3.3 2nd stage bootloader
I (30) boot: compile time 10:35:25
I (30) boot: Enabling RNG early entropy source...
I (32) boot: SPI Speed      : 80MHz
I (34) boot: SPI Mode       : DIO
I (36) boot: SPI Flash Size : 4MB
I (39) boot: Partition Table:

borjaburgos

The Bikepacking Computer

Background

Current bike computers, primarily from manufacturers like Garmin, Wahoo, HammerHead, and Coros, are designed with road cycling and triathlons in mind. While some features cater to off-road cycling (e.g. MTB/gravel), these devices often fall short for ultra-distance and multi-day bikepacking events. Issues such as short battery life, limited/non-existent satellite connectivity options, and lack of ruggedness make them less than ideal for bikepacking.

This document is not intended to argue the market potential for a bikepacking-specific computer. Instead, it outlines the key features and capabilities that could define a better bike computer specifically designed for ultra-cycling and bikepacking.

Key Considerations for Bikepacking

borjaburgos

Preparing variables...
Preparing images...
1-1-A.png: Background contains too many unique 8x8px tiles (256 where limit is 192) meaning it may not display correctly. Consider reducing the amount of detail in this image.
1-2.png: Background contains too many unique 8x8px tiles (256 where limit is 192) meaning it may not display correctly. Consider reducing the amount of detail in this image.
meta_data_tilemap.png: Background is too small, must be at least 160px x 144px
meta_data_tilemap.png: Background contains too many unique 8x8px tiles (256 where limit is 192) meaning it may not display correctly. Consider reducing the amount of detail in this image.
1-1.png: Background contains too many unique 8x8px tiles (256 where limit is 192) meaning it may not display correctly. Consider reducing the amount of detail in this image.
1-2-A.png: Background contains too many unique 8x8px tiles (256 where limit is 192) meaning it may not display correctly. Consider reducing the amount of detail in this image.
1-4.png: Backg