Red Star has a banger of a driving game.
https://www.youtube.com/watch?v=B0WhdhbImLM
If it really watermarks USB drives then Jucheism is cancelled
I never found Arch installs all that difficult, but if you accidentally skip a step it can take days of figuring out what's wrong.
Honestly the hardest part of my Arch install was the fucking wifi card nonsense. Couldn't get it to recognize the card for the longest time, but now that I have it runs like a dream. All of my movies through Plex get transcoded faster and it's so stable and :chefs-kiss: Arch on a Thinkpad is a dream.
Fuck Arch, Gentoo is easy, universal, understandable and logical. Why should beginners have to mess around with ramdisks and systemd when most casual users don't need it?
Can you give a concrete example of a complicated task that's hard in systemd but easy in initd? I've never actually heard of one given although everyone complains about them.
From my standpoint, the average user doesn't interact with systemd or initd beyond spinning up services installed via the package manager. So this whole spat is isolated to power users and admins. The most complicated systems script I wrote myself was a mbsyc service on a timer.
I am the average user and not a power user. I prefer the initd system by far because it's basically impossible to break and very simple. I've run into systemd bugs too many times to ever use it again.
I'm sure you can break the init system if you tried...
Its just really telling to me that everyone who gives non-ideological complaints about systemd are never specific about the issue. Like are you sure it was a systems bug and not a bug with whatever service? Or maybe your weren't using it right?
Because systemd is basically everywhere in a Linux system, I suspect its falling victim to a simple pattern:
- Something breaks somewhere in your system
- Systemd is always involved in the system that broke because its involved in everything.
- User concludes systemd is bad because it has a 100% correlation your systems bugs even if it wasnt the culrpit.
emerge -e worldis a good way to heat your home and run linux at the same time.I'd like to interject for just a moment. What you're referring to as GNU/Linux is actually just one free component of a fully functioning systemd system.
It tries to do a lot in a very centralized way and (initially) didn't have many devs so it was kinda risky.
Because it does so much and is centralized, making something that works with it can sometimes be quite the pain. Some init systems just require you to write a script, for example. One little file. systemd requires at least its own special service file and if you want to do anything more complex there are 5-10 subcomponents you might have to study for a while before you can begin.
I think it's a good direction, though. I'd much rather see iterations on this one central system where you can find/edit/start/stop/log services than fight with some random hackneyed init system.
BROKE: Getting mad at systemd
WOKE: Getting mad at pulseaudio and pipewire.
Systemd unit file are not so hard to write really and are much more robust than older script systems, which are usually held together with tape and do not handle failure well. They were always one of the worst design choices of UNIX and are extremely fragile, to order especially. Systemd also keep a central state for services, which is very logical and necessary to manage services to modern standard.
Yeah I've written a few they're not so bad. But it is one of the things people complain about.
I managed to set up Arch by myself once, but after that I just switched to using installers instead. I'm not going to go through the hour long process (assuming you don't make any mistakes) of making a LUKS2 encrypted btrfs partition again.
I'm curious, why did you use veracrypt rather than something like LUKS?
Edit: I just realised that I mixed up the words, yeah I used LUKS2, I just mixed up the names.
I'll edit the original comment.
The things you can do with LVM and device-mapper are jaw dropping, but issuing so many commands that deal directly with disks and partitions and volumes and filesystems makes my ass so tight you couldn't pull a needle out of it. Anyway, I've never tried LUKS, but I did just set up an SSD cache for my 3TB HDD using lvmcache.
LUKS is fairly easy to setup on its own. Everything is done through the
cryptsetuptool.- format a device with
cryptsetup luksFormat /dev/sdX - open with
cryptsetup luksOpen /dev/sdX myContainer - new device is available under
/dev/mapper/myContainer
Linux will treat the opened container as a new disk so you can give it a file system or create a lvm device out of it. You can even have an LVM volume contain a LUKS container which contains another LVM volume group, etc.
The hard part about LUKS is getting your system to open it on boot. For that refer to the archwiki.
Right, that makes sense. I've managed to avoid building an initramfs by only using LVM for /home and leaving / as a regular btrfs partition, but you certainly do enter the "keys are locked inside the car" situation when you're trying to load the modules for encrypted filesystems from an encrypted filesystem.
Changes to the initramfs are easy and well documented. Just edit
/etc/mikincpio.confand runsudo mkinitcpio -p linux.The hard part is telling your bootloader to use the luks module you added to the initramfs. It changes depending on your bootloader.
- format a device with
