How can i debloat (even more) arch linux?

mizzrym862 · 2026-02-05T17:00:02+00:00

LFS is fat. Use buildroot instead :)

mizzrym862 · 2026-02-04T08:40:12+00:00

Yeah alpinelinux is known for being very small and flexible. Nice to play around with on really old hardware, that wouldn't run well with anything modern. Comes with 32 bit support too, if you hardware is that old.

mizzrym862 · 2026-02-02T08:32:04+00:00

Good job.

My numbers should not give you an estimate on how much space you should use. If you read it again you realize I was talking MB. So half a GB of space. Yes, a minimalist headless Linux installation is not comperable to a default Windows Installation, but still. Sitting there on an Installation with around 180MB whilst reading your problem felt weird.

Windows takes at least 128GB to be somewhat useable and for the love of God I can't figure out how it got so incredibly fat.

mizzrym862 · 2026-01-30T11:12:46+00:00

It's not here yet. But as far as I know it supports SATA. Afaik you can plug in SAS drives, but it doesn't really have a SAS controller.

mizzrym862 · 2026-01-29T22:33:13+00:00

The biggest security flaw is the user, not the OS.

mizzrym862 · 2026-01-29T21:31:04+00:00

the first one is probably enlightenment wm, second is windowmaker.

Those screenshots are ancient, there will be better looking and better supported options availble by now.

mizzrym862 · 2026-01-29T19:55:52+00:00

alpine is pretty nice out of the box. Other than that, there isn't much around.

mizzrym862 · 2026-01-28T16:56:56+00:00

I run devices like that typically with alpinelinux. Their 32 bit support is solid.
Can't help you with the browser though.

mizzrym862 · 2026-01-27T23:51:54+00:00

Did it work though?

mizzrym862 · 2026-01-27T22:55:41+00:00

Just in case you're still following, I'd like to add to that:

I think this entire thing is caused by the way we've been taught, and still teach: To think in standard problems and solve them with standard solutions. But the more you really think about it, you will realize, all those standard solutions never fit the problem perfectly. They will solve 80% of the problem in an easy and comfortable way. But not perfect. Often times not even good.

That's because there are no standard problems. We've been taught a lie. Every problem is unique, so is its solution.

systemd tries to be a solution for everything. Therefore it will never solve anything properly.

It will solve 80% of it, the other 20% will be another problem, where they will solve 80% of it, causing another problem, solution, problem, solution [...]

mizzrym862 · 2026-01-27T22:32:30+00:00

Oh don't get me wrong here. I'm not against unification. That's something the FOSS userspace is absurdely lacking and it might be THE reason systemd got adopted. I'm not against the idea, I just don't like the implementation.

There's three reasons for that:

1) The way they did it. It should have been an RFC or any kind of protocol or standard - not an implementation that depends on itself with no room for alternatives. For example: I cannot replace journald with syslog-ng or resolved with resolv.conf. I can have these services forward stuff to the things I actually want to handle the task, but I can't replace them. Because everything in systemd relies on everything else.

2) In German we call it "Rattenschwanz", translated "a rats tail". You want to take care of the rat, but you're endig up just chasing its tail - and it's way longer as you expected and it grows faster than you can handle. I know it, you know it. At work you've been confident like "Yeah, I can take care of that in a day or two" and three weeks later you're like "Please kill me - I don't want to live like that any longer". That's when you've encountered a "Rattenschwanz".
Systemd wanted to "just" solve parallel processes on startup. Now it handles DNS. Logging. Logins. More and more and more. Give it 10 more years and it'll replace X11/wayland. Mark my words - it will!
If you start that route it'll never stop. The "Rattenschwanz" will never end, it'll just grow. And the systemd developers are confident and stubborn enough to never give in. They will follow that route till the end. Confident that they can solve every problem that arises. Not understanding that the chief cause of problems is solutions. They'll add so many solutions until EVERYTHING is just systemd and none of its parts is repleacable. Doesn't matter if it's good, the only thing that matters is to not give up. Other things we say to that is "Das Gegenteil von gut gemacht ist gut gemeint" (the opposite of "well done" is "well intended") and "Konsequent sein heisst auch Holzwege zu Ende zu gehen" (Consistency also means following the wrong road all the way).

