[–] 2 points 1 week ago

I think what I would have expected in this situation would have been for the upgrade to have prompted me to read the changelog before starting, and I would have expected the changelog to describe in detail what was going to be broken and what the steps would be to fix it.

THIS UPGRADE CONTAINS BREAKING CHANGES. YOU ARE STRONGLY RECOMMENDED TO READ THE CHANGELOG BEFORE PROCEEDING. [Y/n]
  • source
  • parent
  • context
  • [+] -14 points 1 week ago (2 children)

    Yeah nice I could run Half-Life on my MacOS... Why would any sane person, wake up in the morning and say: "Hey I'm going to dev a proton alternative but for MAC? Why, what?...

    Just let that horrible ecosystem die and suffocate in their own horrible closed source shit. If they want to play half-life (or any game) on their MacOS they should pay 99,89 $ a month ! Or run their ressource hogging VM (which you also need to pay for) and install windows 🤯🤯

    I guess masochist live in different forms with different kinks...

  • source
  • [–] 9 points 1 week ago*

    It arrived at the right time with the right promises.

    It came up during the SteamOS craze where a lot of people were looking to switch over to Linux, but wanted something easy.

    • SteamOS was not yet released for anything but the Steam Deck
    • It has an easy installer and good GUI tooling
    • It comes with KDE & gaming optimizations, so it's easy to use for people coming from Windows with no fiddling
    • It's not immutable, so you can actually use your PC for anything, not just gaming
    • It has an Arch base and still uses arch repos (apart from their own custom packages), so it's also familiar to people already using Linux

    Unlike other distros, it doesn't have anti-features, and doesn't sacrifice anything for the sake of ease-of-use, while providing a very smooth experience (and welcoming to people who never used Linux).

    And it came out at the perfect time - it wasn't an old thing you had to persuade people was "good all along"; it's a purpose-built distro made to answer the specific use case people were seeking when leaving Windows, at the exact time articles & youtube videos were hammering on Windows & Linux gaming was a huge topic of discussion.

  • source
  • parent
  • context
  • [–] 8 points 1 week ago

    They don't support really old hardware which enables to ship better optimized packages by default and other performance boosts at expense of non-gamers. I have noticed multiple times that a package I wanted was not available in classic arch repos but was in Cachy's. As far as I know it's not that different from EndeavourOS (not that I've tried it). To me it really just seems like a distro that suits ME, a bit lazy tech savvy gamer, the best and there is not any visible dirt.

  • source
  • parent
  • context
  • [–] 7 points 1 week ago

    I was on arch, had a hardware failure, reinstalled my OS as troubleshoot, but went with Cachy. I use it exactly like Arch, except for the updater which is a pacman + flatpak manager (it just runs the CLI commands sequentially)

    Honestly it feels more like an arch with tweaks than a full on independent distro. It still uses pacman & arch repos, has the AUR available etc; they have additional repos & custom packages (like the kernel), but for the end user it's about the same.

    If someone didn't know anything about Linux but wanted to switch over to it, I'd recommend Cachy just because it's easy to install & properly sets up the OS for high performance without needing to fiddle with it. Also it has GUI update tools (I just use their CLI version instead) which may look more inviting to people scared of the terminal

  • source
  • parent
  • context
  • That's still useful information. I use the Linux Command Library from FDroid. It is really good for seeing similar commands, variations, one liner examples, cheat sheets for Vim/Emacs, etc.

    I can recommend that for others like me who have trouble with commands.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago

    I moved over from Arch to CachyOS when my OS SSD started to fail SMART tests. So far this is what I've liked about Cachy: Very easy to use installer. Really nice btrfs snapshot system by default. Optimized kernels and packages repos, compiled with modern CPU instructions (not that much of a difference in real use, but still a nice to have). Its Steam Proton fork (Cachy-Proton) has a lot of niceties too for FSR and stuff (Although I barely use that so I stick with GE-Proton). Its just a smooth arch experience with sane defaults. Of course, I ended up tweaking some things. I switched from the fish shell to zsh with my reliable plugins. I don't use Shelly, Its GUI package manager, so it's just kind of there. It really is like endeavour OS with the gaming aspect turned to eleven, and I'm very happy with it.

  • source
  • parent
  • context
  • [–] 7 points 1 week ago* (last edited 6 days ago)

    It is possible, but it is not a wayland limitation per-say but a compositor one (aka the wayland server), and I say "limitation" if the compositor doesn't have multi-display option.

    Technically wayland is not the issue:

    If you look at your /run/user/[uid] (uid is probably 1000) you will see the wayland "displays" (socket here), usually named wayland-X. The /run[...] is usually set from $XDG_RUNTIME_DIR while the wayland socket to be used is set in the environment variable $WAYLAND_DISPLAY. So running an application in a 2nd session would just require setting the $WAYLAND_DISPLAY to an other value (that exists).

    It seems that Sway is able to do this with the output command.

  • source
  • [–] 9 points 1 week ago* (3 children)

    Crontabs can live in different places on different systems, but generally when you run crontab -e you're editing the crontab of the current user, which is generally placed in /var/spool/cron/{username}. If you do sudo crontab -e that edits the crontab/file for root. There can be other files nested in /etc/cron.d, /etc/cron.hourly, /etc/cron.daily et cetera as well.

    To find out where those old cronjobs are still defined, you can recursive grep the name of that unique log file you mentioned (if the log file is part of the command in the crontab). grep -r "{unique log file name}" /etc and /var/spool should find it. If the log file name isn't in the command, grep for some other unique string from that cronjob that would stand out amidst everything else in /etc.

    To add timestamps to log output, you can pipe it through ts.

  • source
  • [–] 2 points 1 week ago

    I've been looking into ways to do funky things with graphical sessions and am considering switching to a setup based on GNOME Remote Desktop and headless mode to have multiple sessions at the same time (although that differs from what OP is looking for)

  • source
  • parent
  • context
  • [–] [S] 4 points 1 week ago (1 child)

    Sorry for the inconvenience. I'd like to explain a bit:

    Vanilla OS is based on the rolling-release Debian sid, which lets us bring newer features and better hardware support. But that also means some libraries will inevitably be deprecated over time. That's why we always recommend Flatpak as the first option for installing apps.

    Regarding the Augest update: that was a major release (Vanilla OS 3 Reunion), and we did everything we could to minimize the migration impact for existing users. The subsystem change is one of the breaking changes we couldn't avoid. The underlying Distrobox v1 is no longer receiving updates and had already been causing quite a few compatibility issues, so we had to move to Distrobox v2. Unfortunately, v2 introduces breaking changes in exporting bins and apps, which meant the containers had to be recreated. We fully understand the impact this has on our users, but this migration is necessary to ensure stability over the next few years.

    We really appreciate your feedback, and we remain committed to improving reliability in the future, in line with our original vision of providing an obstruction-free Linux experience for people around the world.

  • source
  • parent
  • context
  • view more: ‹ prev next ›