SUsuprjami·May 7, 2026
Go forth and combine with this: https://github.com/o8vm/rust_dos
In Show HN: TRUST – Coding Rust like it's 1989o8vm
rust_dos
Rust2021–2026
o8vm / rust_dos
rust_dos
Rust DOS : Creating a DOS executable with Rust
5Distinct people
5Mentions
0Explicit recommenders
203GitHub stars
What to know before exploring
What it is
Rust DOS : Creating a DOS executable with Rust
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year5 dated mentions
Observed mentions: 2021-01-22 14:23:47 UTC to 2026-05-07 23:52:12 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesYou do not need segment registers much if you stick to the tiny model. Here is someone compiling Rust to a 16-bit DOS COM executable:
https://github.com/o8vm/rust_dos
Not sure what the approach would be for them to expand that to support segments.
In DJGPP there are macros to allow your protected mode application access physical real-mode addresses (like when you want to write to video RAM). I don't know if IA-16 also does something like that, or if they added far/near keywords to the language like old 16-bit C compilers did (at least the ones I used).
Free Pascal has helper-functions to work with segment+offset pointer pairs, also without having to modify the language itself. I think that would work well enough in C, but I guess the old method of adding non-standard keywords was seen as slightly more convenient.
In DJGPP> Rust DOS : Creating a DOS executable with Rust
https://github.com/o8vm/rust_dos
In Who invented file extensions in file names?Rust can link 32-bit code that can run 16-bit segmented mode [0] and if you can figure out the right set of protected mode magick, you could almost certainly get it working in flat mode.
I started working on a DOS-based project and played around with Rust before deciding that it was going to be tough and would not be as optimal as just dropping to C and using OpenWatcom which is pretty capable considering its age, IMO.
[0] https://github.com/o8vm/rust_dos
In I work in DOS for a day (2014)Rust DOS: Creating a DOS Executable with Rust
6 points · Open discussion