this post was submitted on 12 Sep 2024
20 points (100.0% liked)
FreeAssembly
75 readers
6 users here now
this is FreeAssembly, a non-toxic design, programming, and art collective. post your share-alike (CC SA, GPL, BSD, or similar) projects here! collaboration is welcome, and mutual education is too.
in brief, this community is the awful.systems answer to Hacker News. read this article for a solid summary of why having a less toxic collaborative community is important from a technical standpoint in addition to a social one.
some posting guidelines apply in addition to the typical awful.systems stuff:
- all types of passion projects and contributions are welcome, including and especially those that aren't programming or engineering in nature
- this is an explicitly noncommercial, share-alike space
- don't force yourself to do work you don't enjoy, or demand it of others
(logo credit, with modifications by @[email protected])
founded 8 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Some cool stuff: I went to a cs high school kind of deal and we learned some pretty fun stuff, then were encouraged to experiment:
teacher showed us to render the Mandelbrot set, and when I had that written I wrote a little thing that lets you zoom into it (it was buggy, but who cares! Infinite fractals!)
in school, I installed Linux on my pc, played around and then fucked up my primary disk’s boot sector and partition table. That meant my DOS install would be fucked up too (and I needed that for homework!), so I read up on MBRs and realized that if I remember the size of the partition, I can restore it to how it was.… and ext2 gives you a correct size even if the partition table is screwy, meaning that with the first primary partition activated I could find the correct size and then make an entry for the second one, and so on, until everything was working again. Data loss prevented!
I’d written a pretty good solution to a homework problem in C, but typo’d a cleanup command and deleted the source file. The previous data loss scenario had prepared me: I rebooted into a rescue disk, grepped the disk drive for parts of the source and got the file back! (Got multiple copies of the file back, in fact. That’s when I started using version control, hah)
Speaking of data loss, I once had just finished a physics lab assignment in OpenOffice and planned to print it off and walk to the University, 4 miles away, shortly.
Unfortunately an extremely confusing quirk of the OpenOffice file "recovery" UI meant that I clicked the wrong button and it helpfully deleted my document for me. I then spent the next hour learning Linux file recovery from scratch including finding and compiling a data recovery tool from source and learning about inodes.
In the end I managed to recover everything except for the images embedded in the document, hastily recreated them, and then ran the four miles to the university (my body would not be able to take that today haha)
the classic! your recovery from this was a lot smarter than mine — I think losing my data on Linux was what got me started on BSD
LOL, now that you mention it, I think installing FreeBSD was exactly the thing that got my MBR blown up that way. Ever since, I’ve taken a snapshot of the first 512 bytes of any bios-formatted drive…