New approach: user processes get two cspaces, upper and lower, mapped such that upper capabilities are addressed 0xAA...... and lower caps are 0x00....BB. Services go in the upper cspace and file descriptors in the lower. User processes lose the ability to modify their own cspace, and all lower capabilities are managed by sysinit.
New filetab interface (implemented by proc) is used to manage the lower cspace, you pass it to a filesystem on open.
I *really* need to figure out a better way of managing file descriptor lifetimes
I think I will have to do something about file desctiptors
nostr:npub1suam9f3gwqeqxstd3rlccpekpfuxrgawc8est0jtkhpzm63zz5nqxtszrk nostr:npub1sg4rcvkxkp3sx7f0ex8rtdd9ylcdd2fchtfm22fy45h4w02p306qq7xslc It’s been wonderful watching this project slowly unfold over the past year.
As I recall this started as a test of harelang? Did it evolve into a full blown, actually serious new OS effort?
Whatever it is, it’s very exciting. 😁
nostr:npub1qtxx0w9mgv9qs4waw7h2m6qvwqaaz686zdhazuj3qmuxpqfqts3qtrdvvy nostr:npub1suam9f3gwqeqxstd3rlccpekpfuxrgawc8est0jtkhpzm63zz5nqxtszrk initially I started working on it because I wanted to see if you could use Hare to write an operating system. Now I dunno, it's fun so I keep working on it
My code is, of course, perfect and therefore it never segfaults, but just in case I added this
I definitely don't need this to debug any fault in particular

Implemented MBR partitions today, GPT soon?
Aside, this is probably sufficient to dual-boot Ares and Linux on my laptop once I have the inclination to set that up

nostr:npub128z8vfdg9krjxxmnnpzgw50327n2a8s6dc5lmlsgetz33j6ea6ts0ddec0 nostr:npub16z76095gd8xctwdfqxgcmg5revavhr3qd7rsks7a9272xvtqce7swtfmyl not sure about "great" but nearly all of them are good enough
nostr:npub1dj6x4lwjgkdc6jgf2md9aw3d8jtfe840rcw47zt6ptyys2rnl7eqxfp9tr no, but it hasn't gotten any better and it was always pretty bad
Alpine is really great, except for the internal politics, which are horrible.
Good luck with the whole anti-adblocker thing Google, that will totally last at least, like, a week before the adblockers figure out how to shut you up
If you make a nonfree fork of your code to save it from AWS then you are doing the same thing with your community that AWS would have done, only worse
January 2021: Elastic steals ElasticSearch from its community, shifts to nonfree version
November 2022: Elastic lays off 13% of its staff
Take notes.
nostr:npub1tgexgylwtx0wr5kxmwwuuuh84mspu3w93wvnte3hs7h7jp7v4qts7djx9v I haven't made much progress
More filesystem stuff

nostr:npub14wsy68pyduanfdrqrrrr7j62qezr0nemfvsprcvkyk7xz49gyrxs0rdrhu for sure. Not reinventing everything
So the ext4 driver for Mercury is admittedly just glue code connecting the Mercury IPC system to lwext4, but it is only about 500 lines which is cool
lmfao @ that bitcoin shit which generated private keys with a mersenne twister