Corporate management sucks. Lol
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: dlots on February 09, 2017, 09:16:45 AM
Honestly I plan to just keep doing what I have been doing. He's been my boss for 8 months and I think I have talked to him less than an hour, and that includes the 1/2 hour meeting yesterday, and apparently he had no clue what my workload has been for those 8 months.
docker run --rm -ti -p realport:fakeport ubuntu:16.04 bash
Quote from: deanwebb on February 11, 2017, 08:10:45 AM
We have a docker environment?
By that, I mean that I know about our VM environment, so I can imagine a solution that involves a VM.
Quote from: wintermute000 on February 05, 2017, 05:37:11 PM
I've only looked @ tmux briefly (installed it, set it up with a template).
What's the main advantages to screen?
QuoteSome of the (major) reasons I prefer tmux over screen:
Status bar is much easier to use. You can easily set up different text/styles for current window, windows with activity, etc. and you can put things on the left and right of the status bar, including shell commands that can be run at a specified interval (default 15s).
Almost any command you can run inside tmux can be run from a shell with tmux command [args]. This makes it very easily scriptable, as well as making it easy to do complex commands.
Much more accurate automatic window renaming. While screen sets the title based on the first word of the command, and requires shell configuration to do even that in a shell window, tmux keeps track of what processes are actually running in each window, and updates the title accordingly. This way you get dynamic renaming with any shell and zero configuration. For example: Let's say you're running Z Shell; the window's name would be "zsh". Now let's say you want to edit some configuration file, so you type sudo emacs /etc/somefile. While sudo is asking for your password, the window's name will be "sudo", but once you've done that and sudo launches emacs, the title will be "emacs". When you're all done and you exit emacs, the title will change back to "zsh". This is pretty useful for keeping track of windows, and it can also be especially useful in specific situations, like if you have some long-running process in another window that occasionally prompts you for input using dialog; the window name would change to "dialog" when that happened, so you would know you had to switch to that window and do something.
Nicer session handling (IMHO). You can do a lot more with sessions within tmux itself. You can easily switch, rename, etc. and you can move and share windows between sessions. It also has a different model, where each user has a server which controls his/her sessions and which the client connects to. The downside of this is that if the server crashes, you lose everything; I've never had the server crash on me, though.
tmux seems to be more actively developed. There are updates pretty frequently, and you can file a bug report or feature request through SourceForge and get an answer within a few days.
Quote from: Otanx on February 07, 2017, 12:36:34 PM
typical time frame for a company to detect a breach is over 200 days.