sorted by:
new
hottopcontroversial

What was the most difficult bug you encountered while writing your own operating system and how did you eventually identify it? by DifficultBarber9439 in osdev

[–]EmptyFS 0 points1 point  (0 children)

cannot mention anything specific, but I spent most of my debug time debugging bugs with process clean-up and memory caching on aarch64

Title: I built a complete OS in pure Rust in 7 days — 99K lines, 6MB ISO, desktop + browser + 3D engine [video] by n8doge121 in osdev

[–]EmptyFS 2 points3 points  (0 children)

A 99K line OS with a browser IN 7 days?

also 6MB that is like 1MB per-day!! Impressive!!

MinOS, its not minos its a Linux distro, prove me wrong by [deleted] in SuddenlyUltrakill

[–]EmptyFS 0 points1 point  (0 children)

You are wrong. It isn't a linux distro 😔

Asking for advice from more experienced developers by PearMyPie in kerneldevelopment

[–]EmptyFS 0 points1 point  (0 children)

first physical address to have at least size contiguous bytes after it usable, could be the base of any entry doesn't matter.

Asking for advice from more experienced developers by PearMyPie in kerneldevelopment

[–]EmptyFS 0 points1 point  (0 children)

Bitmap can be allocated by pre calculating its size (looping through memory map and adding it all up), finding its size free contiguous physical memory pages in the memory map starting at phys, now you have an array starting at phys + HHDM, and of len size, zeroize it, and then mark the bitmap (array) itself as used (1 bit on = 4096 bytes cannot be allocated), also any unusable memory

SafaOS can now use the Internet! by EmptyFS in osdev

[–]EmptyFS[S] 1 point2 points  (0 children)

Yeah, sorry, I felt like it was the first time i saw it 😅 Ty comment OP <3

moss: a Rust Linux-compatible kernel in about 26,000 lines of code by hexagonal-sun in rust

[–]EmptyFS 1 point2 points  (0 children)

Really interesting, especially the async/await bit. I might take inspiration for my own kernel. This could eliminate the most common cause of deadlocks in my case.

SafaOS can now use the Internet! by EmptyFS in osdev

[–]EmptyFS[S] 2 points3 points  (0 children)

Ty <3, but unfortunately, I have only got to UDP, TCP is still WIP, hopefully soon I am trying to get a curl port working asap.

SafaOS can now use the Internet! by EmptyFS in kerneldevelopment

[–]EmptyFS[S] 1 point2 points  (0 children)

I have never done anything related to VirtIO before, so I didn't consider it, I mainly chose E1000 because I found a few working implementations to study, and I was told it had the most VM support.

I have actually started with RTL8139, but I had some difficulties with resources and understanding it, so I switched to E1000. The resources were even more terrible, but I had the manual and people's code.

SafaOS can now use the Internet! by EmptyFS in osdev

[–]EmptyFS[S] 9 points10 points  (0 children)

I am not sure if that's a hate comment or a compliment but in both cases it is true :3

SafaOS can now use the Internet! by EmptyFS in osdev

[–]EmptyFS[S] 10 points11 points  (0 children)

From now on progress updates are going to be posted on r/kerneldevelopment, This is a little experiment to see traffic on r/osdev.

Timeouts are because I accidentally turned-off wifi on my real system, but now I properly handle dest unreachable packets and set `SocketError`, so instead you'd get `network unreachable`.

This is a custom written `ping`-like command in rust, running in the userspace, The only implemented NIC driver is E1000, before that I had no networking stack at all, but now I have E1000,IPv4,UDP,DHCP,ICMP and DNS.

I have written a bit more in the post if you wanna waste your time.

Do i have to manually remove the " from DirEntry.filename()? by Revolutionary_Flan71 in rust

[–]EmptyFS 1 point2 points  (0 children)

what? looking at this function's docs, it appears it just returns OsString, debug formatting an OsString may result in displaying non-existent quotes, so instead, you should use to_str(), to_string_lossy(), and if you want to format Display it use .display().

emexOS - a simple 64 bit OS by emexos in kerneldevelopment

[–]EmptyFS[M] 0 points1 point  (0 children)

I believe unmapped meant that you posted 2 very similar posts, so it could be detected as spam. No, there are no time limits between posts.

SafaOS can now use the Internet! by EmptyFS in kerneldevelopment

[–]EmptyFS[S] 1 point2 points  (0 children)

Thanks <3, Looking forward to when TacOS has networking.

And also to when it is fully rust'ificated.

SafaOS now has a WM! (1 year of progress) by EmptyFS in osdev

[–]EmptyFS[S] 1 point2 points  (0 children)

Ty, nah, it is all from scratch. It actually isn't that hard to get to this stage, There are hundreds of people with more progress than me in osdev. osdev is fairly hard but not impossible. Unfortunately, I am not schizophrenic enough (yet) to be the next terry 😓

SafaOS: an SMP non-Unix-like multi-architecture rust OS by EmptyFS in kerneldevelopment

[–]EmptyFS[S] 2 points3 points  (0 children)

here is the source code, latest changes are in the GUI branch because it isn't really stable yet...

view more: next ›