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.
@SweetAIBelle makes sende tho you propably just went "hard mode" with QEMU/KVM.
There's a reason why I'd likely just use #ProxMox or even #ESXi instead, tho that's only because I've to deal woth these professionally and developed some speed at using them, not necessarily because it's the best approach.
It's kinda like Simon Smith using #SCORE vs. @tantacrul using #Sibelius:
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...
@kkarhan
The thing we'll want to be careful of is that currently, the new scripts symbolically link the config files in the old area, and also copy a few files as part of the process, mostly the init scripts.
I can either move the init scripts over to profiles or make a new area for them, but I'm pretty much thinking I'll do that once you aren't using the old area any more...
@SweetAIBelle personally, I think we should sort those configs into profiles and subdirectories.
Ideally allowing to specify a "meta config" for non-interactive building and providing an interactive option without requiring dialog and ncurses to choose between profiles or build a custom one...
@SweetAIBelle ...but I do appreciate your effort and also non-destructive approach.
I really need to start using your scripts and espechally build with them so we can get stuff sorted out for good and thus making it easier for others to have a fully reproduceable from sources minimalist Linux that doesn't take hours if not days to compile on an entry-level modern machine…
Cuz I can't afford to build a monster like @fuchsiii did to rapid-fire recompile #Wine and make old Windows games go brrr…
@SweetAIBelle Ideally we'd end up with something more featureful than #toybox's #mkroot when it comes to OS/1337.
Like a more modular configureability for targets and native- & cross-compiling, where supporting a new architecture/hardware is as easy as plopping in a profile with configs (plus i.e. necessary drivers / firmware not included in the kernel) into a folder and kicking off the build pipeline to generate a bootable image to dd onto a drive…
@kkarhan
I used to use Virtual Box any time I was going to do something like this, but I'd been wanting to switch away from it, and I knew Qemu was good, just missing an actual UI, and that there were third party ones out there. It mostly seemed like a good time to switch...
@SweetAIBelle given #Oracle's hostility towards #FLOSS and blatant disregard towards commitments done by #SunMicrosystems when they were (sadly against everyone but #FTC & @EU_Commission 's decisions) allowed to absorb #Sun I think that is sadly more necessary than ever before.
Were it not for the absurdly high cost of electricity in Germany (~€0,33/kWh) I would've already converted several Workstations into Servers running #ProxMox.
I make due with some hp t620 #ThinClients that are fanless…
#Oracle pissed off a lot of loyal #Sun customers - including research centers that prior to te acquision basically preordered the latest #SPARC-based servers running #Solaris and had them installed before those were even publicly announced.
Add comment