Torbjörn Törnkvist etnt
etnt
/ gist:4475308
Created
January 7, 2013 14:20
I've created a bridge with two internal ports (with IP's set) and set a controller. With netcat I'm able to communicate between the two ports although no controller is running (yet). Why? I was expecting they would be unable to communicate until my controller is running and set things up...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| $ sudo ovs-vsctl show | |
| ce811cee-69c8-4123-87a4-8132a5f77b28 | |
| Bridge "br0-loc" | |
| Controller "tcp:127.0.0.1" | |
| fail_mode: secure | |
| Port "a10" | |
| Interface "a10" | |
| type: internal | |
| Port "veth1" | |
| Interface "veth1" |
etnt
/ gist:3b62a226f4617c575982cda85dc75c94
Created
January 15, 2025 18:24
Hanging when calling ssh_channel_read from Zig
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| (lldb) bt | |
| * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP | |
| * frame #0: 0x00000001857b2710 libsystem_kernel.dylib`poll + 8 | |
| frame #1: 0x00000001001f3464 libssh.4.dylib`ssh_poll_ctx_dopoll + 144 | |
| frame #2: 0x00000001001f43fc libssh.4.dylib`ssh_handle_packets + 184 | |
| frame #3: 0x00000001001f4250 libssh.4.dylib`ssh_handle_packets_termination + 208 | |
| frame #4: 0x00000001001d9f14 libssh.4.dylib`ssh_channel_read_timeout + 168 | |
| frame #5: 0x000000010001fde0 zinc`netconf_ssh.SshChannel.read(self=0x0000000100260038, buffer=(ptr = "\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\xaa\ |
etnt
/ gist:65f2b171f38cd81b4b446d9f3803df70
Created
May 20, 2026 17:20
Running Erlang, BEAM and Tyn kernel
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Quickstart: Running BEAM on Tyn | |
| Step-by-step guide to get the Erlang BEAM VM running on the Tyn microkernel with KVM/QEMU. | |
| ## Prerequisites | |
| - Rust nightly toolchain with `rust-src` component | |
| - QEMU with KVM support (`qemu-system-x86_64`) | |
| - `musl-tools` (`sudo apt install musl-tools`) | |
| - `autoconf`, `m4`, `gcc`, `make` |