After a couple hesitating months to move to github pages, and from my hacked together static site generator, yesterday was my 4th attempt in getting started with github pages blogging, just because there where a few annoyances with the different variations I've tried.
Decided to go with Octopress, just for their nice logo. And for their Github pages oriented focus. That didn't pan out, but at least I learned a few things about their blogging process and setup, which I'm adapting for sculpin.
It should work by default when connected, however you might reach this page with the same issue I had, where you where missing a few essential steps.
usb-storage is enabled, you can check with sudo modinfo usb-storage and enable
it with sudo modprobe usb-storage| %.hex: %.asm | |
| avra -fI $< | |
| rm *.eep.hex *.obj *.cof | |
| all: $(patsubst %.asm,%.hex,$(wildcard *.asm)) | |
| upload: ${program}.hex | |
| avrdude -c arduino -p m328p -P /dev/arduino-uno -b 115200 -U flash:w:$< | |
| monitor: |
LVM snapshots are logical volumes that reflect the state of the snapshoted volume at the exact moment in time the snapshot was created. Useful for backups and reference points we can revert back to.
$ sudo lvcreate --size 5G --snapshot --name root-backup /dev/vg0/root
Logical volume "root-backup" created.
I hereby claim:
To claim this, I am signing this object:
I have a Dell Inspiron 5570 (5000 series) and for some obscure reason in my default linux instalation the default keyboard backlight timeout is something like 1 second. Doesn't make any sense, what benefit does a keyboard backlight have if I can only see it in the dark only when I'm already typing?
Took a couple of wrong paths searching for a solution until I found how to manually tweak that value. Keyboard backlights
configuration files are located under /sys/class/leds and for a Dell laptop the magic file is
/sys/class/leds/dell::kbd_backlight/stop_timeout.
There's no option to disable the timeout completely so I've created a systemd service that sets the timeout to 30 minutes
(just an arbitrary large value) each time graphical.target is reached.
| libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./compat -I./include -I./include -g -O2 -Wall -fno-strict-aliasing -pthread -MT bufferevent_openssl.lo -MD -MP -MF .deps/bufferevent_openssl.Tpo -c bufferevent_openssl.c -o bufferevent_openssl.o | |
| bufferevent_openssl.c: In function ‘bio_bufferevent_new’: | |
| bufferevent_openssl.c:106:3: error: dereferencing pointer to incomplete type ‘BIO’ {aka ‘struct bio_st’} | |
| b->init = 0; | |
| ^~ | |
| bufferevent_openssl.c: At top level: | |
| bufferevent_openssl.c:228:1: error: variable ‘methods_bufferevent’ has initializer but incomplete type | |
| static BIO_METHOD methods_bufferevent = { | |
| ^~~~~~ | |
| bufferevent_openssl.c:79:27: warning: excess elements in struct initializer |
| { | |
| "rules": { | |
| "indentation": 4, | |
| "block-opening-brace-space-before": "always", | |
| "block-closing-brace-newline-before": "always", | |
| "block-opening-brace-newline-after": "always", | |
| "selector-list-comma-newline-after": "always", | |
In the last few months, I had to write multiple Ansible playbooks, to the point that the slow write/test cycle became a major annoyance. What seemed to work well for me was a mix between Ansible tags and Vagrant snapshots. I would be happy to hear what workflow others employ, that specifically minimizes the time they spend testing.
Vagrantfile
Vagrant.configure("2") do |config|
I've started using [Vimwiki][0] recently, mostly for note keeping, and this post is about how I integrated it into my workflow.
The main feature I use from Vimwiki is the Diary. And the way I've used past note taking applications were always in short bursts.