• Jumuta@sh.itjust.works
    link
    fedilink
    arrow-up
    23
    arrow-down
    1
    ·
    edit-2
    1 year ago

    I really hate the harsh colouring of the terminals in both RpiOS and windows, it makes them look so unwelcoming and dangerous, especially for beginners.

    I much prefer the colours on the KDE and GNOME terminals and wish more OSes implement them

  • apprehensively_human@lemmy.ca
    link
    fedilink
    English
    arrow-up
    17
    ·
    edit-2
    1 year ago

    Without thinking or reading to the last paragraph of this article, I went and started a dist-upgrade on my pi.

    Curious now to see if it still boots after it’s finished.

    Edit: Oops

    ~ » ssh pihole@172.16.0.1
    Last login: Wed Oct 11 09:38:31 2023 from 172.16.0.96
    compdump:print:36: write error: no space left on device
    compdump:print:42: write error: no space left on device
    compdump:print:44: write error: no space left on device
    compdump:44: write error: no space left on device
    compdump:print:44: write error: no space left on device
    compdump:44: write error: no space left on device

    • Rob Bos@lemmy.ca
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      1 year ago

      One thing Debian introduced recently: apt upgrade --without-new-pkgs and they recommend that before a full dist-upgrade. I think it’s made a pretty big difference in the upgrade smoothness, eliminating some possibly-breaking package upgrades.

      edit: I say recently but I mean new-to-me

    • Rob Bos@lemmy.ca
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 year ago

      I haven’t tried this, but maybe ssh -t "rm /var/cache/apt/archives/*deb" or something like to clear up some space would work.

    • Engywuck@lemm.ee
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      1 year ago

      I have plenty of space, as the OS boots from a 256 GB SSD and a very minimal install. I may try to dist-upgrade after a backup.

      • Engywuck@lemm.ee
        link
        fedilink
        arrow-up
        1
        arrow-down
        3
        ·
        1 year ago

        As a followup, I just changed the repos and did the apt full upgrade. Everything works beautifully. But as I said, I had a very minimal headless install without any DE.

  • Engywuck@lemm.ee
    link
    fedilink
    arrow-up
    14
    arrow-down
    2
    ·
    edit-2
    1 year ago

    Ah, shit… The only way to update is to reimage/reinstall… It’ll take a couple of days for me.

    • neo [he/him]@hexbear.net
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 year ago

      I don’t get it. You could have probably maintained a Debian Sarge install and upgraded it all the way through to Bookworm. I’m kind of surprised they don’t provide an upgrade path in place for Raspian when Debian can manage it.

      • Yer Ma@lemm.ee
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        “This time, because the changes to the underlying architecture are so significant, we are not suggesting any procedure for upgrading a Bullseye image to Bookworm; any attempt to do this will almost certainly end up with a non-booting desktop and data loss. The only way to get Bookworm is either to create an SD card using Raspberry Pi Imager, or to download and flash a Bookworm image from here with your tool of choice.”

        • craigevil@lemmy.ml
          link
          fedilink
          arrow-up
          6
          ·
          1 year ago

          that is the same bs rpios says with every release. most likely they just don’t want the forum with a bunch of people having ods issues.

          I installed rpios on my pi400 three yrs ago then changed the Debian repos to Sid and updated. Been doing apt upgrade ever since with no problems.

        • everett@lemmy.ml
          link
          fedilink
          arrow-up
          5
          ·
          1 year ago

          It would be great if they provided more details. Are the issues specific to desktop usage? And to work around it, is it enough to start with a fresh home directory?

  • tankplanker@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    I did an in place upgrade to testing about a month ago on my PIs after running Bookworm on x86 VMs since it came out. Worked fine for me but my usage is pretty light compared to some as they are headless servers for me and I can rebuild really quickly if I had needed to from backups.

    Today I had a shed load of updates per PI, about 160 packages so I guessed it had gone live.

  • HughJanus@lemmy.ml
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    1 year ago

    Why would they change the name instead of the version number? 🤦‍♂️

    • floofloof@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      1 year ago

      Based on Debian. I’m a bit confused though because I’ve been running a Bookworm-based version of the Raspberry Pi OS for some time (I switched from Bullseye maybe a year ago) because I thought that was the current version. Is this a second Bookworm-based release, or did I inadvertently jump the gun and run something that was pre-release until now? The Pis did receive some kind of big distribution upgrade this week, but it was from Bookworm to Bookworm.

      • Heratiki@lemmy.ml
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 year ago

        Yeah this is some bonkers mental leaps people are making. It’s not like RPiOS is telling Microsoft anything you’re doing. It’s out there for installing and maintaining Visual Code much more easily.

    • sederx@programming.dev
      link
      fedilink
      arrow-up
      6
      arrow-down
      15
      ·
      1 year ago

      Not sure why people downvoted this. It’s true and it’s fucked up.

      Luckily I never used their os.