Spyke

Replies

Comment on

First FAT32 Write for my OS project (D.eSystem 6.1.8)

Reply in thread

Sure, add a Readme which explains the core design of the OS. Clearly attribute other peoples work you copied or got inspired on (like tutorials). Even if this sounds minor, it will show that you actually engaged with 3rd party resources and maybe did something on your own. This is what would make this project more than just a hacked together experiment with a few bolts on.

Also, people commonly do not share their experiments, except if they are doing something really groundbreaking new. There is a difference of what people do alone in their home, and what they share as a public, at least a bit polished, release.

If you could add a spin of why you feel like your mess is worth it (like you just getted starting coding with this and learn along the way), there would be another reason to engage with it, except to criticize it.

Comment on

First FAT32 Write for my OS project (D.eSystem 6.1.8)

Reply in thread

You are right: You are not posting that often, but when you do, you broadcast it across many different communities - which is also a kind of spam.

Normally, other people will x-post interesting stuff, if they feel like it. You could stop spamming by posting to only one target.

Also, please read the room: I feel like due to the countless issues raised (a long time) before, you should first address those before posting again - as we nerds like to engage with at least something valuable, but this project is currently a burning dumpster fire.

Comment on

Is ansible worth learning to automate setting up servers?

I think it is a great way to document what you have done too. Especially with larger setups this can be quite time-intensive.

Then add that you may want to dynamically reconfigure your systems to interact with each other and then Ansibles template-rendering comes in really handy.

Finally, it is standardized - so other peopke can work with it too (relevant in work context).

linux

Comment on

am I reading this right, that my cpu just died?

Most common issue would be something with your system memory. I could imagine that this caused the timeout of your cpu, which waited for the startup code, which never arrived.

In case you want to test that, swap your memory sticks around. Or tell the kernel to ignore that cpu (see command line arguments of the kernel).

Comment on

First FAT32 Write for my OS project (D.eSystem 6.1.8)

So... You spammed it often enough for me to take a look.

Your source archive is a mess... It contains local configs, build artifacts (oh well I learned a lot about your system, lol), .git-folders (from other projects) and a shitton of stolen code.

First off, you are based on https://github.com/Limine-Bootloader/Limine or more precisely use it to boot into your kernel, which is taken from other sources, but also just 1:1 snippets from https://github.com/shrike-505/ComputerSystemIII/blob/8c80719e/kernel_XPart/arch/riscv/include/fat32.h (part of a tutorial from https://deepwiki.com/shrike-505/ComputerSystemIII/4.9-file-system:-mbr-fat32-and-vfs-abstraction ). Core components like the c-libs are also just copy-pasted repos (at least using git to clone, so one has the exact ref). There are chinese and german comments in the code, which is also just a mess of hard-coded constants and duplications all over the place. Not even apps like the calc are much orignal, as you also uploaded the inspiration sources you modified in original (well, at least preserving the original sources I guess)?

This is not cool! If you copy code, attribute it. Your license is unmodified and potentially wrong, as you apply it to 3rd party code (which lacks any license, so you cannot just use it in the first place).

Most of the code looks quite well, because it is not yours and just copied from other projects.

Please... Do better? Even I would not think of cleaning this mess up, but instead starting from scratch as it is just such a mess of copy-paste, experiments, random artifacts and... (Binary-)Crap.

Comment on

Is ansible worth learning to automate setting up servers?

Reply in thread

Sorry, but I fear not. Ansible has a good getting started out there, but I think you'll learn the most just using it.

Maybe a broad roadmap... Try to add systems. Test them via Ansible-Ping. Change some configs (add file, add line-in-file). Add handlers to react to changes by restarting services. Add host variables and customize behavior per host. Add templates...