Social 📸 Photography

Kevin Karhan :verified:<a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@mrmasterkeyboard</a> <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> I mean, that's why I use <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> for <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a>, because I can't be assed to deal with the convoluted mess of <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> and I do want to make a <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a>-free, minimalist distro that I can use as a baseline for <a href="https://infosec.space/tags/Firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firmware</a>.

Kevin Karhan :verified:<a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@mrmasterkeyboard</a> If that <a href="https://infosec.space/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> is mostly <a href="https://infosec.space/tags/POSIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#POSIX</a>-compatible it should be possible to port <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> over there (<a href="https://github.com/OS-1337/pkgs/blob/main/docs/WISHLIST.tsv" rel="nofollow noopener" target="_blank">alongside any other software one may want to get running</a> on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a>), but that's as far as I know.Not shure if <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> has the time and spoons beyond testing toybox against <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> as he does aim to make it a better alternative to <a href="https://infosec.space/tags/BusyBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#BusyBox</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a>.

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://todon.nl/@burnoutqueen" class="u-url mention" rel="nofollow noopener" target="_blank">@burnoutqueen</a> Yeah...<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> is a desaster as it's 99% ideology and 1% license text and alongside <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> completely ignores the reality of how <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#licensing</a> and <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#patents</a> and <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> works.<ul><li>Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.</li></ul>And on the flipside we basically get "source available" stuff like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> which only serves as a means to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssetDenial</a> and monopolize commercial offerings...<ul><li>I think <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2only</a> is a good compromise and my personal gripes with <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSF</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> as well as <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> are something different...</li></ul>

Kevin Karhan :verified:And OFC <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=SGmtP5Lg_t0&t=2271s" rel="nofollow noopener" target="_blank">good baseline</a> in terms of <a href="https://infosec.space/tags/userland" class="mention hashtag" rel="nofollow noopener" target="_blank">#userland</a> - espechally when I want a <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a>-free <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distro <a href="https://www.youtube.com/watch?v=R2SKenHRhMg" rel="nofollow noopener" target="_blank">because there are very good reasons beyond</a> <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> being a bloated mess...

Kevin Karhan :verified:<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener" target="_blank">@dalias</a> <a href="https://mastodon.transneptune.net/@owen" class="u-url mention" rel="nofollow noopener" target="_blank">@owen</a> <a href="https://woof.group/@aphyr" class="u-url mention" rel="nofollow noopener" target="_blank">@aphyr</a> nodds in agreement I want stuff to be portable and reproduceable!<ul><li>And that means actually including - or at the very least declaring - ALL dependencies...</li></ul>The whole <a href="https://infosec.space/tags/PainAndFrustration" class="mention hashtag" rel="nofollow noopener" target="_blank">#PainAndFrustration</a> with <a href="https://infosec.space/tags/LinuxFromScratch" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxFromScratch</a>, bloated <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> and <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> constantly breaking shit (among other things) is why I started <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> …

Kevin Karhan :verified:<a href="https://mk.absturztau.be/@enigmatico" class="u-url mention" rel="nofollow noopener" target="_blank">@enigmatico</a> <a href="https://plasmatrap.com/@privateger" class="u-url mention" rel="nofollow noopener" target="_blank">@privateger</a> there's a reason I work on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> and why it's intended to be a <a href="https://infosec.space/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a>-free <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:<ul><li><a href="https://infosec.space/tags/GLibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GLibC</a> is a shitshow maintained by nonchalant assholes that constantly brick systems with minor updates whilst denying the right to exist to <a href="https://infosec.space/tags/CCSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CCSS</a> and who think "recompile it yourself" is an acceptable answer even outside of <a href="https://infosec.space/tags/FLOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FLOSS</a> projects.</li></ul>The only <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> part that neither <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> nor I were able to replace is the <a href="https://infosec.space/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> because AFAIK Linux just won't compile under <a href="https://infosec.space/tags/Clang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Clang</a> / <a href="https://infosec.space/tags/LLVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLVM</a>...<ul><li>The moment that isn't the case anymore I')( happily ditch tht too, cuz GNU / <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSF</a> are just bad and the only recourse I have aggainst them is to <a href="https://infosec.space/tags/boycott" class="mention hashtag" rel="nofollow noopener" target="_blank">#boycott</a> them into irrelevancy...</li></ul>Shall all those people at the FSF complain at <a href="https://infosec.space/tags/RMS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RMS</a> for <a href="https://youtu.be/R2SKenHRhMg" rel="nofollow noopener" target="_blank">alienating people and harming FLOSS in general</a> or as <a href="https://social.restless.systems/@ncommander" class="u-url mention" rel="nofollow noopener" target="_blank">@ncommander</a> once said: ' […] <a href="https://infosec.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> thrives not hecause but in spite of <a href="https://infosec.space/tags/Stallman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stallman</a> […]' cuz being a visionary predicting <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> like <a href="https://infosec.space/tags/DRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#DRM</a> doesn't make him a less unlikeable character to be polite...

