Husband, father, cloud engineer.
@Zezin just displaying quick information, could have it open in a window on an external monitor too.
I mostly did it as part of a challenge of getting it setup on the CHIP since the screen is so small and I wanted it console/text only.
While looking for some cables today, dug out some old SBCs.
Left: IFC6540 - Snapdragon 805
Right: IFC6410 - Snapdragon 600
Middle: Experimental modular Snapdragon SoC + Breakout board.
The IFCs are dual-boot to either Android or Ubuntu. Downside is they store the boot partition on eMMC and require specialized Linaro builds and aren't as easy to setup as a RaspberryPi.
One thing I really like about them is they have an actual SATA port instead of just USB mass storage.
@kelbot I've really been digging reading Gemini on the PocketCHIP.
Have an older Kindle that I may try to leverage for more than ebooks, but I really like the tactile keyboard on the CHIP.
Android was a lot of fun in the early years, and hacking away on AOSP were good times. But modern phones are themselves heavily proprietary, (even the Allwinner SoCs in the PinePhone heavily use binary blobs)
I love FOSS, but phones are so proprietary at hardware level it's not worth the effort for me anymore so I focus on FOSS other places.
For fun, here's the Surfboard I used when hacking on AOSP in 2012, it was running Android 2.3.5 (mmmm Gingerbread).
@Zezin For context I've had: OG Droid, Google Nexus, HTC One, Google Pixel Android phones. Rooted, flashed, built custom kernels, installed Debian, compiled OpenAFS kernel modules, and worked in engineering at the Company that makes all the chips for mainstream Android phones.
Why I left.
Google kills things, Inbox was the last straw
Rooting/flashing is fun but I need a phone to work and stay supported.
Apple ecosystem for families has no peer equivalence.
Deep inside is NeXT.
@kelbot I start everything in #!/bin/sh, and then immediately move to Ruby or Python once "need an array" or "need to parse json" show up.
Then there's no focusing on how to do it but what to do with it
Initial setup of my PocketCHIP desk terminal using Tmux and various terminal utilities.
How to DDOS a uWSGI app on Kubernetes.
Add 500+ nodes to a cluster, use an ALB ingress with a 15 second healthcheck with nodePort.
Fire up stern and watch as all 500 nodes will continually hit the healthcheck and pods start to restart with,
uWSGI listen queue of socket ":1111" (fd: 3) full !!! (101/100) ***
Solution: If using aws-cni, use ClusterIP instead of nodePort. Then only replicas and not nodes are in the ALB target group.
sshd will run by default, but you'll need to setup a secondary user other than root.
This guide gives a good overview of how to install it on a RPI3,
I used to run it in the early aughts in combination with FreeBSD to support a Counter-Strike server (back when it could do Linux emulation) https://web.archive.org/web/20020610071911/http://www.ecliptik.com/about.php
Also run OpenBSD on my work laptop (x61s Thinkpad) for a couple of years and it worked great. This was for a Fortune 500 too with all the compliance and restrictions that came with it.
@kelbot when I was looking at the default pocket-wm and saw it was dwm my first thought was awesome, it's a suckless tool.
Second thought was how it's probably not going to be straightforward to config, haha.
@kelbot these look nice, thanks for the links.
Fluxbox on the CHIP, while fun, doesn't work all that well unfortunately, even with the touchscreen.
I challenge myself when working on OpenBSD (as a hobby, not professionally) to only use the official sources and on-system documentation first before hitting up duckduckgo and the results are good.
Husband, father, cloud engineer.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.