This seems like the right answer to me. Whether or not you decide to dual boot, make one of these USB keys so you can recover if something goes wrong.
Just a basic programmer living in California
This seems like the right answer to me. Whether or not you decide to dual boot, make one of these USB keys so you can recover if something goes wrong.
When I was using Debian I found I could generally get the latest version of software I wanted from Nix if it wasn’t in the main Debian repos, or was outdated. Nix works quite well on any Linux distro - it doesn’t interfere with the rest of the system.
All I can tell you is that this is done differently for each shell. So decide whether you want completions for bash, zsh, fish, all of the above, or whatever, and look at the docs for the relevant shells.
This is why I switched to labelling USB sticks with two-character codes, and I keep a file that lists the current content of each stick.
Anyone else read these newsletter titles in Pixlriff’s voice? “This week, in Hermitcraft Gnome!”
There’s a relevant community post, NixOS is not dying, please don’t spread fear actively
iOS also supports third-party passkey managers so that’s an alternative to Android for helping to fill gaps creating passkeys.
Nice! I may take a look. I’ve been happy with Enpass except that I recently switched to a window manager that doesn’t implement xwayland, and Enpass is one of only two apps that I haven’t gotten working in native wayland mode, or found a substitute for. So I’ve been running Enpass in a rootful xwayland window running a nested i3 session. The IPC connection to the browser extension still works so it’s not too bad, but I’m a little tempted to try alternatives.
I forgot to mention that to use a passkey manager on Android in addition to setting that Chrome feature flag you also need to set the app as your passkey manager. That’s done at the system level in Settings > Passwords & accounts > Passwords, passkeys, and data services
FYI I’ve been running Steam and Wine games in Gamescope because I’m using a window manager that doesn’t implement XWayland. I don’t know if that would help with Nvidia, but might be worth a try. It works ok; Gamescope has a Steam integration switch that helps.
I think Electron apps mostly switch to native Wayland mode if you set an environment variable, ELECTRON_OZONE_PLATFORM_HINT=wayland
. The one I don’t have working in Wayland mode is Discord. See https://wiki.archlinux.org/title/wayland#Electron
I read a few articles. I think Andres Freund’s announcement gave me the best context for the exploit itself. https://www.openwall.com/lists/oss-security/2024/03/29/4
The most helpful source I saw on which systems are affected was this Lemmy post, https://beehaw.org/post/12813772
I have a Ryzen 7 5800X and I’ve had no problems
I would install a systemd user service with the setting Restart=always
. If your window manager is started with systemd, or defines a systemd target you can configure the waybar service to start and stop automatically with the window manager.
Ooh - thanks for the tip!
Yeah, the first thing I do when I log in is restore my Firefox session, which includes several windows with quite a lot of tabs. I also use the Auto Tab Discard extension so I can keep lots of tabs in my workspace without having all of them loaded all the time.
Yeah, I stopped using display scaling and switched to this text scaling setting to get a similar result in a cleaner way,
$ gsettings set org.gnome.desktop.interface text-scaling-factor 1.25
That’s great, but yours is not the universal experience since different tasks have different RAM requirements, even within the realm of programming. I had RAM shortages when I was running the Haskell LSP server and compiler at the same time on a largish project. Haskell’s type checker does a lot more than other mainstream languages’ which is how it delivers such strong correctness guarantees. You trade RAM for scrutiny. Then the LSP server has to be fast so it has to do a lot of caching, and you get an additional trade of yet more RAM for speed.
When niri runs applications it will now put them into transient systemd scopes. One concrete benefit is that when an application uses too much RAM and systemd-oomd kills it, niri won’t go down alongside the app, so the rest of your session will stay intact.
Does Gnome do this? I’ve certainly had my entire session crash when a certain LSP server used up all of my memory. I appreciate this feature!
I think it’s time for me to try Niri as my main WM. The main thing I want to figure out is getting XWayland going so my Wine games will work. I know there is info on this in the Niri docs, so I’ll start there.
Edit: The key to getting the games working is gamescope! It runs a nested X session. Lutris does not work without X, but Bottles does and it has a handy gamescope checkbox in the bottle settings.
Well I’ll throw in my endorsement for kitty. I like the ligature support, the fact that it can be configured to hide all UI, and it uses text files for configuration that I can put in my dot files repo.
There are some particular features that I use constantly:
I can yank a file path to the prompt from previous output by pressing ctrl+shift+p then f then a 1-character label. I can do the same with a git hash (or other hash) by pressing h instead of f.
I can scroll back and search previous output using only the keyboard with ctrl+shift+h which puts the terminal history in a pager.
I can get the output of only the previous command in a pager with ctrl+shift+g. Or jump to previous prompts with ctrl+shift+x and ctrl+shift+z.
I use kitty-scrollback.nvim which replaces that pager with neovim so I can use all of my editor features to search history, copy what I want, etc.
Probably not directly helpful, but Nix packages for Chromium and Electron apps are set up so that you can switch to native Wayland mode globally by setting an environment variable,
NIXOS_OZONE_WL=1
I don’t know of any global setting that isn’t distro-specific.