The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
systemd is nice when it works but it's a pain in the ass when it has a tism fit. A good example is if you modify your grub entry for linux with init=/bin/bash, once you're done, if you try to reboot or shutdown via the shell, the kernel panics because of systemd and you have to power the system down.
You sure that's a systemd issue? Because I've had the same thing happen with other init systems.
 
My sample size is 1 so no :jaceknife:
Just thinking about it.

You probably need to put the root filesystem you want it to boot into, and the filesystem type. So the kernel will know what filesystem it needs to boot into. Then it can find the /use/bin/bash program to run.

All of that stuff is nornally taken care of by systemd and the initramfs (depending how you have stuff setup). I would add those to the kernel command line and see if that changes anything.
 
Just thinking about it.

You probably need to put the root filesystem you want it to boot into, and the filesystem type. So the kernel will know what filesystem it needs to boot into. Then it can find the /use/bin/bash program to run.

All of that stuff is nornally taken care of by systemd and the initramfs (depending how you have stuff setup). I would add those to the kernel command line and see if that changes anything.
My scenario was fixing something that borked my boot, so I had to get shell and fix it.
 
My scenario was fixing something that borked my boot, so I had to get shell and fix it.

Well I recommend adding these.

I obviously put your actual root filesystem and filesystem type. But add these along with the init.

root=/dev/sda1 rootfstype=ext4

See if that helps.

Just saw lunduke did another one talking about gnome and how they hate him, and the xlibre guy.


Most of it is what you would expect.

According to lunduke gnome's official stance is that "he is a dirty, dirty, evil Jew". I'm not sure why he's trying to make gnome look good all of a sudden, but I'm starting to come around to liking them.
 
Last edited:
Stalker GAMMA works well on Linux using https://github.com/Mord3rca/gamma-launcher
Just make sure you have 7zip, unrar and libunrar installed
The prefix needs winetricks -q d3dcompiler_47 d3dx10 d3dx11_43 d3dx9 cmd dxbk vcrun2019 (I'd use 2022 to get them all)
The game may crash on launch due to a bug related to a Saiga mod. To fix it, just search for the mod in Mod Organizer and uncheck any duplicates, as that’s what caused the crash for me
 
  • Informative
Reactions: ZMOT and Sake Ojone
According to lunduke gnome's official stance is that "he is a dirty, dirty, evil Jew". I'm not sure why he's trying to make gnome look good all of a sudden, but I'm starting to come around to liking them.
I disagree. The GNOME antifas are much more supporting of great replacement than any Israeli migrant NGO. Don't get fooled by their anti Israel stance, they are worse at this point. Like Sam Hyde said, "They want you killed and your children raped and brainwashed. And they think it is funny".

Indeed, Lunduke is pro Israel biased, which I don't agree with, but he is still good linux/tech reporter.
 
I've been running various distros of Fedora because it's the one I have so far liked the most.

GNOME desktop can suck a dick because who ever thought I wanted a smartphone interface on my PC? I like the Plasma KDE. But ran into a nice one today. I got the system update and it led to a Kernel error in 6.15. I suspect it has something to do with NVIDIA I have on this machine but IDK. I rolled it back and reset the drivers and I was back to normal.

I may have to go buy an AMD 9070 to play nicer with this as I mostly use my personal for games and dicking around. I have a LattePanda I am going to run Miracle on for a bit and see if I like that window manager. Or another ultralight Fedora distro.
 
  • Like
Reactions: YoRHa No. 2 Type B
But ran into a nice one today. I got the system update and it led to a Kernel error in 6.15. I suspect it has something to do with NVIDIA I have on this machine but IDK
Here is how to fix it (just updated myself so ran into same thing).
 
  • Informative
Reactions: Vesperus
If I do that, then how do I undo that?
Delete the caret ("not").

enable journal:
Code:
sudo tune2fs -O has_journal /dev/drivename

Also, I fucked that last one up, should be tune2fs, not mke2fs. In other words,

disable journal:
Code:
sudo tune2fs -O ^has_journal /dev/drivename
 
  • Informative
Reactions: ToroidalBoat
hey @analrapist (lol @ username)

So if I get this right, it is...

disable: sudo tune2fs -O ^has_journal /dev/[drivename]
enabled: sudo tune2fs -O has_journal /dev/[drivename]

... and not that earlier sudo mke2fs -t ext4 -O ^has_journal /dev/drivename thing?
 
hey @analrapist (lol @ username)

So if I get this right, it is...

disable: sudo tune2fs -O ^has_journal /dev/[drivename]
enabled: sudo tune2fs -O has_journal /dev/[drivename]

... and not that earlier sudo mke2fs -t ext4 -O ^has_journal /dev/drivename thing?
Yep.

https://man7.org/linux/man-pages/man8/tune2fs.8.html -- I double checked the man page. Apparently you need two -f flags when removing the journal because they don't want people to do it because if you've had an unclean poweroff, you can lose data.

So, then,

disabled: sudo tune2fs -f -f -O ^has_journal /dev/[drivename]

I reckon you'd probably get told this by trying your disabled command without the -f. Been a while since I've done this.
 
Let me just state for the record that turning off a filesystem journal is a Reddit tier move. Outside of some super specialized cases needing reduced latency about all it does is increase the chances of lost files in case of a system crash or unexpected power cut.
 
Outside of some super specialized cases needing reduced latency about all it does is increase the chances of lost files in case of a system crash or unexpected power cut.
I don't disagree that it's disrecommended. Write-limited contexts like flash storage show some improvements as well. That's the core of what ToroidalBoat is getting at. I agree, you usually want a journal, but turning it off does decrease writes, which is what his aim is.
 
  • Agree
Reactions: ToroidalBoat
I don't disagree that it's disrecommended. Write-limited contexts like flash storage show some improvements as well. That's the core of what ToroidalBoat is getting at. I agree, you usually want a journal, but turning it off does decrease writes, which is what his aim is.
Doesn't matter if your SSD lasts 3% longer when your system crashes and ends up with half the files in /lost+found
I mean, maybe on a MicroSD or something.

The correct solution is to monitor the smart data and see where the lifetime really is. My root/home drive on my main fileserver which also runs some databases and other containers is all the way down to 99% lifetime after 70TB written and 6 years.
 
Doesn't matter if your SSD lasts 3% longer when your system crashes and ends up with half the files in /lost+found
I mean, maybe on a MicroSD or something.
MicroSD on Raspberry Pi and other ARM rigs are the chief place I've used this. I've routinely shut these systems down by just cutting power. The concern about corruption is quite overstated, so long as you're not pulling the power while writing something you care about or during an update or something.
 
Back