European guy, weird by default.

You dislike what I say, great. Makes the world a more interesting of a place. But try to disagree with me beyond a downvote. Argue your point. Let’s see if we can reach a consensus between our positions.

  • 10 Posts
  • 315 Comments
Joined 2 years ago
cake
Cake day: August 19th, 2023

help-circle




  • I moved to a DDR4/AM4 platform when I assembled my current machine because the AM3 platform was being labelled as end of cycle and the FM segment seemed too niche.

    The scales tiped when I discovered many AM4 CPUs carried on chip graphic processing capabilities and being in need of a graphics card it was more affordable for me to just buy an APU than buy a CPU and add a GPU on top.

    Not being a gamer and a Linux user, throwing money on a graphics card, that by then were heavily price inflated, made little sense, so I opted by the AM4 platform.

    Currently, I’m considering building a machine capable of running Wasteland 2, because that game has been under my eye for years.

    I’m finding graphic cards with 4GB of memory on the market with very interesting prices. Used CPUs are cheap, unless I aim for the top tier models, with 6 or more cores. I still have the memory chips from the machine I retired (8GB) and getting an additional 8 is nothing out of reach. I just need to find a motherboard that can take 16GB or more of memory.

    If I can assemble a machine capable of running that game, I’m fairly confident the system itself will be more than enough to comply with my daily computing needs and then some.













  • I worked with someone that defend this isea to the letter, just not contemplating companies.

    The argument stemmed from an alledge visit he had done to Japan, where he had seen terminals connected to mainframes, and people used those from their house.

    I was only able to raise one argument: that is not my computer.

    Mind that this man was extremely tech savvy, an experienced and proficient programmer and played the roles of IT solutions an security implementer and supervisor at the company we worked at. And we handled sensitive information.

    To him, relegating everything to an outside server was a dream, as removed the hassle and responsability of having to maintain, repair, replace and upgrade hardware. Everything needed should be a monitor, a keyboard and a mouse or trackball.



  • @mvirts@lemmy.world @kumi@feddit.online @wickedrando@lemmy.ml @IsoKiero@sopuli.xyz @angband@lemmy.world @doodoo_wizard@lemmy.ml

    Update - 2026.01.12

    After trying to follow all advices I was given and failling miserably, I caved in and reinstalled the entire system, this time using a Debian Stable Live Image.

    The drives were there - sda and sbd - the SSD and the HDD, respectively. sda was partioned from 1 through 5, while sbd had one single partition. As I had set during the installation. No error here.

    However, when trying to look into /etc/fstab, the file listed exactly nothing. Somehow, the file was never written. I could list the devices through ls /dev/sd* but when trying to mount any one of it, it returned the location was not listed under /etc/fstab. And I even tried to update the file, mannually, yet the non existence of the drives persisted.

    Yes, as I write this from the freshly installed Debian, I am morbidly curious to go read the file now. See how much has changed.

    Because at this point I understood I wouldn’t be going anywhere with my attemps, I opted to do a full reinstall. And it was as I was, again, manually partitoning the disk to what I wanted that I found the previous instalation had created a strange thing.

    While all partions had a simple sd* indicator, the partition that should have been / was instead named “Debian Forky” and was not configured as it shoud. It had no root flag. It was just a named partition in the disk.

    I may be reading too much into this but most probably this simple quirk botched the entire installation. The system could not run what simply wasn’t there and it could not find an sda2 if that sda2 was named as something completely different.

    Lessons to be taken

    I understood I wasn’t clear enough of how experienced with Debian I was. I ran Debian for several years and, although not a power-user, I gained a lot of knowledge about managing my own system tinkering in Debian, something I lost when I moved towards more up-to-date distros, more user-friendly, but less powerful learning tools. And after this, I recognized I need that “demand” from the system to learn. So, I am glad I am back to Debian.

    Thank you for all the help and I can only hope I can returned it some day.