Sessions are a built-in feature of vim to allow you to quickly restore buffers and window layouts to a viminfo-file. These files can be reused and can usually be transferred to other machines. This is particularly nice if you have many config files across the system where the location is hard to remember, or if you like your window layout a certain way every time.
In my example below I will show how I like to setup some Session files for OBIEE.
Amazon has really made it quite simple to pull down the ODBC/JDBC drivers needed to connect to Redshift. Today, however, I attempted to test connectivity with isql and got the error “Could not SQLConnect”
The Error [oracle@obiee-server ~]$ isql "Redshift ODBC" [ISQL]ERROR: Could not SQLConnect Digging In Locate the primary driver config [oracle@obiee-server ~]$ odbcinst -j unixODBC 2.3.1 DRIVERS............: /etc/odbcinst.ini SYSTEM DATA SOURCES: /etc/odbc.ini FILE DATA SOURCES..: /etc/ODBCDataSources USER DATA SOURCES.
.tmux.conf Starting in tmux 1.8 a new feature called “zoom” (Ctrl+b z) was introduced. This allows you zoom into a pane, do work, and zoom back out.
Out of the box tmux should allow you to use Hotkey z (Ctrl+b z by default) right away, but something I found lacking was the ability to know if I was already zoomed in or not. Add the following to your .tmux.conf file to turn your active window red in the status bar:
The Problem Today I was doing some local testing with OBIEE (Oracle Business Intelligence 12c) and Oracle Database 12 within Docker. Now typically due to the size of the Oracle installers and resource usage I would install these on VMs, but today I am writting deployment scripts – And I need the ability to build up and tear down quickly, over and over.
The problem is, I only have about 20GB diskspace free on my laptop’s SSD.
The Problem I recently switched back to using gnome 3 when I did a fresh install of Fedora 25 – Which, I’ve been super happy with!. Last night I started a new project on github and did my first code push. Suddenly a GUI password prompt pops up!
What is this?? Bro, you’re killing my commandline flow!
$ env |grep --color SSH SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass The solution $ unset SSH_ASKPASS I would suggest adding that to your .
Background We’ve all been there.. slapping away at your keyboard – Perhaps hoping through an SSH tunnel, or maybe SSHing into a NAT’d virtualbox vm, and suddenly BAM!.. You’re smacked in the face by this ugly chunk of message:
$ ssh -p2222 localhost @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)!
Background Recently I started working more on linux systems that require X windows to run, mostly due to GUI installers. I am not new to the idea of X forwarding over SSH, and I am not new to the idea that some installers must be run as certain users — But this was a first for me where the graphic installer had to be run on a remote machine, and had to be run as a user with no password.