RESISTOS by rado84

[Perpetual Padawan]

Is there a way to make Fastfetch display This logo? Let's say I put it in /home

 

[osprey]

Is there a way to make Fastfetch display This logo? Let's say I put it in /home

Yes.

cat logo.txt | fastfetch --raw - --logo-width 40 --logo-height 29 --logo-padding-left 0

Adjust numbers to suit. Note that logo.txt is in ascii. Here is an example:

[tom@min ~]$ cat logo.txt | fastfetch --raw - --logo-width 40 --logo-height 29 --logo-padding-left 0
       ,
       \`-._           __                   ben@min
        \\  `-..____,.'  `.                 -------
         :`.         /    \`.               OS: Debian GNU/Linux trixie trixie/sid x86_64
         :  )       :      : \              Host: B760M PG Lightning WiFi
          ;'        '   ;  |  :             Kernel: 6.11.7-amd64
          )..      .. .:.`.;  :             Uptime: 11 hours, 43 mins
         /::...  .:::...   ` ;              Packages: 2159 (dpkg)
         ; _ '    __        /:\             Shell: bash 5.2.32
         `:o>   /\o_>      ;:. `.           Display (HDMI-1): 1920x1080 @ 60Hz
        `-`.__ ;   __..--- /:.   \          WM: dwm (X11)
        === \_/   ;=====_.':.     ;         Cursor: redglass
         ,/'`--'...`--....        ;         Terminal: xterm 395
              ;                    ;        Terminal Font: fixed (8.0pt)
            .'                      ;       CPU: 13th Gen Intel(R) Core(TM) i5-13500 (20) @ 4.80 GHz
          .'                        ;       GPU: NVIDIA GeForce GT 710 [Discrete]
        .'     ..     ,      .       ;      Memory: 2.87 GiB / 15.27 GiB (19%)
       :       ::..  /      ;::.     |      Swap: 0 B / 14.90 GiB (0%)
      /      `.;::.  |       ;:..    ;      Disk (/): 29.00 GiB / 442.25 GiB (7%) - ext4
     :         |:.   :       ;:.    ;       Local IP (enp3s0): 192.168.0.6/24,192.168.0.5/24 *
     :         ::     ;:..   |.    ;        Locale: en_AU.UTF-8
      :       :;      :::....|     |
      /\     ,/ \      ;:::::;     ;        ████████████████████████
    .:. \:..|    :     ; '.--|     ;        ████████████████████████
   ::.  :''  `-.,,;     ;'   ;     ;
.-'. _.'\      / `;      \,__:      \
`---'    `----'   ;      /    \,.,,,/
                   `----`

 

[rado84]

Refers to my post at #5.

I have my Terminal prompt on all of my Arch-based distros (Manjaro, Cachy, Bluestar, Endeavour, Liya, and so on) displaying what you are seeking.

If you are interested, you could also let me know

1. EXT4, BTRFS, or other?
2. Content of both of /etc/hosts and /etc/hostname

Wizard

Arch started ignoring hosts about 5 years ago, if not more, so that file's useless. Plus, hosts is about external hosts, like blocking or allowing access to a website online. It has nothing to do with the host name.
/etc/hostname doesn't exist here.

I don't see what the filesystem has anything to do with what I need to do.
As for the prompt, changing it has a bug (happens every time): when I open a dir and type "rsync *.mkv "/path/to target - just before I close the path with the final double quote, the cursor jumps (and gets stuck there) right before the first square bracket. If the new prompt is [rado@resist], the cursor jumps to this position:
|[rado@resist]
With the cursor being stuck there, I can't do anything. So I'm back to the original prompt.

 

[Perpetual Padawan]

@rado84 That file is created at installation time in most distros, when you choose the computer name (not user name). Try a back-up and re-install of your OS and use ResistOS as the computer name (and Rado, I assume, your username) so you end up with

rado@ResistOS

as a terminal prompt.

 

[Perpetual Padawan]

@osprey can I get the colors and all that from the text file? I'd like it to look like the image above in my previous post.

 

[osprey]

@osprey can I get the colors and all that from the text file? I'd like it to look like the image above in my previous post.

Yes, you can configure colors, but you would need to write or amend a json file in
~/.config/fastfetch/config.jsonc which specifies the colors to be used. I haven't used colors myself, but my approach would be to download the source of fastfetch from github, check out how it codes color into the logos it uses, and learn how to include the code in the json config file. There's a bit of learning involved which I haven't done at this point, so that the limit of my contribution unfortunately.

 

[wizardfromoz]

Try a back-up and re-install of your OS...

Unlikely to happen, Robin, as the OP has so heavily customised his distro over years, and the time it will take him to check replacement (or not) confirmations. he will have a Clonezilla backup that would do for his purposes, but there are simpler methods.

