Entries tagged 'cat:Computer' (Page 9)

I don't have a capsule in the Gemini Space

Entry created on 2021-06-20 author:steeph (374) cat:Computer (78) cat:Gemini (2) cat:Gopher (1) cat:Shared (17) lang:en (253)

When I first read about Project Gemini (the Gemini protocol) I was excited. I think it's a good idea for several reasons and I'm happy that it's reality and more than a handful of people help building that space and filling it with content. I never got into gopher mainly because I don't find the structure of gopher sites (gopherholes?) suitable for most kinds of content. And because the web exists and, with the right browser extensions and configuration, isn't annoying enough most of the time.

But now that there is a new kid on the block with a different feature set and the right ideological background of the initiator(s) of the protocol, I seriously thought about moving this site over to the Gemini Space. Or to participate in any way. But I've decided against it for now. I've just started building this site and the software behind it and I don't want to abandon thi project already or start a competing one before this one is established in my mind.

So this blog entry shall be my only contribution for now. Go check it out, there already is a lot of interesting content in Gemini capsules.

  • Project Gemini Website - with many good links to get started
  • Lagrange - a famous GUI Gemini browser (web link)
  • medusae.space gemini directory - one of several good collections/directories of gemini capsules (gemini link)
  • Geminispace Search engine(gemini link)
  • Project Idea And A Little Story: High Power PC Cooled Completely Passively With Heat Pipes And A Large Surface Aluminium Case And My First Online Post Ever

    Entry created on 2021-06-02 author:steeph (374) cat:Bulletin Boards (2) cat:CPU Cooler (2) cat:CPUs (5) cat:Case Modding (11) cat:Computer (78) cat:Cooling (2) cat:DIY (17) cat:Heatsinks (2) cat:Personal (12) cat:Projects (41) cat:Useless Memories (5) lang:en (253) top:Projects:Case Modding (9) top:Projects:Ideas (8)

    Here is another project idea that I'll probably never realise. It's not really an ingenious idea or a new concept. But there is a reason for why I can't forget about it.

    In the very early 2000s, when I started to tinker with PC cases and also made my first steps in web communities, I thought about how I could reduce the noise my computers made without running chips at dangurously hight temperatures or forgoing performance. I've read about heat pipes in some case modding community. And I thought why not take it to the extreme to move heat quickly not just to a larger heat sink than the CPU sockets could safely hold (Motherboards didn't have cooler brackets back then.) but to a heat sink or several heat sinks that cover the majority of the case's surface. When the first commercial CPU coolers with heat pipes came on the market, targetet at computer tinkerers, but still nobody in the community seemed to attempt to make a case with a huge heat sink on the outside of the wall to cool even a 2 GHz Pentium 4 with its 75 Watts TDP passively, I decided to register in a small case modding web forum and present my idea to see what might be wrong with the concept. I was actually younger 20 years ago than I am now and I had never before tried to get myself out there in such a way. I thought it was a rather good idea. But I wasn't sure how much surface and aluminium mass I needed and wether it was realistic to cool a powerful CPU passively that way. Trying to cool a Pentium 4 only passively sounds like a stupid idea after all.

    So I created a post on said web forum that I've never read before, presented my idea and asked for opinions. I got a few answers and everybody seemed to think it was a stupid idea. One respondant didn't seem to get my idea but still seemed to think it was stupid. One person seemed rather friendly in comparison and asked if I could explain the idea in more detail. I felt bullied by the negative answers, I felt mocked by being inline quoted (which I don't think I had seen before) and I felt that my ideas were generally worthless since I wasn't one of those hobbyistic experts that actually know stuff and are able to answer questions asked in a web forum. So rather than explaining my idea in more detail as requested, I searched for a way to delete my post, didn't find one and asked in the same thread how I could remove it.

    I didn't find the post when i searched for it a few years ago. Like most small web forums it has probably gone offline with nothing or almost nothing in a web archive. But with the experiece that I have today I suspect that I didn't explain my idea very well and the other forum members didn't realise that I was a very insecure child. I also realised many years later that it wasn't a bad idea. I even saw a computer case that implemented the same idea being sold at some point. I don't know if many people bought this. But at least somebody other than me seemed to think it made sense and could even be commercialised. This redeemed my idea in my mind and I started to think about making such a case again. But I don't have the need for high-power CPUs and didn't want to invest money into another project that I wouldn't ever finish once the initial exitement would be over by buying huge heat sinks and heat pipes. So I've added it to that huge imaginary list with projects that I like to would have done but likely wouldn't finish and conclude my decades long considerations and my decision to conclude them by writing this entry.

    Done.

    SBWG 0.8.10

    Entry created on 2021-05-24 author:steeph (374) cat:Bash (31) cat:Code (31) cat:Computer (78) cat:Linux (36) cat:Projects (41) cat:SBWG (18) cat:Scripts (28) cat:Software (53) lang:en (253) top:Projects:Code:Bash Scripts:SBWG (16)

    So, I'm still making slow process with SBWG. I had more fun with it when I was out and implementing new features. But I find it important to finish version 1.0.0 with the currently defined set of festures and goals, which include finishing documentation, testing and code hardening, which are less fun for me.

    I've always treated the third level of the version number (x.x.thisone) as a means to declare a new version done when I feel like having achived something. So today I declare version 0.8.10 as done. There really isn't much left to do to meet my milestones for v0.9.0. And from there on it will only be testing and possibly a little bit of code improvements to get to my set goals for v1.0.0.

    I'm looking forward to this not only because I'll like the feeling of having achived a goal, but also it will mean that I'll be free again to introduce new features. I still have more ideas than necessary about what to do with SBWG.

    But right now I'm enjoing the fact that I'm able to make myself believe that it's okay to move on as slowly as I want and let my colloquial executive dysfunction do its think without impacting my feeling of self-worth oo much.

    Bash script to burn your CPU easily

    Entry created on 2021-05-16 author:steeph (374) cat:Bash (31) cat:CPUs (5) cat:Code (31) cat:Computer (78) cat:Scripts (28) cat:Software (53) lang:en (253) top:Projects:Code:Bash Scripts (23)

    When making my own CPU cooler or testing some other stuff I sometimes need to create as high of a CPU load as possible. After typing while true; do true; done for the one-too-manyth time I finally decided to create an alias for that. But that didn't feel neat enough. So I made this simple Bash script.

    
    #!/bin/bash
    
    if [ "$#" -ne "1" ]
    then
      echo "I need one argument and one argument only: Number of threads to start."
      echo "Hint: You have $(nproc) CPU cores."
      exit 1
    fi
    
    if [[ "$1" =~ ^[0-9]+$ ]]
    then
      n="$1"
    else
      echo "Argument needs to be a number: Number of threads to start."
      echo "Hint: You have $(nproc) CPU cores."
      exit 1
    fi
    
    trap "pkill -P $$; exit 0" SIGHUP SIGINT SIGTERM
    
    while [ "$n" -gt 1 ]
    do
      while true; do true; done &
      n=$((n-1))
    done
    echo "Started $1 threads to burn your CPU."
    pidof -x "$(basename -- $0)"
    while true; do true; done
    

    Download

    For a simpler script, you can also just use this three-liner without any arguments to stress all CPU cores:

    
    #!/bin/bash
    yeah() { while true; do true; done& }
    threads=$(nproc)
    for i in $(seq 1 $threads); do yeah; done
    

    Bash script to quickly open and close a wifi hotspot

    Entry created on 2021-05-15 author:steeph (374) cat:Bash (31) cat:Code (31) cat:Computer (78) cat:Scripts (28) cat:Software (53) cat:WiFi (1) lang:en (253) top:Projects:Code:Bash Scripts (23)

    I needed a wifi hotspot to test some phones. So I looked up how to create one quickly and learned about nmcli. It wasn't quick and easy enough for my taste. So here is how I do it from now on.

    The Bash script maintains only one connection (named quick-hotspot). You can't create multiple connections or access points with it. Not intentionally, but also not accidentally because you forgot that you still have a hotspot enabled from the last time you needed one. (I know I would at some point.)

    Examples:

    
    hotspot # Creates and enables a hotspot with a random name and a random 8-digit password.
    hotspot down # Disables the hotspot if it was enabled.
    hotspot ⊿ⴼͳΞⵖⵡ∃ doctorwho # Creates and enables a hotspot with the SSID "⊿ⴼͳΞⵖⵡ∃" and the password "doctorwho".
    hotspot . password # My use case: quick and short and I don't want to type a complicated password on the phones. SSID: ".", PW: "password"
    hotspot down # Deactivates the hotspot regardless of the SSID you used.
    

    If you activate a hotspot while one is already active, it just changes the SSID and password so that no two connections created by this script are ever active at the same time. I'm sure there already is a program that solves this better. But it was fun for me to create and I felt like sharing.

    Click here to download the bash script.

    Content:

    #!/bin/bash
    
    # Quickly create and activate a WiFi hotspot - optionally defining SSID and password - and deactivate it again when you don't need it anymore.
    
    usage() {
      echo "Usage: $(basename $0) ssid passphrase"
      echo "       $(basename $0) down"
      echo "       $(basename $0)"
      exit 1
    }
    
    activate() {
      # If the connection "quick-hotspot" doesn't already exist...
      if ! nmcli connection show | grep quick-hotspot; then
        # ... then create it.
        nmcli connection add type wifi ifname '*' con-name quick-hotspot autoconnect no ssid "$ssid"
      else
        # ... else change the SSID of the existing connection.
        nmcli connection modify quick-hotspot ssid "$ssid"
      fi
      # Make the connection an access point
      nmcli connection modify quick-hotspot 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
      # Change the password
      nmcli connection modify quick-hotspot 802-11-wireless-security.key-mgmt wpa-psk 802-11-wireless-security.psk "$pw"
      # Enable the connection
      nmcli connection up quick-hotspot
    }
    
    case $# in
      0)
        ssid=$(</dev/urandom tr -dc A-Z] | head -c8; echo "")
        echo "SSID: $ssid"
        pw=$(shuf -i 10000000-99999999 -n 1) 
        echo "PW: $pw"
        activate
        ;;
      1)
        if [ $1 == down ]; then
          nmcli connection down "quick-hotspot"
          exit 0
        else usage
        fi
        ;;
      2)
        ssid="$1"
        if ! [ ${#2} -ge 8 ]; then
          echo "$(basename $0): Password needs to be 8 characters or longer."
          exit 1
        else
          pw="$2"
          activate
        fi
        ;;
      *)
        usage
        ;;
    esac
    

    See also: My Reddit Post

    Go To Navigation Page
    Show/Hide Navigation