OSDNでのリリースファイルやソースコードは全世界の25〜30箇所程の公開ミラーサイトへミラーリングされていた。 現時点ではどれだけ生存しているかは調べていないが、まだそれなりに生きているかと思われる。ただ、日本だとJAIST(ftp.jaist.ac.jp)とIIJ(ftp.iij.ad.jp)しかないようである。
OSDNではファイルの公開方法は二種類存在し、それぞれをファイルリリース、ファイルストレージと呼んでいた。前者は最初期からあるリリースシステムであり、後者はrsync等でも利用できる置き放題のストレージシステムである。
TPM (Trusted Platform Module) is as useful for preventing real attackers as the TSA is at preventing real terrorists. The architecture is fundamentally flawed and most existing implementations are completely broken. I thought this argument was settled decades ago[1] when "trusted computing" was introduced mostly as a way to provide DRM and ownership capabilities to organizations. It has largely failed to impact the consumer market when it was introduced back in the early 2000s. However, recently there seems to be a movement by certain parties to reintroduce this failed product back to the market. Microsoft argues that in order to use Windows 11, you need TPM 2.0 compatible hardware because[2]:
The Trusted Platform Module(TPM) requirement ena
| wpa_supplicant -B -i interface -c <(wpa_passphrase 'SSID' 'key'). | |
| ping 1.1.1.1 | |
| parted /dev/nvme0n1 -- mklabel gpt | |
| parted /dev/nvme0n1 -- mkpart primary 512MiB -0 | |
| parted /dev/nvme0n1 -- mkpart ESP fat32 1MiB 512MiB | |
| parted /dev/nvme0n1 -- set 2 esp on | |
| cryptsetup luksFormat /dev/nvme0n1p1 |
https://review.coreboot.org/c/coreboot/+/46943 cpu/intel/Makefile.inc: Use correct Kconfig symbols https://review.coreboot.org/c/coreboot/+/46977 sb/intel/lynxpoint: Use common code to generate HPET table https://review.coreboot.org/c/coreboot/+/46719 sb/intel/lynxpoint: Drop unnecessary 'UL' suffix https://review.coreboot.org/c/coreboot/+/46720 {cpu,nb}/intel/haswell: Drop unnecessary 'UL' suffix https://review.coreboot.org/c/coreboot/+/46725 sb/intel/lynxpoint/lpc.c: Simplify PM init sequence https://review.coreboot.org/c/coreboot/+/46726 sb/intel/lynxpoint: Align with Broadwell https://review.coreboot.org/c/coreboot/+/46727 azalia: Treat all negative return values as errors https://review.coreboot.org/c/coreboot/+/46728 azalia: Use 'HDA_GCTL_CRST' macro as unset-mask https://review.coreboot.org/c/coreboot/+/46734 Revert "broadwell: Switch to using common ACPI _SWS code" https://review.coreboot.org/c/coreboot/+/46732 soc/intel/broadwell/gma.c: Align struct with Haswell
| FROM rust:alpine | |
| RUN apk add --no-cache \ | |
| bash \ | |
| binutils-gold \ | |
| ca-certificates \ | |
| clang \ | |
| curl \ | |
| g++ \ | |
| git \ |
2019-03-13
@voluntas
19.03.0
| /* ==UserStyle== | |
| @name Mastodon - Hide private posts | |
| @namespace github.com/unarist | |
| @version 1.0.0 | |
| @description Hide private posts from timeline | |
| @author unarist | |
| ==/UserStyle== */ | |
| @-moz-document regexp("^https://[^/]+/web/.*") { | |
| /* :not(.muted) filters notification */ |
| #!/usr/bin/env bash | |
| # | |
| # Author: Markus (MawKKe) ekkwam@gmail.com | |
| # Date: 2018-03-19 | |
| # | |
| # | |
| # What? | |
| # | |
| # Linux dm-crypt + dm-integrity + dm-raid (RAID1) | |
| # |
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