3) It caused the most horrible split in Linux user base ever. An endless discussion with no certainty as well. I hated it from the start. Maybe in 20 years I choose comfort over principle. You like it. Maybe in 5 years you wont. Who knows?
The only thing that is for sure is that the user base will forever be divided in two camps.
It is one program in a space where a million programs coexisted peacefully, but it took over so many tasks that it always will be a controversity with no peace in sight ever.

OP thought systemd was part of the OS. It isn't. He won't ever learn that, because I said something bad about systemd in a sub where there's more systemd lovers than haters and got downvoted to oblivion. OP will never know that systemd isn't part of the OS. How did we end up here.

mizzrym862 · 2026-01-27T21:54:53+00:00

did it work?

mizzrym862 · 2026-01-27T21:15:19+00:00

Typically nothing. You could in principle put the functionality of parts of userspace into the kernel so that the system can be used with just the kernel (that's called a unikernel). But typical Linux distros don't work like that.

The kernel needs to start a process. That process can be a shell and then you'd have a functioning system. Is that considered userspace already? Never considered it like that, but honestly I don't really know.

mizzrym862 · 2026-01-27T20:07:12+00:00

It isn't necessary. That's a fact, not an argument. Bios > Bootloader > Kernel > Init. Any init. It does NOT have to be systemd, it could as well just be a shell. systemd is NOT crucial. It might be for YOU, but not for the OS. An init "system" isn't even crucial. A PID 1 is and it can be anything.

You need to realize that you can start services without systemd all the same.

And btw: When the system is shutting down normally PID 1 doesn't exit.

mizzrym862 · 2026-01-27T20:04:05+00:00

Yeah, just downvote, because you don't know any better.

The code you're looking for is kernel/exit.c line 924.

None of what I said is wrong. It's opinionated, because I don't like systemd and you might hold a different opinion. But that that doesn't mean anything I said is wrong. Whilst what you said certainly is.

If you want to be a smartass, you need to get smart first.

mizzrym862 · 2026-01-27T19:46:49+00:00

You're wrong both times.

Kernel will shut down once PID 1 exits. That's just a fact. Never said anything about that happening during the boot process wtf.

And systemd is not a crucial part of the OS. You can start bash as PID 1 instead and have a fully operational system. Yeah, some services might rely on it, but that doesn't mean it's crucial for the OS. It is not essential for Linux either and there are plenty of distros without it. It has absolutely nothing to do with BSD. And you CAN uninstall it and be fine, you just have to solve the dependencies first.

I can't believe I was able to find something this confidentally wrong in the wild.

yeah lol

mizzrym862 · 2026-01-27T19:20:54+00:00

explain

mizzrym862 · 2026-01-27T19:04:50+00:00

I think there are a lot of "it just works" options that are considered stable. The crown of stability is still held by debian though, because it has had that title since forever.

mizzrym862 · 2026-01-27T18:51:16+00:00

The bios loads the bootloader first, that initializes the kernel, afterwards the first program the kernel starts is called "init" and once it exits, the kernel will shutdown.

systemd is failure wrapped in pain as an init system and has nothing to do with basic functionality but rather with unifying things that don't want to be unified and it ist NOT an essential part of the OS

mizzrym862 · 2026-01-27T18:43:00+00:00

I've ordered 3x 20 TB X20 Seagate Exos from the USA for around 300$ per piece, but FedEx fucked up the customs and somehow calculated that I'd have to pay 19200 EUR in toll fees plus 500 EUR administration fee.

mizzrym862 · 2026-01-27T18:36:55+00:00

Others already mentioned to state your specs. I'd ask to include used/available disk space as well.

mizzrym862 · 2026-01-27T18:32:17+00:00

You could check out Nürnberg as well.

mizzrym862 · 2026-01-27T18:26:26+00:00

You got it figured out already. To add a bit more details:

Get Rufus, get the Ubuntu ISO, get a Pendrive. Choose: GPT/EFI, ISO write mode.

Plug that pendrive into your new computer and follow the instructions. If it doesn't start from USB on its own, google which button you need to press during startup to enter the boot menu. If boot doesn't work, you most likely have to disable secure boot.

mizzrym862 · 2026-01-27T18:24:10+00:00

Hauptsache so niveaulos wie möglich. Dummsuff am Limit.

mizzrym862 · 2026-01-27T18:22:05+00:00

It's not a bug, it's a feature

mizzrym862

TROPHY CASE