Posted On Friday, May 27th, 2011 By ynot
Long time ago a friend of mine showed me how to run locally the GUI of a remote application with cygwin[1], a couple of years ago a request in my job required a X server on the server which sounded like a bad idea to me, this is a cleaner approach to run those apps that require a display, when you are running a windoze. It’s even easier if you are running Linux as it is very likely you will be running in a top of a X server. Installation: Download the cygwin setup binary from here[2]. Open the Cygwin Setup and select the following packages to install. openssh xorg-server xhost xinit x-start-menu-icons twm Configuration:. You need your local IP, remote IP Open cygwin and run startx this will start your X-Server locally. Run: xhost +<remoteIP> on the shell opened by the X-Server. Connect to the remote server: ssh -X -l<user> <remoteIP>. Export your local display on the remote Server: export DISPLAY=<localIP>:0.0 Run a graphical application that will be displayed on your local X-Server and Enjoy the Graphical Interface of a remote process in your locally For troubleshooting/clarification, read the man pages of ssh, xhost and xserver. [1] http://www.cygwin.com [2] Continue Reading
Tags:
cli,
cygwin,
display,
gui,
linux,
remote,
windows,
windoze,
x-server |
desktop,
linux,
ñu,
OS,
shell,
syslinux |
Posted On Friday, January 15th, 2010 By ynot
I’m barely new to git, almost 4 months, and everyday I feel more comfortable with it, yesterday kad helped me to understand better the creation of branches, so I made a quick test to add them and took me to a more complete example of using init, remote, branch, tag, merge and cherry-picks, so I wanted to share. A) Creating a local and remote Repo. 01. mkdir -p ~/{git-master/test.git,git-test/{test1,test2}} 02. pushd ~/git-master/test.git 03. git init –bare 04. popd 05. pushd ~/git-test/test1 06. git init 07. echo “This is the first file in the repo.” > README 08. git add README 09. git commit -m “First commit” README 10. git remote add origin ~/git-master/test.git 11. git push origin master B) Creating a local and remote Branch, submitting some code, creating a tag. 12. git checkout -b dev 13. git push origin dev 14. echo “This is the first file in the dev branch.” > DEV 15. git add DEV16. git commit -m “First commit on dev” DEV 17. git push 18. git tag -a -m “First tag in the repo” v0.1 19. git push –tags 20. echo “This is a modification of DEV file.” >> DEV 21. git commit -a -m Continue Reading
Tags:
bare,
branch,
cherry-pick,
example,
git,
init,
merge,
remote |
branch,
cherry-pick,
example,
git,
init,
merge,
remote |
Posted On Wednesday, July 29th, 2009 By ynot
Hi hate when I have to connect to a remote server and some keys like up, down, home, end, etc. don’t work. This is because the way the key is sent over the terminal and interpreted on the remote system. At least on Emacs you can re-define the keys, or as in this case define them, to serve as required. I’m on Ubuntu 9.04(Jaunty Jackalope) connecting remotely to a Red Hat Enterprise(Taroon); when at the remote emacs I hit <C-right> I got an ugly “5C”, hitting <home> does nothing! Argh! After googling in different pages I finally figure this out: In your .emacs configuration file add as many key definitions as needed like this template: ;; key bindings over remote terminal (define-key function-key-map “e<key>” [<key-name>]) Where <key> is the raw value of the key, to get that value simply press C-q <key> this will print that value that you need. e.g Pressing C-q <home> prints ^[OH, remove the “^[” and replace the key value, then on the key-name use the name of that key, in this case “home”. The purpose of this definition is to let know emacs that the key <home> needs to move to the begining of the Continue Reading
Tags:
binding,
commands,
emacs,
home,
kbd,
keybinding,
keys,
linux,
remote,
shell |
binding,
commands,
emacs,
home,
kbd,
keybinding,
keys,
linux,
remote,
shell |
![[FSF Associate Member]](wp-content/uploads/2011/01/getButton.png){kind=small}