- cross-posted to:
- iot@lemmy.sdf.org
- technews@radiation.party
- hackernews@derp.foo
- cross-posted to:
- iot@lemmy.sdf.org
- technews@radiation.party
- hackernews@derp.foo
You must log in or register to comment.
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
I totally support adopting KDE as RPi default DE
KDE is nice, but it’s also a massive beast not very well suited to low power SBCs.
I think the Pi 4 and Pi 5 could run it pretty well. Definitely would recommend it for older Pi models though.
Plasma is one of the lowest resource utilization DEs available. Has been for years now. I get tired of hearing this from people that last used KDE at like version 4.
RPis are really low spec though, I tried to run GNOME on my 3b+ and it was so laggy
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 deviceOne thing Debian introduced recently:
apt upgrade --without-new-pkgsand 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
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.This worked! I’ve got it running on a 4gb SD card so it’s no wonder it ballooned, but once I got apt cleaned up it’s now humming along at 83% usage.
Oh, yay! I’m a helper \o/
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.
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.
Ah, shit… The only way to update is to reimage/reinstall… It’ll take a couple of days for me.
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.
“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.”
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.
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?
I did this and everything seems to work:
https://9to5linux.com/how-to-upgrade-raspberry-pi-os-to-debian-bookworm-from-bullseye
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.
Are all of the remaining LXDE programs going to be using XWayland? Or have they been ported by now?
Why would they change the name instead of the version number? 🤦♂️
Is that a name colission or is it based on Debian?
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.
I read recently that RPiOS has a Micro$oft key pre-installed (so that your RPi phones home to Microsoft)… It totally puts me off what is an excellent lightweight OS.
https://www.reddit.com/r/linux/comments/lbu0t1/microsoft_repo_installed_on_all_raspberry_pis/
That’s just an apt repository(with a signing key)…
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.
Not sure why people downvoted this. It’s true and it’s fucked up.
Luckily I never used their os.
