GenderNeutralBro

@GenderNeutralBro@lemmy.sdf.org

This profile is from a federated server and may be incomplete. Browse more on the original instance.

GenderNeutralBro,

I would guess that’s not a hard limit. Maybe they decided to undersell it because many 4TB+ nvme drives are physically larger and/or require heat sinks, so they might not fit. I don’t see any details on their web site though.

Given two drives with the same size, same heat output, and same interface, it shouldn’t make a difference.

It’s pretty common to see fake limits like that on spec sheets. I can definitely put more RAM in my motherboard than is officially supported since higher-capacity DIMMs are out in the same form factor now compared to when the mobo was released.

GenderNeutralBro,

It’s insane how many things they push as Snaps when they are entirely incompatible with the Snap model.

I think everyone first learns what Snaps are by googling “why doesn’t ____ work on Ubuntu?” For me, it was Filebot. Spent an hour or two trying to figure out how the hell to get it to actually, you know, access my files. (This was a few years ago, so maybe things are better now. Not sure. I don’t live that Snap life anymore, and I’m not going back.)

GenderNeutralBro,

Yes, thanks! I did indeed mean Termux. I’ll edit my post.

GenderNeutralBro,

Good point. I can never keep my USB 3 naming schemes straight.

The faster nvme-based sticks can even exceed 3.0’s 5gbps!

GenderNeutralBro,

Definitely look for portable SSDs rather than flash drives. Different technology, usually significantly larger (physically). Easily saturates a USB 2.0 connection, so look for USB 3.0.

Back when Microsoft supported Windows To Go, they had a short list of verified drives to use. Surely outdated now but might be a good starting point.

FWIW I used to run Windows 10 off a Samsung T5. It worked fine, except that it would always shut down when I tried to suspend. Still works as far as I know, I just haven’t used it in a long time.

GenderNeutralBro,

Thanks! I checked and actually, dark mode was already on. Huh. I guess I haven’t tried since…I don’t even know. Maybe I didn’t have qt6 installed last time?

GenderNeutralBro,

You can verify the signature of the manual download as well. Either way, you are trusting the files you download over HTTPS from mullvad.net. There’s no real difference, except that when you use the repo, you are trusting it indefinitely, whereas if you download the deb directly, you are only trusting it once.

Using the repo is less secure, because it opens you to future attacks against the repo itself.

GenderNeutralBro,

You’re downloading the signing key over HTTPS either way, from the same server. That’s the common point of failure.

GenderNeutralBro,

Agreed.

Unfortunately, Mullvad’s instructions just have you download the key from mullvad.net and add it in with no further validation.

You can also get it from their GitHub page, at least for the individual debs. Not sure if they have the repo key on GitHub.

GenderNeutralBro,

In theory, faster updates compared to Debian Stable.

I haven’t compared the repos directly though so I’m not sure what the current differences are specifically.

GenderNeutralBro,

MacOS also supports exfat out of the box. So do most Android phones, TVs, consoles, etc.

It’s only viable choice for cross-platform use, AFAIK. Not the best fs out there by any means but I still use it on my all my USBs because I need them to work everywhere.

GenderNeutralBro,

I’m also interested in hearing Proton users’ experience. On paper it looks like an okay deal, but you could get a similar suite of services from Posteo + iDrive + Mullvad + BitWarden for cheaper and not end up locked into an “ecosystem”.

However, there is legitimate value in combining email and drive space. Posteo only gives you 2GB for email, and their upgrades are rather expensive.

Also, Mullvad might not be equivalent since they axed the port forwarding feature a while back, making BitTorrent only kind-of usable (incoming connections will not work).

GenderNeutralBro,

I appreciate your well-reasoned arguments.

I disagree with the characterization of Homebrew as a “virtual environment”. It installs binaries and libraries in its own directory and by default adds those directories to your PATH. This makes them first-class entities on macOS. Unlike with WSL, there is no secondary kernel and no hypervisor. Everything runs natively within the macOS environment. There’s no bridge, no virtualizer, not even sandboxing with Homebrew or MacPorts. Homebrew and MacPorts do not install “Linux” software; they install Mac software.

As a real-world example, I can install newer versions of standard tools like openssl and kerberos5 via MacPorts or Homebrew, and native Mac apps that rely on those pick them up seamlessly. I don’t think that is realistic with WSL, if even possible.

I haven’t re-evaluated a lot of development stuff since the release of WSL2, so perhaps things are smoother now, but in WSL1 I found there to be a big disconnect between e.g. a Windows-native installation of Spyder and a WSL-based Python environment. If there is a way to set that up, rather than installing Spyder within WSL and wrestling with X11 to run it as a second-class GUI, I’d love to hear it.

GenderNeutralBro,

Which bloat? It’s just a regular terminal

It’s a virtual environment that requires installation of an entire Linux system. The disk and memory usage is not comparable to a native Unix OS.

GenderNeutralBro, (edited )

To clarify, this is my first time using Spiral Linux. My experience regarding Nvidia drivers is across several different distros (most recently Ubuntu LTS and OpenSuse Tumbleweed). I have never had a seamless experience. Often the initial driver installation works, but CUDA and related tools are finicky. Sometimes a kernel update breaks everything. Sometimes it doesn’t play nice with other kernel extensions.

The Debian version of the drivers didn’t set up Secure Boot properly. Instead, I rolled back and used the generic Nvidia .run installer, which worked fine. Not seamless, obviously, but not really worse than my experience on other distros. In the future I will always just use the generic installers from Nvidia.

Point is, with BTRFS you can just try anything without fear. I’m not going to worry about installing kernel updates from now on, or driver updates, or anything, because if anything goes wrong, it’s no big deal.

GenderNeutralBro, (edited )

Nvidia just sucks across every distro I’ve used. Have you had good experience running CUDA, cuDNN, and cuBLAS? If so, which distro?

And have you run it alongside other things that require kernel modules, like ZFS and VirtualBox?

GenderNeutralBro,

I was expecting Copland (what would have been Mac OS 8, had the project survived).

GenderNeutralBro,

I noticed this is also true in the standard Lemmy web UI and Jerboa.

GenderNeutralBro, (edited )

I’m seeing it working correctly on web now on two different instances, so…I dunno, guess I’m crazy? I was sure it wasn’t working yesterday. I actually tried to use it in a comment just a few days ago and gave up.

Still doesn’t show correctly in Jerboa though.

GenderNeutralBro,

I’m about to jump from Ubuntu back to good ol’ Debian. I was planning on testing, but I’ve heard a few times recently that people are running unstable for day-to-day desktop use. Is there any particular reason you went with unstable instead of testing? Any issues so far?

GenderNeutralBro,

No way Linux is 32! I remember when it first came out and it was just…oh.

Don’t mind me, I’ll just be here yelling at the cloud.

GenderNeutralBro,

Seriously? My Nvidia drivers broke every time I got a kernel update on Tumbleweed. Eventually I pinned the kernel to an old version. Gah.

Maybe my PC is just haunted.

GenderNeutralBro,

I’m also on SDF. They’ve been in the business of offering free computing resources to the public since the 80s. So I feel confident that they won’t close up shop due to lack of expertise or resources.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #