IRC channel logs

<oriansj>I think I forgot storing of file size or any permission meta-data

<oriansj>I probably should store the file size in the directory as it only needed to be stored once.

<xentrac>if you don't have hardlinks, yeah

<xentrac>you need to special-case . and .. but you need to special-case those anyway

<oriansj>well it is a copy-on-write to remove need for journaling.

<oriansj>also the filesystem on disk itself doesn't have to support . or .. as those can be handled by the code running filesystem support

<xentrac>you don't need journaling if it's just in RAM

<oriansj>name idea: En Passant filesystem?

<xentrac>haha, because everyone always forgets about it and it's probably not all that useful anyway?

<xentrac>how about Castling or Sicilian Defense or Promotion?

<oriansj>knight-fork?

<xentrac>Bongcloud? Open Catalan?

<xentrac>knight-fork is a strong move but it strongly implies that you're forking Knight

<oriansj>forking-knight filesystem

<oriansj>because file forks and the first filesystem we will make for knight?

<oriansj>or is GFK a better variation (Good forking knight)

<xentrac>ha! that's greate!

<Hagfish>it's a little crude

<Hagfish>you could call it the London System, and then if you improve the performance, you could call it the Accelerated London System

<xentrac>it's not in the same ballpark of crude as "hardcore forking action'

<stikonas[m]>Had a tiny bit of time, finished GAS prototype of M0 for risc-v

<oriansj>stikonas: nice

<stikonas[m]>Shouldn't be too hard to convert it to final form (M0.hex2)

2021-09-02.log