• 0 Posts
  • 128 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle

  • Gentoo does have systemd, actually—package sys-apps/systemd—and there are optional sections in the install documents that explain how to go about using it as your primary init. It’s an officially supported configuration, just not the default.

    (But yeah, as for the main problem, sounds like hardware—RAM, your primary hard disk, or the disk controller on the mobo. Start with The Bleeding Obvious and make sure all cables are solid in their sockets and all the RAM is properly inserted.)


  • For gaming, you should be using the most current version of nvidia’s proprietary drivers that supports your GPU, unless that GPU is really old. Have a look at this page: https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/

    If your GPU isn’t listed there, use the most recent driver you can find.

    If your GPU is on the 470.xx supported list, try 470.223.02, as that seems to be the last in the series.

    If your GPU is on the 390.xx supported list, try 390.157.

    If your GPU is on one of the other lists, it’s a really old chipset and you should be using the Nouveau driver that’s built into the kernel.

    If you’re using the nvidia proprietary drivers on a system that also has Nouveau installed, make sure you’ve blacklisted Nouveau so that you’re loading the correct driver.

    Dual-graphics laptops are a bit of a bear to work with under Linux generally. Good luck.



  • To set the record straight, since you apparently have no idea of the history: systemd isn’t the original Linux init system, and wasn’t foisted on the Linux community because it was technically superior for most people’s use cases. It still isn’t the only viable Linux init system, but it pulled a Microsoftian embrace-extend-extinguish on udev, which makes it more difficult to switch away. Its current popularity is still not based on technical merits. Instead, it’s political, because most people don’t care about what init they’re using and most distro-makers take the path of least resistance.

    It’s true that you’re not required to use all of the individual executables that comprise systemd, but most distros will require you to install them. So they’re still present as unwanted clutter, and bugs could still pose a security risk if an attacker can run the executables. (This doesn’t mean that OpenRC or runit would necessarily be any more secure—every non-trivial piece of software has bugs, and some percentage of those are going to be security-relevant. You’re not required to care about small amounts of on-disk clutter, either, but some people choose to make their system partitions small and micromanage the contents even if they’re not working on embedded.)

    Compiling your own copy of systemd without the clutter, judging from the contents of the systemd ebuild, requires setting more than 30 compiler options. And then installing the result manually without trashing your system. Not trivial, in other words.

    If systemd works for you, then by all means use it, but accept that other people may choose to install something different on their own machines for what you consider to be bad reasons, or no reason at all, and arguing about it just annoys them without providing any benefit to you.





  • If I recall correctly, the aircraft manufacturer writes the maintenance guidelines.

    This could be a Boeing issue, if it’s due to something that happened at the time the aircraft was built, or due to a foreseeable gap in the maintenance guidelines.

    It could be a Delta issue, if they weren’t following the maintenance guidelines, or a maintenance contractor working for them wasn’t following them and they didn’t catch it.

    It could also have been (very small but nonzero chance) the result of physical trauma to the plane that wasn’t foreseen, back in the 1990s when it was built, as something that might cause an issue of this magnitude. I haven’t yet seen any information on whether this particular aircraft has a history of hard landings or running over debris on the runway. Freak accidents do happen.

    All of those have precedents in aviation history.




  • Part of the problem is the chip manufacturers. They provide precompiled device drivers for one version of one kernel only, no source, and refuse to update them ever again. It can be a bit difficult to update the rest of the software stack when there’s no way to shore up the foundations. Device manufacturers need to start insisting on updated drivers and/or provided driver source code before they buy the chips to put in their phones, tablets, and other systems.

    Good luck on that.




  • Deceptive list that appears to include only distros that don’t package systemd at all. A distro can offer more than one init system. For instance, Gentoo defaults to OpenRC but offers systemd as an option for users who want it for whatever reason. It isn’t on that list.

    (But I agree that if you know what systemd is and that you don’t want it, you’re not using Distrochooser. You’re not looking up your next distro in Wikipedia, either.)