I'm really liking the Ghostty terminal.

I feel over the past few years, terminals have become less customizable. In Gnome, transparency is a hidden pref! You get lots of predefined themes, but they're difficult to modify.

Recently, I wanted to rice my fastfetch output and I found only one terminal that accurately displays an image - **Ghostty**.

It's also easy to customize with just a dozen lines in a config file. (pasted below).

Anyway, if you miss being able to fine-tune the look of your terminal, give Ghosttty a try.

# Save to ~/.config/ghostty/config

window-height = "29"
window-width = "110"
quick-terminal-position = "center"
background = 000000
foreground = ffffff
background-opacity = 0.85
background-blur = true
font-family = "Intel One Mono Regular"
font-size = 14
window-padding-x = 9
cursor-style = "underline"
bold-is-bright = "true"



https://preview.redd.it/197xl9mf56ye1.png?width=2560&format=png&auto=webp&s=261ab2cafdd04110bd39c2289af64eb008f00865





https://redd.it/1kc8bn4
@r_linux

Redis is Open Source again
https://antirez.com/news/151

https://redd.it/1kcdc2j
@r_linux

TMUX user here... what's all the hype about latest Terminal Emulators?

I've been a TMUX user for years, and nothing will ever make me change. No, I don't need tabs...pshaw. I see all this hype for Ghostty, Wezterm, Kitty, etc. Is there any real advantage to using these over the default terminal that comes with the desktop I'm on? I feel like I might be missing something.

https://redd.it/1kccwv5
@r_linux

systemd-analyze blame doesn't say what you think it does

In my experience the systemd-analyze blame output is grossly misinterpreted all over the internet and it's influencing people to kneecap their systems in a misguided pursuit of efficiency.

OK, so let's say I'd like to improve the boot time of my system. Let's take a look:

$ systemd-analyze
Startup finished in 6.321s (firmware) + 529ms (loader) + 1.043s (kernel) + 3.566s (initrd) + 32.429s (userspace) = 43.891s
graphical.target reached after 32.429s in userspace.

32 seconds doesn't seem very good. Let's look at the blame output to find out the cause:

$ systemd-analyze blame | head -n5
30.021s lazy.service
4.117s sys-devices-pci0000:00-0000:00:1a.0-0000:05:00.0-nvme-nvme1-nvme1n1.device
4.117s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1.device
4.117s dev-disk-by\x2did-nvme\x2dnvme.1987\x2d3436394630373138314537303030303034393739\x2d53616272656e7420526f636b657420342e3020325442\x2d00000001.device
4.117s dev-nvme1n1.device

Oof, 30 seconds!? That has to be it! Let's see:

$ systemctl cat lazy.service
# /etc/systemd/system/lazy.service
Unit
Denoscription=a very slow service

Service
Type=oneshot
ExecStart=/usr/bin/sleep 30
RemainAfterExit=yes

Install
WantedBy=multi-user.target

$ journalctl -b --no-hostname -o short-precise -u lazy.service
May 01 08:39:31.852947 systemd1: Starting a very slow service...
May 01 08:40:01.874683 systemd1: Finished a very slow service.

Yep that takes 30 seconds alright. But is it making my "boot" time slow? What happens when I reboot? After logging in I'll check systemctl status:

$ systemctl status | head -n5
...
State: starting
Units: 347 loaded (incl. loaded aliases)
Jobs: 3 queued
Failed: 0 units

We're still starting up as I write this reddit post — lazy.service has not yet finished! That's because the userspace time reported by systemd-analyze and the startup time reported by blame don't correspond to the "boot" time at all by colloquial usage of the word: I could have logged in, started firefox, checked my email, and written this whole post before my system "booted". Instead, blame is reporting on all the tasks that systemd executes in parallel at startup time, including those that can continue to run in the background.

Crucially, many services' (e.g. udev-settle, wait-online, etc.) only explicit purpose is to wait and watch for some event to occur so that subsequent services can be started. For example, Time and time again users notice that something like systemd-networkd-wait-online.service appears near the top of the blame output and go about disabling it. This service uses event polling to be notified when a network connection is available, so that subsequently started services are more likely to complete a successful connection immediately instead of after several attempts. An alternative strategy like exponential backoff implemented as a fallback in most networked applications is much slower because you are waiting during the time when the network becomes available practically by definition. Technically you could disable this service, but that makes your observable "startup time", the time before your startup applications start doing useful work, quicker, not slower. The numbers don't matter.

