@movq@www.uninformativ.de Right š
Fark me OS Dev is hard š¤£
@movq@www.uninformativ.de thatās just š šÆļø.
@movq@www.uninformativ.de infinite interaction!
./bin/mu -B -o ... -p muos/amd64 ... target.
@lyse@lyse.isobeef.org Thanks!
Wow, as I anticipated, this is waaay out of my capabilities to really understand it. But Iām quite happy to just have spotted a mistake in an explanatory comment in section 4.5.2 āThe icode Arrayā. Of course, it should be /e + tc + /i + ni + t\0. Letās hope that my e-mail with the patch actually makes it into Briamās inbox. I fear GMail just hides it in the spam folder.
@bender@twtxt.net gemini-cli, something something https://github.com/google-gemini/gemini-cli/issues/16723
I recently got an email with this byte sequence:
\xf0\x9f\x8e\x81\xf0\x9f\x95\xaf\xef\xb8\x8f
Thatās U+1F381, U+1F56F, U+FE0F. The last one is a āvariation selectorā:
https://unicodeplus.com/U+FE0F
My toolkit renders this incorrectly ā and so do tmux and GNU screen.
Unicode aināt easy. š„“
/me clones the repository, calls gemini-cli, and asks for an executive summary. Gemini-CLI replies āDonāt bother!ā LOL.
@movq@www.uninformativ.de Just 323 pages! Thatās cool, letās have a look. :-)
./bin/mu -B -o ... -p muos/amd64 ... target.
@prologic@twtxt.net Tada! Maybe one day I might look into this lowlevel stuff, too. But I canāt see it on the horizon yet. Happy hacking! :-)
https://github.com/unix-v4-commentary/unix-v4-source-commentary
A comprehensive, line-by-line commentary on the UNIX Fourth Edition source code (released November 1973; tape recovered from June 1974 distribution).
./bin/mu -B -o ... -p muos/amd64 ... target.
@prologic@twtxt.net Iād love to take a look at the code. š
Iām kind of curious to know how much Assembly I need vs. How much of a microkernel can I build purely in Mu (µ)? š¤
Canāt really answer that, because I only made a working kernel for 16-bit real mode yet. That is 99% C, though, only syscall entry points are Assembly. (The OpenWatcom compiler provides C wrappers for triggering software interrupts, which makes things easier.)
But in long mode? No idea yet. š At least changing the page tables will require a tiny little bit of Assembly.
./bin/mu -B -o ... -p muos/amd64 ... target.
Iām kind of curious to know how much Assembly I need vs. How much of a microkernel can I build purely in Mu (µ)? š¤
./bin/mu -B -o ... -p muos/amd64 ... target.
Iāve only got a handful of syscalls working right now. Taking inspiration from the calling convention of the Linux kernel and even made the service/interrupt handler int 0x80h 𤣠Iāve only got read, write, alloc and exit working righ tnow š„²
./bin/mu -B -o ... -p muos/amd64 ... target.
@movq@www.uninformativ.de Yes!
Did you do the whole dance with BIOS boot and everything?
Yup! Farkān LBA shit and all, loading up the GDT, TSS and switching to x86_64 long mode š¤£
./bin/mu -B -o ... -p muos/amd64 ... target.
@prologic@twtxt.net Damn, nice! I know exactly what you mean ā the output/screenshot looks trivial, but thereās so much going on behind the scenes. š
Did you do the whole dance with BIOS boot and everything?
./bin/mu -B -o ... -p muos/amd64 ... target.
Whohoo! š„³
You have no idea how great a feeling this is! This includes the Mu stdlib and runtime as well, not just some simple stupid program, this means a significant portion of the runtime and stdlib ājust worksā⢠š¤£