Announcement

Collapse
No announcement yet.

Oreboot Is Taking Shape As Rust'ed, Purely Open-Source Focused Coreboot

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #21
    Oreboot similar to Libreboot is focused on targeting "truly open systems" as Coreboot without binary blobs.
    Requires compiler which can not be built from source code without downloading a binary blob.

    Comment


    • #22
      Originally posted by Vistaus View Post

      Rootboot.
      Rooty Tooty Rusty Booty

      Comment


      • #23
        Originally posted by jjkk View Post

        Requires compiler which can not be built from source code without downloading a binary blob.
        C is no different aside from having a forest of options you can compare the output of to achieve some degree of trust and, on the Rust side, there's mrustc if you want to re-bootstrap from a trusted C++ compiler... though you may have to do it in multiple mrustc->rustc->rustc->rustc stages to reach the current version of rustc since it is eager about using new language features it implements within itself and mrustc has limited manpower to keep up.
        Last edited by ssokolow; 09-03-2019, 06:13 PM.

        Comment


        • #24
          Originally posted by ssokolow View Post

          On the Rust side, there's mrustc if you want to re-bootstrap from a trusted C++ compiler...
          It seems you have never tried the method you are suggesting. Because it is utterly broken. If that was possible why would the one and only official method to install Rust was so ridiculous and laughable?

          Code:
          curl https://sh.rustup.rs -sSf | sh
          Seriously? Why there is no even a trace of a tutorial on how to actually bootstrap it? Unfortunately your answer will be "because nobody needs it" and then usual bull crap mantras "secure, safe, productive". What a hypocritical nonsense.

          Comment


          • #25
            Originally posted by jjkk View Post
            Seriously? Why there is no even a trace of a tutorial on how to actually bootstrap it? .
            Thanks for volunteering. When can expect your initial RFC?
            Last edited by bachchain; 09-03-2019, 07:40 PM.

            Comment


            • #26
              Originally posted by jjkk View Post
              Requires compiler which can not be built from source code without downloading a binary blob.
              Yeah, both GCC and LLVM can be built from source without requiring a binary compiler, because somehow you can compile them by looking at them in a certain way.

              Are you fucking serious?

              Comment


              • #27
                Originally posted by jjkk View Post
                It seems you have never tried the method you are suggesting. Because it is utterly broken. If that was possible why would the one and only official method to install Rust was so ridiculous and laughable?

                Code:
                curl https://sh.rustup.rs -sSf | sh
                Seriously? Why there is no even a trace of a tutorial on how to actually bootstrap it? Unfortunately your answer will be "because nobody needs it" and then usual bull crap mantras "secure, safe, productive". What a hypocritical nonsense.
                For the same reason that GCC doesn't provide a tutorial on how to bootstrap GCC from a non-C++ compiler... or, as far as a quick google shows, from a non-GCC C++ compiler. (And, yes, GCC stopped being pure C a few years ago as was mentioned here on Phoronix.)

                Bootstrapping is not intended as an official method to install it, any more than expecting building GCC with some random compiler like TCC to be an official supported method of install. If you want to bootstrap a self-hosting compiler, there's an implicit expectation that you're skilled enough to write your own instructions as you go.

                mrustc's purpose is to prove that the official binaries are safe by producing bit-for-bit identical replicas through a laborious but much more auditable process.

                If it's the "running arbitrary shell scripts" part you have a problem with, that's what the Other Installation Methods page is for. (Though you won't see me arguing if you complain that the current incarnation of the site is an iOS-ishly confusing "determined to be simpler than is actually possible" mess.)

                Comment


                • #28
                  Originally posted by ssokolow View Post

                  For the same reason that GCC doesn't provide a tutorial on how to bootstrap GCC from a non-C++ compiler... or, as far as a quick google shows, from a non-GCC C++ compiler. (And, yes, GCC stopped being pure C a few years ago as was mentioned here on Phoronix.)
                  https://bootstrappable.org/projects/mes.html Many project maintain the tutorial howto bootstrap current gcc from non C++ compiler

                  Clean bootstrapping current gcc has come a pain in the ass its tinyc to GCC 2.95.0 to gcc 4.7 then to current. Yes this bootstrap path is required when you have a clean platform with no binaries.

                  https://en.wikipedia.org/wiki/Cfront

                  Its not like it really was impossible to write the core of the compiler in C++ yet still boot strap with C just no one really wanted to.

                  ssokolow gcc boot strapping build the xgcc is built then the xgcc rebuild the code again. So its currently 7 builds to clean boot strap gcc due to the change to c++.

                  Yes a C++ to C converter + tcc could possible allow building the current xgcc so making 3 builds to boot strap.

                  Really needing to clean bootstrap with audited code current gcc is a bastard.

                  Comment


                  • #29
                    Originally posted by oiaohm View Post

                    https://bootstrappable.org/projects/mes.html Many project maintain the tutorial howto bootstrap current gcc from non C++ compiler

                    Clean bootstrapping current gcc has come a pain in the ass its tinyc to GCC 2.95.0 to gcc 4.7 then to current. Yes this bootstrap path is required when you have a clean platform with no binaries.

                    https://en.wikipedia.org/wiki/Cfront

                    Its not like it really was impossible to write the core of the compiler in C++ yet still boot strap with C just no one really wanted to.

                    ssokolow gcc boot strapping build the xgcc is built then the xgcc rebuild the code again. So its currently 7 builds to clean boot strap gcc due to the change to c++.

                    Yes a C++ to C converter + tcc could possible allow building the current xgcc so making 3 builds to boot strap.

                    Really needing to clean bootstrap with audited code current gcc is a bastard.
                    My point exactly. The GCC developers don't provide official instructions and the bootstrapping process that does work is a pain in the neck... just like using mrustc to do the same for Rust.

                    Comment


                    • #30
                      Originally posted by bug77 View Post

                      Because ore rusts
                      "Was macht dein Moderboot?" .. "Es modert."

                      Comment

                      Working...
                      X