shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

269
active users

#os1337

2 posts2 participants0 posts today
Kevin Karhan :verified:<p>I wounder if it would be possible to build like a <a href="https://infosec.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROM</span></a> <a href="https://infosec.space/tags/cart" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cart</span></a> for <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> that just plonks into an <a href="https://infosec.space/tags/ISA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISA</span></a> slot (or <a href="https://infosec.space/tags/PCI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PCI</span></a> / <a href="https://infosec.space/tags/PCIe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PCIe</span></a> as a <em>"nice to have"</em>) to boot from.</p><ul><li>And yes I got inspired from <span class="h-card" translate="no"><a href="https://mastodon.social/@vwestlife" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vwestlife</span></a></span> <a href="https://www.youtube.com/watch?v=JIEPqD4luG8" rel="nofollow noopener" target="_blank">'s Tandy 1000RL</a></li></ul><p>And I don't mean like an XT-IDE or similar <a href="https://infosec.space/tags/SSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSD</span></a>, but more like a <a href="https://www.youtube.com/watch?v=Ys7RXkzbXw0&amp;t=118s" rel="nofollow noopener" target="_blank">Boot-ROM</a>...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@lymenzies" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lymenzies</span></a></span> I know that an <a href="https://infosec.space/tags/i486SX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i486SX</span></a> with at least 16 MB RAM is the absolute minimum you'll need to get the <a href="https://github.com/OS-1337/OS1337/raw/refs/heads/main/OS1337-core-prerelease.img" rel="nofollow noopener" target="_blank">1440kB prerelease image</a> to go brr...</p><ul><li>I've tested <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> both in VMs and on physical devices like the <a href="https://infosec.space/tags/EeePC701" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EeePC701</span></a> and <a href="https://infosec.space/tags/Vaio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vaio</span></a> <a href="https://infosec.space/tags/P11Z" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P11Z</span></a> and it runs super-fast on those. </li></ul><p>As for <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i386</span></a> support, <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> yeeted that with <a href="https://github.com/OS-1337/OS1337/blob/c4a19af5a62d7afbb80dfc416773a92074e6cc32/docu/internal/linux.kernel.versions.tsv#L2" rel="nofollow noopener" target="_blank">Kernel 3.4.99 LTS &amp; 3.6.9 respectably</a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@lymenzies" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lymenzies</span></a></span> Granted the <a href="https://infosec.space/tags/Wyse3040" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wyse3040</span></a> has <a href="https://infosec.space/tags/DisplayPort" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DisplayPort</span></a> and there are cheap driver boards that do <a href="https://infosec.space/tags/DP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DP</span></a> -&gt; <a href="https://infosec.space/tags/eDP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eDP</span></a>. </p><ul><li>Using the <a href="https://infosec.space/tags/iGPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iGPU</span></a> which AFAICT can't be deactivated but only given less <em>shared VRAM"</em> makes adding a different output besides some USB-Serial Console port kinda redundant.</li></ul><p>Worst-Case you just go with <a href="https://infosec.space/tags/MDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MDA</span></a> output at 80x25 (or even higher if you feel fancy and/or have something better than some tiny 480x800 screen(s)) as <a href="https://infosec.space/tags/VGA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VGA</span></a> is 100% backwards compatible with with that.</p><ul><li>Tho even if you don't do much in terms of fancy display output, you'd still get some decent output for a <a href="https://fishshell.com" rel="nofollow noopener" target="_blank">fancy shell</a> like <a href="https://infosec.space/tags/fish" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fish</span></a>... (which I have <a href="https://github.com/OS-1337/pkgs/blob/350e9579d2660cc87b41d819a67733bd900e36d1/docs/WISHLIST.tsv#L16" rel="nofollow noopener" target="_blank">wishlisted</a> for <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a>. </li></ul><p>In terms of hardware there's an M.2 A+E key slot <a href="https://www.youtube.com/watch?v=wS5PEG2rNJQ&amp;t=257s" rel="nofollow noopener" target="_blank">AFAICS</a> and for PS/2 &amp; VGA you can find ample of adaptors to go from USB and DisplayPort respectably: They don't cost much and I'm confident you won't get better DIY results anyway with limited time and budget.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mrmasterkeyboard</span></a></span> maybe if I can get <a href="https://infosec.space/tags/PipeWire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PipeWire</span></a> and <a href="https://infosec.space/tags/Audio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Audio</span></a> support on <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> working I'd consider something like it for it...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@katyswain" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>katyswain</span></a></span> I din't think that <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CCSS</span></a> is good either, but the demands of <a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv3</span></a> are not compatible with the (adnitteldy shitty) reality of how <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a>, <a href="https://infosec.space/tags/Licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Licensing</span></a> and <a href="https://infosec.space/tags/Patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Patents</span></a> work and thus it kneecaps a lot of things.</p><ul><li><p>GPLv3 caused <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> to freeze their <a href="https://infosec.space/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bash</span></a> version and divest into <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLVM</span></a> and adopt <a href="https://infosec.space/tags/zsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zsh</span></a>.</p></li><li><p>As <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> showed, enforcing the <a href="https://infosec.space/tags/GPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPL</span></a>(v2) resulted in exactly 0 code being committed to <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BusyBox</span></a> and it only made said project look toxic and litigatious. </p></li><li><p>Also i've yet to see anything happen re: <a href="https://infosec.space/tags/paywalled" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paywalled</span></a> <a href="https://infosec.space/tags/SourceCodeAccess" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SourceCodeAccess</span></a> for <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>grsec</span></a> &amp; <a href="https://infosec.space/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHat</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>. Maybe <a href="https://infosec.space/tags/GPLv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv4</span></a> will ban <a href="https://infosec.space/tags/paxwalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>paxwalling</span></a> and force violators to work on <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNU</span></a> / <a href="https://infosec.space/tags/HURD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HURD</span></a>?</p></li></ul><p>I chose <a href="https://infosec.space/tags/0BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>0BSD</span></a> for _OS/1337 because as with any "intellectual labour", <em>one cannot force others to collaborate</em> and I'd rather have people join in out of the goodness of their hearts instead of just dumping <em>some random git commit</em> that is useless.</p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fedi.catto.garden/users/gettie" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gettie</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.bsd.cafe/@chesheer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>chesheer</span></a></span> Sadly not even <a href="https://infosec.space/tags/AdelieLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AdelieLinux</span></a>, which <span class="h-card" translate="no"><a href="https://bitbang.social/@ActionRetro" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ActionRetro</span></a></span> uses all the time...</p><p>I am working on an <a href="https://infosec.space/tags/i486" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i486</span></a> distro ( <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>) but for <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>i386</span></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 &amp; 3.6.9 respectably, and my <a href="https://infosec.space/tags/userland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>userland</span></a> &amp; <a href="https://infosec.space/tags/toolchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toolchain</span></a> (<a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> &amp; <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a>-cross) doesn't support that <em>at all</em>, and I'd propably have more success convincing <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> to join <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> than to support i386 <em>even if I could pay him for that</em>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mrmasterkeyboard</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> glad I could get you guys connected then...</p><p>I'm convinced <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> is a good <a href="https://infosec.space/tags/userland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>userland</span></a> to get a basic OS up and running and on it's feet. If it's good enough for <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> then it's certainly gonna be good enough for <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>embedded</span></a> stuff as well...</p><ul><li>After all that seems to be the main goal of it: Allowing <em>"self-hosting"</em> as in <em>building itself under itself</em> if not <em>deliver under the same OS</em>...</li></ul><p>I don't leverage that capability with <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> (at least for now) but that's because I treat it more akin to <a href="https://en.wikipedia.org/wiki/VxWorks#Development_environment" rel="nofollow noopener" target="_blank">how</a> <a href="https://infosec.space/tags/VxWorks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VxWorks</span></a> <a href="https://en.wikipedia.org/wiki/Wind_River_Systems#Wind_River_Linux" rel="nofollow noopener" target="_blank">and</a> <a href="https://infosec.space/tags/WindRiverLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindRiverLinux</span></a> is being developed and deployed...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mrmasterkeyboard</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@cesarpose" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cesarpose</span></a></span> case in point: </p><p>Just because <em>"My Little Distro"</em> (<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a>) runs of a <a href="https://github.com/OS-1337/OS1337/blob/main/build/0.CORE/fdd/fs/etc/init" rel="nofollow noopener" target="_blank">single <code>/etc/init</code> file</a> doesn't mean this is the <em>"correct"</em> or <em>"authoritative"</em> way to do it nor that this is scalabe <em>at all</em>.</p><ul><li>Just <em>'let me cook'</em> on <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> because it's more of a <em>'learning exercise'</em> rather than <em>"production grade"</em>...</li></ul><p>Back to <a href="https://infosec.space/tags/Xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xorg</span></a>: I do think that metux's actions really salted the fields re: <a href="https://infosec.space/tags/Xlibre" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xlibre</span></a> and any <a href="https://infosec.space/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>X11</span></a> releases!</p><ul><li>Granted non-<a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> OSes like <a href="https://infosec.space/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> already <a href="https://www.youtube.com/watch?v=95Vn9HHptok" rel="nofollow noopener" target="_blank">forked off</a> or DIY'd and now <a href="https://www.youtube.com/watch?v=nscwGQSfmXQ" rel="nofollow noopener" target="_blank">moving towards</a> <a href="https://infosec.space/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wayland</span></a> because it <em>is</em> <a href="https://www.youtube.com/watch?v=UW3nYiK3nd0" rel="nofollow noopener" target="_blank">the way forward</a> just by virtue that there's hardware in stores right now that doesn't support <a href="https://infosec.space/tags/Xserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xserver</span></a> but Wayland...</li></ul>
OS/1337<p>The <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> [website](<a href="https://os1337.com" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">os1337.com</span><span class="invisible"></span></a>) has been updated.</p><p>- We moved from <a href="https://infosec.space/tags/UbuntuMono" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UbuntuMono</span></a> to <a href="https://infosec.space/tags/B612Mono" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>B612Mono</span></a> because the <a href="https://infosec.space/tags/B612" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>B612</span></a> font family is licensed under SIL OFL and <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a>'s fonts have their own licenses.</p><p>- Also B612 is a *superior font* given that <a href="https://infosec.space/tags/Airbus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Airbus</span></a> got it designed, tested, and certified for *Civil Aviation Use*, which means it got extensive testing under harsh conditions.</p><p>Aesthetically, it's not much different!</p><p>- OFC the <a href="https://infosec.space/tags/Logo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Logo</span></a> is next with the <a href="https://infosec.space/tags/Font" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Font</span></a> change...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fe.disroot.org/users/ramin_hal9001" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ramin_hal9001</span></a></span> except that's <em>yet another package</em> and <em>yet another config file</em> and thus requires <a href="https://infosec.space/tags/Guix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Guix</span></a> to support the target system. Which may not be the case (i.e. ancient versions of <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Solaris</span></a> or some <a href="https://infosec.space/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a>-based distro or <em>some weird embedded linux device</em>... </p><ul><li>So whilst that may be attractive to some (and I don't deny the fact that it has merits) I don't think that <a href="https://github.com/greyhat-academy/sconfm?tab=readme-ov-file#why" rel="nofollow noopener" target="_blank">me</a> <em>publicly hating <a href="https://infosec.space/tags/YAML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>YAML</span></a></em> and <a href="https://os1337.com" rel="nofollow noopener" target="_blank">working on</a> a <a href="https://infosec.space/tags/GNUfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNUfree</span></a> toybox+musl/linux <a href="https://github.com/OS-1337/OS1337" rel="nofollow noopener" target="_blank">distro</a> is the target audience of it.</li></ul><p>I mean if someone wants to port <code>guix</code> to <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> they are <a href="https://github.com/OS-1337/pkgs/blob/main/docs/WISHLIST.tsv" rel="nofollow noopener" target="_blank">happily invited to do so</a> and I'll gladly accept that contribution, but it's currently <em>not on my agenda</em>...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://climatejustice.social/@HeatSinkAmbassador" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>HeatSinkAmbassador</span></a></span> yeah, but we both can agree that these distros are <em>"rounding errors"</em> compared to the rest just as much as <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> is an anomaly compared to them.</p><ul><li>I don't deny the necessity to have more than 1 option at hand, but I doubt we'll see much of it going to get any foothold...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@Madic" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Madic</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@lmemsm" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lmemsm</span></a></span> <em>nodds in agreement</em> </p><p>Last time I checked <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> only had <a href="https://landley.net/toybox/help.html#su" rel="nofollow noopener" target="_blank"><code>su</code></a>, not <a href="https://infosec.space/tags/sudo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sudo</span></a>, but outside if <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> I do stick with the distro's defaults cuz they should know best how to keep it as secure as can be.</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> I do agree in that we need more <a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a> options.</p><ul><li>If I really wanted and needed to I could do my work on an <a href="https://infosec.space/tags/EeePC701" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EeePC701</span></a> or a Vaio <a href="https://infosec.space/tags/P11Z" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P11Z</span></a> and I think these devices have still potential to be used.</li></ul><p>That's why I started <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>: <br><a href="https://os1337.com" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">os1337.com</span><span class="invisible"></span></a></p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaosfem.tw/@freya" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>freya</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> makes sense, ofc.</p><ul><li>I like SystemD but for <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> had to stick with the classic <code>/etc/init</code> file for space reasons alone.</li></ul><p>Tho in fairness I'm shure <a href="https://infosec.space/tags/SMF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SMF</span></a> did inspire <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> to do <a href="https://infosec.space/tags/LaunchD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LaunchD</span></a> which in turn was copied with <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SystemD</span></a>, abeit all 3 are very much centric about the Kernel and Userland they target.</p><ul><li>Reminds me of that legendary talk <a href="https://www.youtube.com/watch?v=o_AIw9bGogo" rel="nofollow noopener" target="_blank"><em>"The Tragedy of SystemD"</em></a>…</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaosfem.tw/@freya" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>freya</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 mean, why not?</p><ul><li>That's the beauty of <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FLOSS</span></a>...</li></ul><p>If someone wants to make a <a href="https://www.youtube.com/watch?v=CIN8Q_4iaxU" rel="nofollow noopener" target="_blank"><em>"Square-Wheeled Car"</em></a> then they can...</p><ul><li>I don't expect <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> to get anywhere, because it's more of an exercise in minimalism but hey, I see it as a fun little idea...</li></ul><p>Me wanting to do something <a href="https://infosec.space/tags/GNUfree" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNUfree</span></a> and going <em>"statically compiled binaries only"</em> is also a bit of <em>"headbanging against concrete"</em> kinda style...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.cloud/@lavxnews" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lavxnews</span></a></span> point is: <em>"reinventing the wheel"</em> is rarely easy nor worth the effort.</p><ul><li>Shure one <em>can</em> design their own OS or Kernel but the cost of doing so rarely makes sense.</li></ul><p>That's why I use <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>, <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> and <a href="https://infosec.space/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>musl</span></a> for <br>OS/1337 ...</p><ul><li>Same reason why <em>noone</em> spins their own <a href="https://infosec.space/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>encryption</span></a>, except here it's a matter if <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ITsec</span></a> and thus <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a>, <a href="https://infosec.space/tags/CopSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CopSec</span></a> &amp; <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpSec</span></a>!</li></ul><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bagder</span></a></span> Problem with that is (besides occasional bugfixes), most people including myself would see <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>curl</span></a> to be <em>functionally complete</em> and anything <em>"nice to have"</em> would be considered not worth the balooning in <a href="https://infosec.space/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>complexity</span></a> and <a href="https://infosec.space/tags/size" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>size</span></a>. </p><ul><li><p>I mean, does <a href="https://curl.se/" rel="nofollow noopener" target="_blank">curl</a> <em>need</em> to be able to do <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BitTorrent</span></a> (magnet:), <a href="https://infosec.space/tags/IPFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPFS</span></a> (ipfs://) or god forbid <a href="https://infosec.space/tags/blockchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blockchain</span></a> (i.e. <a href="https://infosec.space/tags/EVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EVM</span></a>) support? </p></li><li><p>Do you really want to integrate <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> support <em>natively into curl</em> when using <a href="https://infosec.space/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> (localhost:8118) and <a href="https://infosec.space/tags/SOCKS5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOCKS5</span></a> (localhost:9050) <a href="https://infosec.space/tags/proxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxy</span></a> allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??</p></li></ul><p>In fact if <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>toybox</span></a> didn't have a <a href="https://infosec.space/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wget</span></a> implementation that I could use for OS/1337 I would've merely chosen <a href="https://curl.se/tiny/" rel="nofollow noopener" target="_blank"><code>tiny-curl -o</code></a> as a <a href="https://stackoverflow.com/questions/30702803/set-aliases-globally-for-all-users" rel="nofollow noopener" target="_blank">global alias</a> or if <a href="https://infosec.space/tags/tinycurl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tinycurl</span></a> wasn't an option, <a href="https://linux.die.net/man/1/curl" rel="nofollow noopener" target="_blank"><code>curl -o</code></a> instead.</p><ul><li>Maybe someone who wants to have said functionality like <code>tor</code> support built-in will go and IDK make i.e. <code>#neocurl</code> or sth. along those lines or build something like <code>#ethcurl</code> or <code>#torcurl</code>or <code>#ipfscurl</code> or whatever...</li></ul><p>That being said I am glad <code>curl</code> isn't <em>solely</em> maintained by you but has other contributors (give them a shoutout!) but I also am glad you maintain that vital software that most <em>"<a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TechIlliterate</span></a> <a href="https://infosec.space/tags/Normies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Normies</span></a>"</em> most likely never heard of but propably use on a daily basis as part of all the <a href="https://infosec.space/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tech</span></a> they use to <a href="https://infosec.space/tags/consume" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>consume</span></a> media with...</p><ul><li>I consider curl to be <em>"the <a href="https://infosec.space/tags/vim" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vim</span></a> of downloaders"</em> (tho that's kinda insulting and limiting since <code>curl</code> is more than just a downloader <em>and</em> more intuitive than <code>vim</code>) with wget being <em>"the <a href="https://infosec.space/tags/vi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vi</span></a> of downloaders"</em> (tho <code>wget</code> is even simpler to use than <code>vi</code>)...</li></ul><p>Either way, curl is awesome... </p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enshittification</span></a> <a href="https://infosec.space/tags/Bloat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bloat</span></a> <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bloatware</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SweetAIBelle</span></a></span> very nifty...</p><ul><li>Personally, I wish there were more <em>"<a href="https://infosec.space/tags/LiveCD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LiveCD</span></a>"</em> (or rather <em>"<a href="https://infosec.space/tags/LiveUSB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LiveUSB</span></a>"</em>) distros like <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://infosec.exchange/@kalilinux" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kalilinux</span></a></span> that that offer a comprehensive set of <a href="https://infosec.space/tags/tools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tools</span></a> and benefits for users.</li></ul><p>Ideally with some nifty tools (compareable to Tails' <a href="https://infosec.space/tags/PersistentSotrage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PersistentSotrage</span></a>) to allow mounting local/remote storage as <code>$HOME</code> and potentially leverage <code>toram</code> as boot option.</p><ul><li>Bonus if that works via <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iPXE</span></a> for a <a href="https://infosec.space/tags/Diskless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Diskless</span></a> <a href="https://infosec.space/tags/Administrator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Administrator</span></a> Desktop to boot into.</li></ul><p>Certainly that <em>"<a href="https://infosec.space/tags/RescueLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RescueLinux</span></a>"</em> part is mid- to ongterm goal of OS/1337 and I am working on it (abeit at a pace slower than I want to cuz <em>'things happen in meatspace'</em> and those sadly require my full attention...</p><ul><li>Needless to say it's always good to have a nifty system at hand (worst-case I'd install <span class="h-card" translate="no"><a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ubuntu</span></a></span> / <a href="https://infosec.space/tags/UbuntuLTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UbuntuLTS</span></a> <a href="https://infosec.space/tags/Desktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Desktop</span></a> on an external SSD/HDD and have that at hand) if one doesn't have their Distro on a hot-swappable / toolless replaceable drive anyway...</li></ul><p>Using <a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ArchLinux</span></a> is quite good because it makes it easy to get started and adapt said system as need be.</p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dalias</span></a></span> <span class="h-card" translate="no"><a href="https://peoplemaking.games/@eniko" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>eniko</span></a></span> Personally, I'll sooner or later have to engange the whole <a href="https://infosec.space/tags/ARMv5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARMv5</span></a> / <a href="https://infosec.space/tags/ARM11r7" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM11r7</span></a> / <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPi</span></a> architecture anyway with OS/1337.</p><ul><li>Tho given it's a minimalist Linux merely booting an initramfs and never doing any writes, there should be no indurance issues.</li></ul><p>But I know a <a href="https://infosec.space/tags/readonly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>readonly</span></a> - OS isn't practical and where it is people already use <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iPXE</span></a> &amp; <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iSCSI</span></a> for <a href="https://infosec.space/tags/diskless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diskless</span></a> setups!</p><ul><li>THO AFAICT there should be an option to basically partition the system and only keep <code>/boot</code> on an SD card, and the rest could be on any USB mass storage device (i.e. SSD or even HDD)...</li></ul><p>That being said Raspberry Pi do have the key advantage of being by far the best in terms of <a href="https://infosec.space/tags/documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>documentation</span></a>.</p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://infosec.space/tags/distro" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distro</span></a> <a href="https://infosec.space/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>development</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>nixCraft</span></a></span> cool...</p><p>Personally I'd propably make a <em>"screenless" <a href="https://infosec.space/tags/NUCbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NUCbook</span></a></em> down the lane and use that as an <a href="https://infosec.space/tags/AiO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AiO</span></a> similar to those that <span class="h-card" translate="no"><a href="https://mastodon.social/@vwestlife" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vwestlife</span></a></span> seemingly likes... </p><ul><li>Sadly I couldn't find <a href="https://www.youtube.com/watch?v=vksDNN6YDbM" rel="nofollow noopener" target="_blank">that</a> <a href="https://infosec.space/tags/WintelK3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WintelK3</span></a> at reasonable prices anymore when I first saw it... </li></ul><p>Would've been the ideal testing system for OS/1337 .... </p><p><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><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a></p>