Something like systemd-analyze critical-chain systemd-user-sessions could be helpful, but it has several caveats as noted in the manpage, in particular that it only tracks start jobs for units that have an "activating" state. For example, the following output:

$ systemd-analyze critical-chain initrd-switch-root.target
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the

systemd-analyze blame doesn't say what you think it does

In my experience the `systemd-analyze blame` output is grossly misinterpreted all over the internet and it's influencing people to kneecap their systems in a misguided pursuit of efficiency.

OK, so let's say I'd like to improve the boot time of my system. Let's take a look:

$ systemd-analyze
Startup finished in 6.321s (firmware) + 529ms (loader) + 1.043s (kernel) + 3.566s (initrd) + 32.429s (userspace) = 43.891s
graphical.target reached after 32.429s in userspace.

32 seconds doesn't seem very good. Let's look at the blame output to find out the cause:

$ systemd-analyze blame | head -n5
30.021s lazy.service
4.117s sys-devices-pci0000:00-0000:00:1a.0-0000:05:00.0-nvme-nvme1-nvme1n1.device
4.117s dev-disk-by\x2dpath-pci\x2d0000:05:00.0\x2dnvme\x2d1.device
4.117s dev-disk-by\x2did-nvme\x2dnvme.1987\x2d3436394630373138314537303030303034393739\x2d53616272656e7420526f636b657420342e3020325442\x2d00000001.device
4.117s dev-nvme1n1.device

Oof, 30 seconds!? That has to be it! Let's see:

$ systemctl cat lazy.service
# /etc/systemd/system/lazy.service
[Unit]
Denoscription=a very slow service

[Service]
Type=oneshot
ExecStart=/usr/bin/sleep 30
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

$ journalctl -b --no-hostname -o short-precise -u lazy.service
May 01 08:39:31.852947 systemd[1]: Starting a very slow service...
May 01 08:40:01.874683 systemd[1]: Finished a very slow service.

Yep that takes 30 seconds alright. But is it making my "boot" time slow? What happens when I reboot? After logging in I'll check `systemctl status`:

$ systemctl status | head -n5
[...]
State: starting
Units: 347 loaded (incl. loaded aliases)
Jobs: 3 queued
Failed: 0 units

We're still starting up as I write this reddit post — lazy.service has not yet finished! That's because the userspace time reported by systemd-analyze and the startup time reported by blame don't correspond to the "boot" time at all by colloquial usage of the word: I could have logged in, started firefox, checked my email, and written this whole post before my system "booted". Instead, blame is reporting on _all_ the tasks that systemd executes in parallel at startup time, including those that can continue to run in the background.

Crucially, many services' (e.g. udev-settle, wait-online, etc.) _only_ explicit purpose is to wait and watch for some event to occur so that subsequent services can be started. For example, [Time](https://www.reddit.com/r/archlinux/comments/1hclnjf/systemdnetworkdwaitonlineservice_takes_much/m1s19yp/) and [time](https://www.reddit.com/r/linux/comments/1kber3v/so_i_noticed_many_dont_know_about_the/) again users notice that something like `systemd-networkd-wait-online.service` appears near the top of the blame output and go about disabling it. This service uses event polling to be notified when a network connection is available, so that subsequently started services are more likely to complete a successful connection _immediately_ instead of after several attempts. An alternative strategy like exponential backoff implemented as a fallback in most networked applications is much slower because you are waiting during the time when the network becomes available practically by definition. Technically you could disable this service, but that makes your observable "startup time", the time before your startup applications start doing useful work, _quicker_, not slower. The numbers don't matter.

Something like `systemd-analyze critical-chain systemd-user-sessions` could be helpful, but it has several caveats as noted in the manpage, in particular that it only tracks start jobs for units that have an "activating" state. For example, the following output:

$ systemd-analyze critical-chain initrd-switch-root.target
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the

"+" character.

initrd-switch-root.target
└─systemd-tmpfiles-setup.service @2.290s +54ms
└─systemd-journal-flush.service @1.312s +957ms
└─var-log.mount @1.302s +7ms
└─local-fs-pre.target @371ms
[...]
└─system.slice
└─-.slice

shows the startup time of some units in the initrd, but completely misses that the bulk of time in the initrd was waiting for amdgpu to initialize, since its a udevd stop job that waits on this action:

$ journalctl -b --no-hostname _RUNTIME_SCOPE=initrd _KERNEL_DEVICE=+pci:0000:03:00.0 -o short-delta
[ 1.162480 ] kernel: pci 0000:03:00.0: [1002:73df] type 00 class 0x030000 PCIe Legacy Endpoint
[...]
[ 1.163978 < 0.000039 >] kernel: pci 0000:03:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[ 2.714032 < 1.550054 >] kernel: amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
[ 4.430921 < 1.716889 >] kernel: amdgpu 0000:03:00.0: amdgpu: detected ip block number 0 <nv_common>
$ journalctl -b --no-hostname _RUNTIME_SCOPE=initrd -u systemd-udevd -o short-delta
[ 1.160106 ] systemd-udevd[279]: Using default interface naming scheme 'v257'.
[ 2.981538 < 1.821432 >] systemd[1]: Stopping Rule-based Manager for Device Events and Files...
[ 4.442122 < 1.460584 >] systemd[1]: systemd-udevd.service: Deactivated successfully.
[ 4.442276 < 0.000154 >] systemd[1]: Stopped Rule-based Manager for Device Events and Files.
[ 4.442382 < 0.000106 >] systemd[1]: systemd-udevd.service: Consumed 3.242s CPU time, 24.7M memory peak.

So eliminating these services would not be faster. These commands are useful, but just make sure you actually have a problem before trying to fix it.

https://redd.it/1kcg7b0
@r_linux

Sriracha - Imageboard and forum
https://codeberg.org/tslocum/sriracha

https://redd.it/1kcdata
@r_linux

Got stuck in vi

So I have a story to tell. My phone suddenly decided to get stuck infinitely booting after usual force shutdown because of low battery. While it was failing to boot, adb was accessible. I decided to try adb shell in it. Android apparently has vi preinstalled, because of course it does. And while I was realizing I couldn't access su, I SOMEHOW typed vi and hit Enter. In one moment I realized what all these "Can't exit vim" memes were about. In one moment my ego shattered. Ctrl+C didn't work, Ctrl+Q didn't work, Ctrl+X didn't work. I was stuck. I literally had to google how to exit it. I haven't been more betrayed by Android than that.

#Step bro I'm stuck, help me exit vi

https://redd.it/1kcjrym
@r_linux

Flathub: A paradigm shift for distributing applications — Jordan Petridis at LAS 2025
https://inv.nadeko.net/watch?v=NxOH4wJkfLY

https://redd.it/1kcgnps
@r_linux

People who got photoshop to work on linux,; how's the experience?

sup y'all

this post is for people who were able to get photoshop to work on their linux machines.

what version was it, and how was the performance & stability.

I made the jump to gimp already, just curious about people who achieved this feat.

thank you in advance, <3 yall

https://redd.it/1kcr9w5
@r_linux

Which distro is stable and easy to use

Guys, I have an old pc lying in the corner of my home, we are not using it because it runs windows 7. I wanted to test whether if it's actually works. So i wanted to install a dstro that is easy to use and handle , cuz my family only uses that one for entertainment (I also want to code in it). The specs are low like 4gb ram and 256ssd. Anybody please help.

https://redd.it/1kcqoon
@r_linux

Switched from Windows 11 + WSL to Fedora 42 Workstation – 1.5 Months Later as an ML & Renewable Energy Researcher

My setup running Fedora 42 Workstation on a Legion Pro 5 with NVIDIA 4070, triple monitor setup, and fastfetch output showing my specs.

About 1.5 months ago, I made the switch from Windows 11 Pro with WSL to Fedora Workstation — first tried version 41, then clean installed 42. I used to run my machine learning models in WSL, but I realized it was time to take back control over my system: better privacy, more freedom, and a smoother coding workflow.

Here’s my experience so far as a researcher in renewable energy working mainly with large datasets and machine learning models:

Pros:

1. The Linux community is amazing. Everyone is super helpful and welcoming — you always get support, and it makes you feel at home.
2. Privacy is significantly better.
3. Freedom! No more Microsoft watching, collecting data, or nagging me to pay for licenses.
4. Performance boost: My code runs faster now compared to WSL.
5. Customization: I can tailor my desktop exactly how I want it — way more flexibility than Windows.

Cons:

