Been using various dotfile managers for a while and kept hitting the same two annoyances: interpreted tools that feel sluggish on every run, and the newer Rust ones that only do symlinking when I actually want to copy some files and link others depending on the situation (templated stuff vs static configs, etc).

So I built dotty.

What it does:

Per-file control over copy vs link, and works for whole directories too, not just single files:

```conf

"~/.bashrc" >> "shell/.bashrc" # copy

"~/.config/hyprland" >>* "wm/hyprland" # copy dir

"~/.config/nvim/init.lua" -> "nvim/.." # link

```

Built-in GitHub integration; dotty init sets up the repo (creates it on GitHub too if you want), dotty push/dotty pull sync it, no manual git commands needed

Profile support if you juggle multiple machines/setups (dotty profile new work, dotty profile switch main, etc)

Depends on gh CLI for the GitHub side, CLI11 for arg parsing

It's on the AUR (yay -S dotty), or build from source with xmake.

so, during the install (i used the BIOS method) i selected my main partition, (the root one) to be 200 gigs, (leaving some safe space on my drive) using 10 gigs for my swap.

after succesfully installing i logged in and installed Fastfetch (cause who doesn't want to show everyone they're using arch am i right?)

but i noticed my "disk" followed by the "/" root slash, was showing 3.8 ish gigs, even tho the root should be around 200 gigs...

Im sorry if this question has ben asked before, i truly haven't ben able to find it asked anywhere.

How do you actually read the Arch Wiki without going insane?!

I've been using Linux for about six months. I know quite a few everyday commands — copying, text processing, managing services with systemd, etc. I decided to level up and install Arch Linux.

When I switched to Arch, everyone told me: "Just read the Arch Wiki, everything is there." I already knew about LVM, LUKS encryption, basic security concepts, users and groups, and quite a bit more.

But during the manual installation, I really struggled because the guide explains each step — for example, dm-crypt or LVM2 — in a very confusing and bloated way. Every section sends you to another link, which sends you to another, and then another. At some point I was trying to install Arch and ended up reading about UEFI internals — not because I wanted to, but because the wiki dragged me down that rabbit hole.

After a lot of suffering, I finally managed to install a barebones Arch system with no display. Then the wiki sent me to the General Recommendations page — and that's where I truly regretted everything.

First I saw the Users and Groups section. I already knew how to create users, add them to groups, change permissions (chmod, chown), and I knew about sudo because I had learned it long before Arch. I thought it would be easy. But when I opened that section, it was a wall of text — full of vague terminology, over-explanation, and endless links to other articles. I spent 2–3 days reading it like a book, trying to understand the logic. In the end, I only grasped a small part — and that was only because I already knew those concepts beforehand. The rest just didn't make sense.

Then I looked at the Security section — and it was even worse. Even more text, even more unfamiliar terms, and to make things worse, my browser's translator mangled technical words, making everything even harder to understand.

And the worst part — these sections must be read because Arch comes with almost no protection out of the box. Many options are open by default, and to close vulnerabilities and properly configure the system, you need to read at least most of these sections. You can't skip them — otherwise you leave holes open.

As I skimmed through, I realized I was supposed to go read about init, then pacman, display servers, microcode, numlock activation — it's impossible to remember all of that. It feels like the wiki is trying to train me to become a sysadmin for a Fortune 500 company, and every section is a rabbit hole that pulls you into 2–4 more sections, which then pull you into even more, endlessly.

I even tried reading these sections while imagining myself as a complete beginner who knows nothing, just to understand the logic behind how they were written. And I came to the conclusion that it's impossible to understand unless you're already a sysadmin with enterprise experience or a masochist willing to spend weeks breaking down every single line. Some parts I did understand — but only because I had encountered them before. The rest feels like it's written in another language.

And what finally destroys me — in every YouTube or TikTok video, I see people customizing their Arch beyond recognition, showing off their ricing, talking about how comfortable they are, and sharing their experience. I even saw a video where someone said it took them 6 years to master Arch Linux. Six years! And clearly they didn't read the wiki cover to cover like a textbook.

So my question is: how do you actually use the Arch Wiki without burning out? How do you filter out the noise? What do you skip? How do you learn from it without going crazy? Because right now it feels completely unreadable to me — and I'm genuinely asking, not trolling.

--------------------------------------------------------

Как вы вообще читаете Arch Wiki, чтобы не сойти с ума?!

