OS/1337

@OS1337@infosec.space
192 Followers
42 Following
1.4K Posts

A minimalist musl + toybox/Linux Distribution focussed on being the bare minimum of a useable desktop whilst making most of the space it does.

like/star ≠ endorsement, but acknowledgement of being read.

Websitehttps://os1337.com
Project Sitehttps://github.com/OS-1337/OS1337
Git Changes Bot ( still under construction!)@OS1337_git
Current Preleasehttps://github.com/OS-1337/OS1337/blob/04256bfa4cf0f359039a81ae4508bbc8af9c4e72/build/0.CORE/os1337.img

Given that I want to target i486 with @OS1337 but don't want to deal with obsolete hardware that is dying of old age, I think it's more fitting to consider a sort-of mainboard to shove some 486SX-SOM with PC/104-Plus on and have the few necessities hooked up to it. Maybe even put it inside a THINN #Pizzabox-style #case?

It would also make a new "bridge" machine to interface old PCI & ISA hardware and allow connecting i.e. a #QuadFlop and roll with that...

https://github.com/OS-1337/tiny486

Thoughts, @rasteri @polpo @TechTangents @lazygamereviews @foone ??

#Tiny486 #embedded #EmbeddedComputing #retro #RetroComputing #Linux #EmbeddedLinux #Development #DevKit #DevelopmentKit #ideas #concepts #Hardware #OpenSource #OpenSourceHardware #Mainboard #i486 #i386 #i487 #486SX #486DX #PCI #ISA #BridgeMachine #Bridge #PC104 #PC104Plus

(this is orthogonal to any 32 bit packages you might provide for 64 bit systems. Ideally they're built with the same options as 64 bit packages)
My tiny controversial niche technical opinion that's somehow related to the meta of the day is that if you have an x86 32-bit Linux distro in 2025 it should be built for i486, because it's far more likely that people want to run it on tiny embedded boards than a Pentium 3 at this point

@mrmasterkeyboard @landley @OS1337

I'd likely stick with xenon because that's the Codename for the #Xbox360 and if I use that as a short architecture handle it's pretty certsin people won't confuse it with ppc64 or anything else.

  • So "OS/1337 for Xenon" because I'd not count on #Microsoft (who also own #GitHub) to not #DMCA anything that violates their #Trademarks on Xbox and Xbox 360 and avoiding any "confusion" that they could argue "it's misrepresented as an officially licensed / endorsed product" is one way to be left alone.

The #OS1337 [website](https://os1337.com) has been updated.

- We moved from #UbuntuMono to #B612Mono because the #B612 font family is licensed under SIL OFL and #Ubuntu's fonts have their own licenses.

- Also B612 is a *superior font* given that #Airbus got it designed, tested, and certified for *Civil Aviation Use*, which means it got extensive testing under harsh conditions.

Aesthetically, it's not much different!

- OFC the #Logo is next with the #Font change...

_OS/1337

Things #musl 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.

@HeatSinkAmbassador @halva @ubuntu @opensuse Then why did #Linux standard on SystemD?

  • Certainly @linuxfoundation or whoever writes the #LSB took their time re: that change and if you have ever habe to deal with huge amounts of servers, the whole benefits of the "#SystemD suite" really works well, because noone wants to deal with a shitton of filters & #syslog over journalctl -xe …

Don't get me wrong, @OS1337 runs off a single /etc/init file..., but for an embedded distro of it's tinyness, that is acceptable.

OS1337/build/0.CORE/fdd/fs/etc/init at main · OS-1337/OS1337

OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.

GitHub

As for the choice of Treehouse Systems, this was the outcome of a long delay trying to find the right place to move to.

What it came down to is that:

- Shared values on safety and moderation: Particularly on the type of situation that led to this move.

- Shared values on the responsibilities of an instance: Not to play games with defederation, ragequitting, etc. and break people's social graphs without adequate notice and chance to move.

- Connection to community: Lots of people and projects using musl are already associated with Treehouse.

This thread by @ariadne on Treehouse's intent to defederate from Fosstodon lays out more details, in more diplomatic terms:

https://social.treehouse.systems/@ariadne/114632131776730666

I (@dalias) 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 #musl libc updates on the fedi.

Ariadne Conill 🐰:therian: (@ariadne@treehouse.systems)

After some extended discussion with the rest of the Treehouse moderation team, as well as extended discussion with Gina, the new owner of fosstodon, we are planning to take incremental steps that will result in full defederation of fosstodon from Treehouse. Fosstodon has been a consistent moderation headache for our team for years, initially because of the same problems we have seen from many of the tech instances: drive-by snippy and unhelpful comments like "oh YOU wouldn't be having that problem if you just used GNU/Linux instead!" In the past year or so, however, things have changed in the nature of the moderation issues we have seen from Fosstodon. While the "reply guy" behaviour is still present, the overall temperature has shifted in the direction of the alt-right, both in terms of moderation incidents and, as recently seen, staffing incidents. Gina has outlined her philosophy regarding [the management of Fosstodon and its role in the greater fediverse](https://ginablogs.com/views-on-the-fediverse-zghd), however this blog does not address any of the specific problems we, and our users, have observed from their community. We are increasingly unconvinced that the situation will improve in any meaningful way, so we conclude that defederation is the only option. These conclusions are always disappointing, but as a community of queer hackers, these decisions are necessary to protect the psychological safety of our local Treehouse community. As we begin to bring our federated relationship with Fosstodon to a close, we encourage our local community to be thoughtful and kind in regard to their frustrations with the Fosstodon community. To help with continuity, instead of immediate defederation, Fosstodon will be upgraded to a full limit with report suppression in a few hours following this announcement. This will allow local users to continue to interact with Fosstodon users that they explicitly consent to interacting with while they make the transition to a new instance, and allows for reversal if Fosstodon commits to acceptable management practices which we have already outlined in our discussions with Gina. In the event that nothing meaningfully changes, Fosstodon will then be fully defederated on July 1.

Treehouse Mastodon

@musl The immediate cause for this move is that the admin and moderation staff at Fosstodon have proven themselves untrustworthy and unsafe.

Following an incident in which a person on their moderation staff was found to be using moderation privileges specifically and intentionally to harm LGBTQ folks, Fosstodon claimed to have "cleaned house" and committed to change.

The new admin immediately proceeded to recruit mods with the exact same values, and dug in and tone policed when challenged on that.

Fosstodon is proving itself a "nazi bar instance".