I tried Firefox Focus a few years before the pandemic when I was testing Android browsers for digital signage. Focus didn’t meet my needs at the time and I moved on. (I ended up using Fully Kiosk Browser. Eventually left Android for Screenly OSE)
Fast forward to now. Most of my screen time is on my phone during my commute and break. The news sites I like to visit are almost unreadable on my phone, due to excessive ads. Google Chrome doesn’t accommodate extensions. A search on ad blocking Android brought me to Focus. I find Focus fast, efficient at blocking ads, and fun to use.
The remote host has a case "$TERM" in .bashrc setting the prompt to one that will change the terminal title. My .bashrc does not, either due to operator error, or perhaps a faulty gpg-agent package install script clobbered it. Copy /etc/skel/.bashrc to your $HOME. If you already have a .bashrc you want to keep, prepend the contents of /etc/skel/.bashrc.
This /etc/skel/.bashrc is found on Debian and Debian derived distributions. Your mileage may vary.
Here are the lines that set the title:
$ grep -A4 -B3 ]0 /etc/skel/.bashrc
# If this is an xterm set the title to user@host:dir
case "$TERM" in
You can’t have your cake and eat it too. If you set your .bashrc to change the title with every prompt, the title you set with the first solution will be overwritten by the next prompt, before you can see it.
you can have it both ways
Define a function in the current shell, so $PS1 in that shell can be accessed. $PS1 will reset the title without user action, once the title has been set.
$ cat ctt
# save prompt part
Add to your .bashrc, or test by copying and pasting the function at the prompt or pasting into a file and sourceing that file
this post is from my old, first website, dated 2011-08-10. It’s the one I most refer back too.
The usual way is to pull data. This is often more secure. Say you have a web server and a file server for backup. The backup server is likely more trustworthy than the web server. You don’t want to be typing your backup server password on a possibly compromised web server. So from the backup server, you type:
ssh firstname.lastname@example.org tar cvf - some-folder >some-folder.tar
The dash tells tar to use standard output for the -f option. The redirection to some-folder.tar is interpreted by the local shell.
But sometimes, you are working on a server, already logged in, and you consider the server secure. Say a virtual host system. You want to run a program and send the output to another machine, a backup server or another virtual host, without leaving an intermediate file laying around. This is slightly more obscure: