8 ms·

> remote persistence This is the real reason I actually need tmux. I often lose connection to a server for various reasons and don't want to lose my vim sessio

by j2kun 2y ago

> remote persistence This is the real reason I actually need tmux. I often lose connection to a server for various reasons and don't want to lose my vim session or whatever

adtac 2y ago
tmux over mosh over wireguard is all you need
- deleted 2y ago
  [deleted]
- blueflow 2y ago
  why the wireguard step?
  - adtac 2y ago
    everything works fine with just tmux + mosh, but I like to bind sshd on the wireguard interface so that there aren't any listening ports accessible from the public internet
    - blueflow 2y ago
      ... except for the UDP port where wireguard receives its pakets.
      - adtac 2y ago
        yes, but wireguard is undetectable because the server won't reply to packets that fail auth whereas sshd will respond (with a banner!) to anyone who comes knocking stealth is basically impossible with TCP
pessimizer 2y ago
I've literally had projects running from screen sessions for years. I always assumed the purpose of them was so I could turn off my computer while doing something over the network that was either long-lived, on an unstable connection, or a daemon/server of some sort.
e40 2y ago
I can’t live without X11 emacs, so I use Starnet’s FastX, which allows me to disconnect and reconnect either when my connection drops or when I move between office and home. I absolutely couldn’t live without it.
bradfox2 2y ago
Is there anything better than tmux for this purpose? I need persistence but hate the key bindings and general interface.
- timdev2 2y ago
  My use-cases are pretty basic, and my use isn't all that frequent, but I've been very happy with: https://zellij.dev/ https://zellij.dev/
- johnchristopher 2y ago
  There's still `screen` ? Also, I think tmux keys can be rebinded ?
- schainks 2y ago
  Byobu is equivalent, different hotkeys: https://www.byobu.org/ https://www.byobu.org/ I have moved between tmux, byobu, and screen at various times in my career. I wouldn’t say one is better than the other, as they all do the job I need just fine (eg persistent session state on remote machines)
  - supercheetah 2y ago
    Byobu just works on top of either screen or tmux. By default it will try to use screen, but you can force it to use tmux with byobu-tmux.
- mananaysiempre 2y ago
  Dtach[1] does session persistence and nothing else—it leaves refreshing the screen to the program running inside it (it can send a ^L or a SIGWINCH upon reattaching but that’s it). [1] https://dtach.sourceforge.net/ https://dtach.sourceforge.net/
  - simonmic 2y ago
    +1 for dtach. That plus mosh and emacs works extremely well with no fuss.
bayindirh 2y ago
It's not only a safety net for losing connection. As soon as I connect to a server to do work, I automatically fire screen, and create new terminals and rename them as I work with the system. If my work is unfinished, I leave the screen as is, and disconnect. We don't touch each others' screen instances on servers, so it's a safe workspace which I can return whenever I want.
marcosdumay 2y ago
Nowadays everybody is in a GUI terminal emulation anyway. Multiplexing is completely redundant. I imagine everybody uses screen and tmux mainly for remote persistence.

by j2kun 2y ago

> remote persistence This is the real reason I actually need tmux. I often lose connection to a server for various reasons and don't want to lose my vim session or whatever

adtac 2y ago

tmux over mosh over wireguard is all you need

deleted 2y ago
[deleted]
blueflow 2y ago
why the wireguard step?
- adtac 2y ago
  everything works fine with just tmux + mosh, but I like to bind sshd on the wireguard interface so that there aren't any listening ports accessible from the public internet
  - blueflow 2y ago
    ... except for the UDP port where wireguard receives its pakets.
    - adtac 2y ago
      yes, but wireguard is undetectable because the server won't reply to packets that fail auth whereas sshd will respond (with a banner!) to anyone who comes knocking stealth is basically impossible with TCP

pessimizer 2y ago

I've literally had projects running from screen sessions for years. I always assumed the purpose of them was so I could turn off my computer while doing something over the network that was either long-lived, on an unstable connection, or a daemon/server of some sort.

e40 2y ago

I can’t live without X11 emacs, so I use Starnet’s FastX, which allows me to disconnect and reconnect either when my connection drops or when I move between office and home. I absolutely couldn’t live without it.

bradfox2 2y ago

Is there anything better than tmux for this purpose? I need persistence but hate the key bindings and general interface.

timdev2 2y ago
My use-cases are pretty basic, and my use isn't all that frequent, but I've been very happy with: https://zellij.dev/ https://zellij.dev/
johnchristopher 2y ago
There's still `screen` ? Also, I think tmux keys can be rebinded ?
schainks 2y ago
Byobu is equivalent, different hotkeys: https://www.byobu.org/ https://www.byobu.org/ I have moved between tmux, byobu, and screen at various times in my career. I wouldn’t say one is better than the other, as they all do the job I need just fine (eg persistent session state on remote machines)
- supercheetah 2y ago
  Byobu just works on top of either screen or tmux. By default it will try to use screen, but you can force it to use tmux with byobu-tmux.
mananaysiempre 2y ago
Dtach[1] does session persistence and nothing else—it leaves refreshing the screen to the program running inside it (it can send a ^L or a SIGWINCH upon reattaching but that’s it). [1] https://dtach.sourceforge.net/ https://dtach.sourceforge.net/
- simonmic 2y ago
  +1 for dtach. That plus mosh and emacs works extremely well with no fuss.

bayindirh 2y ago

It's not only a safety net for losing connection. As soon as I connect to a server to do work, I automatically fire screen, and create new terminals and rename them as I work with the system. If my work is unfinished, I leave the screen as is, and disconnect. We don't touch each others' screen instances on servers, so it's a safe workspace which I can return whenever I want.

marcosdumay 2y ago

Nowadays everybody is in a GUI terminal emulation anyway. Multiplexing is completely redundant. I imagine everybody uses screen and tmux mainly for remote persistence.