4 ms·
Must be nice being able to work in the same shell every day, and one you have complete control over no less. For those of us ssh-ing into uncountable remote ser
by 63 3y ago
Must be nice being able to work in the same shell every day, and one you have complete control over no less. For those of us ssh-ing into uncountable remote servers all day with unprivileged accounts, it's not really a practical option unfortunately.
- bheadmaster 3y agoIf your utilities are written as self-contained exported Bash functions, you could concatenate them all in a single file (say, `utils.sh`), with a single line at the end: exec /bin/bash Then you could do something like: ssh hostname@address -tt bash -s < /path/to/utils.sh And have all your utilities available on the remote machine :)
- Noumenon72 3y agoDoes this work for aliases?
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- pdmccormick 3y agoBy "personal computing" I guess I do mean machines that I have full root on, so usually either a laptop/desktop or a local headless server. Out of curiousity, these servers that you're dealing with, do you have to use them for long/focused work like writing or software development, or are these more like sysadmin interactions? Have you noticed any repeated commands or sequences you find yourself running over and over? Is there any opportunity for you to write local scripts that then SSH into the targets and run those commands on your behalf? Or locally use sshfs and manipulate files like they were local.