Ltning

@ltning@weirdr.net

He/him. This is one of my alter egos in the retro world. Read about this instance on front page. My goal is to be able to post here from a 286* running DOS. Might be a while..

and enthusiast with a craving for retro (mostly PC) hardware. Four kids and a wonderful patchwork family.

*Speaking of 286es: http://floppy.museum/

32 following, 88 followers

1 ★ 0 ↺

[?]Ltning » 🌐
@ltning@weirdr.net

Yeah, but if the binary was built on the PIII, then it will not work on the PII assuming the compiler uses "current machine" as default target..

CC: @DeltaLima@social.la10cy.net

    ...

    [?]Fritz Adalis [he/him] » 🌐
    @FritzAdalis@infosec.exchange

    @ltning @DeltaLima
    OpenBSD source will always output the same code independent of the current cpu capabilities, but other code may not.

      ...

      [?]DeltaLima 🐧 » 🌐
      @DeltaLima@social.la10cy.net

      @FritzAdalis @ltning I think I'll try NetBSD next as troubleshooting step, hope I will find time at the weekend for it. Thank you so far! :)

        ...
        1 ★ 0 ↺

        [?]Ltning » 🌐
        @ltning@weirdr.net

        NetBSD is likely to be a fair bit faster than OpenBSD - especially on such old hardware, where most of the various CPU vulnerability mitigations are useless but OpenBSD enables them anyway. T(h)rashing of caches and pipelines for no good reason makes for a suboptimal experience.

        You may want to make sure you disable encrypted swap unless you have a ton of RAM. Someone seems to think that if you're on x86 you always have CPU to spare for encryption :D

        Also, pkgin is fantastic and many (more than on OpenBSD) packages are built so they work on even an i486.

        CC: @FritzAdalis@infosec.exchange

          [?]DeltaLima 🐧 » 🌐
          @DeltaLima@social.la10cy.net

          @ltning no, I built it new from scratch. I also reinstalled the whole system today to ensure everything is fine.

            History

            about this site - powered by snac/2.91-dev