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:

252
active users

#toybox

9 posts2 participants0 posts today
Replied in thread

@landley @mrmasterkeyboard yeah.

Personally, if "producing paper" wasn't undesireable you'd propably consider just taking the subsets of #POSIX and #LSB you're implementing and standardizing that as a sorf-of "#TINYNIX" (MININIX may be confused with Minix, MICRONIX and NANONIX already exist) standard.

  • Simply because you've propably taken a look at every userland-tool you want to include or have included in #toybox and asked if it's necessary to make a self-hosting OS.

I just tend to ask what are the comfort features and tools that I use and want if I have to use "my little distro" for my daily job as linux sysadmin.

OS/1337 Package Repository. Contribute to OS-1337/pkgs development by creating an account on GitHub.
GitHubpkgs/docs/WISHLIST.tsv at main · OS-1337/pkgsOS/1337 Package Repository. Contribute to OS-1337/pkgs development by creating an account on GitHub.
Replied in thread

@mrmasterkeyboard @landley glad I could get you guys connected then...

I'm convinced #toybox is a good #userland to get a basic OS up and running and on it's feet. If it's good enough for #Android then it's certainly gonna be good enough for #embedded stuff as well...

  • After all that seems to be the main goal of it: Allowing "self-hosting" as in building itself under itself if not deliver under the same OS...

I don't leverage that capability with #OS1337 (at least for now) but that's because I treat it more akin to how #VxWorks and #WindRiverLinux is being developed and deployed...

en.wikipedia.orgVxWorks - Wikipedia
Replied in thread

@mrmasterkeyboard If that #kernel is mostly #POSIX-compatible it should be possible to port #toybox over there (alongside any other software one may want to get running on @OS1337), but that's as far as I know.

Not shure if @landley has the time and spoons beyond testing toybox against #Linux as he does aim to make it a better alternative to #BusyBox & #GNUtils.

OS/1337 Package Repository. Contribute to OS-1337/pkgs development by creating an account on GitHub.
GitHubpkgs/docs/WISHLIST.tsv at main · OS-1337/pkgsOS/1337 Package Repository. Contribute to OS-1337/pkgs development by creating an account on GitHub.
Replied in thread

@mrmasterkeyboard np.

To me @OS1337 is just an attempt to a minimalist #Linux distro because I want some #reproduceable & #auditable #firmware for various other projects, and both @yoctoproject and #RaspberryPiOS 'lite' seem rather excessive to me.

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...

  • 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 ( @landley 's #toybox is a clean & minimalist userland) and being better than #GNU stuff (i.e. @musl / #musl) by not bricking shit at random minor updates…
Replied in thread

@lmemsm basically the Idea behind it is to be a brutally simple #toybox + #musl / #linux distro that grew out of the necessity for me to actually think about #firmware for some projects.

Basically I want something that is so simple and auditable that it's practical to make it pass any #verification demands for #SecureTerminal|s in #CriticalInfrastructure and #Communications.

  • OFC one may point at my other projects and say: "Why don't you just put #RaspberryPiOS on a #microSD?" ignoring that the smallest image is >330MB in size and that seems kinda overkill for essentially my demands for a minimalist #Linux with very few programs in userspace.

Not to mention a #GNUfree - #Linux distro is the way to go if I want that thing to not get bricked constantly by minor #GlibC-changes...

  • End goal is something akin to #MSDOS in it's brutal simplicity, but way more extendable.

I hope that answers your question...

  • Sorry for the delay.
Infosec.SpaceOS/1337 (@OS1337@infosec.space)1.38K Posts, 46 Following, 178 Followers · A minimalist musl + toybox/Linux Distribution focussed on being the bare minimum of a useable desktop whilst making most of the space it does.
Replied in thread

@wyatt Also glancing from the #PC98 architecture and specific quirks that #Linux accounts for in menuconfig it's most likely not gonna be enough to "just boot the #i486 version of @OS1337"...
github.com/OS-1337/OS1337/blob

  • Tho given the fact this is just a #toybox + #musl / Linux Distro that is barely booting using #syslinux and able to spit out a 80x25 MDA console, it is in an early infancy.

As for the specifics of the #PC9821+ and their detailed hardware I'm clueless beyond the Wikipedia Article and can only Assume anything before a (RAM-upgraded) #9821Ap & #9801BA is off the table and a #9821Af 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 linux-6.6.6 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)...

  • The #9821Ce should be workable in theory tho again that's just me reading a specsheet.

On the flipside I did manage to install #WindowsXP 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.

  • Worst-Case one could see to build a bootable CD-ROM or dd something on a #BlueSCSI or similar...
OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.
GitHubOS1337/OS1337-core-prerelease.img at main · OS-1337/OS1337OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.
Replied in thread

@gettie I know #i386-#linux support was deprecared and #i486SX became minimum spec as per linux-3.4.99 & linux-3.6.9 respectably.

  • And yes, the deprecared i386 support and non-support by #toybox is why @OS1337 requires an #i486 minimum. (And frankly, I don't blame @landley cuz by the time toxbox got started i386 was long deprecared)…
GitHubOS1337/docu/linux.kernel.versions.tsv at main · OS-1337/OS1337OS/1337 Project . Contribute to OS-1337/OS1337 development by creating an account on GitHub.
Replied in thread

@wolf480pl OFC limiting the scope of a project is important.

  • I.e. "I don't want to do a #GUI with like a modern desktop for @OS1337 because that'll exceed the desired complexity and sticking to #TUI / #CLI is the best I want to do." is such a scope.

OFC there are reasons why #bash is bash and why i.e. #toybox will most likely only implement a tiny subset of bash in toysh and why @landley hasn't implemented support for .bash_aliases yet [if he'd ever do that considering there are more pressing TODOs than "some hobbyist doodler's wish"...

  • Either way I don't fault either #developers for that: I don't pay them for their work so I don't get to tell them what they should do! In fact I'm grateful for their work and that they decided to release it and license it as #FLOSS and not #CCSS...
landley.netToybox 0.8.12 command help