mforney

6 ms·

1.
by mforney 4mo ago
I followed the code path when you change the cabinet type, and saw it write some values to the DSP based on a 2D array of doubles, one for each cabinet, each with 41 values, and it was processing them 5 at a time. Looking at the values, the
2.
by mforney 4mo ago
Unfortunately there were no firmware updates for the THR10c, so the only way to get the firmware is to dump it from the device.
3.
by mforney 4y ago
git -C /src/oasis pull && samu commit && doas git -C / merge The first command pulls updates from the source repository, the second command builds a new filesystem tree and commits it, the third command merges
4.
by mforney 4y ago
Sorry for the confusing wording. I meant that oasis has more similarities to a BSD than a typical Linux distribution. I've updated the README to be a bit clearer.
5.
by mforney 5y ago
> A simple way to fix this would be to shift c by 24u, "(c << 24u)" which would promote both values to unsigned int This works for most arithmetic operators, but not shift: "The type of the result is that of the prom
6.
by mforney 6y ago
Yep, you can install firefox via pkgsrc or nix. Due to the complexity of the modern web browser and all of its dependencies, it is unlikely to ever be part of oasis itself.
7.
by mforney 6y ago
There is rudimentary hardware acceleration for certain older GPUs that I own in wld (intel at https://github.com/michaelforney/wld/blob/master/intel.c and nouveau https://github.com/micha
8.
by mforney 6y ago
> I was ever so slightly disappointed to see how manual the packaging is, with every .c file listed in each lua script. It looks quite maintenance-intensive. I was worried about this, too, but it turns out most of the cost in just the in
9.
by mforney 6y ago
I suppose you could argue that, but it is not a package manager in the traditional sense. My main point here is that once you build the system, there is no longer any notion of "package", just files that make up your root filesyst
10.
by mforney 6y ago
> Statically linking all the OS utilities to their dependency libraries, over and over again? Dear god that sounds awful. Just curious, why does that sound awful to you? Are you worried that it will take a long time to relink the binarie
11.
by mforney 6y ago
The idea with oasis is to choose smaller software with fewer dependencies that offsets the slightly higher disk usage, as well as to deliberately not have thousands of binaries.
12.
by mforney 6y ago
It exists because I wanted a complete system where I could easily experiment with various minimal/alternative software. I wanted this so that I could easily understand and hack on any component without spending weeks/months famili
13.
by mforney 6y ago
Yes, but with the oasis build system this is just a single command to do an incremental build that relinks your binaries and takes a matter of seconds. The user experience is essentially the same as updating your system on a dynamically-lin
14.
by mforney 6y ago
You bring up some good points here. Here are some of my experiences with these problems when working on oasis (my static linux distro). > 1. symbol collisions -> accidental interposition (and crashes); I've encountered symbol col
15.
by mforney 6y ago
I'm not sure what you mean here. Are you asking whether I build my kernel drivers as modules or built-in? Personally, I build my kernels without modules, but I've never heard of that technique being called "static-linking Lin
16.
by mforney 6y ago
I don't think stali has seen any activity in several years. As far as I know, the only completely statically linked Linux distribution that is actively developed is my own project (inspired by stali), oasis: https://github.c
17.
by mforney 6y ago
Most Linux/musl systems support it. On Alpine, gcc is built with `--enable-default-pie` so all static libraries can be linked into a static PIE. On vanilla gcc (since version 8 when static PIE was upstreamed), `-static` means non-PIE s