1. NVIDIA support still needs work.
2. dGPU issues: I can’t run on the discrete GPU alone — the system crashes every 30–60 minutes unless I use hybrid mode.
3. Multiple monitors with mixed refresh rates: My built-in screen runs at 240Hz, but my 24" and 27" externals are 120Hz and 170Hz. Unfortunately, they don’t feel as smooth as they did on Windows — everything feels like it's running at 60Hz. dGPU mode made them smoother, but led to instability/crashes.
4. Battery drain on suspend: On Windows 11, I could close the lid and barely lose any battery overnight. On Fedora, the battery drains much faster during suspend — this seems to be common across many Linux distros, especially with hybrid graphics.
5. Hardware customization: I miss the manufacturer-specific software for fan control, overclocking, and RGB — more vendors need to support Linux.

Final Thoughts:
If you care about privacy, performance, freedom, and being part of a fantastic open-source community, I highly recommend switching to Linux. No more ads, telemetry, or licensing headaches — and the system is truly yours.

That said, if you're a multiplayer gamer, Windows is unfortunately still your best option for now. Most anti-cheat systems don’t work reliably on Linux, if at all. That’s the only real reason I see to keep using Windows in 2025.

https://redd.it/1kcuh10
@r_linux

Owen Le Blanc: creator of the first Linux distribution
https://lwn.net/Articles/1017846/

https://redd.it/1kcuvwb
@r_linux

Any OneNote alternatives in linux?

I tried fedora KDE Plasma for a week to get used to it (dual boot). Now i wanna change my full system to linux. I was checking all the apps i use, assuming if any one my workspace will be gone to hell and well my personal notes are in onenote. I love to just free form my notes around, draw on them and i think onenote is the best for that. Unfortunately there is no OneNote support in linux. So any alternatives or if i just use OneNote browser as a shortcut in desktop or use wine for onenote desktop. Help :)

https://redd.it/1kcw4mq
@r_linux

Easy Wi-Fi control from terminal for Linux

I built this app for my own problem, because when I work on my laptop, I need to switch access points sometimes. And doing so with default tools of Linux is over-complicated and time-consuming.

So I thought that it will help some people too and I wanted to share it. The main goal for this project was to be genuinely easy to it.

>Check it out in Github:

>https://github.com/Vistahm/ewc

https://redd.it/1kcwnzz
@r_linux

Should I make the switch from windows to linux

I am a developer and I'm very familiar with linux. My machine at home is a Windows desktop and I am kinda hesitating to make the switch to linux because of the Amazing ease it brings when I need to program. However, I also use my machine machine for gaming when I don't have to work or when my work is done. But is linux 100% gaming ready? is it safe when we look to compatibility?

I read online that not all games are playable because of the anti-cheat software it comes with. In my case I play a lot of Call of Duty: BO6 wich has a ricochet anti-cheat. Will this be compatible in the near future? Is there a workaround except dual boot?

I'm really curious what your thoughts are about this situation. Do you use linux for your private machine and/or gaming. Do you recommend the switch? Let me know! :D

https://redd.it/1kcxx05
@r_linux

Daily OS marketshare in Finland: April 2025
https://redd.it/1kcznbd
@r_linux

Mint and De's (Wayland?)

Hi guys,

I'm a Mint user, I know some people like it some people hate it but to me it just do what it's meant to do. No bug, never had big issues, well-supported by community.

As I'm a lover of breaking and experimenting I was wondering if I could change my Mint DE with something more light-weighted.

I like Cinnamon but I can see it slow performance a bit, expecially for gpu and gaming.

I'm trying Wayland (experimental) but I cannot see difference with Cinnamon and I read it does not increase pc performance (Anyway it solved my laggy logitech Mx Master 3s for some reason).

I've a full AMD Desktop pc (R5 2600,RX6600XT 8GB, 16GB Ram), my main use is gaming and editing (video/photo) for fun, aaand breaking my distro as well.

So: Should I try other DE's or change distro at all?

Main goal: Lightweight my distro as much as possible but still customizable and usable (Not gonna use Arch!)

https://redd.it/1kd2f1o
@r_linux

Installed Mint on my aunt's laptop
https://redd.it/1kd47ex
@r_linux

I told my dad I wanted to try out Linux and he gave me this
https://redd.it/1kd55a2
@r_linux

Am I the only carzy person here? Or do I have any Slackware friends here?

I installed Slackware in 1995 and while I had some idea what I was doing coming from a *nix background, Slackware is a different beast.
I fell in love with it and kept running it. I have tried different distros over the years, but since around 2010 I've been running Slackware on my main computer.

I see very little love for this wonderful distro here. I can't be the only one.

Edit: Damn, it! Crazy. Not carzy.. Carzy, what is that?

https://redd.it/1kd60lq
@r_linux