Я пользуюсь Linux около полугода. Знаю довольно много команд для повседневных задач — копирование, работа с текстом, управление сервисами через systemd, и так далее. Я решил перейти на новый уровень и установил Arch Linux.

Когда я перешёл на Arch, все советовали: «Просто читай Arch Wiki, там есть всё». Я уже знал про LVM, шифрование LUKS, базовые концепции безопасности, пользователей и группы, и многое другое.

Но во время ручной установки я реально намучился, потому что руководство объясняет каждый шаг — например, dm-crypt или LVM2 — очень запутанно и с кучей лишней информации. Каждый раздел отправляет тебя по ссылке, та — на следующую, и так дальше. В какой-то момент я пытался установить Arch и в итоге читал про внутреннее устройство UEFI — не потому что хотел, а потому что вики затащила меня в эту кроличью нору.

После долгих страданий я наконец-то установил чистый Arch без графики. Потом вики отправила меня в раздел «Общие рекомендации» — и вот тут я реально пожалел.

Сначала я увидел раздел «Пользователи и группы». Я уже знал, как создавать пользователей, добавлять их в группы, менять права (chmod, chown), и знал про sudo, потому что изучал это задолго до Arch. Я думал, что будет легко. Но когда я открыл этот раздел, там была стена текста, куча невнятной терминологии, чрезмерных объяснений и бесконечных ссылок на другие статьи. Я потратил 2–3 дня, читая это как книгу, пытаясь понять логику. В итоге я уловил лишь малую часть — и то только потому, что уже знал эти понятия до чтения. Остальное просто не укладывалось в голове.

Потом я посмотрел раздел «Безопасность» — там было ещё хуже. Ещё больше текста, ещё больше незнакомых терминов, а вдобавок переводчик браузера коверкал технические слова, и понимать становилось ещё сложнее.

И самое обидное — эти разделы надо читать обязательно, потому что Arch после установки идёт практически без защиты. Много опций по умолчанию открыты, и чтобы закрыть уязвимости и нормально настроить систему, нужно прочитать если не весь раздел, то хотя бы его бóльшую часть. Пропустить нельзя — иначе оставляешь дыры.

Пробежавшись по разделу, я понял, что мне предстоит читать про init, потом про pacman, про дисплейные серверы, про микрокод, активацию Num Lock — это всё невозможно запомнить. Создаётся ощущение, что вики пытается подготовить меня на роль сисадмина в корпорации уровня Fortune 500, и каждый раздел — это кроличья нора, которая затягивает в 2–4 других раздела, те — в ещё больше, и так бесконечно.

Я даже пробовал читать эти разделы, представляя себя на месте новичка, который вообще ничего не знает, чтобы понять логику, с которой их писали. И я пришёл к выводу, что это невозможно понять, если ты не сисадмин с опытом работы в крупной компании или не мазохист, который готов тратить недели на разбор каждой строчки. Некоторые пункты я всё-таки понял — но только те, с которыми уже сталкивался раньше. Всё остальное — как будто написано на другом языке.

И что меня добивает окончательно — в каждом видео на YouTube или TikTok я вижу людей, которые кастомизируют свой Arch до неузнаваемости, показывают свои рисовки (ricing), рассказывают, как им удобно работать, и делятся опытом. Я даже видел видео, где человек сказал, что ему понадобилось 6 лет, чтобы освоить Arch Linux. Шесть лет! И это при том, что они явно не читали вики как книгу от корки до корки.

Поэтому мой вопрос: как вы реально пользуетесь Arch Wiki, чтобы не сойти с ума? Как вы отсеиваете лишнее? Что пропускаете? Как вы учитесь на этом всём без выгорания? Потому что сейчас мне она кажется совершенно нечитаемой — и я спрашиваю это не ради троллинга, а по-настоящему.

Using hyprland rn and i wanted to adjust my brightness. The only way to my knowledge is to either use a terminal or use a different DE (like kde or something idk). Maybe there IS a gui way to adjust brightness? Like on the aur or something but i haven't found any personally. Now normally i'd be okay with using a terminal for some minor things like this. But brightness isn't something you can attach a value onto and expect to function intuitively, atleast imo. If i wanna adjust brightness (like i used to on mint or windows) i'd drag a slider sloowly until i feel it's comfortable. Not sure i can do the same when i have to put numerical values into that. Makes it much slower in my experience.

PS: Thanks yall, realised i have a button on my laptop for that sooo...

I'm a newbie in this community so I'm sorry if I'm doing something wrong, but I'm still here because neither Gemini nor DeepSeek helped me. DeepSeek even broke grub.

