- Disable Secure Boot in BIOS, enable Boot of Ubuntu
- Boot this ISO via USB stick: https://plus.google.com/+IanMORRISON/posts/igAkD5j3MAq
- Use arch-bootstrap to install Arch Linux on the stick: https://github.com/tokland/arch-bootstrap
- aloso install the wifi driver https://aur.archlinux.org/packages/rtl8723bs-dkms-git/
- Copy Firmware
rtl8723bs_nic.bin
for Wifi from https://github.com/hadess/rtl8723bs - Update Compute Stick Firmware (to make headless work): https://communities.intel.com/message/347428#347428 https://downloadcenter.intel.com/download/25506
- To boot headless: add kernel parameters
text
(maybe not needed anymore)
[Unit] | |
Description=Disable GPE6F interrupts | |
[Service] | |
Type=oneshot | |
ExecStart=/bin/bash -c "echo disable > /sys/firmware/acpi/interrupts/gpe6F" | |
[Install] | |
WantedBy=multi-user.target |
--- | |
BasedOnStyle: LLVM | |
Language: Cpp | |
IndentWidth: 8 | |
UseTab: Always | |
BreakBeforeBraces: Linux | |
AlwaysBreakBeforeMultilineStrings: true | |
AllowShortIfStatementsOnASingleLine: false | |
AllowShortLoopsOnASingleLine: false | |
AllowShortFunctionsOnASingleLine: false |
What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.
In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.
Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th
#!/usr/bin/perl | |
use strict; | |
use warnings; | |
use File::Copy qw(copy); | |
#use X11::Protocol; | |
my $fname = $ARGV[0]; | |
if(not defined $fname) { | |
die "No input\n"; | |
} |
#include <time.h> // Robert Nystrom | |
#include <stdio.h> // @munificentbob | |
#include <stdlib.h> // for Ginny | |
#define r return // 2008-2019 | |
#define l(a, b, c, d) for (i y=a;y\ | |
<b; y++) for (int x = c; x < d; x++) | |
typedef int i;const i H=40;const i W | |
=80;i m[40][80];i g(i x){r rand()%x; | |
}void cave(i s){i w=g(10)+5;i h=g(6) | |
+3;i t=g(W-w-2)+1;i u=g(H-h-2)+1;l(u |
GNOME's tracker is a CPU and privacy hog. There's a pretty good case as to why it's neither useful nor necessary here: http://lduros.net/posts/tracker-sucks-thanks-tracker/
After discovering it chowing 2 cores, I decided to go about disabling it.
Directories
{ ES BBS Intro - 1995 } | |
{ Binary can be get at http://www.pouet.net/prod.php?which=55705 } | |
{$M $800,0,655360} | |
{$N-,E-,F+} | |
uses Strings,XBuf,XMode; | |
const |
# Synchronize history between bash sessions | |
# | |
# Make history from other terminals available to the current one. However, | |
# don't mix all histories together - make sure that *all* commands from the | |
# current session are on top of its history, so that pressing up arrow will | |
# give you most recent command from this session, not from any session. | |
# | |
# Since history is saved on each prompt, this additionally protects it from | |
# terminal crashes. |