And that’s exactly why it’s called Krita. Also it was previously called ‘Krayon’, so they just kind of kept the name.

This, in turn, is different from APT, which is not Debian’s repository, but Debian’s package manager. So, technically, I could write “sudo apt install (anything)” to get any piece of software from Debian’s repository indeed, but I could also use that command to get software from somewhere else also in the form of a Deb package but which would not have come from Debian itself.

With apt (and discover which uses apt/dpkg at the background) you can install anything from repositories configured on your system. So, if you want to use apt to install packages not built by Debian team you’ll need to add those repositories in your system, so they don’t just appear out of nothing.

Some software vendors offers .deb packages you can install which then add their own repository on your system and then you can ‘apt install’ their product just like you would on native Debian software and the same upgrade process which keeps your system up to date will include that ‘3rd party’ software as well. Also some offer instructions on how to add their repository manually, but with a downloaded .deb it might be a bit easier to add repository without really paying attention to it.

Spotify is one of the big vendors who have their own repository for Debian and Ubuntu and with Ubuntu there’s “ppa” repositories, which are basically just random individuals offering their packages for everyone to use and they are generally not going trough the same scrutiny than official repositories.

Also apparently really high in protein compared to human food.

Pretty much all ‘major’ distributions (Debian, Ubuntu, Mint, Fedora, openSuse…) have 20+ years on their belt and none of those are not likely to go away any time soon. Some niche variants of those might vanish, but the main distributions will be there.

You are on the right track. Installing Debian packages don’t require password to access shared libraries but to write into system wide directories. That way you don’t need to install every software separately for every user. Flatpacks are ‘self sufficient’ packages and thus often way bigger, since they don’t generally share resources.

From security point of view there’s not much difference in every day use for average user. Sandboxed flatpacks can be more secure in a sense that if you harden your system properly they have limited access to the underlying system, but they can be equally unsafe if you just pull random software from a shady website and run it without any precautions.

Flatpacks tend to have more recent versions of the software as they can ‘skip’ the official build chain and they don’t need to worry about system wide libraries. Tradeoff is that the installations are bigger and as flatpacks run on their own little sandbox you may need to tinker with flatpack environment to get access to files or devices. Also if you install flatpacks only for your user and you have multi-user setup other users of the machine can’t access your software, which might be exactly what you want, depends on your use case.

Personally I stick with good old Debian packaging whenever possible, I don’t see benefits of containers like flatpack on my own workstation. Newer software releases or using software not included in official repository are pretty much the only exceptions when flatpacks make more sense to me.

But there’s a ton of nuances on this, so someone might disagree with me and have perfectly valid resons to do so, but for me, on my personal computer, flatpacks just don’t offer much.

Wikipedia has a decent history lesson on Fedora. It’s not just sponsored by Red Hat, it practically replaced the open version of RHEL, so it’s pretty tightly tied to the Red Hat company. CentOS was a bit similar case, which is now discontinued and functionally replaced by AlmaLinux.

Red Hat has already a lot of control over the project, but if they decided to do something stupid with it, something else would take Fedoras place pretty quickly, so I don’t see any ‘corporate threat’ to Fedora nor Linux community in general. That’s the way things have been for a long time and Red Hat has contributed quite a lot to the Linux development over the years which we all can enjoy.

Fedora might get obsolete in the future, maybe because of changes in Red Hat or maybe for some other reason. New distributions raise and others pan out for multiple reasons. Mandrake (or later Mandriva) was somewhat popular at the time, but it’s now dead. Damn Small Linux had it’s userbase for a while, but it’s also now dead, like a handful of other somewhat decent sized projects.

It’s not monitored for security patches as it gets all the latest stuff anyways pretty quickly, security patches (and new vulnerabilities) included. It’s just not meant to be hardened nor rock solid as it’s excactly what it claims to be: development branch of the whole project. That doesn’t mean it’s insecure by default, it just works differently from stable releases where security patches are provided for years after official release.

Our previous president son is on the files. There was a news article where he explained that Epstein had contacted him for fundraising or some other legal thing and they met somewhere once for a short while but that’s all. There was also other finns, like one young woman who applied for an assistant job on some of his businesses but didn’t get hired.

So, while there’s a crapload of people who should be convicted and thrown in a jail there’s also a ton of people who don’t have anything to do with pedo-ring or anything else. Good to keep in mind that having someones name on the files alone doesn’t mean too much.

And just to avoid any confusion, if you are mentioned in the files more than Jesus is mentioned on the bible it’s not an accident or one time thing. Allegedly that applies at least to Trump and there should be a small and dark cell somewhere ready.

Run the command and it all dies.

And all of your data on that machine is gone as well.

What errors excactly? Copy and paste what you’re getting from your terminal. Also post output of ‘df -h’.

What kind of errors you’re getting? First what you can try is to run ‘dpkg --configure -a’. If that doesnt help we need more information on what’s going on.

It wasn’t for nothing, you got some learning out of the experience and a story to tell. Good luck with the new system, maybe hold upgrading that to testing for a while, there’s plenty to break and fix even without extra quirks from non-stable distribution :)

Have fun and feel free to ask for help again, I and others will be around to share what we’ve learned on our journeys.

