Live data from Hacker News

Redox – A Unix-Like Operating System Written in Rust

redox-os.org

101–110 of 215 posts

Re: Redox – A Unix-Like Operating System Written in Rust

#102
post #7

Earlier quoted context omitted.

When choosing a name you can't exactly predict future people using your name.

Yeah, but if you are unknown you can easily rebrand

They are well-known in the world of kernel-developers. If JS developers don't know something... well, who cares?

Re: Redox – A Unix-Like Operating System Written in Rust

#103
I like the home page: unusually good choice of attributes for a security or reliability-focused OS. The path usually not taken. So, for those familiar, what milestones has the project achieved since we last discussed it here?

Note: Best bang-for-buck will be getting solid networking, filesystem, time API, and crypto lib in there. People can crank out purpose-built appliances or VM's for all Internet or Web servers with... not ease but easier. 80/20 rule always best for OSS projects to get adoption & contributions up. ;)

Re: Redox – A Unix-Like Operating System Written in Rust

#104
post #85

Earlier quoted context omitted.

Project lead here. I haven't had time in the last few weeks to work on this, so the book is pretty far behind the kernel itself at the moment. Playing the long game. I was hoping to do some more today, in fact...

The "everything is a URL" concept is interesting. QNX uses pathnames in a somewhat similar way; programs with the privilege to do so can register to own some portion of the pathname space, and requests with such pathnames go to that program. The kernel has no idea what pathnames mean. This gets file systems out of the kernel. It looks like Redox is doing something similar, but not enough of the documentation is writt…

To be clear, lead on intermezzOS, not Redox. I do some small editing to their docs but don't regularly contribute.

Re: Redox – A Unix-Like Operating System Written in Rust

#105
post #46

Earlier quoted context omitted.

Project lead here. I haven't had time in the last few weeks to work on this, so the book is pretty far behind the kernel itself at the moment. Playing the long game. I was hoping to do some more today, in fact...

I'm reading through now, and would love to contribute. I've been trying to break into this space (systems programming, especially OS and compilers) for a long time and the biggest hurdle for me has been to actually do it . I really appreciate that this project is focused on explaining just enough to jump in, complemented with nods to further resources that can add on to whatever knowledge the reader brings. Steve, th…

Thanks so much. We had a few contributors at the start, but once I lost time, so did they. Would be very happy to have you involved :)

Re: Redox – A Unix-Like Operating System Written in Rust

#106
post #50

Earlier quoted context omitted.

Project lead here. I haven't had time in the last few weeks to work on this, so the book is pretty far behind the kernel itself at the moment. Playing the long game. I was hoping to do some more today, in fact...

This is great and so much clearer than osdev wiki. I've wanted to learn os development for quite some time and I think this is where I'll start.

That is exactly my goal. Thanks :)

Re: Redox – A Unix-Like Operating System Written in Rust

#107

Earlier quoted context omitted.

Project lead here. I haven't had time in the last few weeks to work on this, so the book is pretty far behind the kernel itself at the moment. Playing the long game. I was hoping to do some more today, in fact...

It looks really interesting! I'm going to be looking at it probably next weekend :)

Awesome. Please open issues if anything is confusing!

Re: Redox – A Unix-Like Operating System Written in Rust

#109
post #18

Earlier quoted context omitted.

Warning: I have no idea about systems programming. I understand that the amount of lines of driver code comes from the variety of devices. But still, it looks completely unbalanced, when compared to the kernel code itself. So I have some questions here: 1) Shouldn't there be common interfaces / abstractions for most of the devices? 2) If they exist, could they be improved somehow? 3) A bit unrelated, but how fun / in…

1) They do, 2) ... but the meat of a driver is putting the right values in the right registers of some chip, and sometimes work around bugs in said chip, or sometimes take into account that popular variant that's almost the same that the original but not quite... It takes a lot of boilerplate code. 3) It depends on your definition of fun. A driver by definition is a middle man between the OS and the hardware; so prog…

[deleted]
Post reply on HN