Kevin Karhan :verified:<a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener" target="_blank">@SweetAIBelle</a> <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> shure.I'm convinced that a fully-fledged image of that would be similar to <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a>'s <a href="https://infosec.space/tags/mkroot" class="mention hashtag" rel="nofollow noopener" target="_blank">#mkroot</a>, which is <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> 's reference implementation for a toxbox + <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> system.<ul><li>Last time I checked it came out just below 4 MB, but that was the premade image using only the stuff <a href="https://youtu.be/MkJkyMuBm3g" rel="nofollow noopener" target="_blank">toybox included</a> [and linux & being statically compiled against musl] like <a href="https://infosec.space/tags/gzip" class="mention hashtag" rel="nofollow noopener" target="_blank">#gzip</a> instead of <a href="https://infosec.space/tags/xz" class="mention hashtag" rel="nofollow noopener" target="_blank">#xz</a> for compression, so there already is room to shave a few hundred kB without reducing functionality out of the get-go as I've seen with my build tests of <a href="https://infosec.space/tags/kernel666" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel666</a>...</li></ul>Either way, we're close to <a href="https://youtu.be/cz6iGrhnMKs" rel="nofollow noopener" target="_blank">his reference matterial</a> AFAICT and I do think that OS/1337 can become a good and solid foundation for <a href="https://infosec.space/tags/minimalist" class="mention hashtag" rel="nofollow noopener" target="_blank">#minimalist</a> & <a href="https://infosec.space/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#embedded</a> systems. For comparison:<ul><li><a href="https://infosec.space/tags/YoctoLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#YoctoLinux</a> is <a href="https://www.yoctoproject.org/" rel="nofollow noopener" target="_blank">quite</a> <a href="https://infosec.space/tags/THICC" class="mention hashtag" rel="nofollow noopener" target="_blank">#THICC</a> in comparison (using LSB & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> for the most part!) and stuff like <a href="https://infosec.space/tags/OpenADK" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenADK</a> seems to be overly complex...<ul><li>tho <a href="https://infosec.space/tags/Viprinet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Viprinet</a> <a href="https://www.viprinet.com/en/support/downloads#viprinux" rel="nofollow noopener" target="_blank">hasn't updated their stuff in like 8 years</a> and I sincerely hope that's just them loginwalling access to <a href="https://infosec.space/tags/SourceCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#SourceCode</a> like <a href="https://infosec.space/tags/grsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsecurity</a> to paying customers only and not them such old Kernels.</li></ul></li></ul> Speaking of <a href="https://infosec.space/tags/grsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#grsec</a>, I wounder if Bruce Perens actually sued them for allegedly violating <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2</a> when in fact said license allows <a href="https://infosec.space/tags/paywalling" class="mention hashtag" rel="nofollow noopener" target="_blank">#paywalling</a> aka. restricting access to buyers of the product it contains.<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a>

Kevin Karhan :verified:<a href="https://infosec.exchange/@nuintari" class="u-url mention" rel="nofollow noopener" target="_blank">@nuintari</a> I disagree.<a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemD</a> is a "necessary evil" because what existed previously was bad for anything that isn't a "build once never change" server that never gets changed much... <a href="https://www.youtube.com/watch?v=o_AIw9bGogo" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=o_AIw9bGogo</a><ul><li>Most <a href="https://infosec.space/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a>-esque OSes already used something like it way before <a href="https://mastodon.social/@pid_eins" class="u-url mention" rel="nofollow noopener" target="_blank">@pid_eins</a> even did <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>: Like <a href="https://infosec.space/tags/SMF" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMF</a> on <a href="https://infosec.space/tags/Solaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solaris</a> and espechally <a href="https://infosec.space/tags/LaunchD" class="mention hashtag" rel="nofollow noopener" target="_blank">#LaunchD</a> which is basically what inspired systemd.</li></ul>The only reason I "cut" systemd from <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> as of now is because I can't make it - or the <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> that preceded it - fit within the few hundred kB on a 1.440 kB FDD I can spare.Noone wants to go back to <a href="https://infosec.space/tags/SysVinit" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysVinit</a> when even the fastest systems took longer to boot that most peoole need to make a shitty coffee or dump ass on the toilet.<ul><li>Amd dumping SysVinit - just like <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> dumping <a href="https://infosec.space/tags/i386" class="mention hashtag" rel="nofollow noopener" target="_blank">#i386</a> - is somewhat inevitable given the amount of work it took to keep it workable at all...</li></ul>

