Teams actually has Linux builds on the AUR. Obviously they are wrapping the web version, but it does integrate much more nicely with the GUI. I’m running the version that uses your already installed electron. I don’t have to use chrome for teams, which is the real upside for me.

Ssh over Internet is fine as long as it’s properly setup (no password auth, root not allowed, etc.). Obviously a VPN is even better.

I would like to add that I did look at the GitHub before commenting. And I still didn’t get it. Matthew with just explain what it does, but also why is different from the common tools/suggestions that seem similar. Maybe it’s more about highlighting the differences (or the additional capabilities).

Ah now I understand the purpose. I only use it for my (personal) dotfiles, which as a term is ambiguous at best, but in my case I mean config files. That was how I essentially misread your title. Obviously all those files are owned by my user, and most live in ~/.config or similar locations beneath my home directory. Things like application preferences, basically.

Obviously your tool also works for this, but I now understand it’s more meant for system wide config files.

I’m also just using GNU stow into a git repo. It needs no configuration file and just works on any system. Rolling out a new system takes 2 commands. I really don’t see the need for a specialized tool for this use case.

I only have one entry in there, which is for /boot. The others are implicit anyway since I’m using ZFS. The boot entry is needed afaik, as there are multiple efi-type partitions in the system.

If that is necessary depends on your BIOS/MoBo. I did have to on mine. But the effort for a normal CachyOS install is t really like 5 minutes: boot into live iso, enter ‘cachy-chroot’ or whatever the command is, follow instructions on screen. Then just reinstall grub and/or kernel (which regenerates initramfs). There’s a wiki entry and pinned posts in discord for this whole thing. Ask in discord if you get stuck, they are incredibly responsive and helpful.

Once you’ve done it, you’ll notice it’s really no big deal. Btw. “Losing” your Linux install is very hard. It’s not as fragile as Windows. You can bork things, but they can usually be un-borked as well. The only real way is fully deleting partitions or their contents, which you can’t just do accidentally.

Especially just moving it to a new host can’t break it, you just need to get it to boot. Once you know how, it’s like 5 minutes. You can take the drive from a 20 year old PC, pop it into a modern system and it’ll work fine (assuming the system is semi-updated). Windows has a hard time moving to a different MoBo or platform. Linux doesn’t care. Drivers aren’t ‘installed’ like they are in Windows. They are just in the kernel available to be used. Almost everything is detected fresh on every boot, making this incredibly robust. As I said, you might just have to fiddle a bit to get it to boot, once it does, it’ll just work fine.

This is actually not even necessary. The systems are similar enough it’ll just work. I have recently swapped an SSD from a laptop to a newer model with CachyOS, and that was more of a generational jump in terms of cpu and other hardware.

But CachyOS has a quirk. Linux systems specify which partitions are mounted to which directories in the /etc/fstab file. Unfortunately, the boot partition is specified using a device name and not a UUID. this is problematic when switching an SSD from a system to another as this may very well change device names. It did for me and I then had to rescue boot + chroot to fix it.

The fix, if done before, is trivial: edit the line for /boot in that file to start with UUID= (followed by the actual UUID of the partition) instead of with /dev/nvme0n1p1 or whatever the current device name is. Google should be able to tell you how to find the UUID of your boot partition.

Or if you have separated your devices into subnets/VLANs. Which becomes more important as your get more hardware that you don’t really trust.

It’s a misconception that is any “trouble”. I’m using CachyOS, which is basically Arch but with additionally optimized repositories and settings. You just install it an use it, like Mint or Ubuntu. It just works, but it’s also faster for performance related tasks (especially gaming, but also others), importantly and explicitly without any tinkering.

Quite the opposite, actually: there much less tinkering required to get gaming specific things to “just work”, as the tweaks are all there by default. This includes running Windows programs often considered hard to run (through Wine).

I do happen to enjoy and want a rolling release. There’s a new kernel released, and I can install it like a day later. New KDE comes out, update is there for me in a few hours. Software is generally up to date, which was such a refreshing experience as I’m used to running Debian server side. Oh what a contrast.

Tailscale is WireGuard under the hood, if you didn’t know. It’s an overlay network that uses WireGuard to make the actual connections, and has some very clever “stuff” to get the clients actually to connect, even if behind firewalls without needing port forwarding.

