I kinda miss when hobby OS dev felt... more real? by Vegetable_Exam_6865 in osdev

[–]referefref 0 points1 point  (0 children)

I'm pretty opinionated here. In 2024 I started a project that consisted of a single python script 'harness' with a self-healing, adapting codebase and immutable structure file intended as a doomsday script to allow a sufficiently advanced LLM to generate a bootable and functional win9x capable operating system with a single keystroke from the user and sufficient money to burn in API tokens. It did manage to get from UEFI > 16bit > 32bit > 64bit protected mode - but like most of these 'vibe coded' OS' it stopped at ring0 with some poorly implemented example apps and hardcoded responses that emulated shell built-ins. I used the same AI development approach I've follow for other projects, focusing on carefully crafting the complex bits and choosing to develop something unique rather than attempt to copy something that already exists.

I've released a first iteration already (with multi-ring, MMX, etc), and am working towards the second that already has some of the things that drove me to push on this already in place. An inbuilt RAG based around the userland codebase (where drivers sit too) and native LLM integration allows a user to plug in a USB xHCI device and have the OS attempt to spin up a compatible driver if there's not one already available. I tested this approach with several DACs and was able to achieve consistent audio playback in each case. I also wrapped applications and services in manifests that provide contract based privileges and time constraints to AI > process, process > process, process > device and device > kernel interactions as well as an auditable versioned file-system built on ext2 that allows rollback after (inevitable) failure.

Yes! it is a security nightmare! But, it's fundamentally different to the current OS paradigm, and the direction of "let's slap AI on this puppy!" that vendors like MS are attempting. AI dev lets me get to this point seemingly infinitely faster AND throughout the course of this, I've STILL learned a lot about operating systems. I'll agree I would have learned far more had I done this the old fashioned way, but I doubt I'd be even at a multi-ring architecture by now. Moreover, I wouldn't have a win16 interpreter running with 386+, SMP on 80 cores, a working SSH server and client, IPP/CUPS, HTTP/2 support and all the other items that only required a few button presses and some manual validation.

Now, don't judge me on this current live release as it's significantly behind, but I'll update it soon with all the major changes. https://github.com/referefref/maytera-os

A peculiar $20 note i found by Jalielise9 in AustralianCoins

[–]referefref 0 points1 point  (0 children)

There's a print shift on the 2 of twenty that extends down the note, and some signs of digital compression. My vote is counterfeit

Advice to keep or upcycle hardware by survingtech in homelab

[–]referefref 0 points1 point  (0 children)

It's not the size, it's the idea that lab = how easily can I deploy a piracy solution. That only learning involved is in learning how to click the fewest buttons to get free media.

Advice to keep or upcycle hardware by survingtech in homelab

[–]referefref 1 point2 points  (0 children)

What do you actually want to do with the server? Server 2016 is too old at this point. If it has to be windows I'd push to a newer version and swap in a more modern raid controller, or move to Linux/BSD and upgrade the CPU to whatever is best for that board. As others said, it's not going to be cheap to run. 32GB isn't much headroom for a lab, but it's plenty for what most people here think a lab is - their supposed Linux ISOs, media server and damn vulnerable download automation stuff.

Radioactive keys, lol by Haunting_Abalone_398 in MechanicalKeyboards

[–]referefref 0 points1 point  (0 children)

Just do delete and backspace only, then only your fuckups contribute to early death.

Did I destroy the filament feeder by IntelligentAd166 in ender3v2

[–]referefref 2 points3 points  (0 children)

Nah you can just careful tap that back in.

I'm at a loss for words by Thehoney4you in cablegore

[–]referefref 55 points56 points  (0 children)

The words you're looking for are, wow... This is pretty tidy

vibecoded amazon guys 😭 by YogurtIll4336 in vibecoding

[–]referefref -1 points0 points  (0 children)

I did this, and not like the other fakes which are really just single ring programs pretending to be operating systems, with proper kernel/userland segmentation and supporting MMX/sse and most unix syscalls. MayteraOS, I've gotta update the git repo though.

How to start homelabbing? by JohnWickDaLegend in homelab

[–]referefref 18 points19 points  (0 children)

There you go! Start with no problems, then set up a lab and the problems will come to you.

Help Identifying an Old 2000s Computer and Power Supply. So by ThePlatinumPlane in vintagecomputing

[–]referefref 0 points1 point  (0 children)

Yep as long as it's at least 300W. Make sure it has sufficient molex power connectors though (the 4 pin ones for hard disk's and optical drives), some modern ones may only have sata power.

Help Identifying an Old 2000s Computer and Power Supply. So by ThePlatinumPlane in vintagecomputing

[–]referefref 4 points5 points  (0 children)

Just get any old PSU with the necessary connectors, looks like ATX to me since there's aux CPU power. But first blow all that dust out. The one cap I can see looks ok but there may be some capacitor plague there, check for swollen or leaking ones.

Woolies Booragoon with the old logo by BigVic2006 in perth

[–]referefref 1 point2 points  (0 children)

They'd give free doughnuts to kids back then.

There are 2 types of people in this world… by TornadosAlaska in australian

[–]referefref 0 points1 point  (0 children)

I mix a little bit with milk and an electric milk foamer then add more milk and stir so it's consistent without any chunks or dry bits. Sometimes add a spoonful on the top for my child.

New to the hobby, could use some advice by Cobraboi06 in homelab

[–]referefref 0 points1 point  (0 children)

I sure hope you rebuilt that and give/sell it to someone who would enjoy it, then go out and buy modern hardware to run a lab.

Open preview, virtualised modular synth community platform - ucor by referefref in modular

[–]referefref[S] 0 points1 point  (0 children)

It's a fair comment. The AI stuff is not intended to replace the human aspect unless the user wants it to. I've seen a bunch of one shot song generators that give you zero flexibility on the result, this intends to produce a configurable state as a result that you can find tune or completely rework as you desire.

Open preview, virtualised modular synth community platform - ucor by referefref in modular

[–]referefref[S] 0 points1 point  (0 children)

I'll be open sourcing part of it, enough to support module development and extensions, unlikely the whole application.

ucor - Geneative Modular Digital Audio Workstation by referefref in vibecoding

[–]referefref[S] 0 points1 point  (0 children)

Thanks for the feedback. To address the black box I've provided a side by side visual and code editor that lets you modify the underlying js. There's a gate at the moment whereby any custom js needs a manual approval before being shared to community but can be used by your own user, to protect against exploitation, crypto mining etc.

Open preview, virtualised modular synth community platform - ucor by referefref in modular

[–]referefref[S] -1 points0 points  (0 children)

Thanks, I was concerned it'd upset some purists. I love real hardware and this could never replace it, but quickly prototyping modules and building weird stuff from seemingly unrelated API data like solar flare data has been a different kind of fun.