#LinuxHacks #SoftwareHacks #Assemblylanguage #Bashscript #Bourneshell
Một sinh viên Tây Ban Nha đã tạo script Bash tự động hóa cài đặt và cấu hình Pi-hole v6 trên Ubuntu. Script này còn tích hợp cài đặt Unbound, PADD và tự động thêm blocklist. Tác giả muốn chia sẻ dự án để nhận phản hồi từ cộng đồng.
#Pihole #Ubuntu #BashScript #Automation #SelfHosted #Project #PiholeV6 #ScriptBash #TựĐộngHóa #DựÁn #UbuntuServer
https://www.reddit.com/r/selfhosted/comments/1q45acf/i_wrote_a_bash_script_to_automate_pihole_v6_on/
Learn how to display Animated Christmas Tree in Terminal (2026). Merry Christmas and a Happy New Year 2026 to all.
Full Blog Post Here: https://ostechnix.com/display-animated-christmas-tree-terminal/
Okay, I'm sure a lot of people already know about this one, but it's new to me. I just found out you can do one of these in your systemd service itself:
Environment=SOME_SILLY_NAME=%i
And then reference that specific variable from inside of that environment, instead of using whatever variable was already there anyway, that usually works even though it's not actually made for that.
The problem I've been running into is that X11 cares about $DISPLAY, and so usually if you're gonna reference %i from a script from within an X11 environment, you would use that and it would work; but then if you're on Wayland, that doesn't mean anything to Wayland itself, because it calls it $WAYLAND_DISPLAY instead; WHICH MEANS that if you're on a Wayland compositor to start with, but you're also running XWayland, then you have both variables set automatically.
I'm on Niri with xwayland-satellite, and so I have both (I never had $DISPLAY in Niri until after I installed xwayland-satellite). This is a huge problem because neither of those variables actually have anything to do with the systemd instance by design, and I can't just make one of them go away (without giving myself more problems). There is no variable that's ever set by default, that is specifically put there to refer to the exact same thing as %i does in the unit itself, that I know of.
Now I can just do this instead, and never have to worry about my stuff getting mixed up with my other stuff. 😀
Haskell/Rust/Bash/systemd is a good combination, right?

OK... Too much of my world runs on bashscript.
It's fine. It's a tool, I get it.
...
It's just... It's too much.
Also, stop using Go instead of bashscript.
#go #bash #bashscript #programming
I love you all.
Learn how workflow automation has evolved from simple Bash scripts to advanced AI-driven systems, boosting productivity and transforming operations.
More details here: https://ostechnix.com/from-bash-scripts-to-ai-evolution-of-workflow-automation/