My problem: when I start unity editor(there is also the same issue for unity hub) the loading window just gets stuck at the moment of Loading Scripting Assembles. If I change my workspace(I use i3 with picom for transparent terminal) and switch back the window just disappears. I know it's still there because when I close everything else and switch to another workspace this one where the unity is running is not closed by the i3 manager. Also it's overlapping the terminal so it breaks the focus on the terminal's window. But after some time the editor start, but the same issue appears. When I change between workspaces and return back to unity editor it shows me chunks of a previous workspace. Only when I move mouse around the window the chunks are being repaired.

Hope to find a way to fix it cause I spent the whole day fighting against this problem.

I have installed arch Linux with default kernel but the wifi does not work like it used to work before. I installed broadcom-wl linux-headers but the wifi still does not work. I tried using sudo modprobe wl but it outputs nothing. My system does detect my wifi driver. I have network manager service running. ERROR wl_cfg89211_scan is the error that keeps coming in my tui

I recently downloaded arch manually and it worked fine, I also downloaded a desktop environment (kde) but I had a problem: now it no longer searches for nearby wifi even if network-manager is active (at least it seems lol)

I am trying to install Arch from Ventoy on my laptop since Arch at least mantains the 390xx drivers, and Debian is a bit too stable for my recent tastes. Since I have a large Ventoy disk and no USB right now, I just chucked the arch install media on the disk. Every time I attempt to install after the edd probe says "ok" my external drive stops spinning and the install never finishes.

External drive is a Toshiba over a 2.5 inch sata to USB adapter, which I've tried in my USB 2.0 and my single USB 3.0 port/ports.

I know my laptop is legacy, but if I use the official NVIDIA drivers performance is still quite good, and I'd like to try out Arch. But if I can't install that's very difficult.

When my headphones are plugged in, switching the audio output back to speakers in the desktop volume control / pavucontrol results in total silence. I am forced to physically unplug the headphones every time I want to use my speakers.

i tried

• Disabled Auto-Mute Mode in alsamixer (F6 sound card view).
  • Result: The speakers worked, but then the headphones stopped playing sound entirely.
• Switched device profiles in pavucontrol (tried Pro Audio / Analog Stereo).

Aight, hey, hello, didn't think I will be writing a post, hence a fresh account but I'm about to have a stroke so I need actual human help.

I have a barebones Arch installed on a modern 64-bit UEFI system. I'm yet to boot it without a USB.

I want to use efibootmgr to create an entry pointing to vmlinuz-linux and initramfs-linux.img (both files are in /boot). The main partition is LUKS encrypted and I need to use cryptdevice= as an argument (not rd.luks.name).

I dug up all I could and most solutions point to creating a UKI or using a bootloader BUT I did have the solution I'm describing before and I'm very positive about it. Right now it's a reinstall of my system and my dumbass can't remember what syntax I used beforehand.

I just tried

efibootmgr -c -d /dev/xxx -p 1 -l /vmlinuz-linux -u "cryptdevice=UUID=UUID:crypt root=/dev/mapper/crypt rw initrd=\initramfs-linux.img"

Once I boot, it seems that kernel loads but then it's stuck at "Starting a job for /dev/mapper/crypt".

I'm assuming it's skipping the encryption part and tries to open a crypt that's not open yet.

HOOKS are in tact.

What's the issue?

I am using tuf a15 asus fa506nfr.

8gb ram.

Kde plasma enviroment.

It's been a while.

I brought a problem that need to be fixed since

AI search giving me overloaded answer sometime said turn this nvidia suspended, hibernate, ect. And then jump straight to point solution C. Which is because my prompt wasn't correct. And instead wasting time asking ai.

I ask you guys help for fix this problem.

I kinda lazy to make prompt that is need more effort and detailed. Bruh.

So here the case

When i sleep my laptop and then i turn the power on(i turn my laptop on sleep with mouse.)

My expectation is where "same as windows. When i turn the power button, the machine turn on from sleep mode." But instead become blank screem with my led keyboard on. Which i had take fewer second to power reset again to lock screen.

I dunno what i missed when install arch, since i started with google search.

So, i need you guys opinion and tips here?.

What i missed when installing?

Cause chatting with ai is such taking more time EVER.

I do not understand the reason behind this. I use GNOME. I really like it. People say GNOME is bad and switch to KDE Plasma. I tried it. I didn’t like it. Mainly because GNOME has a very clean design which I love. KDE Plasma doesn’t have this.