Live data from Hacker News

Show HN: My from-scratch OS kernel that runs DOOM

github.com

61–70 of 90 posts

Re: Show HN: My from-scratch OS kernel that runs DOOM

#61
post #36

A few months work by one guy and already more capable than the Hurd. Imagine what you could accomplish given 35 years.

Hurd isn't exactly a useful project, but using Doom as the benchmark for the capability of an OS is a bit ridiculous.

Why?

Re: Show HN: My from-scratch OS kernel that runs DOOM

#64

Earlier quoted context omitted.

> A few months work by one guy and already more capable than the Hurd It is no way capable than Hurd. It is a cool project though. Have you used Hurd recently? It can run a modern desktop.

I searched YouTube for actual evidence of Hurd booting to a desktop and only found two videos of Hurd freezing during boot, and a third video of RMS explaining to a very confused convention attendee that he's "never installed GNU slash lynn-ox" because he could just ask someone else to do it. No videos of Hurd running Doom either, but anyone is welcome to create one and share.

Youtube isn't an evidence of anything.

Set up yourself.

Re: Show HN: My from-scratch OS kernel that runs DOOM

#65

Earlier quoted context omitted.

Not being upvoted to the top doesn't mean downvoted. Your negativity is baseless.

[flagged]

The funny thing about meta comments is that they can change

Almost always for the worse - for instance now you have this pointless tangent hanging off a topcomment. That's why the site guidelines ask you not to do this.

Re: Show HN: My from-scratch OS kernel that runs DOOM

#68

Really curious to learn more about TacOS. How does it manage running multiple programs safely at the same time?

Read up on OS design: https://pages.cs.wisc.edu/~remzi/OSTEP/

Read the intro : https://pages.cs.wisc.edu/~remzi/OSTEP/dialogue-virtualizati...

https://wiki.osdev.org/ has platform details and other resources.

Re: Show HN: My from-scratch OS kernel that runs DOOM

#69
post #57

Earlier quoted context omitted.

Thanks for that explanation. I've been doing some low-level programming lately, and I'm getting interested on running stuff bare-metal. Every previous description of multitasking I've seen has been very hand-wavy.

Yeah no problem. Multitasking isn't really complex - it's generally split into two categories: collaborative and preemptive. Collaborative multitasking is simply having user programs call a yield syscall which tells the kernel that it's ready to give up control of the CPU and it switches to the next task, but this is not very secure and is uncommon on newer systems. Alternately, preemptive scheduling generally has a…

> but this is not very secure

Not so much about security but stability. If a program enters an infinite loop then it never yields and the entire system is hung. Hopefully you have an interrupt you can fire off (like ctl-alt-del) that can wake up the kernel and allow you to take action.

Post reply on HN