Linux printing is very complex. Before Foomatic came along you got to experience it in all it's glory and setting up a working printing chain was a pain. The Foomatic Wikipedia page has a diagram that will make your head spin.
If you end up with resizing /var as the only solution, please post your partition layout first and ask, don't rush into it. A screenshot from an app like Disk Manager or Gparted should do it, and we'll explain the steps and the risks.
When you're ready to resize, you MUST use a bootable stick, not resize from inside the running system. You have to make a stick using something like Ventoy, and drop the ISO for the live version of GParted on the stick, then boot with it and pick the Gparted live. You'll have to write down the instructions and be careful what you do, and also hope that there's no power outage during.
The safest method, if your /home has enough space, is to use it instead of /var for (some) Flatpak installs. You can force any Flatpak install to go to /home by adding --user to the command.
If you look at the output of flatpak list it will tell you which package is installed in user home dir and which in system (/var). You can also show the size of each package with flatpak list --columns=name,application,version,size,installation.
I don't think you can move installed apps directly between system/user like Steam can (Flatpak is REALLY overdue for a good package manager) but you can uninstall apps from system, then run flatpak remove--unused, then install them again with --user.
Please note that apps installed with --user are only seen by the user that installed them. Also you'll have to cleanup separately for system and user(s) in the future (flatpak remove--unused for system, then flatpak remove --unused--user for each user).
Try using an addon like Basic Automatic Tabs Unloader, it will kill tabs completely a while after they've been closed. You can set the grace period as low as you want.
The Firefox native tab unloader is extremely permissive and only kills tabs when the whole system starts running low on RAM.
Looking through the packages available for OpenWRT I would suggest Tcl, Lua, Erlang or Scheme (the latter is available through the Chicken interpreter). Try them out, see what you like.
Repology artificially reduces the number of packages instead of reporting the actual number. Which I find highly dubious because most packages have a purpose. In particular for repositories like the AUR artificially eliminating packages goes against everything it stands for. Yes it's supposed to have alternative versions of something, that's the whole point.
If there wasn't for this the ranking would be very different. Debian for example maintains over 200k packages in unstable.
Login with biometrics. Wants password and 2fa each time. As it should, but it gets tedious, especially when I want to confirm online payments (which need to be confirmed inside the interface after you login).
No contactless payments. You can enroll a card into Google Pay but fuck Google, I don't want them seeing what I buy.
No notifications, hope the bank is willing to send SMS instead.
Bit more tedious to send money to someone because the website can't look up contacts by name, have to look them up separately and copy the phone number over.
It's not that the ad issue isn't going to be solved, it's that ads are here now and we have to deal with them.
They are going to be replaced by direct micro-payments eventually but the puzzle pieces have been slow to get into place (also Google and the whole ad industry haven't been cooperating for obvious reasons).
One of the major hurdles was the [in]ability to make online payments of a fraction of a cent but the digital Euro aims to make that possible (among other things).
With that and support for direct micropayments implemented in the browser we'll be able to give a web page owner that fraction of a cent they get from ads now but only IF we want to, and when we do that we cut out all the ad industry as middlemen.
The graduation from Linux from Scratch is to be able to make your own mini-distro. I reckon anybody who gets that far is above petty feuds about the install process or packaging in this or that distro.
It does need regular maintenance, as highlighted in every single stable update announcement.
If you're talking about "Known issues and workarounds" those aren't caused by Manjaro, they're issues that crop up with various packages. The forum attempts to crowdsource fixes as part of Manjaro's mission to make it easier on its users.
It's a great resource and it can be used by people on any Arch-related distro (and potentially other distros as well). I wish more distros would do this.
It is absolutely not stable (as in Debian Stable or RHEL or SLES stable) as things are moving quickly.
Well it's still a rolling distro with Arch heritage. It's as stable as you can make Arch. Which is quite stable in the sense that a Manjaro install won't stop working out of the blue (I can attest to that personally, going on the 5th year as a daily driver). And they've gone and added Timeshift snapshots as default so if you mess something up you can simply restore a snapshot, which takes care of user-related tinkering as well.
Okay, almost-semi-regular then.
Not sure I understand your point about the updates (or the "almost-semi" thing). What does it matter if updates come after 13 or 17 days? Is it important to you to be exactly 14 or what?
AUR creators, on the other hand, are overwhelmingly Arch users who builds their scripts targeting an up-to-date Arch system.
10% of AUR packages are abandoned. Another 20% have never been updated after the initial release. Only 35% have been updated within the last year.
Anyway, it doesn't matter. AUR "packages" are recipes that either compile packages from source or download binary releases. Both methods are very resilient and don't care about delays of a couple of weeks.
While you can in theory run into an AUR package that was just updated to require something that was just added to Arch the chances are extremely small. It's hardly a common problem.
Wow, basically everything you wrote about Manjaro was wrong:
It doesn't need constant maintenance, and it doesn't break. The whole point of it is to be a stable variation of Arch.
It doesn't have a highly irregular update schedule, it's quite regular — every two weeks. There are also updates for outstanding security issues which can come faster (as needed). Occasionally very large updates can take longer in order to weed out all the issues, such as the recent example with Plasma 6 — those are announced in advance.
AUR doesn't "expect" anything, it's a dumping ground where anybody can put anything. I successfully run about 100 AUR packages on Manjaro without any issues, but nobody can guarantee anything when it comes to AUR. It's officially unsupported on Arch and every Arch-based distro. If you want to call it dangerous that's fine (if a bit hyperbolic) but don't blame that on Manjaro, it just shows that you don't understand how AUR works.
·1 month ago
·3 months ago
Linux printing is very complex. Before Foomatic came along you got to experience it in all it's glory and setting up a working printing chain was a pain. The Foomatic Wikipedia page has a diagram that will make your head spin.