3 ms·

I have also developed a preemtive-multitasking O/S (and some programming languages to build this and apps) targeted for embedded soft cpu (not x86). I build to

I have also developed a preemtive-multitasking O/S (and some programming languages to build this and apps) targeted for embedded soft cpu (not x86). I build tools in Rust, too. I joined your discord but cannot comment anywhere yet (lack of permissions). Do you use AI coding agents?

crackanimador 1mo ago
And by the way, I think I've fixed the Discord issue. Try testing it when you can.
- softwarewright 1mo ago
  yes, works now, thanks
crackanimador 1mo ago
Yes. But only for the coding. The rest is still done by me (hardware testing, QEMU, debugging, instructions, ideas, and so on).
- softwarewright 1mo ago
  I have forked, cloned, and built (had to pin a specific nightly Rust for it to build). When I run it, it crashed at login; I reran it with VNC, was able to login as root, issue ls and uptime, but then it crashed. My AI is debugging...
  - softwarewright 1mo ago
    My AI wrote scripts to launch and attach. I was able to do a lot login in as root. One bug: when I run the ring3 demo, the shell stops accepting input.
  - softwarewright 1mo ago
    so the built-in nano helps a lot, since the help output scrolled off the screen. I tried to use head, less, and more. I could redirect help output to a file (but until I found nano, could not page that). I also looked for dd. The VNC UI seems generally stable, I was able to log in as all three users, and issue many commands. Is there a bundled assembler or compiler. How can I write apps for this? Do you have a way to cross-compile and mount a shared folder or scp binaries in?
    - crackanimador 1mo ago
      Hey. Sorry I couldn't reply sooner (I was asleep). Here's how it works: you put your files directly from your main OS into the "inyect" folder (where the `bin` folder and other items are located). You add your binaries there and then rebuild the ISO. That way, when you boot up MesaOS, your file(s) should be inside.
  - softwarewright 1mo ago
    In my fork, I've added ./experiments where I hacked together a shell wrapper for a no_std Rust app to implement head -<n>. help > help.txt <script path>/head -2 help.txt works. This shows how I can cross-compile code to run in the MesaOS shell. This is a workaround until I have better libraries/APIs for argc/argv handling, file I/O, etc. Fun!

crackanimador 1mo ago

And by the way, I think I've fixed the Discord issue. Try testing it when you can.

softwarewright 1mo ago
yes, works now, thanks

crackanimador 1mo ago

Yes. But only for the coding. The rest is still done by me (hardware testing, QEMU, debugging, instructions, ideas, and so on).

softwarewright 1mo ago
I have forked, cloned, and built (had to pin a specific nightly Rust for it to build). When I run it, it crashed at login; I reran it with VNC, was able to login as root, issue ls and uptime, but then it crashed. My AI is debugging...
- softwarewright 1mo ago
  My AI wrote scripts to launch and attach. I was able to do a lot login in as root. One bug: when I run the ring3 demo, the shell stops accepting input.
- softwarewright 1mo ago
  so the built-in nano helps a lot, since the help output scrolled off the screen. I tried to use head, less, and more. I could redirect help output to a file (but until I found nano, could not page that). I also looked for dd. The VNC UI seems generally stable, I was able to log in as all three users, and issue many commands. Is there a bundled assembler or compiler. How can I write apps for this? Do you have a way to cross-compile and mount a shared folder or scp binaries in?
  - crackanimador 1mo ago
    Hey. Sorry I couldn't reply sooner (I was asleep). Here's how it works: you put your files directly from your main OS into the "inyect" folder (where the `bin` folder and other items are located). You add your binaries there and then rebuild the ISO. That way, when you boot up MesaOS, your file(s) should be inside.
- softwarewright 1mo ago
  In my fork, I've added ./experiments where I hacked together a shell wrapper for a no_std Rust app to implement head -<n>. help > help.txt <script path>/head -2 help.txt works. This shows how I can cross-compile code to run in the MesaOS shell. This is a workaround until I have better libraries/APIs for argc/argv handling, file I/O, etc. Fun!