toad.social

Cassandrich<a href="https://social.vlhl.dev/users/navi" class="u-url mention" rel="nofollow noopener" target="_blank">@navi</a> This (including spaces following tabs where alignment within an indent level is wanted) is exactly the indent/whitespace policy in <a href="https://hachyderm.io/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> libc, for pretty much exactly these reasons.

Alex Haydock @ WHY2025Everything I've read suggests <a href="https://infosec.exchange/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> resolv.conf only supports 3 nameservers in resolv.conf.So why does dnscheck.tools suggest that all 6 of the resolvers I configured are actually working?😵‍💫 Very puzzling

JdeBP<a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@mcc</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.social/@whitequark" class="u-url mention" rel="nofollow noopener" target="_blank">@whitequark</a> <a href="https://tech.lgbt/@becomethewaifu" class="u-url mention" rel="nofollow noopener" target="_blank">@becomethewaifu</a> Changing compiler is not the problem. But changing the standard library becomes one. systemd gained problems with <a href="https://tty0.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> because of this.<a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://tty0.social/@JdeBP/114646325165347305" rel="nofollow noopener" translate="no" target="_blank">https://tty0.social/@JdeBP/114646325165347305</a>

CassandrichJust designed and tested an algorithm to build a reverse-iterator on top of an iterator that can only run in forwards direction (part of the <a href="https://hachyderm.io/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> collation project) and it seems to be good!63 underlying forward-iterate steps to perform 21 reverse-iterate steps in simple test case.

Kevin Karhan :verified:<a href="https://fedi.catto.garden/users/gettie" class="u-url mention" rel="nofollow noopener" target="_blank">@gettie</a> <a href="https://mastodon.bsd.cafe/@chesheer" class="u-url mention" rel="nofollow noopener" target="_blank">@chesheer</a> Sadly not even <a href="https://infosec.space/tags/AdelieLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#AdelieLinux</a>, which <a href="https://bitbang.social/@ActionRetro" class="u-url mention" rel="nofollow noopener" target="_blank">@ActionRetro</a> uses all the time...I am working on an <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#i486</a> distro ( <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a>) but for <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#i386</a> the support in terms of Linux <a href="https://github.com/OS-1337/OS1337/blob/c4a19af5a62d7afbb80dfc416773a92074e6cc32/docu/internal/linux.kernel.versions.tsv#L2" rel="nofollow noopener" target="_blank">ended</a> with Versions 3.4.99 LTS & 3.6.9 respectably, and my <a href="https://infosec.space/tags/userland" class="mention hashtag" rel="nofollow noopener" target="_blank">#userland</a> & <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#toolchain</a> (<a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> & <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>-cross) doesn't support that at all, and I'd propably have more success convincing <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> to join <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a> than to support i386 even if I could pay him for that!

Kevin Karhan :verified:<a href="https://social.linux.pizza/@FandaSin" class="u-url mention" rel="nofollow noopener" target="_blank">@FandaSin</a> <a href="https://mastodon.social/@cleverboi" class="u-url mention" rel="nofollow noopener" target="_blank">@cleverboi</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> <a href="https://social.gompa.me/@neal" class="u-url mention" rel="nofollow noopener" target="_blank">@neal</a> I think <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#i486</a> is a good baseline because that's the furthest some systems can go!<ul><li>And supporting <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#i386</a> is out of the question for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> - unless someone wants to also abckport <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> and <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>!</li></ul><a href="https://infosec.space/@kkarhan/114738983433662865" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/114738983433662865</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@cleverboi" class="u-url mention" rel="nofollow noopener" target="_blank">@cleverboi</a> <a href="https://social.linux.pizza/@FandaSin" class="u-url mention" rel="nofollow noopener" target="_blank">@FandaSin</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> <a href="https://social.gompa.me/@neal" class="u-url mention" rel="nofollow noopener" target="_blank">@neal</a> as for <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#i386</a> I understood why cuz it was more and more painful m, but the problem with <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#i486</a> is that in several <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#embedded</a> and <a href="https://infosec.space/tags/industrial" class="mention hashtag" rel="nofollow noopener" target="_blank">#industrial</a> setups there are still newly deloyed systems based off it.I.e. <a href="https://infosec.space/tags/Vortex86" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vortex86</a> <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoC</a>'s cuz <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> and shit still gets used in <a href="https://infosec.space/tags/industrial" class="mention hashtag" rel="nofollow noopener" target="_blank">#industrial</a> equipment.<ul><li>And <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> is kinda necessary to keep that rollin'...</li></ul>Linux <a href="https://github.com/OS-1337/OS1337/blob/main/docu/linux.kernel.versions.tsv" rel="nofollow noopener" target="_blank">stopped supporting i386</a> with versions <code>3.4.99 (longterm)</code> & <code>3.6.9</code> respectably.<ul><li>And unlike with <code>i386</code> where none of the toolchain (<a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>) and utilities (<a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a>) supoort it, <code>i486</code> is still supported there.</li></ul>And I really want to continue developing a minimalist "rescue" distro that can handle such legacy hardware because it may be the only option to <code>ddrescue</code> stuff from certain systems or to properly & reproduceably backup & restore them!

Kevin Karhan :verified:<a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@mrmasterkeyboard</a> I mean, that's why I <a href="https://os1337.com/" rel="nofollow noopener" target="_blank">chose</a> <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a>... Shoutout again to <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> for making this super easy by releasing the <code>musl-cross</code> - <a href="https://landley.net/toybox/downloads/binaries/toolchains/latest/" rel="nofollow noopener" target="_blank">toolchain</a> used for <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a>, making it super easy to just build against that.

Kevin Karhan :verified:<a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@mrmasterkeyboard</a> np.To me <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> is just an attempt to a minimalist <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distro because I want some <a href="https://infosec.space/tags/reproduceable" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproduceable</a> & <a href="https://infosec.space/tags/auditable" class="mention hashtag" rel="nofollow noopener" target="_blank">#auditable</a> <a href="https://infosec.space/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#firmware</a> for various other projects, and both <a href="https://fosstodon.org/@yoctoproject" class="u-url mention" rel="nofollow noopener" target="_blank">@yoctoproject</a> and <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPiOS</a> 'lite' seem rather excessive to me.<ul><li>Also a proper minimalist <a href="https://infosec.space/tags/CLI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CLI</a>-based <a href="https://infosec.space/tags/distro" class="mention hashtag" rel="nofollow noopener" target="_blank">#distro</a> that can be used for an "<a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSH</a>-<a href="https://infosec.space/tags/Terninal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Terninal</a>" does have merits.</li></ul>I just think that it can have serious benefits being less distracting and allowing me (and others) to just use basically any hardware to get work done...<ul><li>The rest of the component selection came because it was either dictated by necessity (Linux has the most driver support and biggest community), alignment with values & goals ( <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> 's <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> is a <a href="https://www.youtube.com/watch?v=cz6iGrhnMKs" rel="nofollow noopener" target="_blank">clean & minimalist userland)</a> and being better than <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> stuff (i.e. <a href="https://social.treehouse.systems/@musl" class="u-url mention" rel="nofollow noopener" target="_blank">@musl</a> / <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>) by not bricking shit at random minor updates…</li></ul>

Kevin Karhan :verified:<a href="https://fosstodon.org/@lmemsm" class="u-url mention" rel="nofollow noopener" target="_blank">@lmemsm</a> basically the Idea behind <a href="https://infosec.space/@OS1337" rel="nofollow noopener" target="_blank">it</a> is to be a brutally simple <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> / <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> distro that grew out of the necessity for me to actually think about <a href="https://infosec.space/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#firmware</a> for some projects. <ul><li>And lets just say I did saw <a href="https://fosstodon.org/@w84death" class="u-url mention" rel="nofollow noopener" target="_blank">@w84death</a> 's <a href="https://infosec.space/tags/Floppynux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Floppynux</a> and <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> did present <a href="https://www.youtube.com/watch?v=SGmtP5Lg_t0" rel="nofollow noopener" target="_blank">a</a> <a href="https://www.youtube.com/watch?v=MkJkyMuBm3g" rel="nofollow noopener" target="_blank">lot</a> of convincing arguments <a href="https://www.youtube.com/watch?v=Sk9TatW9ino" rel="nofollow noopener" target="_blank">alongside a literal walktrough</a> to get started.</li></ul>Basically I want something that is so simple and auditable that it's practical to make it pass any <a href="https://infosec.space/tags/verification" class="mention hashtag" rel="nofollow noopener" target="_blank">#verification</a> demands for <a href="https://infosec.space/tags/SecureTerminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecureTerminal</a>|s in <a href="https://infosec.space/tags/CriticalInfrastructure" class="mention hashtag" rel="nofollow noopener" target="_blank">#CriticalInfrastructure</a> and <a href="https://infosec.space/tags/Communications" class="mention hashtag" rel="nofollow noopener" target="_blank">#Communications</a>. <ul><li>OFC one may point at my other projects and say: "Why don't you just put <a href="https://infosec.space/tags/RaspberryPiOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPiOS</a> on a <a href="https://infosec.space/tags/microSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#microSD</a>?" ignoring that the smallest image is >330MB in size and that seems kinda overkill for essentially my demands for a minimalist <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> with very few programs in userspace. </li></ul>Not to mention a <a href="https://infosec.space/tags/GNUfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUfree</a> - <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distro is the way to go if I want that thing to not get bricked constantly by minor <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a>-changes... <ul><li>End goal is something akin to <a href="https://infosec.space/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a> in it's brutal simplicity, but way more extendable.</li></ul> I hope that answers your question...<ul><li>Sorry for the delay.</li></ul>

Kevin Karhan :verified:<a href="https://mastodon.social/@stman" class="u-url mention" rel="nofollow noopener" target="_blank">@stman</a> <a href="https://mastodon.social/@eff" class="u-url mention" rel="nofollow noopener" target="_blank">@eff</a> <a href="https://masto.hackers.town/@theruran" class="u-url mention" rel="nofollow noopener" target="_blank">@theruran</a> <a href="https://cathode.church/@50htz" class="u-url mention" rel="nofollow noopener" target="_blank">@50htz</a> <a href="https://social.solarpunk.au/users/vidak" class="u-url mention" rel="nofollow noopener" target="_blank">@vidak</a> <a href="https://mastodon.net2o.de/@forthy42" class="u-url mention" rel="nofollow noopener" target="_blank">@forthy42</a> once you have a "<a href="https://infosec.space/tags/SoftCPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftCPU</a>" that can be supported by gcc or llvm as well as <a href="https://infosec.space/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>, <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> & <a href="https://infosec.space/tags/toxbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toxbox</a> I can port <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> to it.<a href="https://en.wikipedia.org/wiki/Soft_microprocessor" rel="nofollow noopener" translate="no" target="_blank">https://en.wikipedia.org/wiki/Soft_microprocessor</a>

musl libcThings <a href="https://social.treehouse.systems/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> libc will never do (broad but not comprehensive):- Nag you to update. - Phone home to check it if should nag you to update. - Tell you a CVE can't be fixed without updating to the latest version. - Try to force you to switch from glibc to musl. - Get other software you depend on dependent on musl. - Rant against "wokeness" or "DEI". - Integrate "AI" into your libc. - Give you up. - Let you down.

CassandrichDetails on progress in this post to the <a href="https://hachyderm.io/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> mailing list: <a href="https://www.openwall.com/lists/musl/2025/06/11/1" rel="nofollow noopener" translate="no" target="_blank">https://www.openwall.com/lists/musl/2025/06/11/1</a>Actual draft code repo is now up too, at <a href="https://github.com/richfelker/musl-uca-draft" rel="nofollow noopener" translate="no" target="_blank">https://github.com/richfelker/musl-uca-draft</a>

CassandrichUpdate on <a href="https://hachyderm.io/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> LC_COLLATE work: NFD code is functional and Unicode test vectors for normalization to NFD all pass..rodata 14161 bytes .text 1089 bytes🎉

musl libcThis thread by <a href="https://social.treehouse.systems/@ariadne" class="u-url mention" rel="nofollow noopener" target="_blank">@ariadne</a> on Treehouse's intent to defederate from Fosstodon lays out more details, in more diplomatic terms:<a href="https://hachyderm.io/@ariadne@treehouse.systems/114632132509359067" rel="nofollow noopener" translate="no" target="_blank">https://hachyderm.io/@ariadne@treehouse.systems/114632132509359067</a>I (<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a>) have tried my best to engage with the new Fosstodon admin in good faith on what mistakes they're making, only to be met with assertions that their comfort is more important than marginalized folks' safety on their instance. I cannot in good conscience ask folks to maintain a relationship with Fosstodon in order to follow <a href="https://social.treehouse.systems/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> libc updates on the fedi.

JdeBP<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://social.treehouse.systems/@ska" class="u-url mention" rel="nofollow noopener" target="_blank">@ska</a> Well they *are* making their own versions of those two macros. I'd already read the ostensible rationale for it, and it seemed poor.They have a problem with their own code's headers having lots of cross-dependencies. (Strong coupling and low cohesion: a long-standing <a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> problem.) That's not a reason for fiddling with the <a href="https://tty0.social/tags/StandardC" class="mention hashtag" rel="nofollow noopener" target="_blank">#StandardC</a> library, let alone making one's own FILE and DIR macros.<a href="https://tty0.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>

JdeBP<a href="https://social.treehouse.systems/@ska" class="u-url mention" rel="nofollow noopener" target="_blank">@ska</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> I understood Daniel J. Bernstein's avoidance of the Standard C library, especially strings and standard I/O which had been rife with pointer mis-uses for decades.But this is not that.Why on Earth would one continue to use stdio but roll one's own version of the GNU C library's FILE and DIR macros?<a href="https://github.com/systemd/systemd/issues/37779#issuecomment-2952813363" rel="nofollow noopener" translate="no" target="_blank">https://github.com/systemd/systemd/issues/37779#issuecomment-2952813363</a><a href="https://tty0.social/tags/StandardC" class="mention hashtag" rel="nofollow noopener" target="_blank">#StandardC</a> <a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> <a href="https://tty0.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>

datenwolfAll I want is just a collection of <a href="https://chaos.social/tags/binutils" class="mention hashtag" rel="nofollow noopener" target="_blank">#binutils</a>, <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a>, <a href="https://chaos.social/tags/llvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llvm</a>+<a href="https://chaos.social/tags/clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#clang</a>, <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> and <a href="https://chaos.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> that are "free standing" / relocatable, which I can pack into a <a href="https://chaos.social/tags/squashfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#squashfs</a> image to carry around to my various development machines.You'd think that for something as fundamental as compiler infrastructure with over 60 years of knowledge, the whole bootstrapping and bringup process would have been super streamlined, or at least mostly pain free by now.Yeah, about that. IYKYK

Kevin Karhan :verified:<a href="https://soc.megatokyo.moe/users/wyatt" class="u-url mention" rel="nofollow noopener" target="_blank">@wyatt</a> Also glancing from the <a href="https://infosec.space/tags/PC98" class="mention hashtag" rel="nofollow noopener" target="_blank">#PC98</a> architecture and specific quirks that <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> accounts for in <code>menuconfig</code> it's most likely not gonna be enough to "just boot the <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#i486</a> version of <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a>"... <a href="https://github.com/OS-1337/OS1337/blob/main/OS1337-core-prerelease.img" rel="nofollow noopener" translate="no" target="_blank">https://github.com/OS-1337/OS1337/blob/main/OS1337-core-prerelease.img</a><ul><li>Tho given the fact this is just a <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> + <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a> / Linux Distro that is barely booting using <a href="https://infosec.space/tags/syslinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#syslinux</a> and able to spit out a 80x25 MDA console, it is in an early infancy.</li></ul>As for the specifics of the <a href="https://infosec.space/tags/PC9821" class="mention hashtag" rel="nofollow noopener" target="_blank">#PC9821</a>+ and their detailed hardware I'm clueless beyond the <a href="https://en.wikipedia.org/wiki/PC-98#Models" rel="nofollow noopener" target="_blank">Wikipedia Article</a> and can only Assume anything before a (RAM-upgraded) <a href="https://infosec.space/tags/9821Ap" class="mention hashtag" rel="nofollow noopener" target="_blank">#9821Ap</a> & <a href="https://infosec.space/tags/9801BA" class="mention hashtag" rel="nofollow noopener" target="_blank">#9801BA</a> is off the table and a <a href="https://infosec.space/tags/9821Af" class="mention hashtag" rel="nofollow noopener" target="_blank">#9821Af</a> or better is desireable as the 14,6MB RAM limit will really become a problem quickly, as I'm pretty shure it's impossible to get <code>linux-6.6.6</code> run on anything below 8MB at all and most recommendations hint that 16MB is more often than not a practical limit (tho that may be becaise 10/12/14 and other "asymetric" configurations were already avoided back then)...<ul><li>The <a href="https://infosec.space/tags/9821Ce" class="mention hashtag" rel="nofollow noopener" target="_blank">#9821Ce</a> should be workable in theory tho again that's just me reading a specsheet.</li></ul>On the flipside I did manage to install <a href="https://infosec.space/tags/WindowsXP" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsXP</a> on machines with 32MB RAM and actually get them to display a desktop (abeit with seconds per frame instead of frames per second) so this is more likely a question of chipping down things.<ul><li>Worst-Case one could see to build a bootable CD-ROM or <code>dd</code> something on a <a href="https://infosec.space/tags/BlueSCSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#BlueSCSI</a> or similar...</li></ul>

Recent searches

Search options

Administered by:

Server stats:

#musl