This might sound silly, but I installed virt-manager to make things a little easier when using qemu, then created a new virtual machine with debian 12 on it... then installed qemu on that.
The actual reason for this is to make github account separation a little easier...
If you get virt-manager set up properly, it definitely makes using qemu easier, though. I practically just had to tell it to make a new virtual machine using this iso with this much memory and this big of a hard drive, and it was right at the debian install screen. (Set it up with xfce...).
Main tricky parts were that I had to install libvirt first, make myself a member of the libvirt user group, enable the service, and install dnsmasq. Not great, but could've been worse...
Used debian on the virtual box just for a little variety. I like to keep my hand in on different distributions a bit.
But speaking of OS/1337, i really need to get crackin' on those open issues and start using the reworked scripts of yours so my old mess can get yeeted sooner than later...
Thanks again to @SweetAIBelle for extensive contributions to OS/1337, making the pipeline and scripts to reproduceably build OS/1337 images and it's parts more flexible and nifty.
I've been re-reconverting a lot of my "stuff" to the BSDs (Free, Open, Net). It's refreshing. The Linux every-tool-has-to-be-a-swiss-army-knife ethos is exhausting after a while. The relative simplicity and clean organization of *BSD (especially OpenBSD) re-affirms my fondness for UNIX-y things.
You might think there's not that much difference but, in many cases, I'd rather admin a BSD box. Try it, you'll see.
Also, NetBSD is soo lean, it has made my old Pentium III almost useful again. Even with 333Mhz and 128 MB of RAM 🙃
@rory Well, for OS71337 I took inspiration from @w84death 's #Floppinux and took his #documentation and went full "chimp banging rocks together" on it, but swapping #BusyBox for @landley 's #toybox since I prefer #bash over #ash and wanted something really basic that would do more than cat text files but provide i.e. a portable #SSH#client on a FDD.
Something that could serve as a foundation or rather plain "slate for my other projects in lieu of a THICC distro that is not practically auditable
I know.
It's the part where I derivated from the #Floppinux manual which went with #gzip instead of #xz, likely because that was customary for quite some time and even used by most #busybox - based distros otherwise.
After all, rarely do #embeddedLinux systems need to conserve storage that aggressively like with #OS1337...
Granted, the minimalist version will be minimal for obvious reasons: Neither of us can defy gravity...
For a minimalist system that wants to be a successor to #tomsrtbt and #Floppinux there isn's anything smaller nor more efficient.
After all, I don't expect OS/1337 to be used as a "#Server" in lieu of @ubuntu / #UbuntuLTS or #Debian but instead want to use it as a clean foundation for other projects of mine in need of an #OS.
@lupo the problem is that i already compress the hell out of stuff:
I literally chose #xz over #gzip and #lzma for both #kernel ans #initramdisk to get both as small as possible...
I'm convinced that it's possible to get a #i486-SX #linux with #toybox and #dropbear into 1440kB since someone managed that with way less optimization and with ample wiggle room [272kB] using Linux 5.13.0-rc2 and #BusyBox 1.33.1 manual and not even halfassing optimization at all.
So yeah I've to look deeper into it and see what I'm missing.
@landley The reason I literally choose the latest released #Linux#Kernel is because this means I'll also be able to profit from latest features or at least fixes done to it.
Some old #longterm kernels don't even support #xz compression...
In terms of drivers beyond #floppinux I only want basics like #TCP / #IPv4, support for some old #3Com, #AMD, #Intel and #VIA NICs as well as /dev/ devices so I can use #cfdisk or at least #dd to shove something on a disk.
I guess I've to start @ allnoconfig.
Currently I just need to find out what went wrong and see how I can make OS/1337 go brrrrrr.
So if anyone has any ideas, please feel free to contact me: https://mstdn.social/@kkarhan/111409592616485280
Also #boosts appreciated!
:boost_ok: :boost_requested: :boost_animated:
But maybe my toybox .config is also dysfunctional as I basically gutted most functions out of it since I only want to launch #dropbear#SSH Client (aka. #dbclient)...
I'm trying to play with SH4 CPUs in a few set-top boxes I have. This is difficult as the whole STLinux FTP server is long gone.
If you, or anyone you know has these files:
@gorplop right now I'm still working on getting like a 1440kB 3,5" FDD relese (version 0.1) for #i486-SX done but in theory everything should just cross-compile to #SuperH 4 / #SH4...
I just wanted to make something more practical to use than #Floppinux whilst also making something a bit more versatile than #mkroot.
Kinda going from @landley 's #mkroot and working towards building something that is actually useable and not just some EoL tool (i.e. #tmsrtbt / #TomsRootBoot) or a simple test of feasibility (i.e. #Floppinux which uses #BusyBox instead of #toybox).
With the "CORE" / #Floppy version of #OS1337 being almost done I'd like to ask if anyone would be interested in ordering a physical 3,5" 1440kB Version on a disk + smol printed manual?
@JohannessNilsson personally, I just wanted to beat #Floppinux and actually make something that is more practical than just existing and spitting out text on screen.
OFC long-term I do want to expand this further and make something that is still smaller than #TinyCore yet also practical to run on my #Atom#Z520-powered #VaioP11Z or any of those shitty #StickPC's and #Trash-#Tablets that have a #Z8300 and just 1GB of RAM and that already felt painfully slow on #Windows8 when they got released.