Using WireGuard directly basically just changes the app you use, which may or may not help with your issues. But the connecting technology is the exact same.

It’s only light if you configure it to be. It can be as heavy or as light as you want it to be, but it’s a good place to learn and experiment, as it’s comparatively trivial to switch stuff around. Arch wiki is probably the best Linux resource out there.

I’d suggest looking into TeamSpeak, like others have mentioned. Trivial to self host, too.

Edit: to be clear, this would cover the voice call aspect of discord, not the chat channels and other community tools. While it’s can do text chat, it’s more of a side feature rather than core. I didn’t think it does images or video, but it’s been a hot minute.

but you can do everything without it.

yes but why would you? There’s a reason we use GUIs, especially when new to a field (like virtualization).

I know it has been mentioned in passing a few times but I would highly recommend CachyOS. Just to emphasize how good that is.

Avoid Mint.

Many distros have screenshots bound to a shortcut by default. So it’s working by default, just not the default you know. Even Windows only introduced that shortcut a few years ago. The real shortcut (working without any program even in Windows) is the dedicated PrtScr button. If you hold alt, it’ll only capture the current window. It won’t be saved but put in the clipboard.

On KDE Ctrl+shift+s worked by default for me, but I don’t didn’t know if that comes from my distro or from KDE.

I’ve finally swapped over my main personal (gaming) PC 6+ months ago. Should’ve probably done that a lot sooner, but lazy. I knew I wouldn’t upgrade my Win 10 to 11, and didn’t wanna wait until the last minute, but have fallback options and time to distro hop if needed.

I’m not new to Linux at all, as most servers I’m running (personally or in my job) are Linux based. Debian, usually, cause servers. But I haven’t used a Linux desktop in well over 20 years.

My choice fell on CachyOS, as I wanted something pre-configured for performance/gaming/wine, but kinda dislike fedora (rules out Bazzite, Nobara, and actual fedora). Also in the running was PikaOS, but I tried CachyOS first and stuck with it. I had no experience with Arch, but what a brilliant base that turns out to be for me. Love the rolling up-to-date-ness and AUR accessibility. I’m used to having to contort myself to get a more current version of software, possibly compiling from source and screwing with dependencies, but everything is literally just there and up to date. Critically, all games basically just worked. Everything just worked. EXcept all mail programs suck to an unexpected degree, but that is literally my only complaint.

I do use the EoL of win 10 as an opportunity to get people to move over or at least try it out. Depending on their use case, I usually still recommend Mint for non-technical people, mostly because searching for help from a Windows convertee likely finds appropriate solutions. The more technical ones get personalized recommendations, depending on context. For example I do have a colleague who spends half his day complaining about anything Microsoft, but still uses Windows at home, but that is mostly because of a single piece of software (and so far I haven’t been able to get that to run, but haven’t tried very hard yet either).

Not really possible, because how a desktop feels or what can be configured it’s hard to show on a website. Especially how you can visually adapt it. And what you can configure in general. Running it from a live USB takes like 5 minutes.

For example KDE is also very close to Windows, but can also be configured to behave more like a Mac. Visually most desktop environment can be themed. Cinnamon just got additions to be able to theme gnome apps globally I think? If you want to use a central dock like a Mac and have running apps at the top, that’s just a master of setting that up on KDE.

Mine are of course also on a VLan but with no Internet access unless they need it for everyday operation (like a radio, or the amplifier that can play Spotify).

We don’t use the manufacturer apps at all. Everything is integrated into (fully local) home assistant. No need to open a specific app to operate a switch, or a light. Everything in one place. Trivial and incredibly clear. Things that can be are of course automated.

Just because it’s a “smart” service doesn’t mean it has to connect to the Internet or a server or the manufacturer. If it does neither, it can’t be turned off by them.

All my devices run local-only protocols. Nothing leaves my house. The devices that would be proprietary were reflashed to tasmota (fully open source, local only). Others are either Zigbee or Shelly. While Shelly has a cloud connection, it’s fully optional and disabled by default (including automatic updates). The hardware is also supported by tasmota, and reflashing is always just 5 minutes of effort away.

There is absolutely nothing that any manufacturer has to do to keep my stuff working. I have to do a little something (keep my tiny server on, basically). But more importantly there is nothing any manufacturer can do to stop my stuff from working.