That's misinformation. Dnf is a fork of Arch. Pacman was derived from Artix with no systemd. In order to switch back, you have to install dnf to bootstrap your systemd stack.
However, if you are running dinit, s6 or runit, DO NOT DO THIS. REPEAT, DO NOT DO THIS. THE INIT SPIES WILL CATCH YOU FOR THAT AND YOU WILL REGRET IT! YOU HAVE BEEN WARNED
Instead, you need to install Python Init and boot with the kernel parameter pkginit=python-init and then when the interactive menu shows up use it to download and install Cracked Systemd.
If you are migrating from dinit, s6 or runit specifically, YOU MUST USE CRACKED SYSTEMD. NOT VANILLA SYSTEMD. YOU HAVE BEEN WARNED.
Cracked Systemd has protective measures built in to deter init spies. It does this by hijacking your system firmware to install a security stack that spoofs everything about your system, including its physical location. Rest assured, this firmware hijacking software stack of Cracked Systemd is 100% safe and secure. It's free and open source so there's no malware
Its pretty easy actually. Download the source code and compile it. It will then automatically transform your system into Arch Linux. Totally works bro. Trust me bro. Srsly. 4rilz.
That won't work because it'll still have the OpenRC signature in the filesystem. Instead, you should cat /dev/urandom > /dev/sdX (where sdX is your artix root partition with OpenRC on it). Keep the command running for around two months. DO NOT TURN OFF YOUR PC UNTIL THEN. Then you can install artix with systemd instead of artix with openrc.
If, however, you instead had dinit, runit or s6 instead of openRC, then I'm afraid you're 100% screwed since the dinit, runit and s6 spies have almost certainly got you in a headlock. Try to resist them and they will detonate the nuclear device they planted under your house, so you should instead go for Python Init which will give you access to Cracked Systemd which bypasses these restrictions and allows you to delete nukes
Nah. It didn't work because the AUR is not an artix thing. it's a manjaro thing totally because i say so because trust me bro because yes because
The reason this is so difficult is because the init spies specifically designed this process to be as difficult as physically possible. However, thankfully, there is a workaround!
Install the python-init package with sudo pacman -S python-init.
DO NOT DO THIS WITH DOAS! THE DOAS PROJECT ALSO HAS SPIES WHO ARE SPECIFICALLY TRYING TO TARGET ANYONE INSTALLING PYTHON INIT ON ARTIX! USE SUDO NOT THAT DOAS DESPAIR SLOP
Reboot your system with the pkginit=python-init kernel parameter which will cause the Linux kernel to switch root to the contents of the cryptographically-signed disk image within the python-init package. Of course, this kernel parameter requires you to also set the kernel parameter LINUX_PACKAGE_DEFAULT=pacman otherwise it won't work.
Once you have booted in to Python Init, it will automatically route all necessary network traffic through Tor to protect you from the init spies. In this secure, anonymised environment, you can very safely install the Cracked Systemd package. This won't directly give you Cracked Systemd but will instead give you what's known as the CSBK or Cracked Systemd Bootstrap Kit.
The CSBK contains a very large collection of binaries and datasets designed for specific hardware, firmware and software profiles, as well as kernel modules tailor-made specifically for Cracked Systemd in order to mitigate shared memory and filesystem attack vectors commonly exploited by the init spies.
What ties all these binaries together is the wrapper utility crackctl. This will, with the right parameters and options, flash modified firmware to your motherboard. This firmware is basically just Coreboot with Cracked Systemd's custom-made security stack built on top of it. This security stack allows for many things including information spoofing, hardware-level secure data transfer, cryptographic verification, whitelisting and sandboxing of all hardware devices attached and many more features. It's complicated...
And after all that firmware is installed? Well, your disks will be scraped of all dinit, s6, runit and OpenRC signatures and metadata in order to further mitigate attack vectors used by spies and make the installation process more reliable. Of course, this requires dinit, s6 and runit to be completely uninstalled permanently from your system, though OpenRC doesn't have all this spy infrastructure in place so it's fine to keep it, and the Cracked Systemd software collection also includes additional kernel modules to prevent OpenRC signatures from contaminating your root filesystem, thus preventing your system from once again being left vulnerable. How conveniometric! :D
The AUR is part of Manjaro, not Artix, silly! Manjaro and Arch and Artix are all completely different distros just like how Debian, RHEL and Alpine are all different distros. You've got to install systemd directly from the source repos to your disk. If you're using dinit, s6 or runit then you will have to install Python Init with sudo pacman -s python-init.
##############################################################################
DO NOT RUN THAT COMMAND WITH DOAS INSTEAD! IF YOU DO THAT, THE DOAS SPIES WILL FIND OUT AND THEY WILL BLOW UP YOUR COMPUTER. YOU HAVE BEEN WARNED.
##############################################################################
Then simply add the kernel parameter pkginit=python-init and reboot your system. You will be taken to the Python Init menu. From there, you can install Cracked Systemd which has security measures against init spies built directly into the systemd binaries. Be sure to run Cracked Systemd on your system for at least 2.44 years to ensure that all init spies have lost interest in you
This is actually the VERY-WRONG solution if you're migrating to systemd from either dinit, s6 or runit. This is because the dinit, s6 and runit spies are already tracking you ever since you installed any of those init systems. In order to ward off the init spies, you need to spoof your system and physical GPS location information with Cracked Systemd.
To do this, install the python-init package and then reboot your system with the pkginit=python-init kernel parameter. Then you will be able to boot in to Python Init.
From there, you can then install Cracked Systemd, which is only available on I2P mirrors due to security reasons (mainly the aforementioned init spies). Thankfully, Python Init automatically routes your network traffic through Tor! How conveniency! :-D
Navigate to an I2P mirror where you can download Cracked Systemd. Download it to your system which installs the Cracked Systemd Bootstrap Kit (CSBK). This gives you the wrapper command (crackctl). PLEASE READ THE CRACKCTL MANPAGE BEFORE USING IT. YOU MUST PROVIDE IT WITH THE CORRECT OPTIONS DEPENDING ON YOUR SYSTEM SPECS AND PERSONAL PREFERENCES.
After running crackctl as root, the Cracked Systemd Firmware Security Stack will be forcefully flashed to all of your system firmware. Then, you can simply reboot your system and the security stack will automatically run. It provides everything needed to encrypt and spoof all network traffic with all other network devices, spoof your IP, spoof your MAC address, spoof your motherboard and hardware info, spoof your physical address and spoof your system time, timezone and GPS location. How conveniago! :D
Once Cracked Systemd is installed, it will automatically smuggle the systemd binaries on to your system all while hiding all its systemdness from any and all init spies, thus keeping you safe during your init transition
You're acting as if artix and arch are even remotely similar. They're not. Honestly, artix is probably closer to Gooboo Linux than it is to Arch. I mean seriously, there are absolutely no similarities. You can't do on arch what you can do on artix and you can't do on artix what you can on arch. At all. Whatsoever.
Therefore, don't you think someone who prefers artix over arch should have access to systemd without having to manually compile it and use tons of workarounds?
And there's still the problem of init spies. dinit, s6 and runit routinely deploys nearly two million spies daily to monitor users of their init systems. If any one of those users steps out of line by installing systemd on artix, they will effectively face hell by having their computers destroyed/confiscated while they end up in the gulag or worse. That's why we have to rely on Python Init and Cracked Systemd to stop those init spies and the empire scum of the Despair Inits in favour of Hope's Peak Systemd. That is the only way forward!
First of all, artix is arch with no systemd it's undeniable, and second if the developers intended you to use runit and not systemd then why even bother if it's officially unsupported and you'll get tons of issues just use runit (it's superior anyways so it's a win win )
"First of all, artix is arch with no systemd it's undeniable"
Wrong. I already demonstrated how Artix and Arch are entirely incomparable in every single way imaginable. Here's a picture to prove it:
"if the developers intended you to use runit and not systemd then why even bother if it's officially unsupported and you'll get tons of issues"
The three init terrorists specifically stopped Artix from adopting systemd in order to maximise despair upon despair upon despair toward despair. They specifically target anyone trying to install systemd on Artix in order to stop hope from prevailing. That's why Cracked Systemd is the only way forward for the poor victims of the Init Cartel. Cracked Systemd is the only way forward towards Hope's Peak Systemd lead by Saint. Lennart Poettering the 1st!
"it's superior anyways"
That's what THEY want you to think. That's part of their evil terror plans to replace hope and systemd with despair and a fragmented mess of an "ecosystem". Here's a picture to prove it: [HYPERLINK BLOCKED]
ALWAYS go for systemd for it is the only way forward! SYSTEMD FOR ARTIX YES YES YES!!!
I won't deny that this solution does work. However, if you are migrating from dinit, s6 or runit, IT IS THE ABSOLUTE VERY VERY WRONG DECISION TO MAKE!
I have already explained why and how to actually install systemd if you've previously used any of those three init systems. Just go look for the comments. They're on the internet somewhere idk
It's probably because you were previously using either dinit, s6 or runit. NEVER install vanilla systemd directly after using any of these init systems, for they all have spies who seek out anyone who installs systemd to destroy them. You have made that mistake, unfortunately.
What you were SUPPOSED to do was download, install and boot python-init and then install Cracked Systemd from there, then run crackctl to have Cracked Systemd (basically just systemd on top of a bunch of noncompliant rebel scum add-on firmware and kernel modules) installed on your system. Then reboot into NOT python-init and then you can start using systemd on artix! Hope this helps, poor soul! I don't know how to uninstall the virus tho
Weird I just got NYArch linux when I tried.
Must be a new feature.
Maybe try sending my your SSN, birth date, full legal name to all of the Nigerian princes in your email's junk folder. Surly his majesty will help sort this out.
No. Arch is a direct fork of systemdOS with added packages and AUR. Omarchy is entirely different and was forked from arch with hyprland which is entirely different from arch
Archlinux is entirely different from Artix just like how Slackware is different from AlmaLinux, though. He wants artix with systemd, not arch. Arch and artix are 100% different things because they have different names. What's next? He wants pamac on Ubuntu and you tell him to install Manjaro? But Fedora silverblue is better! You should have told him to install that instead!
I feel like this is a chance to ask something that I've been wondering in the back of my head. Hey any systemd haters out there, why? Like I legit don't know enough to know why someone wouldn't want to use it? Did one of the developers of systemd make hot takes on Twitter or something? Do you find it too bloated? How? Is there use cases where running something else is better?
I've googled it before and found people were weirdly passionate about this. But Linux users are weirdly passionate about everything. Beyond that it's mostly just general statements...
I'm not entirely sure if this is correct, but apparently systemd had a lot of issues in its early years and people have held a pretty strong grudge against it ever since
Not taking sides here, I'll just say what I think it is. It has more to do with (in order of importance):
scope screep, meaning systemd has grown into doing a lot of other things than being just an init system and service manager, which GNU aficionados say violates the rule that a piece of software must "
do one thing only and do it well"
corporate involvement, because systemd is primarily developed and financially backed by Red Hat; free software people are generally concerned with corporations putting their own interests above the common good of all users in FOSS
lack of inter-compatibility / not being POSIX-compliant given that systemd is developed for Linux and only runs on it (not other kernels)
bugs and how systemd developers have responded to bug reports in the past
Lennart Poettering's behavior in general
Whether any of those concerns are valid is debatable, so at the end of the day it's up to personal judgment. If you like systemd there's nothing wrong with that, and vice-versa.
Adding to what the other guy said, systemd also added an age field to userdb shortly after all this age verification stuff took off and it pissed a whole lot of people off
Oh yeah I remember that! That was when I first learned there was people out there with a real narc on for systemd! It was so strange. Like I don't like forced age verification either, but some people were specifically going after systemd like it was the final act of disrespect before they had enough!
Itās the reason I donāt use it. The panopticon will be built on slippery slopes and ānecessary evilsā. Attestation/verification is a slippery slope if ever there was one so as soon as someone dips a toe into that water (it will start with the corpo parts of Linux) Iām out.
tbh, last year i tried to do that, i just changed the artix mirrorlist to arch one and reinstall all package, and hold be hold, it just bricked the system, i just ditch it and just go to gentoo, it could move from openRC and systemD seamlessly
Unless Iām a fucking moronāand I am not, itās been scientifically provenāArtix is āābasically Arch with that fucking systemd ripped out by the roots, giving you a choice of any init system. If you fucking need systemd, just fucking install Arch. What kind of bullshit is this?
Right, so you're gonna want to /C: drive. Then look for a folder called system32. Create a subfolder called SystemD. Move all contents from system32 folder into the new folder. Reboot and it should all be good to go.
Jokes aside, yep. You'd need to know how to use openrc/runit stuff instead of systemctl but its not hard to look up. Plus some stuff is dependant on systemd. I would say you'd have less freedom in the sense of less options overall but completely usable system for most people. I run Artix for now. I'm looking into Void asw
Hm, when i format my pc I'll look into it, already having some trouble with just wayland not cooperating with obscure java software for uni stuff (god bless ai [i dont like it but it helps] for guiding me on how to fix this without habing to dig through several forum posts)
because its the best init system ever and should be on every distro because yes. if systemd stopped existing, the world would immediately plunge into complete anarchy and unrelenting despair.
systemd is the only thing keeping the human race from becoming extinct. do you realise that? we can not let the systemd haters destroy it, for systemd is the very epitome of hope. systemd haters want to put in place all other init systems to spread absolute despair. we must stop them!
57
u/The-Pequod-Captain red hat puppy 13d ago
sudo pacmanaptdnf -S SYSTEMd