Kevin Karhan :verified:<a href="https://social.restless.systems/@ncommander" class="u-url mention" rel="nofollow noopener" target="_blank">@ncommander</a> nodds in agreementEspechally since <a href="https://infosec.space/tags/Zones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zones</a> are a built-in containerization and isolation feature of <a href="https://infosec.space/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#illumos</a> nee <a href="https://infosec.space/tags/OpenSolaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSolaris</a> and it would be a good match for hat exact scenario...That being said, it reminds me why I did start my own:Because <a href="https://infosec.space/tags/Viprinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Viprinux</a>'s <a href="https://infosec.space/tags/OpenADK" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenADK</a> is an unworkable mess even cringier than the <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> toolchain... <a href="https://www.viprinet.com/en/support/downloads" rel="nofollow noopener" translate="no" target="_blank">https://www.viprinet.com/en/support/downloads</a> <a href="https://github.com/OS-1337/OS1337" rel="nofollow noopener" translate="no" target="_blank">https://github.com/OS-1337/OS1337</a>

Kevin Karhan :verified:<a href="https://veganism.social/@beforewisdom" class="u-url mention" rel="nofollow noopener" target="_blank">@beforewisdom</a> <a href="https://turtleisland.social/@Yehuda" class="u-url mention" rel="nofollow noopener" target="_blank">@Yehuda</a> <a href="https://hostux.social/@fsf" class="u-url mention" rel="nofollow noopener" target="_blank">@fsf</a> exactly.As for the <a href="https://mstdn.social/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> like <a href="https://mstdn.social/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a>, I do work on getting rid of them as well where I can.I am currently working on a <a href="https://mstdn.social/tags/minimalist" class="mention hashtag" rel="nofollow noopener" target="_blank">#minimalist</a> <a href="https://mstdn.social/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#embedded</a> distro based off <a href="https://mstdn.social/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> / <a href="https://mstdn.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> + <a href="https://mstdn.social/tags/musl" class="mention hashtag" rel="nofollow noopener" target="_blank">#musl</a>, because <a href="https://mstdn.social/tags/Glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#Glibc</a> is a shitty mess that bricks stuff at random in minor version updates for no good reason! <a href="http://os1337.com" rel="nofollow noopener" target="_blank">http://os1337.com</a>

Kevin Karhan :verified:<a href="https://mastodon.ar.al/@aral" class="u-url mention" rel="nofollow noopener" target="_blank">@aral</a> <a href="https://soc.citizen4.eu/profile/miklo" class="u-url mention" rel="nofollow noopener" target="_blank">@miklo</a> thx.For Same does for a lot of of other things: I'd love to get <a href="https://mstdn.social/tags/FSF" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSF</a> / <a href="https://mstdn.social/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> out of my tech stack just for them letting <a href="https://mstdn.social/tags/Stallman" class="mention hashtag" rel="nofollow noopener" target="_blank">#Stallman</a> back in but alas I'm kinda forced to work with <a href="https://mstdn.social/tags/bash" class="mention hashtag" rel="nofollow noopener" target="_blank">#bash</a> and <a href="https://mstdn.social/tags/nano" class="mention hashtag" rel="nofollow noopener" target="_blank">#nano</a> and stuff...<a href="https://www.youtube.com/watch?v=R2SKenHRhMg" rel="nofollow noopener" target="_blank">https://www.youtube.com/watch?v=R2SKenHRhMg</a>

Free Software FoundationFebruary GNU Spotlight with Amin Bandali: Eighteen new GNU releases in the last month, including <a href="https://hostux.social/tags/LinuxLibre" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxLibre</a>, <a href="https://hostux.social/tags/Lilypond" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lilypond</a>, <a href="https://hostux.social/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a>, <a href="https://hostux.social/tags/Jami" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jami</a>, and more. Full details: <a href="https://u.fsf.org/3x9" rel="nofollow noopener" target="_blank">https://u.fsf.org/3x9</a> Big thanks to @bandali0 <a href="https://mastodon.sdf.org/@bandali" class="u-url mention" rel="nofollow noopener" target="_blank">@bandali</a>, all the devs, and other contributors!

Recent searches

Search options

Administered by:

Server stats:

#gnutils