mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,4 Tsd.
aktive Profile

#amd64

2 Beiträge2 Beteiligte0 Beiträge heute
Alexander Shendi<p>New computing setup...</p><p><a href="https://rollenspiel.social/tags/HP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HP</span></a> <a href="https://rollenspiel.social/tags/Stream7" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Stream7</span></a> <a href="https://rollenspiel.social/tags/Baytrail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Baytrail</span></a> <a href="https://rollenspiel.social/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> <a href="https://rollenspiel.social/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://ipv6.social/@miyuru" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>miyuru</span></a></span> AFAICT <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> did drop <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ix86</span></a> in favour of <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> some time ago.</p><ul><li>Personally I do want to continue working on an <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i486</span></a>-supporting distro with <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a>...</li></ul>
Kevin Karhan :verified:<p>Thanks to <span class="h-card" translate="no"><a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>geerlingguy</span></a></span> for <a href="https://www.youtube.com/watch?v=GKGtRrElu30&amp;t=290" rel="nofollow noopener" target="_blank">addressing the elephant in the room.</a></p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@RaspberryPi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>RaspberryPi</span></a></span> dominates the <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SBC</span></a> market because they know how to write <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>documentation</span></a> and build <a href="https://infosec.space/tags/drivers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>drivers</span></a> that get accepted into <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mainline</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> kernel.</p><ul><li>The best specs and hardware is useless if it needs intimate knowledge on how to roll one's own kernel. And oftentimes one doesn't even get proper drivers and reproduceable build instructions but just some <em>"vomited" out</em> bootable images to <code>dd</code> onto a microSD!</li></ul><p>That's why my <a href="https://infosec.space/tags/BananPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BananPi</span></a> Zero M2 is still unused to this day: It's way too inconvenient and whilst I <a href="https://github.com/OS-1337/OS1337/blob/c4a19af5a62d7afbb80dfc416773a92074e6cc32/docu/ideas/architectures.tsv#L10" rel="nofollow noopener" target="_blank">do want to support it someday</a>, it's just not a good start when the 1st <a href="https://infosec.space/tags/RasperryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RasperryPi</span></a>'s documentation to this day is still the bare minimum and vendors can't be assed to do that.</p><ul><li>The only reason <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a>-based <a href="https://infosec.space/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SBC</span></a>|s don't have the same issues as <a href="https://infosec.space/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> is because <a href="https://infosec.space/tags/BIOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BIOS</span></a> &amp; <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a>-boot alongside the way <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a> is initialized make it trivial to make it <em>"go brrrr..."</em></li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://suya.place/users/a1ba" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>a1ba</span></a></span> unsarcastically, I like that.</p><ul><li><p>But then again I'm a sucker for non-<a href="https://infosec.space/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMD</span></a> / <a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Intel</span></a> <a href="https://infosec.space/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ix86</span></a> / <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> <a href="https://infosec.space/tags/CPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CPU</span></a>|s and non-<a href="https://infosec.space/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMD</span></a> / <a href="https://infosec.space/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Intel</span></a> / <a href="https://infosec.space/tags/nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nvidia</span></a> / <a href="https://infosec.space/tags/3dfx" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>3dfx</span></a> (wallet sez so!) <a href="https://infosec.space/tags/GPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPU</span></a>|s.</p></li><li><p>Like some <a href="https://infosec.space/tags/Transmeta" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Transmeta</span></a> / <a href="https://infosec.space/tags/VIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VIA</span></a> / <a href="https://infosec.space/tags/Vortex86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vortex86</span></a> / <a href="https://infosec.space/tags/Cyrix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cyrix</span></a> / <a href="https://infosec.space/tags/Xiaoxin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xiaoxin</span></a> CPU with like a <a href="https://infosec.space/tags/SiliconMotion" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SiliconMotion</span></a> / <a href="https://infosec.space/tags/ASPEED" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ASPEED</span></a> / <a href="https://infosec.space/tags/Matrox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Matrox</span></a> / <a href="https://infosec.space/tags/S3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>S3</span></a> GPU added to it.</p></li></ul><p>Won't run Crysis, but will run <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span>!</p>
DocYeet :verified:<p>Funnily enough, it takes more than 5 minutes to bump the char limits on Mastodon's toots</p><p>It's been compiling for ages (I'm just bumping to 1000) and doesn't seem to get anywhere, almost as if it was stuck for the arm64 target</p><p>On the other hand, the amd64 target is working like a charm, so I guess it has to do with architecture emulation ?</p><p><a href="https://mastodon.halis.io/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastoadmin</span></a> <a href="https://mastodon.halis.io/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://mastodon.halis.io/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> <a href="https://mastodon.halis.io/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> <a href="https://mastodon.halis.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://mastodon.halis.io/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediverse</span></a></p>
Felix Palmen :freebsd: :c64:<p>I recently took a dive into <a href="https://mastodon.bsd.cafe/tags/C11" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C11</span></a> <a href="https://mastodon.bsd.cafe/tags/atomics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>atomics</span></a> to come up with alternative queue implementations not requiring locking some <a href="https://mastodon.bsd.cafe/tags/mutex" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mutex</span></a>.</p><p>TBH, I have a hard time understanding the <a href="https://mastodon.bsd.cafe/tags/memory" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>memory</span></a> <a href="https://mastodon.bsd.cafe/tags/ordering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ordering</span></a> constraints defined by C11. I mean, I code <a href="https://mastodon.bsd.cafe/tags/assembler" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>assembler</span></a> on a <a href="https://mastodon.bsd.cafe/tags/mos6502" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mos6502</span></a> (for the <a href="https://mastodon.bsd.cafe/tags/c64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>c64</span></a>), so caches, pipelines and all that modern crap is kind of alien rocket science anyways 😆.</p><p>But seriously, they try to abstract from what the hardware provides (different kinds of memory barrier instructions, IMHO somewhat easier to understand), so the compiler can pick the appropriate one depending on the target CPU. But wrapping your head around their definition really hurts the brain 🙈.</p><p>Yesterday, I found a source telling me that <a href="https://mastodon.bsd.cafe/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> (or <a href="https://mastodon.bsd.cafe/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>x86</span></a> in general?) always has strong ordering for reads, so no matter which oderding constraint you put in your atomic_load and friends, the compiler will generate the same code and it will work. Oh boy, how should I ever verify my code works on e.g. aarch64 without owning such hardware?</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jbqueru</span></a></span> OFC and in terms of <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCv</span></a> vs. <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM</span></a> it won't be competitive for quite some time as ARM includes a lot of <a href="https://infosec.space/tags/proprietary" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proprietary</span></a> and <a href="https://infosec.space/tags/patented" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>patented</span></a> <a href="https://infosec.space/tags/PowerSaving" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PowerSaving</span></a> technologies that are just not available outside of said closed ISA.</p><ul><li>I do thus treat <a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM64</span></a> like <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a>: A <em>"black box"</em> that I cannot audit, verify or control beyond what it allows me to.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jbqueru</span></a></span> Also I hope for <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCv</span></a> to be the <a href="https://infosec.space/tags/ISA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISA</span></a> of the future for long-term <a href="https://infosec.space/tags/OpenSourceHardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSourceHardware</span></a> and support.</p><p><a href="https://infosec.space/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM64</span></a> - just like <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> - is <em>yet another proprietary ISA</em> and almost all devices with it in terms of <a href="https://infosec.space/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Laptops</span></a> have <a href="https://infosec.space/tags/AntiRepairDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AntiRepairDesign</span></a> like <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a>'s <a href="https://infosec.space/tags/MacBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MacBook</span></a>|s that self-destroy their <a href="https://infosec.space/tags/SSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSD</span></a>|s which also contains it's <a href="https://infosec.space/tags/EFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EFI</span></a> / <em>"<a href="https://infosec.space/tags/BridgeOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BridgeOS</span></a>"</em>, <a href="https://www.youtube.com/watch?v=RYG4VMqatEY" rel="nofollow noopener" target="_blank">making machines with fried SSDs <em>'braindead'</em>…</a></p><p>And yes, <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> to also fails and making it not fully replaceable and upgradeable is inherently bad and I'm still mad at <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> for their botched <a href="https://infosec.space/tags/FrameworkDesktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrameworkDesktop</span></a> <a href="https://infosec.space/tags/PC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PC</span></a>!</p><ul><li>Cuz it's neither necessary nor beneficial for a <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Desktop</span></a> PC, unlike with the <a href="https://infosec.space/tags/Framework12" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Framework12</span></a> where the <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoC</span></a> used only supports single channel and a single SODIMM so it makes sense for them to take that into account.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@pauliehedron" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pauliehedron</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>BrodieOnLinux</span></a></span> I daily drive a <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> <a href="https://infosec.space/tags/t620" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>t620</span></a> as a mini server, because in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Germany</span></a> power is expensive af and I want something cheap (€30 used), quiet (fanless!) and having <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> durig the <a href="https://infosec.space/tags/PiShortage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PiShortage</span></a>.</p><ul><li>And yes, it'll even run <span class="h-card" translate="no"><a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails_live</span></a></span> / <span class="h-card" translate="no"><a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails</span></a></span> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tails</span></a> and <span class="h-card" translate="no"><a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>torproject</span></a></span> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tor</span></a> if you are patient with it ir chug in a 2nd 4GB RAM stick in it.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@JessTheUnstill" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>JessTheUnstill</span></a></span> <span class="h-card" translate="no"><a href="https://mamot.fr/@bohwaz" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bohwaz</span></a></span> <span class="h-card" translate="no"><a href="https://indieweb.social/@punkfairie" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>punkfairie</span></a></span> <span class="h-card" translate="no"><a href="https://social.vivaldi.net/@ajsadauskas" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ajsadauskas</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.world/@tomiahonen" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tomiahonen</span></a></span> <span class="h-card" translate="no"><a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fuchsiii</span></a></span> <em>Exactly</em>...</p><p>Coincidentially, that's why <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> (and <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a>) doesn't let users have <a href="https://infosec.space/tags/root" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>root</span></a> access because billions of devices owned by mostly <em>"<a href="https://infosec.space/tags/TechIlliterates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterates</span></a>"</em> that hardly get <a href="https://infosec.space/tags/SecurityUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SecurityUpdates</span></a> would be an even bigger risk if they didn't boot a locked-down <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROM</span></a> image, thus only allowing for <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> in user-privilegued userspace!</p><ul><li>I'd even go so far that I'd wish for <span class="h-card" translate="no"><a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>torproject</span></a></span> to basically merge fmr. <a href="https://infosec.space/tags/FirefoxOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FirefoxOS</span></a> / <a href="https://infosec.space/tags/KaiOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KaiOS</span></a> &amp; <span class="h-card" translate="no"><a href="https://venera.social/profile/tails_live" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails_live</span></a></span> / <span class="h-card" translate="no"><a href="https://fosstodon.org/@tails" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tails</span></a></span> / <a href="https://infosec.space/tags/Tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tails</span></a> to build a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a>-focussed <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROM</span></a> for <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Smartphones</span></a> and <a href="https://infosec.space/tags/Tablets" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tablets</span></a> i.e. <em>"<a href="https://infosec.space/tags/TailsMobile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TailsMobile</span></a>"</em> or sth.</li></ul><p>Cuz having a mobile OS that shoves everything through <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tor</span></a> and only allows <a href="https://infosec.space/tags/userspace" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>userspace</span></a>-Apps in the form modern web technologies would be a big <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> and <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> gain.</p><ul><li>Not to mention <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> is on it's way out and inevitably they gotta have to transition to supporting <a href="https://infosec.space/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> and eventually <a href="https://infosec.space/tags/RISCv" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCv</span></a>-<a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>64bit</span></a> at some point.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@asmw" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>asmw</span></a></span> uf yiu don't need <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> maybe there's some <a href="https://infosec.space/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> board fir <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> ?</p><ul><li>Most of the <em>"<a href="https://infosec.space/tags/magic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>magic</span></a>"</em> of <a href="https://infosec.space/tags/ARM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM</span></a> is a shitload of patented power savings...</li></ul>
Denzil Ferreira :fedora:<p>Blows my mind that I can use my AMD Ryzen laptop to build a container that will ultimately run on an Nvidia Jetson Orin NX (arm64). What were we doing before Docker was a thing?<br><a href="https://techhub.social/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://techhub.social/tags/crosscompile" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>crosscompile</span></a> <a href="https://techhub.social/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> <a href="https://techhub.social/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://toot.cat/@riley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>riley</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> heard of it, sadly I need <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> hardware.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@vetgaming" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vetgaming</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@linuxmint" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>linuxmint</span></a></span> It's just a necessity, according to <span class="h-card" translate="no"><a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fuchsiii</span></a></span>, as it's just not feasible longterm to collect rarer-and-rarer <a href="https://infosec.space/tags/VintageComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VintageComputing</span></a> hardware and rely on non-enforcement of copyright on <a href="https://infosec.space/tags/Abandonware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Abandonware</span></a>.</p><ul><li>Plus whilst <a href="https://infosec.space/tags/Valve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Valve</span></a> isn't antragonistic to <a href="https://infosec.space/tags/Proton" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proton</span></a> / <a href="https://infosec.space/tags/DXVK" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DXVK</span></a> repackagings, <em>not relying</em> on them is kinda important, as this setup also helps with otger applications that ain't strictly games or in setups that one may not want to be on the internet.</li></ul><p>It makes <a href="https://infosec.space/tags/TheSims" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TheSims</span></a> and <a href="https://infosec.space/tags/FightingIsMagic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FightingIsMagic</span></a> just work on anything that is <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> and has enough resources to throw at it.</p>
Dendrobatus Azureus<p>A few tooters have asked me what my config is, at which I replied that I run the Fediverse, platform agnostic. Then one asked what one of my main horizontal display systems run, at which I now reply with</p><p>` uname -a`<br>{Linux devakprata 6.12.13-2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.12-18~mx23ahs (2025-02-10) x86_64 GNU/Linux}</p><p>**Note**<br>I left the results of</p><p>`cat /proc/cpuinfo` out since I would get that 16 times!!!</p><p>` cat /proc/meminfo `<br>{MemTotal: 31750332 kB<br>MemFree: 27996612 kB<br>MemAvailable: 29376500 kB<br>Buffers: 85900 kB<br>Cached: 1890756 kB<br>SwapCached: 0 kB<br>Active: 2357024 kB<br>Inactive: 892372 kB<br>Active(anon): 1546640 kB<br>Inactive(anon): 0 kB<br>Active(file): 810384 kB<br>Inactive(file): 892372 kB<br>Unevictable: 48 kB<br>Mlocked: 48 kB<br>SwapTotal: 6291452 kB<br>SwapFree: 6291452 kB<br>Zswap: 0 kB<br>Zswapped: 0 kB<br>Dirty: 156 kB<br>Writeback: 0 kB<br>AnonPages: 1273116 kB<br>Mapped: 719588 kB<br>Shmem: 273900 kB<br>KReclaimable: 67860 kB<br>Slab: 169900 kB<br>SReclaimable: 67860 kB<br>SUnreclaim: 102040 kB<br>KernelStack: 16160 kB<br>PageTables: 30512 kB<br>SecPageTables: 4112 kB<br>NFS_Unstable: 0 kB<br>Bounce: 0 kB<br>WritebackTmp: 0 kB<br>CommitLimit: 22166616 kB<br>Committed_AS: 6017728 kB<br>VmallocTotal: 34359738367 kB<br>VmallocUsed: 98420 kB<br>VmallocChunk: 0 kB<br>Percpu: 7680 kB<br>HardwareCorrupted: 0 kB<br>AnonHugePages: 0 kB<br>ShmemHugePages: 0 kB<br>ShmemPmdMapped: 0 kB<br>FileHugePages: 0 kB<br>FilePmdMapped: 0 kB<br>CmaTotal: 0 kB<br>CmaFree: 0 kB<br>Unaccepted: 0 kB<br>HugePages_Total: 0<br>HugePages_Free: 0<br>HugePages_Rsvd: 0<br>HugePages_Surp: 0<br>Hugepagesize: 2048 kB<br>Hugetlb: 0 kB<br>DirectMap4k: 347964 kB<br>DirectMap2M: 7952384 kB<br>DirectMap1G: 24117248 kB}</p><p>and this screencap</p><p><a href="https://mastodon.bsd.cafe/tags/neofetch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>neofetch</span></a> <a href="https://mastodon.bsd.cafe/tags/sysinfo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysinfo</span></a> <a href="https://mastodon.bsd.cafe/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>POSIX</span></a> <a href="https://mastodon.bsd.cafe/tags/uname" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uname</span></a> <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.bsd.cafe/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fediverse</span></a> <a href="https://mastodon.bsd.cafe/tags/federated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>federated</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.bsd.cafe/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a> <a href="https://mastodon.bsd.cafe/tags/AMD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMD</span></a> <a href="https://mastodon.bsd.cafe/tags/AMD64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMD64</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://gamepad.club/@MaliciousCarp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>MaliciousCarp</span></a></span> consider some <a href="https://infosec.space/tags/fanless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fanless</span></a> <a href="https://infosec.space/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinClient</span></a> instead....</p><ul><li>The work great as mini-servers, can accept quite a lot of RAM and usually have at meast USB 3.0 &amp; M.2 B-Key slots...</li></ul>
Armbian Linux<p>Release is coming - help us with testing!</p><p><a href="https://www.armbian.com/newsflash/release-is-coming-3/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">armbian.com/newsflash/release-</span><span class="invisible">is-coming-3/</span></a></p><p><a href="https://fosstodon.org/tags/release" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>release</span></a> <a href="https://fosstodon.org/tags/upgrade" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>upgrade</span></a> <a href="https://fosstodon.org/tags/features" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>features</span></a> <a href="https://fosstodon.org/tags/fixes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fixes</span></a> <a href="https://fosstodon.org/tags/aarch64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aarch64</span></a> <a href="https://fosstodon.org/tags/armhf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>armhf</span></a> <a href="https://fosstodon.org/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> <a href="https://fosstodon.org/tags/riscv64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>riscv64</span></a> <a href="https://fosstodon.org/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>embedded</span></a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://fosstodon.org/tags/armbian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>armbian</span></a> <a href="https://fosstodon.org/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://fosstodon.org/tags/ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ubuntu</span></a> <a href="https://fosstodon.org/tags/xfce" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xfce</span></a> <a href="https://fosstodon.org/tags/gnome" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gnome</span></a> <a href="https://fosstodon.org/tags/kde" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kde</span></a></p>
Ben Zucker 🍰<p>Some sort of of success. I could place <a href="https://maly.io/tags/nolf2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nolf2</span></a> with <a href="https://maly.io/tags/wine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wine</span></a>. Had (obviously) to install the <a href="https://maly.io/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i386</span></a> versions of the <a href="https://maly.io/tags/mesa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mesa</span></a> packages besides the <a href="https://maly.io/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> ones. <br>Shout-out to <a href="https://maly.io/tags/kisak" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kisak</span></a> for their mesa backporting btw. <br>Just wide-screen support doesn't work well. Stuff gets cropped. </p><p>Maybe I give <a href="https://maly.io/tags/lutris" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lutris</span></a> another try as well.</p>
tulili :v18:<p>We've just published the first multi-arch Bluefin-LTS builds! Bluefin-LTS has been an amazing place to test new things and this worked amazingly well with the new Github runners!</p><p><a href="https://ursal.zone/tags/bluefin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bluefin</span></a> <a href="https://ursal.zone/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://ursal.zone/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://ursal.zone/tags/multi_arch" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>multi_arch</span></a> <a href="https://ursal.zone/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a> <a href="https://ursal.zone/tags/aarch64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aarch64</span></a> <a href="https://ursal.zone/tags/arm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm</span></a> <a href="https://ursal.zone/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a></p>
Armbian Linux<p>Armbian weekly news: <a href="https://www.armbian.com/newsflash/armbian-weekly-highlights-8/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">armbian.com/newsflash/armbian-</span><span class="invisible">weekly-highlights-8/</span></a></p><p><a href="https://fosstodon.org/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://fosstodon.org/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a> <a href="https://fosstodon.org/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://fosstodon.org/tags/armbian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>armbian</span></a> <a href="https://fosstodon.org/tags/ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ubuntu</span></a> <a href="https://fosstodon.org/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://fosstodon.org/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fedora</span></a> <a href="https://fosstodon.org/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>arm64</span></a> <a href="https://fosstodon.org/tags/riscv64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>riscv64</span></a> <a href="https://fosstodon.org/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amd64</span></a></p>