home.social

#shellscript — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #shellscript, aggregated by home.social.

  1. 🐧💻 Ah, behold! A miraculous shell script that supposedly transforms your humble #Linux box into an all-powerful #LLM agent, streaming and mentoring like a tech-savvy #Yoda. Because who needs modern conveniences like Node or npm when you can #curl your way to enlightenment? 🌀 Just make sure you're running it on your grandma's 1995 Alpine container, because why not? 🤦‍♂️
    getclaw.site/#demo #shellscript #tech #enlightenment #HackerNews #ngated

  2. 🐧💻 Ah, behold! A miraculous shell script that supposedly transforms your humble #Linux box into an all-powerful #LLM agent, streaming and mentoring like a tech-savvy #Yoda. Because who needs modern conveniences like Node or npm when you can #curl your way to enlightenment? 🌀 Just make sure you're running it on your grandma's 1995 Alpine container, because why not? 🤦‍♂️
    getclaw.site/#demo #shellscript #tech #enlightenment #HackerNews #ngated

  3. 🐧💻 Ah, behold! A miraculous shell script that supposedly transforms your humble #Linux box into an all-powerful #LLM agent, streaming and mentoring like a tech-savvy #Yoda. Because who needs modern conveniences like Node or npm when you can #curl your way to enlightenment? 🌀 Just make sure you're running it on your grandma's 1995 Alpine container, because why not? 🤦‍♂️
    getclaw.site/#demo #shellscript #tech #enlightenment #HackerNews #ngated

  4. 🐧💻 Ah, behold! A miraculous shell script that supposedly transforms your humble #Linux box into an all-powerful #LLM agent, streaming and mentoring like a tech-savvy #Yoda. Because who needs modern conveniences like Node or npm when you can #curl your way to enlightenment? 🌀 Just make sure you're running it on your grandma's 1995 Alpine container, because why not? 🤦‍♂️
    getclaw.site/#demo #shellscript #tech #enlightenment #HackerNews #ngated

  5. 🐧💻 Ah, behold! A miraculous shell script that supposedly transforms your humble #Linux box into an all-powerful #LLM agent, streaming and mentoring like a tech-savvy #Yoda. Because who needs modern conveniences like Node or npm when you can #curl your way to enlightenment? 🌀 Just make sure you're running it on your grandma's 1995 Alpine container, because why not? 🤦‍♂️
    getclaw.site/#demo #shellscript #tech #enlightenment #HackerNews #ngated

  6. Hacked up a new script to update multiple repositories (or just the one) non-destructively. Doesn't handle all use cases, of course, but useful for a lot of general cases. It stashes any currently uncommitted work, and updates multiple branches---which can be specified as arguments.

    github.com/sanjayankur31/100_d

  7. Just wrote a new blog post: The power of Bash and Awk, about making a real (if simple) static site generator in only 24 lines of #ShellScript nosycat.notimetoplay.org/pmwik

  8. Would you like to get more out of bsddialog(3)?
    BSDCan has a tutorial for that:

    Introduction to TUI Programming using bsddialog with Benedict Reuschling
    Thursday 2026-06-18: 13:00 - 16:00

    Shell scripts have a bad reputation when it comes to usability and eye candy. Modern users find a blinking cursor on a a black screen leaves a lot to be desired when having to interact with a shell script. In this tutorial, we will create shell scripts that look like a GUI application: with buttons to press, input fields, select boxes and animated progress bars. These so called TUI (text user interfaces) programs still use shell script functionality as the backend, but are lightweight enough to not introduce too much overhead. Users will appreciate the ease of use of your shell scripts and you can rely on them to give you the data and visualizations you to need. At the same time, the TUI application is not difficult to learn and implement into existing scripts.

    More info:

    bsdcan.org/2026/timetable/time

    #unix #tui #shellscript #runbsd #bsdcan

  9. Would you like to get more out of bsddialog(3)?
    BSDCan has a tutorial for that:

    Introduction to TUI Programming using bsddialog with Benedict Reuschling
    Thursday 2026-06-18: 13:00 - 16:00

    Shell scripts have a bad reputation when it comes to usability and eye candy. Modern users find a blinking cursor on a a black screen leaves a lot to be desired when having to interact with a shell script. In this tutorial, we will create shell scripts that look like a GUI application: with buttons to press, input fields, select boxes and animated progress bars. These so called TUI (text user interfaces) programs still use shell script functionality as the backend, but are lightweight enough to not introduce too much overhead. Users will appreciate the ease of use of your shell scripts and you can rely on them to give you the data and visualizations you to need. At the same time, the TUI application is not difficult to learn and implement into existing scripts.

    More info:

    bsdcan.org/2026/timetable/time

    #unix #tui #shellscript #runbsd #bsdcan

  10. Would you like to get more out of bsddialog(3)?
    BSDCan has a tutorial for that:

    Introduction to TUI Programming using bsddialog with Benedict Reuschling
    Thursday 2026-06-18: 13:00 - 16:00

    Shell scripts have a bad reputation when it comes to usability and eye candy. Modern users find a blinking cursor on a a black screen leaves a lot to be desired when having to interact with a shell script. In this tutorial, we will create shell scripts that look like a GUI application: with buttons to press, input fields, select boxes and animated progress bars. These so called TUI (text user interfaces) programs still use shell script functionality as the backend, but are lightweight enough to not introduce too much overhead. Users will appreciate the ease of use of your shell scripts and you can rely on them to give you the data and visualizations you to need. At the same time, the TUI application is not difficult to learn and implement into existing scripts.

    More info:

    bsdcan.org/2026/timetable/time

    #unix #tui #shellscript #runbsd #bsdcan

  11. Would you like to get more out of bsddialog(3)?
    BSDCan has a tutorial for that:

    Introduction to TUI Programming using bsddialog with Benedict Reuschling
    Thursday 2026-06-18: 13:00 - 16:00

    Shell scripts have a bad reputation when it comes to usability and eye candy. Modern users find a blinking cursor on a a black screen leaves a lot to be desired when having to interact with a shell script. In this tutorial, we will create shell scripts that look like a GUI application: with buttons to press, input fields, select boxes and animated progress bars. These so called TUI (text user interfaces) programs still use shell script functionality as the backend, but are lightweight enough to not introduce too much overhead. Users will appreciate the ease of use of your shell scripts and you can rely on them to give you the data and visualizations you to need. At the same time, the TUI application is not difficult to learn and implement into existing scripts.

    More info:

    bsdcan.org/2026/timetable/time

    #unix #tui #shellscript #runbsd #bsdcan

  12. Would you like to get more out of bsddialog(3)?
    BSDCan has a tutorial for that:

    Introduction to TUI Programming using bsddialog with Benedict Reuschling
    Thursday 2026-06-18: 13:00 - 16:00

    Shell scripts have a bad reputation when it comes to usability and eye candy. Modern users find a blinking cursor on a a black screen leaves a lot to be desired when having to interact with a shell script. In this tutorial, we will create shell scripts that look like a GUI application: with buttons to press, input fields, select boxes and animated progress bars. These so called TUI (text user interfaces) programs still use shell script functionality as the backend, but are lightweight enough to not introduce too much overhead. Users will appreciate the ease of use of your shell scripts and you can rely on them to give you the data and visualizations you to need. At the same time, the TUI application is not difficult to learn and implement into existing scripts.

    More info:

    bsdcan.org/2026/timetable/time

    #unix #tui #shellscript #runbsd #bsdcan

  13. Are you looking to sharpen your Shell Scripting chops? Then you may be interested in the BSDCan Shell Scripting Tutorial for Beginners and Sysadmins with Mathias Eggers.

    Anyone who works with BSD and other Unix- and Linux-like systems will sooner or later have to deal with the shell and shell scripts, e.g. automation of repetitive task or starting services in /etc/rc.d. Understanding scripts and how to meaningfully extend or rewrite them is the goal of this tutorial, which is mainly designed for beginners and sysadmins.

    Simple shell scripts often consist of a sequence of arbitrary shell commands executed in a specific order to achieve a particular purpose. This is where the tutorial will begin, and I will then walk participants through the other components of a script using examples:

    Variables

    Sourcing

    Control structures

    Loops

    In- and output redirection

    Parameters and options

    Functions

    Testing scripts

    From the tutorial the participants will get an impression of what could be achieved with the well-equipped toolbox the shell provides and use that knowledge for creating own scripts for their projects.

    Participants should bring their own machines to try out the examples. I encourage everybody to ask questions and bring examples or problems from their daily work to the tutorial to foster a vivid discussion.

    I've been writing shell scripts as part of my work since I got in contact with Unix in 1993 and have been teaching shell programming to apprentices for over ten years. This tutorial will be a shortened and in regards to rc-scripts extended version of that one-week course.

    bsdcan.org/2026/timetable/time

    You can register for this tutorial and the BSDCan conference here:

    bsdcan.org/2026/registration.h

    If you register before May 1st, you can take advantage of the free reception on Saturday!

    #runbsd #runsh #sh #bsdcan #shellscript #Unix

  14. Are you looking to sharpen your Shell Scripting chops? Then you may be interested in the BSDCan Shell Scripting Tutorial for Beginners and Sysadmins with Mathias Eggers.

    Anyone who works with BSD and other Unix- and Linux-like systems will sooner or later have to deal with the shell and shell scripts, e.g. automation of repetitive task or starting services in /etc/rc.d. Understanding scripts and how to meaningfully extend or rewrite them is the goal of this tutorial, which is mainly designed for beginners and sysadmins.

    Simple shell scripts often consist of a sequence of arbitrary shell commands executed in a specific order to achieve a particular purpose. This is where the tutorial will begin, and I will then walk participants through the other components of a script using examples:

    Variables

    Sourcing

    Control structures

    Loops

    In- and output redirection

    Parameters and options

    Functions

    Testing scripts

    From the tutorial the participants will get an impression of what could be achieved with the well-equipped toolbox the shell provides and use that knowledge for creating own scripts for their projects.

    Participants should bring their own machines to try out the examples. I encourage everybody to ask questions and bring examples or problems from their daily work to the tutorial to foster a vivid discussion.

    I've been writing shell scripts as part of my work since I got in contact with Unix in 1993 and have been teaching shell programming to apprentices for over ten years. This tutorial will be a shortened and in regards to rc-scripts extended version of that one-week course.

    bsdcan.org/2026/timetable/time

    You can register for this tutorial and the BSDCan conference here:

    bsdcan.org/2026/registration.h

    If you register before May 1st, you can take advantage of the free reception on Saturday!

    #runbsd #runsh #sh #bsdcan #shellscript #Unix

  15. Are you looking to sharpen your Shell Scripting chops? Then you may be interested in the BSDCan Shell Scripting Tutorial for Beginners and Sysadmins with Mathias Eggers.

    Anyone who works with BSD and other Unix- and Linux-like systems will sooner or later have to deal with the shell and shell scripts, e.g. automation of repetitive task or starting services in /etc/rc.d. Understanding scripts and how to meaningfully extend or rewrite them is the goal of this tutorial, which is mainly designed for beginners and sysadmins.

    Simple shell scripts often consist of a sequence of arbitrary shell commands executed in a specific order to achieve a particular purpose. This is where the tutorial will begin, and I will then walk participants through the other components of a script using examples:

    Variables

    Sourcing

    Control structures

    Loops

    In- and output redirection

    Parameters and options

    Functions

    Testing scripts

    From the tutorial the participants will get an impression of what could be achieved with the well-equipped toolbox the shell provides and use that knowledge for creating own scripts for their projects.

    Participants should bring their own machines to try out the examples. I encourage everybody to ask questions and bring examples or problems from their daily work to the tutorial to foster a vivid discussion.

    I've been writing shell scripts as part of my work since I got in contact with Unix in 1993 and have been teaching shell programming to apprentices for over ten years. This tutorial will be a shortened and in regards to rc-scripts extended version of that one-week course.

    bsdcan.org/2026/timetable/time

    You can register for this tutorial and the BSDCan conference here:

    bsdcan.org/2026/registration.h

    If you register before May 1st, you can take advantage of the free reception on Saturday!

    #runbsd #runsh #sh #bsdcan #shellscript #Unix

  16. Are you looking to sharpen your Shell Scripting chops? Then you may be interested in the BSDCan Shell Scripting Tutorial for Beginners and Sysadmins with Mathias Eggers.

    Anyone who works with BSD and other Unix- and Linux-like systems will sooner or later have to deal with the shell and shell scripts, e.g. automation of repetitive task or starting services in /etc/rc.d. Understanding scripts and how to meaningfully extend or rewrite them is the goal of this tutorial, which is mainly designed for beginners and sysadmins.

    Simple shell scripts often consist of a sequence of arbitrary shell commands executed in a specific order to achieve a particular purpose. This is where the tutorial will begin, and I will then walk participants through the other components of a script using examples:

    Variables

    Sourcing

    Control structures

    Loops

    In- and output redirection

    Parameters and options

    Functions

    Testing scripts

    From the tutorial the participants will get an impression of what could be achieved with the well-equipped toolbox the shell provides and use that knowledge for creating own scripts for their projects.

    Participants should bring their own machines to try out the examples. I encourage everybody to ask questions and bring examples or problems from their daily work to the tutorial to foster a vivid discussion.

    I've been writing shell scripts as part of my work since I got in contact with Unix in 1993 and have been teaching shell programming to apprentices for over ten years. This tutorial will be a shortened and in regards to rc-scripts extended version of that one-week course.

    bsdcan.org/2026/timetable/time

    You can register for this tutorial and the BSDCan conference here:

    bsdcan.org/2026/registration.h

    If you register before May 1st, you can take advantage of the free reception on Saturday!

    #runbsd #runsh #sh #bsdcan #shellscript #Unix

  17. Are you looking to sharpen your Shell Scripting chops? Then you may be interested in the BSDCan Shell Scripting Tutorial for Beginners and Sysadmins with Mathias Eggers.

    Anyone who works with BSD and other Unix- and Linux-like systems will sooner or later have to deal with the shell and shell scripts, e.g. automation of repetitive task or starting services in /etc/rc.d. Understanding scripts and how to meaningfully extend or rewrite them is the goal of this tutorial, which is mainly designed for beginners and sysadmins.

    Simple shell scripts often consist of a sequence of arbitrary shell commands executed in a specific order to achieve a particular purpose. This is where the tutorial will begin, and I will then walk participants through the other components of a script using examples:

    Variables

    Sourcing

    Control structures

    Loops

    In- and output redirection

    Parameters and options

    Functions

    Testing scripts

    From the tutorial the participants will get an impression of what could be achieved with the well-equipped toolbox the shell provides and use that knowledge for creating own scripts for their projects.

    Participants should bring their own machines to try out the examples. I encourage everybody to ask questions and bring examples or problems from their daily work to the tutorial to foster a vivid discussion.

    I've been writing shell scripts as part of my work since I got in contact with Unix in 1993 and have been teaching shell programming to apprentices for over ten years. This tutorial will be a shortened and in regards to rc-scripts extended version of that one-week course.

    bsdcan.org/2026/timetable/time

    You can register for this tutorial and the BSDCan conference here:

    bsdcan.org/2026/registration.h

    If you register before May 1st, you can take advantage of the free reception on Saturday!

    #runbsd #runsh #sh #bsdcan #shellscript #Unix

  18. Wrote a #shell function without using ls inside of $( ), so my inner @mirabilos won't harass me. XD

    #slightly easier wireguard command
    function wg {
        local dir file profile profiledir= parm=${1:-} statustext
        #Find profile dir
        for dir in {,/usr/local}/etc/wireguard; do
            if [[ -d $dir ]]; then
                profiledir=$dir
                break
            fi
        done
        #Find config file
        if [[ -n $profiledir ]]; then
            for file in $profiledir/*.conf; do
                if [[ -e $file ]]; then
                    profile=${file//*\/}
                    profile=${profile/.conf}
                    break
                fi
            done
        fi
        [[ -n $profile ]] || profile=proton
        statustext="wireguard profile $profile"
        case ${parm,,} in
            up|on)      doas wg-quick  up  $profile;;
            down|off)   doas wg-quick down $profile;;
            status)     echo -en "$statustext _______\r"
                        echo -en "$statustext "
                        ifconfig |grep -q "^$profile:" && echo enabled || echo disabled;;
            *)          warn "wg usage: wg up|down|status";;
        esac
    }
    

    Hmm, seems ${foo,,} for lower case conversion is #bash-only. I wonder if I should use tr instead.

    #Unix #UnixShell #ShellScript #ShellScripting

  19. Wrote a #shell function without using ls inside of $( ), so my inner @mirabilos won't harass me. XD

    #slightly easier wireguard command
    function wg {
        local dir file profile profiledir= parm=${1:-} statustext
        #Find profile dir
        for dir in {,/usr/local}/etc/wireguard; do
            if [[ -d $dir ]]; then
                profiledir=$dir
                break
            fi
        done
        #Find config file
        if [[ -n $profiledir ]]; then
            for file in $profiledir/*.conf; do
                if [[ -e $file ]]; then
                    profile=${file//*\/}
                    profile=${profile/.conf}
                    break
                fi
            done
        fi
        [[ -n $profile ]] || profile=proton
        statustext="wireguard profile $profile"
        case ${parm,,} in
            up|on)      doas wg-quick  up  $profile;;
            down|off)   doas wg-quick down $profile;;
            status)     echo -en "$statustext _______\r"
                        echo -en "$statustext "
                        ifconfig |grep -q "^$profile:" && echo enabled || echo disabled;;
            *)          warn "wg usage: wg up|down|status";;
        esac
    }
    

    Hmm, seems ${foo,,} for lower case conversion is #bash-only. I wonder if I should use tr instead.

    #Unix #UnixShell #ShellScript #ShellScripting

  20. Wrote a #shell function without using ls inside of $( ), so my inner @mirabilos won't harass me. XD

    #slightly easier wireguard command
    function wg {
        local dir file profile profiledir= parm=${1:-} statustext
        #Find profile dir
        for dir in {,/usr/local}/etc/wireguard; do
            if [[ -d $dir ]]; then
                profiledir=$dir
                break
            fi
        done
        #Find config file
        if [[ -n $profiledir ]]; then
            for file in $profiledir/*.conf; do
                if [[ -e $file ]]; then
                    profile=${file//*\/}
                    profile=${profile/.conf}
                    break
                fi
            done
        fi
        [[ -n $profile ]] || profile=proton
        statustext="wireguard profile $profile"
        case ${parm,,} in
            up|on)      doas wg-quick  up  $profile;;
            down|off)   doas wg-quick down $profile;;
            status)     echo -en "$statustext _______\r"
                        echo -en "$statustext "
                        ifconfig |grep -q "^$profile:" && echo enabled || echo disabled;;
            *)          warn "wg usage: wg up|down|status";;
        esac
    }
    

    Hmm, seems ${foo,,} for lower case conversion is #bash-only. I wonder if I should use tr instead.

    #Unix #UnixShell #ShellScript #ShellScripting

  21. Wrote a #shell function without using ls inside of $( ), so my inner @mirabilos won't harass me. XD

    #slightly easier wireguard command
    function wg {
        local dir file profile profiledir= parm=${1:-} statustext
        #Find profile dir
        for dir in {,/usr/local}/etc/wireguard; do
            if [[ -d $dir ]]; then
                profiledir=$dir
                break
            fi
        done
        #Find config file
        if [[ -n $profiledir ]]; then
            for file in $profiledir/*.conf; do
                if [[ -e $file ]]; then
                    profile=${file//*\/}
                    profile=${profile/.conf}
                    break
                fi
            done
        fi
        [[ -n $profile ]] || profile=proton
        statustext="wireguard profile $profile"
        case ${parm,,} in
            up|on)      doas wg-quick  up  $profile;;
            down|off)   doas wg-quick down $profile;;
            status)     echo -en "$statustext _______\r"
                        echo -en "$statustext "
                        ifconfig |grep -q "^$profile:" && echo enabled || echo disabled;;
            *)          warn "wg usage: wg up|down|status";;
        esac
    }
    

    Hmm, seems ${foo,,} for lower case conversion is #bash-only. I wonder if I should use tr instead.

    #Unix #UnixShell #ShellScript #ShellScripting

  22. Wrote a #shell function without using ls inside of $( ), so my inner @mirabilos won't harass me. XD

    #slightly easier wireguard command
    function wg {
        local dir file profile profiledir= parm=${1:-} statustext
        #Find profile dir
        for dir in {,/usr/local}/etc/wireguard; do
            if [[ -d $dir ]]; then
                profiledir=$dir
                break
            fi
        done
        #Find config file
        if [[ -n $profiledir ]]; then
            for file in $profiledir/*.conf; do
                if [[ -e $file ]]; then
                    profile=${file//*\/}
                    profile=${profile/.conf}
                    break
                fi
            done
        fi
        [[ -n $profile ]] || profile=proton
        statustext="wireguard profile $profile"
        case ${parm,,} in
            up|on)      doas wg-quick  up  $profile;;
            down|off)   doas wg-quick down $profile;;
            status)     echo -en "$statustext _______\r"
                        echo -en "$statustext "
                        ifconfig |grep -q "^$profile:" && echo enabled || echo disabled;;
            *)          warn "wg usage: wg up|down|status";;
        esac
    }
    

    Hmm, seems ${foo,,} for lower case conversion is #bash-only. I wonder if I should use tr instead.

    #Unix #UnixShell #ShellScript #ShellScripting

  23. Ah, it seems my Google-foo is strong. I think I found a modified #Automator #ShellScript to not add the line feed.

  24. Ah, it seems my Google-foo is strong. I think I found a modified #Automator #ShellScript to not add the line feed.

  25. Ah, it seems my Google-foo is strong. I think I found a modified #Automator #ShellScript to not add the line feed.

  26. Ah, it seems my Google-foo is strong. I think I found a modified #Automator #ShellScript to not add the line feed.

  27. Any #Automator #ShellScript experts care to help?

    I created the following script to copy the first 6 characters of a selected filename to the clipboard. But the clipboard item ends up with a hard return after the characters. Is there a way to put a stop to that?

  28. Any #Automator #ShellScript experts care to help?

    I created the following script to copy the first 6 characters of a selected filename to the clipboard. But the clipboard item ends up with a hard return after the characters. Is there a way to put a stop to that?

  29. Any #Automator #ShellScript experts care to help?

    I created the following script to copy the first 6 characters of a selected filename to the clipboard. But the clipboard item ends up with a hard return after the characters. Is there a way to put a stop to that?

  30. Any #Automator #ShellScript experts care to help?

    I created the following script to copy the first 6 characters of a selected filename to the clipboard. But the clipboard item ends up with a hard return after the characters. Is there a way to put a stop to that?

  31. 🤦‍♂️ Ah yes, #Linux is an #interpreter now. Because who needs a perfectly functional kernel when you can make an OS behave like a wannabe shell script interpreter? 👻 Fear not, dear reader, the author promises you an inscrutable command that might just be #malware, but hey, that’s all part of the #fun, right? 🐔
    astrid.tech/2026/03/28/0/linux #ShellScript #HackerNews #ngated

  32. Here's a little puzzle for you. Can you figure out the purpose of this one-off shell script I just wrote?
    If you post an answer put it behind a CW so you don't spoil it for others!
    #programming #scripting #shellScript #shellScripting #Linux

  33. Here's a little puzzle for you. Can you figure out the purpose of this one-off shell script I just wrote?
    If you post an answer put it behind a CW so you don't spoil it for others!
    #programming #scripting #shellScript #shellScripting #Linux

  34. Here's a little puzzle for you. Can you figure out the purpose of this one-off shell script I just wrote?
    If you post an answer put it behind a CW so you don't spoil it for others!
    #programming #scripting #shellScript #shellScripting #Linux

  35. Here's a little puzzle for you. Can you figure out the purpose of this one-off shell script I just wrote?
    If you post an answer put it behind a CW so you don't spoil it for others!
    #programming #scripting #shellScript #shellScripting #Linux

  36. And today's multi-hour confusing time suck was:

    `curl -H "Authorization: ${TOKEN}"`

    (Note conspicuous lack of the word `Bearer`)

    To add #insult to #injury, this old #Perl guy had to dig into some #PHP in order to figure out where his stupid #shellscript went wrong.

    On the other hand, I did gather enough #research to propose a #solution to #decommission a piece of #commercial software in favor of a mix of #cloud services and #selfhosted #opensource.

  37. Muita discussão interessante rolando no fidigerson e eu... há três dias tentando recuperar um arquivo. :angery:
    Provavelmente a parte de recuperar é a mais simples. O difícil é encontrar o diacho do arquivo numa montanha de arquivinhos... Fiz logo um script shell pq a quantidade tá brutal.

    #testdisk #photorec #recuperaçãodearquivos #shellscript #shell #bash

  38. === KIỂM TRA NHANH SỬ DỤNG RAM TRÊN LINUX ===

    📊 Tổng quan: Tổng, đã dùng, trống, khả dụng
    🔝 10 tiến trình tốn RAM nhất
    🗂 Phân loại: Ứng dụng vs hệ thống (kernel, cache)
    💡 Mẹo: Dọn cache nếu cần (sudo sync && echo 3 > /proc/sys/vm/drop_caches)

    Script hoạt động trên mọi hệ thống Linux, hiển thị rõ bộ nhớ thực và khả dụng. Cache nằm trong "available" là bình thường.

    #Linux #Bash #RAM #MemoryUsage #Scripting #LinuxTips
    #Linux #Bash #RAM #Sử_dụng_bộ_nhớ #ShellScript #Mẹo_Linux

    h

  39. 🚀🕰️ Ah, the #nostalgia of square brackets in shell scripting—the forgotten relics of our #coding youth! 🤓📚 Luca Ferrari takes us on a time-traveling adventure to rediscover the ancient art of 'test,' proving once again that some people will do anything to relive their university glory days. 🎓💾
    fluca1978.github.io/2025/12/10 #test #shellscript #retro #tech #HackerNews #ngated