• 1 Post
  • 706 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle


  • just_another_person@lemmy.worldtoLinux@lemmy.worldNew to Linux
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    8 hours ago

    You won’t need a terminal unless you refuse to use the GUI tools that do the same thing.

    If you want to use the terminal, go for it and use the default. If you eventually find it lacking THEN start investigating different options.

    Just use everything as you normally would otherwise, and you shouldn’t notice a huge shift.



  • Well, no. Not to shoot down your comment or anything, but you’ve only learned a lot about Nix still in your example.

    For instance, if someone presented you with an Arch system of some sort and asked why a certain systems unit wasn’t working, or why the speakers on their laptop don’t work but the headphones jack does, or why their Nvidia kmod modules aren’t loading.

    Your experience with Nix is t going to help with some of the more basic functions of a traditional Linux system because of the abstractions in top of abstractions that you’re used to interacting with on Nix.

    I’m not even digging on Nix, like I said, it was designed for a very specific purpose. I’ve run hundreds, if not thousands, of various build system permutations on Nix over the years, and even I wouldn’t even think about using it for really basic stuff like running a Desktop 🤣



  • Traditional and Immutable distros as working OSes are not knowledge compatible at all. The software that runs on it is the same, but everything else about how they run, are executed, managed, installed…etc, all different.

    Nix is Immutable, and on top of that, has an entire configuration language you need to manage.

    If you’re not familiar with a standard Linux OS, you’re going to have a bad time, I can tell you that.

    As far as your concepts of “random commands” not being used as part of the running of a system, that is not quite correct. You will still to track adhoc changes to different services or configurations that would then need to also be applied and executed in a NiX config in the proper place to ensure proper order of execution.

    Let’s just say it’s an advanced system that serves a purpose meant for repeatable testing and CI/CD type operations. It’s not really meant to be a user-friendly system to make managing your desktop easier, so. don’t misunderstand this one important fact.






  • People in here like to hate, but there’s a damn good reason. The majority of the people who are vocal about distribution choice aren’t contributors, long-time users, or experts in the field. A lot of us who are just want a simple, quick installing, porting, “out of the way” (no heavy customizations) and functional distro with a large user base, and a solid team behind it. This means it’s not going to immutable, and it’s not going to to be by Canonical.

    A lot of us use Fedora for this exact reason.




  • Doesn’t matter. Your machine going to another is not simply due to mdns running. In fact, I doubt that’s a default package selection in Fedora Server for security reasons, but I could be wrong.

    Run dig [whateverhostname] from your machine, and then check /etc/systemd/resolved.conf on the server and see if something with MulticastDNS is enabled. Don’t see why that would ever exist as a default.




  • I continue to contribute in the most minor way to both, and it’s very true that Hughes LARGELY runs this repo. This is becoming a problem, especially since the majority of companies do not contribute, though they use the upstream just like everyone else.

    If Amazon, Google, Dell, Hetzner, Equinox, DR, DO…etc all paid their fair share, they’d be able to pay honest contributors just simply for making what is already available MORE readily available. That’s what this project is about.

    On the hardware manufacturer side: AMD, Nvidia, Intel, Realtek…etc are also not chipping in.

    This is a CRUCIAL project for larger adoption for home users. Yes, most enterprise-sized companies manage their own semver releases for firmware, but they still use these tools. They should contribute, not only because it’s the right thing to do, but a miniscule amount of money for them to do so to ensure the same people making this such a success can continue to do so.


  • You generally keep OS and storage separate for functionality, not necessarily because one is more safe than the other these days with more advanced journaling filesystems that can self-heal and keep things pretty safe and sound.

    The main drawbacks to having them combined is all surrounding flexibility. If one fucks up, everything is fucked up. You won’t be able to perform rescue operations on either without impacting both at the same, you can’t change the layout of one without affecting both…etc.

    Performance is obviously another one, but if you’re not running critical operations for a business or whatever, it probably doesn’t matter.