There’s a walkman model which is pretty much just that which runs some flavour of android but I don’t know who they think their customer base is as the pricing is absolutely stupid. Top of the line model has gold plating and a nice 4k price tag. Also it apparently has ‘oxygen free copper’ and other audiophile bullshit, but no FM tuner.

And then there’s a ton of similar products from China but no idea which models (if any) are actually useful.

Rootfs location is passed via kernel parameter, for example my grub.cfg has “set root=‘hd4,msdos1’”. That’s used by kernel and initramfs to locate the root filesystem and once ‘actual’ init process starts it already has access to rootfs and thus access to fstab. Initramfs update doesn’t affect on this case, however verifying kernel boot parameters might be a good idea.

Just in case you end up with reinstallation, I’d suggest using stable release for installation. Then, if you want, you can upgrade that to testing (and have all the fun that comes with it) pretty easily. But if you want something more like rolling release, Debian testing isn’t really it as it updates in cycles just like the stable releases, it just has a bit newer (and potentially broken) versions until the current testing is frozen and eventually released as new stable and the cycle starts again. Sid (unstable) version is more like a rolling release, but that comes even more fun quirks than testing.

I’ve used all (stable/testing/unstable) as a daily driver at some point but today I don’t care about rolling releases nor bleeding edge versions of packages, I don’t have time nor interest anymore to tinker with my computers just for the sake of it. Things just need to work and stay out of my way and thus I’m running either Debian stable or Mint Debian edition. My gaming rig has Bazzite on it and it’s been fine so far but it’s pretty fresh installation so I can’t really tell how it works in the long run.

I’d argue that if the plan is to run Debian testing it’s at the very least beneficial, if not mandatory, to learn some basics of the terminal. Debian doesn’t ship with sudo by default, so it’s either logging in directly as root or ‘su’. Instead of vim (which I’d personally use) I’d suggest nano, but with live setup it’s also possible to use mousepad or whatever gui editor happens to be available.

I suppose it’d be possible to use gparted or something to dig up the same information over GUI but I don’t have debian testing (nor any other live distro) at hand to see what’s available on it. I’m pretty sure at least stable debian installs with UUIDs by default, but I haven’t used installer from testing in a “while” so it might be different.

The way I’d try to solve this kind of problem would be to manually mount stuff from busybox and start bash from there to get “normal” environment running and then fix fstab, but it’s not the most beginner friendly way and requires some prior knowledge.

Do you happen to have any USB (or other) drives attached? Optical drive maybe? In the first text block kernel suggests it found ‘sdc’ device which, assuming you only have ssd and hdd plugged in and you haven’t used other drives in the system, should not exist. It’s likely your fstab is broken somehow, maybe a bug in daily image, but hard to tell for sure. Other possibility is that you still have remnants of Mint on EFI/whatever and it’s causing issues, but assuming you wiped the drives during installation that’s unlikely.

Busybox is pretty limited, so it might be better to start the system with a live-image on a USB and verify your /etc/fstab -file. It should look something like this (yours will have more lines, this is from a single-drive, single-partition host in my garage):

# / was on /dev/sda1 during installation
UUID=e93ec6c1-8326-470a-956c-468565c35af9 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=19f7f728-962f-413c-a637-2929450fbb09 none            swap    sw              0       0

If your fstab has things like /dev/sda1 instead of UUID it’s fine, but those entries are likely pointing to wrong devices. My current drive is /dev/sde instead of comments on fstab mentioning /dev/sda. With the live-image running you can get all the drives from the system running ‘lsblk’ and from there (or running ‘fdisk -l /dev/sdX’ as root, replace sdX with actual device) you can find out which partition should be mounted to what. Then run ‘blkid /dev/sdXN’ (again, replace sdXN with sda1 or whatever you have) and you’ll get UUID of that partition. Then edit fstab accordingly and reboot.

I don’t really follow what’s going on between different distributions as Debian has been my workhorse for decades, but a few weeks ago out of curiosity I threw bazzite on a desktop which was left ower due to work changes and that hardware is now just for gaming. Installation was pretty much just next-next-next and it after boot there was a steam login window ready to go. Every game in my library so far has been just as flawless experience than with windows, if not even better. I don’t have any the new AAA-titles and I’m not a fan of any online-multiplayers, so YMMV. For Epic I installed Heroic-launcher and (atleast games I’ve tested so far) everything works.

~/autoclean and a cron job to delete everything older than 7+ days from there. I can just download whatever, throw it in a special folder and it’s gone after few days. Keeps my ~/Downloads a bit more clean, easy to store temp txt files to keep track of what I currently have on hand and so on.

It’s kinda-sorta social problem, but originally not the way you intend. It used to be possible to self host XMPP and chat with people regardless of the platform since both Google and Facebook (it wasn’t Meta at the time) adopted the protocol. But then they changed their policy and created the walled gardens they have now and thus it’s a social and/or political problem.

They fully followed the playbook of Embrace-Extend-Extinguish which eleijeep@piefed.social mentioned few messages up the thread and pretty much devastated XMPP out of existence. Sure, there’s still handful of users and project itself isn’t dead, but before their policy change I saw quite a lot of servers around which are now either dead or forgotten.

On a previous comment I didn’t mean to describe that as a technological problem but a problem related to big corporations embracing FOSS projects/protocols and killing them by introducing their own walled garden variant of it.