asciilifeform: i probably should have specified this in the signed text
asciilifeform: it should go without saying that asciilifeform-kills-integer-retardation_8685d541f20bcfe8d8cc9fefba663dd861f7b237.patch is not a tree candidate !
asciilifeform: /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/../../../../lib64/libpthread.a: error adding symbols: Bad value
asciilifeform: /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/../../../../lib64/libpthread.a(pthread_cond_wait.o): relocation R_X86_64_32 against `__gcc_personality_v0' can not be used when making a shared object; recompile with -fPIC
asciilifeform: the integer retardation patch includes the one from portatron
asciilifeform: <nubbins`> ok alf i'm applying all 3 of your patches << wai wat, 3?!
asciilifeform: jurov: appreciate that what we are attempting with static build is like digging out one of those lugers ru kids routinely find in the ground and trying to fire it
asciilifeform: there's u_int32_t defined in sys/types.h but not uint32_t << ahahahahaha.
asciilifeform: it is normally fished out of a pre-existing latrine.
asciilifeform: because it is uncommon for the enemy to -invent- a turd ab initio
asciilifeform: this is a fine point but not unimportant zoologically
asciilifeform: in many cases (quite arguably dns included) the turd was an ad-hoc hack from the days of arpa but was cemented in place because guess-why.
asciilifeform: ther for treason against Friend Computer, since none of them are allowed to touch the paint, go near the hallway, or talk about their mission, and they're all charged with enforcing the rules on one another.'
asciilifeform: yone who breaks the rules is a Commie Mutant Traitor, subject to the death penalty. Much of the game revolves around the consequences of the security levels. For instance, Friend Computer might assign a team of Red Troubleshooters to re-paint a hallway that ought to be Orange but was painted Yellow by mistake the Commie Mutant Traitors. It's quite likely in such a case that the Troubleshooters will all end up shooting each o
asciilifeform: 'In Paranoia, everything has a colour-coded security level (from Infrared up to Ultraviolet) and everybody has a clearance on the same scale. You are not allowed to touch, or have any dealings with, anything that exceeds your clearance. If you're a Red Troubleshooter, you're not allowed to walk through an Orange door. Formally, you're not really supposed to even know about the existence of anything above your clearance. An
asciilifeform: it isn't just 'voodoo taint' from nsa.
asciilifeform: and even further discouraging genuine audit, as if this were possible or even necessary
asciilifeform: as if this did something tangible beyond making it even -less- fit-in-head.
asciilifeform: mats: selinux and similar are exemplary of usg approach to 'seek00r1ty' - add layers of 'granular' bureaucracy to the os
asciilifeform: mats: i can trivially make mincemeat of this by issuing raw dma cycles.☟︎
asciilifeform: mats: grsec >> but the sheer nonsensicalness of pretending that kernel can limit what kernel can do. consider this claim: 'Through PaX's UDEREF and KERNEXEC features, grsecurity forces any userland data access to go through an approved accessor and rejects any attempt to execute userland code in kernel context.'
