• 0 Posts
  • 9 Comments
Joined 3 years ago
Cake day: June 19th, 2023
  • taanegl@beehaw.orgtoLinux@lemmy.ml•NVIDIA switching to open kernel modules by default in future driver update for Turing+
    0·
    2 years ago

    It’s a weird time to live in, but not confusing. It’s obvious to see that what you really want as a vendor is control over the operating system stack itself, and relying on Microsoft has become challenging.

    In essence what NVIDIA is doing is bringing it’s entire GPU driver stack open source side, so that entire industries say go on buying tons more hardware.

    Us Linux enthusiasts get to reap the benefit, what with entire open source movements bringing libraries to Linux side first that can turn GPU hardware into whatever tool you’d like. Projects like PyTorch and ffmpeg run as first class citizens on Linux.

    Windows still relies on either shared DotNet stack (which will make a monkey out of you - cough cough) or the nearly ancient MSYS2 build environment. Microsoft of course prefers you run all that software inside their Linux container system known as WSL - and there’s a reason for that.

    The Linux graphics stack is looking more “feature complete” by the month, bringing up the question of where you actually get the best hardware support. This is a good question to have.

    Now, if only the open source desktop movements could clean house, figure out funding and get their stacks in order, we might finally, for the umpteenth time, maybe see the year of the Linux desktop.

    I grow old with anticipation, but seeing what NVIDIA did in the before time versus what they do in the now puts a smirk on this haggered face.

    Onwards to the future.

  • taanegl@beehaw.orgtoMemes@lemmy.ml•Remember, if Fascism wins it is YOUR FAULT.
    0·
    3 years ago

    Biden sucks… but vote for him. I mean the two party system sucks, first passed the post sucks, gerrymandering sucks… but the republican party sucks even more. I’d rather have a dottering old liberal than an outright fascist, and at the same time the system won’t be reformed because of an election cycle. People need to organise, get off their lazy butts. But since you ain’t doing that, there’s only one thing to do.

    Vote Biden. Don’t be dumb. It’s like the only sane alternative, no matter how insane that sounds.

  • taanegl@beehaw.orgtoLinux@lemmy.ml•One single partition for Linux versus using a partition table?
    0·
    3 years ago

    Well technically, if you’re using BTRFS, you might want to check out subvolumes. Here’s my subvolume setup:

    • Subvolume 1, named @ (root subvol)
    • Subvolume 2, named @home (/home subvol)
    • Subvolume 3, named @srv (/srv subvol)
    • Subvolume 4, named @opt (/opt subvol)
    • Subvolume 5, named @swap (which is - you guessed it - the swap subvol)

    You then set up fstab to reflect each of the subvolumes, using the subvol= option. Here’s the kicker: they are all in one partition. Yes, even the swap. Though caveat, swap still has to be a swapfile, but in its own separate subvolume. Don’t ask me why, it’s just the way to do it.

    The great thing about subvolumes is that it doesn’t do any size provisioning, unless specified by the user. All subvolumes share the space available within the partition. This means you won’t have to do any soul searching when setting up the partitions regarding use of space.

    This also means that if I want to nuke and pave, I only need run a BTRFS command on my @ subvolume (which contains /usr, /share, /bin), because it won’t be touching the contents of @home, @srv, or @opt. What’s extra cool here is that I’ll lose 0% FS metadata or permission setup, since you’re technically just disassociating some blocks from a subvolume. You’re not really “formatting”… which is neat as hell.

    The only extra partitions I have is the EFI partition and an EXT4 partition for the /boot folder since I use LUKS2.