Stories
Slash Boxes
Comments

SoylentNews is people

Redox OS Exploring Coreboot Payload

posted by Fnord666 on Monday February 25 2019, @05:34AM   Printer-friendly
from the not-redux dept.

Apparition writes:

Redox OS (the Unix-like microkernel OS written in Rust) is working on a native Coreboot payload along with bug fixes and a new release.

Lead Redox OS developer Jeremy Soller tweeted that "it's time for Redox OS to become a Coreboot payload." It looks like Redox OS is working on native Coreboot payload support for this interesting Rust operating system rather than first needing to use one of the bootloaders as a Coreboot payload before hitting Redox OS.

[...] The Redox OS twitter also went on to outline they are working on fixes to their networking stack, fixes to curl / cargo / git, advancing towards the state of being able to self-host itself (build Redox OS on Redox OS), improving the relibc C library implementation, porting more applications to running on Redox OS, and at that point to also prepare a new release. And, yes, exploring Coreboot payload capabilities.

Previously: Microkernel, Rust-Programmed Redox OS's Devs Slam Linux, Unix, GPL

Original Submission

 
This discussion has been archived. No new comments can be posted.
Redox OS Exploring Coreboot Payload | Log In/Create an Account | Top | 12 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1, Insightful) by Anonymous Coward on Monday February 25 2019, @04:26PM (1 child)

    by Anonymous Coward on Monday February 25 2019, @04:26PM (#806368)

    In other words "we're addressing Linux and the BSD's only, if you're not in that group, fuck you". With language like that directed at them, it pretty much means no-one outside that group will even try and implement it, which in turn kinda limits its applicability as a multi-boot format.

    Today.

    They have to start somewhere, and start with something small enough that they can build it successfully. There is nothing preventing them from expanding beyond this feature-set once it's built and running. The attitude that it has to have EVERYTHING all at once is limited and not helpful.

    Starting Score:    0  points
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Total Score:   1  

  • (Score: 3, Informative) by driverless on Tuesday February 26 2019, @12:01AM

    by driverless (4770) on Tuesday February 26 2019, @12:01AM (#806684)

    In other words "we're addressing Linux and the BSD's only, if you're not in that group, fuck you". With language like that directed at them, it pretty much means no-one outside that group will even try and implement it, which in turn kinda limits its applicability as a multi-boot format.

    Today.

    They have to start somewhere

    Look at the dates on that document. They started somewhere twenty-four years ago. That document has since grown up, enlisted in the military, served its country overseas, returned, gone to college on the GI bill, met and married a cute PDF from freshman year, and is now raising little documents of its own.

    I understand the principle of starting slowly, but the next step after that should be "gradually speed up", not "stop" (meaning "not spread beyond it's initial 24-year-old target set, the Linux/BSD/*nix set of OSes". It lives on because it's the format used for Grub, but it's the tail wagging the dog now, Grub is the driver, not the document).