...so that file's useless

Refers to /etc/hosts , and no, it's not useless, in fact when I started using it and hostname 10 years ago to modify my terminal prompt, it was recommended Best Practice to put exactly the same hostname in both.

Plus, hosts is about external hosts, like blocking or allowing access to a website online. It has nothing to do with the host name.

Likewise.

I don't see what the filesystem has anything to do with what I need to do.

It may not, but I do not use BTRFS, so I wanted to eliminate that possibility.

With the cursor being stuck there, I can't do anything. So I'm back to the original prompt.

On

but for the moment I haven't found a safe way to change it without reinstalling.

Since you are using Systemd, simplest fix is likely

sudo hostnamectl set-hostname "resist"

Then close the terminal and reopen the terminal.

If that works, then reboot and it will likely persist.

You will also then have an /etc/hostname file, which sole content will be

resist

You can use eg

RESIST-OS

but not

RESIST_OS

because it will filter out the underscore.

Try it and see.

HTH

Wizard

 

[rado84]

@rado84 That file is created at installation time in most distros, when you choose the computer name (not user name). Try a back-up and re-install of your OS and use ResistOS as the computer name (and Rado, I assume, your username) so you end up with

rado@ResistOS

as a terminal prompt.

Actually, it IS there but the tool I used to find the file appears to be glitchy, so I dumped it.
Here's a fraction of the problems (listed by an AI but in my case the number of problems was much larger than that) I discovered the last time I tried changing the host name:

Why Changing the Hostname in​

Changing the hostname exclusively in /etc/hostname without updating the rest of the network configuration files leads to a system-wide disaster because it breaks local name resolution. In Linux, many core services and graphical environment components rely on the hostname to communicate with themselves via the loopback interface (127.0.0.1).

When you mismatch the system's runtime hostname and its network map, several critical systems immediately fail:

1. Broken Local Name Resolution (​

The Linux kernel reads the new hostname from /etc/hostname at boot. However, network configuration files like /etc/hosts still point to the old hostname. When an application attempts to resolve the new hostname to an IP address (expecting 127.0.0.1 or ::1), the lookup fails.

• The Result: Networking utilities timeout, network managers fail to initialize properly, and internal sockets drop connections.

2. Xorg / Display Manager Crash (Graphical Interface Failure)​

Display managers (like LightDM, GDM, or SDDM) and desktop environments (like Cinnamon) use local network sockets authenticated by Xauth to manage the display server 0). The authentication tokens (MIT-MAGIC-COOKIE) are strictly tied to the hostname at the time the session started.

• The Result: If the hostname changes mid-session or is unresolvable at boot, Xorg will refuse connections from the display manager. The system hangs at boot (e.g., sticking on Reached target Graphical Interface), crashes to a black screen, or locks the user in an endless login loop.

3. Sudo Authentication Hangs​

The sudo command performs a lookup on the current hostname every time it is executed to check host-based permissions in the sudoers file.

• The Result: When the hostname cannot be resolved, sudo will freeze for 15 to 30 seconds while waiting for a DNS timeout before finally throwing an error (sudo: unable to resolve host...). This breaks administrative scripts and manual terminal commands.

4. IPC (Inter-Process Communication) and D-Bus Failures​

Modern desktop environments rely heavily on D-Bus and Inter-Process Communication (IPC). Many background daemons bind to local sockets using the hostname.

• The Result: Subsystems cannot talk to each other. Audio servers (PipeWire/PulseAudio), system logging, and desktop notifications will lag or fail entirely.

Apparently there's a proper way to change the hostname without using PS1 and I'll try it some day. Just not now bc I have a toothache that's been going for a few days. When it passes away, I'll make a new system backup and try the proper way, offered by Gemini.
I know an AI can't be trusted for everything but so far it has never been lying when it comes to system stuff like this.

The Proper Way to Change a Hostname​

To prevent a disaster, the hostname must be changed uniformly across the system.

1. The Modern Systemd Way: Using hostnamectl changes the hostname in /etc/hostname and updates the kernel transient hostname instantly without requiring a reboot:

sudo hostnamectl set-hostname resist

(or replace resist with whatever new name you want your host to have)

• The Manual Way (The /etc/hosts Fix): If editing manually, you must always update /etc/hosts alongside /etc/hostname. The loopback lines must include the new hostname:
  

  127.0.0.1   localhost
  ::1         localhost
  127.0.1.1   new-resist-os

The automatic way (systemd) sounds best to me, less chance to screw up something.

Edit: apparently there's an addition to the systemd way: you gotta edit /etc/hosts manually and replace all appearances of "arch" with "resist". Which is weird, considering arch started ignoring /etc/hosts years ago.