hipp VS os-tutorial

4. Add SMTP responses that mean "rejecting because your server sends spam" and "rejecting because that user sends spam". Servers can mark sent emails as "Receiver rejected this email" and inform the user.

5. Build a shared spam reporting system that accepts only signed emails and supports searching by email address. Receivers can use it to identify compromised user accounts and reject their email. Senders use it to identify receivers acting in bad faith (reporting ham as spam). A centralized version would be straightforward. A decentralized version would be a challenging project.

6. Add support to the SMTP protocol for reporting rate limits and cooling-off times to email senders. Admins of large shared email systems can feed these metrics into a monitoring system and receive alerts of problems early.

[0] https://github.com/mleonhard/hipp

How to create an OS from scratch

My dude. Your functions have exactly the same names as his. Copying it from a different tutorial based on James Molloy's tutorial does not make it any less James Molloy's code.

I started out with this tutorial: https://github.com/cfenollosa/os-tutorial. It doesn't get you too far but it explains the basics very well, so check it out. After that I looked up James Molloy's kernel tutorials (look it up on Google, it's all on a website). Be advised that he's got a bunch of errors and bugs in the tutorial, there is a whole page on it on the osdev wiki titled known bugs in the JamesM kernel all something like that, but it's still great and gets you pretty far. After that, I chose to develop a FAT32 driver on my own, I can link some sources or my own code for you as well, but it's really up to you to follow what you like. I also found a great youtube series (https://youtube.com/@poncho2364?feature=share9), check out his osdev series, he also has some cool stuff there. And as I said, good luck on your journey and you can ask me in a DM as well if you get stuck somewhere!

tutorial : here

Yeah, I'm following cfenollosa's OS tutorial for guidance. You mentioned that you've seen the same code, with the same bug? What was the solution there?

hey, just in case you actually want to write an operating system, you should check out cfenollosa/os-tutorial: How to create an OS from scratch, it is an amazing tutorial that will get you from basic printing all the way to a command line interface!

You might be able to sink your teeth into something like this if you're interested in real os development, haven't got far myself but it's fun and you'll learn a lot https://github.com/cfenollosa/os-tutorial

So I made a 16-bit x86 toy OS in pure assembly. 3 months ago, I found a very fun tutorial on github that is about Operating system development. I read the first few chapter and from there I made a very simple, extensible (?) toy operating system that could run on hardware (yes, it is madness).