• 0 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: December 16th, 2023

help-circle
  • Some additional nice things about guix:

    Everything is guile. The system definition, the service definitions for shepherd, everything.

    Shepherd is hands down the best init program I’ve ever used. It’s just incredibly simplistic but because it just runs the guile definition you give it, you can do some incredibly complex things that systemd etc. can do as well.

    The OS documentation is built into the distro, with “info guix” you get reams of configuration information for the distro without ever needing to look it up online.


  • About a year and a half.

    To be honest it’s not “easy” to use. The guiding principle behind mainline packages is that everything has to be built from source, so most somewhat unpopular things are missing from the mainline channels.

    To use it like any other distro you’re going to need to learn how to write packages fairly quickly. Luckily the main draw of guix is the entire OS being based on guile so once you get a little under your belt you can just read the specs from other channels to see how a package is written.

    Took me maybe a week to start writing guix packages.

    There’s also The toybox





  • Nouveau is important because Nouveau is the default driver in Ubuntu, Fedora, OpenSUSE, Debian, and ever other distro.

    Linux distributions can’t easily distribute the proprietary nvidia drivers or the slightly less proprietary nvidia-open drivers so they depend on nouveau as the default nvidia driver. When you install a distro it usually has to use the nouveau drivers before downloading the proprietary blobs from Nvidia.

    Nouveau is the only reason anyone can use Linux on an Nvidia card long enough to install the other drivers.

    It’s also actively maintained, receiving updates that get upstreamed almost daily.

    I’m not sure what about those things says “defunct”.

    And the rust developments in Asahi for the M1+ series of CPUs don’t just benefit Mac but all the ARM CPUs as well.




  • WalnutLum@lemmy.mltoLinux@lemmy.mlResigning as Asahi Linux project lead
    link
    fedilink
    arrow-up
    40
    arrow-down
    1
    ·
    edit-2
    2 months ago

    I’m not surprised by this.

    The general attitude around R4L is that it’s largely unneeded and for every 1 person actively working against the project, there are 10 saying either “waiting and seeing if it works is the right decision” or “if rust is so good they should prove it.”

    So as a R4L developer you’re expected by the community to fight an uphill battle with basically no support on your side.

    We will likely keep having developers on that project continue to burn out and leave until the entire thing collapses unless the decision is made ahead of time to cancel the project.

    Every time I read any news about Rust for Linux I leave disappointed by the entire kernel community.







  • Typically when there are “can’t mount” issues with btrfs it’s cause the write log got corrupted, and memory errors are usually the cause.

    BTRFS needs a clean write log to guarantee the state of the blocks to put the filesystem overlay on top of, so if it’s corrupted btrfs usually chooses to not mount until you do some manual remediations.

    If the data verification stuff seems more of a pain in the ass than it’s worth you can turn most of those features off with mount options.