

If this is your content, I have some pointers.


If this is your content, I have some pointers.


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 🤣


If you simply just want to track config file changes, use a flat git repo, or something like Ansible.
That’s going to be a helluva lot simpler for you to learn and execute on.


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.


They are DevKits, as someone else mentioned. Very literally described as such.
Don’t be upset when you get exactly what they state by ignoring their own words.
I’ve seen this exact same video done by like five different people. Are they content milling dumb shorts now? Key-Rist.


Just putting it here because they will spam the shit out of any domain registrar emails not hidden as well.
In this particular case, they were smart enough to actually have business emails on hand for the threat, knowing they’d never actually attempt to actually email this threat to any mail server as they would get filtered immediately.


8GB it more than enough to run whatever desktop. Probably not game, but any desktop distro is fine.


NEVER EVER EVER pay anything to anyone if they are making claims like this.
Simply respond with “Our legal team’s process requires a filed Cease and Desist to be sent directly to them with specific references to infringements based on your claims. Once they have received this, the offending content will be immediately rectified.”
Even if it’s your personal website. Don’t even fucking bother with these people and waste your time and money worrying about it, be sure this is the very first step in any legal action over public content. They can’t just jump to suing you or demanding money.
Scammers will fuck right off.


Mint doesn’t use Gnome or KDE, which is why devs generally steer clear. It’s best to be coding and running the thing the most number of users will be experiencing.


Fatty fingers


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.


As others have stated, it’s probably because you’re activating the network from an IP that is defined as being in another time zone in between two locations. This can sometimes happen with certain VPN configurations as well.
Here’s some info on debugging a bit further to help determine if this is the issue: https://www.linuxtechi.com/sync-time-in-linux-server-using-chrony/
And here’s how to force a time zone if needed: https://www.cyberciti.biz/faq/howto-linux-set-time-zone-per-user-basis/


If it just started out of nowhere, and you haven’t updated recently, then check your heat, power and memory.
If you’ve updated recently, check and see what got updated and go back to the previous versions.


I’m aware of what it is. This is a Fedora Server install that shouldn’t have it enabled by default because it generally only fits the use-case of home users. Someone installing the default package list in an enterprise setting would not want this enabled.
I even checked to be certain, and it is not enabled by default.


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.


Your router is doing that, not Fedora Server.
(typing quickly, excuse errors)
Title: The title is both confusing and misleading to the actual topic being discussed, which is CVEs being used to identify vulnerabilities to be exploited. The tool is irrelevant, and the tool in the headline is actually mentioned very little in the content.
Staying on topic: the title sets out a few things as the topics: 1) NPMScan 2) Vulnerabilities 3) Frameworks being exploited.
It then shifts in the first details to middleware exploits, and how routes are mishandled. So a reader might be asking "Wait, is this a post about middleware attacks, or something specific to NPMScan/CVE exploits?
A title or headline should be a simple summarization of the topics discussed, and the content should stick to what those topics are. A more accurate title to this piece would be “How Hackers use CVE information to craft exploits in X, Y and Z”
Diversion from topics: While keeping the meat of an article as close to the main topic thread, it’s important explain the when/where/why you are diverting from that thread for context. When doing so, you’re explaining the relationship between your main topic, and this new information being pertinent and important to the discussion overall.
Just adding a bunch of unrelated information leaves the reader confused about what those ties to the main thread are, and usually will be forgotten or skipped if they came to your content based on the headline and looking for specific information.
An example of this being used horribly all over the place is recipe sites. You go looking for a Holiday Cookie recipe, and are presented with with pages of journal entries about the authors childhood cookie memories. It’s not pertinent to the actual content being requested, and people will skip it.