ryan ryanwoodsmall

Here's a list of mildly interesting things about the C language that I learned mostly by consuming Clang's ASTs. Although surprises are getting sparser, I might continue to update this document over time.

There are many more mildly interesting features of C++, but the language is literally known for being weird, whereas C is usually considered smaller and simpler, so this is (almost) only about C.

1. Combined type and variable/field declaration, inside a struct scope [https://godbolt.org/g/Rh94Go]

struct foo {
   struct bar {
 int x;

This is pretty simple snippet to get API Token of a user , lets say "MYUser" in jenkins.
its pretty useful when you are working with 'jenkins-job-builder' to update jobs in jenkins, and you need to get the api token which JJB needs inorder to update jobs to ..
run this code in either jenkins script console , or as i prefer, in form of init.groovy.
so when jenkins master starts, i create a user for JJb.
after that i get the token right away and pass it to my JJB jobs folder to file 'jenkins_jobs.ini' :)_ .

import jenkins.security.*       
User u = User.get("Myuser")

(This is a translation of the original article in Japanese by moratorium08.)

(UPDATE (22/3/2019): Added some corrections provided by the original author.)

Writing your own OS to run on a handmade CPU is a pretty ambitious project, but I've managed to get it working pretty well so I'm going to write some notes about how I did it.

How to disable systemd-resolved in Ubuntu

Stages

Disable and stop the systemd-resolved service:

  sudo systemctl disable systemd-resolved.service
  sudo systemctl stop systemd-resolved

Then put the following line in the [main] section of your /etc/NetworkManager/NetworkManager.conf:

	#
	# Building V8 for alpine is a real pain. We have to compile from source, because it has to be
	# linked against musl, and we also have to recompile some of the build tools as the official
	# build workflow tends to assume glibc by including vendored tools that link against it.
	#
	# The general strategy is this:
	#
	# 1. Build GN for alpine (this is a build dependency)
	# 2. Use depot_tools to fetch the V8 source and dependencies (needs glibc)
	# 3. Build V8 for alpine

	;
	; the "monitor ROM" of an apple 1 fit in one page (256 bytes).
	;
	; this is my attempt to take the disassembled code, give names to the
	; variables and routines, and try to document how it worked.
	;
	;
	; an apple 1 had 8KB of RAM (more, if you hacked on the motherboard), and a
	; peripheral chip that drove the keyboard and video. the video was run by a
	; side processor that could treat the display as an append-only terminal that

	package main

	import (
	"errors"
	"net"
	"os"
	"sync"
	)

	type StdinListener struct {

	#!/bin/bash

	# https://retropie.org.uk/forum/topic/2295/runcommand-warning-if-voltage-temperature-throttling

	#Flag Bits
	UNDERVOLTED=0x1
	CAPPED=0x2
	THROTTLED=0x4
	HAS_UNDERVOLTED=0x10000
	HAS_CAPPED=0x20000

	#!/usr/bin/env python
	#
	# erase the esp8266 flash
	# sudo $(which esptool.py) --port /dev/ttyUSB0 erase_flash
	# write the micropython firmware
	# sudo $(which esptool.py) --port /dev/ttyUSB0 --baud 460800 write_flash --flash_size=detect -fm dio 0 /tmp/esp8266-20190125-v1.10.bin
	# save this file to esp8266_wifi.py
	# add your wireless network/password to the wifi.connect() line
	# run:
	# echo "f=open('/main.py','w')"