<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on kitzman&#39;s place</title>
    <link>https://tilde.club/~kitzman/posts/</link>
    <description>Recent content in Posts on kitzman&#39;s place</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 28 Dec 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://tilde.club/~kitzman/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>/mnt/term on UNIX, and other hacks</title>
      <link>https://tilde.club/~kitzman/posts/2023-12-28_unix_mnt_term/</link>
      <pubDate>Thu, 28 Dec 2023 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2023-12-28_unix_mnt_term/</guid>
      <description>Introduction UNIX-like operating systems today already have solutions for file-sharing across machines, and remotely mounting filesystems. The easiest, and a pretty solid way, if a shared network filesystem does not exist, is to use sftp via FUSE. Even on Plan9, mounting a remote UNIX machine&amp;rsquo;s filesystem can be done through sshfs(4).
On Plan9, when rcpu-ing to remote systems, the script exports the whole client tree, which is then mounted on /mnt/term.</description>
    </item>
    
    <item>
      <title>Sysinfo and Vac Archives over Gemini</title>
      <link>https://tilde.club/~kitzman/posts/2023-04-15_vac_over_gemini/</link>
      <pubDate>Sat, 15 Apr 2023 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2023-04-15_vac_over_gemini/</guid>
      <description>Introduction I have a 9front cpu server, which I use for working remotely on my personal projects, build software, and keep backups.
One of its uses, is for keeping vac backups of documentation. As I sometimes needed to access it, and to share it as well, importing and mounting the vac filesystems was not easily accessible, especially for someone who doesn&amp;rsquo;t want to learn to use Plan9.
Gemini Serving the archives via a protocol such as HTTP or Gemini would be the preferred way for most people to access and share files.</description>
    </item>
    
    <item>
      <title>Interfacing an LCD with an SBC - with Zig! #1</title>
      <link>https://tilde.club/~kitzman/posts/2022-05-03_lcd_on_an_sbc_1/</link>
      <pubDate>Tue, 03 May 2022 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2022-05-03_lcd_on_an_sbc_1/</guid>
      <description>Intro When one looks up how to add a display to an SBC (such as a Raspberry PI), most of the examples/tutorials just say to use this or that kernel module, or library.
Since I&amp;rsquo;m a DIY person, I refused this approach when it came to this parallel I/O I randomly got my hands on.
This can shed some light, more on how easy it is to bootstrap a cross platform embedded program, than how to read documentation/a datasheet.</description>
    </item>
    
    <item>
      <title>Watchtower Clock (#1)</title>
      <link>https://tilde.club/~kitzman/posts/2022-02-09_watchtower_clock/</link>
      <pubDate>Wed, 09 Feb 2022 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2022-02-09_watchtower_clock/</guid>
      <description>Intro I can&amp;rsquo;t count how many times a regular alarm failed to wake me up.
But I know what would work - a strobe and a dissonant sound. Powerful lights help the brain, especially during winter, to reset its circadian rhythm. When my sleep is shifted by 6-12h, -if- I manage to wake up, I use light to try to get myself back on track.
Notice the big -if-. How about I create my own clock?</description>
    </item>
    
    <item>
      <title>Android for IoT</title>
      <link>https://tilde.club/~kitzman/posts/2022-02-06_for_iot_1/</link>
      <pubDate>Sun, 06 Feb 2022 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2022-02-06_for_iot_1/</guid>
      <description>Introduction So&amp;hellip;
My previous attempt to use pmOS was not so successful&amp;hellip; &amp;hellip; probably due to lack of vendor libraries which would require the native Android libc, lack of set properties, and daemons I&amp;rsquo;d have to compile in order to use, let&amp;rsquo;s say, the GSM network.
So I decided to give Android a try, as a general-purpose IoT operating system ^^.
Last time I saw it in the wild, for the same usage, was for ODroid.</description>
    </item>
    
    <item>
      <title>Playing with Containers (and Rust)</title>
      <link>https://tilde.club/~kitzman/posts/2021-10-09_playing_with_containers/</link>
      <pubDate>Sat, 09 Oct 2021 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2021-10-09_playing_with_containers/</guid>
      <description>Synopsis I started working, in my free time, on my own solution to containers and VM management. The motivation was, primarily to learn, but decided it can also serve as a tool for others.
I&amp;rsquo;ve had issues with Firejail (non-programmable configuration), Guix (lack of desired features) and QubesOS cannot run on all hardware. I think the best would be to provide a solution which, does not only come with pre-configured settings, but one should be able to program their desired behaviour.</description>
    </item>
    
    <item>
      <title>PostmarketOS mingling</title>
      <link>https://tilde.club/~kitzman/posts/2021-09-26_postmarketos_mingling/</link>
      <pubDate>Sun, 26 Sep 2021 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2021-09-26_postmarketos_mingling/</guid>
      <description>I have this old HTC lying around and I&amp;rsquo;m currently playing around with it.
Setting it up Obviously the first step is installing a bootloader after unlocking. The second step is building and installing pmOS itself, and the &amp;lsquo;pmbootstrap&amp;rsquo; tool does a great job at automating the process.
The partition table is slightly different than Android systems. pmOS creates a single partition, which in itself contains a partition table. This will have the same format as any Linux partition table.</description>
    </item>
    
    <item>
      <title>Reverse engineering &#39;nvdata&#39;</title>
      <link>https://tilde.club/~kitzman/posts/2021-09-26_reversing_nvdata_1/</link>
      <pubDate>Sun, 26 Sep 2021 00:00:00 +0000</pubDate>
      
      <guid>https://tilde.club/~kitzman/posts/2021-09-26_reversing_nvdata_1/</guid>
      <description>Introduction On mobile phone devices, there are different partitions/sections of data, which differs from vendor to vendor.
Samsung for example, keeps the partition information in a PIT file, and the partitions are various: radio (GSM/LTE/etc) firmware, bootloader, network vendor information, etc.
One of the most crucial ones, the EFS partition hold information which is never supposed to be overwritten, such as the IMEI, network vendor data, etc.
nvdata.bin You probably guessed that &amp;ldquo;nvdata&amp;rdquo; stands for &amp;ldquo;network vendor data&amp;rdquo;.</description>
    </item>
    
  </channel>
</rss>
