It doesn’t have anything to do with the distro. With that many files, you’re torturing the hell out of your disks, and your machine’s memory. Depending on how the code is written, it depends on if this is a filesystem scan of the folders that are then imported to a local db which is looked up to go back and find the found files, or a simple approach which is to just scan the directory every time you go to open something.
I’d really think about properly organizing your files. If that’s not an option, you can dig into the settings or code and find the hard limits set (probably for a good reason) on the number of files being scanned or imported.
I’d imagine mpd with one of many frontends would work well enough. You’d just need to use a dummy music library directory with symlinks to your four music storages for mpd to pick up and catalog everything.
I’m not sure what a “music jukebox” is, and how it’s different from a music player, but I would recommend to try mpd. It should work with your collection, although I don’t have personal experience with collections of this size. Some clients might also not have been designed to work with such collections, so probably you’d have to try several.
I’m not sure what a “music jukebox” is, and how it’s different from a music player, but I would recommend to try mpd.
A jukebox lets several people add a song to the playlist and yes, mpd is a solution for that where every event attendant could install a client on their phone.
I think the onboarding and new user experience for Mint could be better, but I think there’s one important thing that I think makes Mint a good intro distro: Its Ubuntu base.
If you look up guides for “linux” it usually gives instructions for Ubuntu, which usually also apply to Mint. Likewise, if you look for software downloads you tend to find Ubuntu debs.
I know flatpak fixes these issues to an extent, but I think we’re not there yet.
some of those ubuntu instructions that come up jn search results are from as far back as the mail order ubuntu cd era and installing debs directly is a slippery slope
Echoing the other sentiments, it’s probably a good idea to hunt down why your system is having trouble because distro hopping might not fix it.
That being said I’ve recently been using bazzite and it’s been relatively smooth. You just have to learn a couple (easy) ways to do package management a little differently.
I’m not the one you posed your question towards, but it’s related to Bazzite’s relation to Fedora Atomic and uBlue.
To put it simply, dnf is the ‘source of truth’ when it comes to package management (i.e. finding, installing, updating, removing (etc) of packages) on (traditional/regular) Fedora. So, dnf is basically to Fedora what apt used to be to Ubuntu. Sure, you can use Flatpak or any other (additional) package manager. But, there’s no need to unless the software you seek is not available for installation through dnf.
Bazzite, on the other hand, does not allow you to install any packages through dnf. Instead, rpm-ostree, flatpak, Toolbx/Distrobox and (exclusive to uBlue projects) brew (and ujust) are provided by default. But, you might have to learn when you’d have to use which and why.
To educate yourself on this, you should definitely consider reading up on the related entry within Bazzite’s documentation. In general, there’s a lot of very useful stuff in Bazzite’s documentation. Therefore, if you intend to use Bazzite, you should definitely read through its documentation.
Ah gotcha okay. Probably explains why sudo dnf update/upgrade wasn’t quite doing what I expected in my Bazzite install. Force of habit since I’ve used Fedora and Debian based systems in the past.
Strawberry or Clementine. I mean 100K entries in a database is nothing. Even for SQLite. You can add multiple library locations, this is no problem.
You probably want Strawberry as it is newer and maintained, but I still like Clementine for the extra features that Strawberry doesn’t have yet. For you probably, not a big deal - things like podcast support, cloud support etc.
You said the bad word that hipster Linux boi’s don’t like. I rarely have trouble our of Ubuntu. I’ve slowly eliminated most of the snaps. But its not cool for it to work. It has to be hyped. This is what they can’t stand.
Stable is not equivalent to “works well”. It is randomly frozen at some point, mostly not in contact with upstream devs, so you just have outdated packages.
OpenSUSE slowroll sounds like a way better model. Or maybe CentOS stream.
But it’s not randomly frozen, it’s tied to Ubuntu’s LTS builds. And they didn’t say “stable” is the same as “works well”, they said Mint is both (which is true from my experience at least)
If you need newer packages with Mint, Flatpak is a good way to go (yes it has its own issues, but they do work well for a lot of people)
It is randomly frozen as not all developers follow Ubuntus release schedule. They just release when it is ready.
Stability means backporting tons of bugfixes to tons of small packages and libraries. I dont think Ubuntu does that for enough packages, best example Plasma 5.27 on Kubuntu. I have reported over 200 bugs I guess and most of the newer ones are just fixed in Plasma 6.
Flatpak for sure is a good way, and if a distro is stable, they should only install Flatpaks.
It is not randomly frozen as Mint does follow Ubuntu’s LTS releases, every new version they put out is based on whatever the current Ubuntu LTS is. Their release cadence isn’t linked that closely as a new LTS usually takes a few months to spawn a new Mint release based on it, but they aren’t just freezing some arbitrary point in time of development.
If you mean Ubuntu is randomly frozen, it isn’t either. It follows a release schedule, determines a roadmap, and at a certain predetermined point in developing a new release, they do freeze for new versions so they can complete testing and ensure everything works together in time to release on schedule. It’s certainly not “random”.
And that’s also not what stability means. Stability means functionality doesn’t change, so an up to date Mint 21.3 installed on release is going to be the same as one installed and updated now, functionally speaking. This is accomplished by only backporting important security patches and bug fixes to the version of the software that’s used by the system rather than getting it with new versions where there are new features and changes to existing functionality that can break things based on the previous version. This does not mean it gets all fixes, just the ones they deem worth the effort of backporting.
Yes I think you mentioned the relevant points here. Ubuntu tests their preinstalled software, while there is tons more in the repos that is not as tested. Same with Mint.
And they backport only stuff they think is necessary. For example Plasma 5 is based on the EOL Qt5 and backporting things to Plasma 5 is nearly impossible as you need real Plasma devs and nobody really wants to do that.
Plasma 6 is really stable, 6.1 not so much, but the timing was not perfect. Simply because they do their release schedule as fixed as that.
It is a total pain if you simply want working software, as they may backport some stuff, but all the stuff not preinstalled, or that is very complex, will not get fixes.
This is the same with all stable distros, if the maintainers dont literally maintain all the software there is.
I mean, that’s definitely a downside to long term stable distros. So, basically, the choice is between that and a rolling release which has the downside of the possibility of things breaking on update and never really having an easily reproducible build
I’m sure talking about the 30days challenge from Raid Owl and I have an idea of his conclusion. First he’s a power user (not in the fact of tweaking and scratch in the file system), he needs a lot of stuff to work. And for someone outside of the traditional office work or maybe developing, Linux is hard to use for graphics works, so sure Linux Mint is not for this kind of people but you should always recommended it to “normal” people and beginner in Linux. Sure in this case his conclusion is wrong, he should have used Fedora, Arch or OpenSUSE, but that’s it.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.