• 0 Posts
  • 327 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle



  • I installed endeavouros on my windows laptop.
    The installer guided me through the partitioning, setting up systemd-boot, and it was all great.
    I had to disable bitlocker in windows (not that bothered about) and secure boot in bios (also not that bothered about).

    Ran smoothly dual booting both for about 4 months.
    Then a windows update hit, and fucked the boot.

    Thankfully, this is a common enough thing that there are plenty of tutorials out there.
    A liveUSB of endeavouros, some tinkering, and I was back up and running.

    The cause seems to be FastBoot, where windows keeps the boot partition mounted. What I think happens is that bios tries to read the boot partition, which is configured/loaded for windows (because it never cleaned up after itself due to FastBoot being on) and boots into windows.
    Since turning off FastBoot, I haven’t had any issues in the past 8 months.




  • https://store.steampowered.com/steamos

    Does this mean I can install SteamOS on any device? We expect most SteamOS users to get SteamOS preinstalled on a Steam Deck or device that incorporates SteamOS. The only devices officially supported on SteamOS right now are Steam Deck and Legion Go S. We are working on broadening support, and with the recent updates to Steam and SteamOS, compatibility with other AMD powered PC handhelds has been improved.

    If you are interested in installing SteamOS on your device and providing feedback, you can follow the instructions here.

    here links to https://help.steampowered.com/en/faqs/view/65B4-2AA3-5F37-4227

    With instructions to install steamos and the note:

    Currently, the only devices officially ‘Powered by SteamOS’ are Steam Deck and Legion Go S. We are working on broadening support, and with the recent updates to Steam and SteamOS 3.7, compatibility with other AMD powered PC handhelds has been improved.

    So, it’s unlikely to be smooth sailing. But it can be done, and steam is working on improving it.

    There seems to be some forks out there that claim to improve desktop installation, but I have no idea how active or decent they are.


    Personally, I think steam is missing a huge market slice by not creating a steamos for desktops.
    However, they don’t need it and probably don’t want it. It’s a market slice in a market they don’t need or want: operating systems.
    People that would use it likely already have steam on windows. So, it’s not bringing in new customers (like the steam deck does).
    People that game on Linux likely already use Steam Proton (which is an amazing contribution). So, no new customers by distributing a whole desktop OS.
    It’s starting a fight with Microsoft (which I think we all want), but with no real benefit to Steam.

    I think steam is smart to stay in their lane of handheld OS and Linux tooling for gaming.
    Let the desktop gaming distros be maintained by other people. Ideally steam would support those distros, but just maintaining Proton and generally pushing Linux gaming is still a huge contribution.






  • especially once a service does fail or needs any amount of customization.

    A failed service gets killed and restarted. It should then work correctly.
    If it fails to recover after being killed, then it’s not a service that’s fully ready for containerisation.
    So, either build your recovery process to account for this… or fix it so it can recover.
    It’s often why databases are run separately from the service. Databases can recover from this, and the services are stateless - doesn’t matter how many you run or restart.

    As for customisation, if it isn’t exposed via env vars then it can’t be altered.
    If you need something beyond the env vars, then you use that container as a starting point and make your customisation a part of your container build processes via a dockerfile (or equivalent)

    It’s a bit like saying “chisels are great. But as soon as you need to cut a fillet steak, you need to sharpen a side of the chisel instead of the tip of the chisel”.
    It’s using a chisel incorrectly.


  • I would always run proxmox to set up docker VMs.

    I found Talos Linux, which is a dedicated distro for kubernetes. Which aligned with my desire to learn k8s.
    It was great. I ran it as bare-metal on a 3 node cluster. I learned a lot, I got my project complete, everything went fine.
    I will use Talos Linux again.
    However next time, I’m running proxmox with 2 VMs per node - 3 talos control VMs and 3 talos worker VMs.
    I imagine running 6 servers with Talos is the way to go. Running them hyperconverged was a massive pain. Separating control plane and data/worker plane (or whatever it is) makes sense - it’s the way k8s is designed.
    It wasn’t the hardware that had issues, but various workloads. And being able to restart or wipe a control node or a worker node would’ve made things so much easier.

    Also, why wouldn’t I run proxmox?
    Overhead is minimal, get nice overview, get a nice UI, and I get snapshots and backups






  • towerful@programming.devtoProgrammer Humor@programming.devThe future is here
    link
    fedilink
    arrow-up
    26
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Yeh, but you only need 10 vibe code cleaner-uppers per vibe coder.
    And a vibe coder is a 10x developer.
    You just have to mitigate the increased cost of AI API calls.
    It pretty much balances out, with the obvious 20% efficiency boost - which is where everyone makes their money: companies, developers and shovel AI platforms… All 20% efficiency boost. Which directly relates to profit boosts. 20% line goes up!
    Which also pays for the datacenters, the shovels GPUs, the power, the cooling and the water for the cooling. It’s all cheaper, cause AI is at least 20% more productive.

    Even if your vibe-coder-code-fixers turn into vibe-coder-code-vibe-fixers… That’s just another 20% efficiency boost. Basically printing money! Oh, but you need to buy more shovels GPUs. But that’s also a win because shovels GPUs don’t have unions or require holidays. Think of the profits! They work 24/7.
    And all you need are vibe-coder-code-vibe-fixer-code-fixers.

    …As long as your vibe-coder-code-vibe-fixer-code-fixers don’t turn into vibe-coder-code-vibe-fixer-code-vibe-fixers (I’m so lost, I think that’s right).

    Edit: forgot some shovels