Install Oracle Java (JDK) 7 in Ubuntu via PPA Repository Update: Java 7 is no longer supported by Oracle. The binaries are no longer available for download, but if you have an Oracle account, you can still download it after logging in. The Oracle Java 7 installer in this article will continue to work only if you manually download Oracle JDK 7 (version 7u80 for 32bit and 64bit or 7u60 for arm), place it in the /var/cache/oracle-jdk7-installer/ folder on your computer, then install "oracle-java7-installer" as explained below in this article. We've previously written about installing Oracle JDK 7 in Ubuntu using a script with a GUI provided by Zenity. If you really need to use Oracle (ex Sun) Java instead of OpenJDK in Ubuntu, here's an easy way to do it: a PPA repository to install and keep your computer up to date with the latest Oracle Java 7 (Java JDK which includes JRE). Please note that this package is currently in alpha and is offered without any guarantees, so it may or may not work! Update: our Oracle Java 7 installer now supports ARM.
Aha! Moments When Learning Git Git is a fast, flexible but challenging distributed version control system. Before jumping in: Along with a book, tutorial and cheatsheet, here are the insights that helped git click. There's a staging area! Git has a staging area. Yowza, did this ever confuse me. git add foo.txtAdd foo.txt to the index. Why stage? But now there's two undos: git checkout foo.txtUndo local changes (like svn revert)git reset HEAD foo.txtRemove from staging area (local copy still modified). Add and commit, add and commit -- Git has a rhythm. Branching is "Save as..." Branches are like "Save as..." on a directory. Easily merge changes with the original (changes tracked and never applied twice)No wasted space (common files only stored once) Why branch? Imagine virtual directories I see branches as "virtual directories" in the .git folder. My inner dialogue is "change to dev directory (checkout)... make changes... save changes (add/commit)... change to master directory... copy in changes from dev (merge)". Local data
msysgit Wiki IQEmu - mirage335 wiki Brings reliable point-and-click Microsoft Windows application integration to the linux desktop using virtualization, file parameter translation, and wrapper scripts. [edit] Features Supports multiple virtualization backends including VirtualBox (recommended), VMWare (deprecated), and QEMU (unmaintained). Supports virtualization platform guest/host file sharing, as well as samba based file sharing. [edit] Code Project is hosted at github. [edit] Support Currently, this system is somewhat difficult to deploy for the first time, since Microsoft's operating systems are non-redistributable. [edit] Demo The file, on linux. Simple to fire up. We're doing nothing more than running launch.sh with the linux hosted file as a parameter. Magic happens... File is automatically semi-sandboxed in a fresh, temporary MS Windows VM. Now the VM is forcibly powered off (no file corruption issues for temporary VMs), and IQEmu scripts delete it. [edit] Wishlist [edit] History The name stands for Integrated QEMU.
Understanding Git Conceptually Introduction This is a tutorial on the Git version control system. Git is quickly becoming one of the most popular version control systems in use. There are plenty of tutorials on Git already. How is this one different? A Story When I first started using Git, I read plenty of tutorials, as well as the user manual. After a few months, I started to understand those under-the-hood concepts. Understanding Git The conclusion I draw from this is that you can only really use Git if you understand how Git works. Half of the existing resources on Git, unfortunately, take just that approach: they walk you through which commands to run when, and expect that you should do fine if you just mimic those commands. This tutorial, then, will take a conceptual approach to Git. Go on to the next page: Repositories
Moving Files from one Git Repository to Another, Preserving History | Greg Bayer inShare If you use multiple git repositories, it’s only a matter of time until you’ll want to refactor some files from one project to another. Today at Pulse we reached the point where it was time to split up a very large repository that was starting to be used for too many different sub-projects. After reading some suggested approaches, I spent more time than I would have liked fighting with Git to actually make it happen. In the hopes of helping someone else avoid the same trouble, here’s the solution that ended up working best. The solution is primarily based on ebneter’s excellent question on Stack Overflow. Another solution is Linus Torvald’s “The coolest merge, EVER! Move directory 1 from Git repository A to Git repository B. Git repository A contains other directories that we don’t want to move.We’d like to perserve the Git commit history for the directory we are moving. Make a copy of repository A so you can mess with it without worrying about mistakes too much.
Chameleon - UIKit for Mac development Préface Git est un couteau suisse de la gestion de versions. Un outil de gestion de révisions multi-usage, pratique et fiable, dont la flexibilité en rend l’apprentissage pas si simple, sans parler de le maîtriser ! Comme Arthur C. Plutôt que de rentrer dans le détails, nous donnons des instructions pour obtenir tel ou tel effet. Je reste modeste devant le travail fourni par tant de monde pour traduire ces pages. Dustin Sallings, Alberto Bertogli, James Cameron, Douglas Livingstone, Michael Budde, Richard Albury, Tarmigan, Derek Mahar, Frode Aannevik, Keith Rarick, Andy Somerville, Ralf Recker, Øyvind A. François Marier maintient le paquet Debian, créé à l’origine par Daniel Baumarr. Ma gratitude va également à beaucoup d’autres pour leurs encouragements et compliments. Si par erreur je vous ai oublié, merci de me le signaler ou, plus simplement, envoyez-moi un patch ! Hébergement Git gratuit héberge des projets libres. Un grand merci à ces sites pour l’hébergement de ce guide.
HOWTO: SSH Tunneling Made Easy By Frank Wiles I was surprised at how long it took me to find a good HOWTO on setting up a simple SSH tunnel that I wanted to write up this Quick-Tip. Using OpenSSH on a Linux/Unix system you can tunnel all of the traffic from your local box to a remote box that you have an account on. For example I tunnel all of my outbound E-mail traffic back to my personal server to avoid having to change SMTP servers, use SMTP-AUTH, etc. when I am behind firewalls. I find that hotel firewalls, wireless access points, and the other various NATing devices you end up behind while traveling often do not play nice. To do this I use the following: ssh -f user@personal-server.com -L 2000:personal-server.com:25 -N The -f tells ssh to go into the background just before it executes the command. This essentially forwards the local port 2000 to port 25 on personal-server.com over, with nice benefit of being encrypted. Another useful feature of port forwarding is for getting around pesky firewall restrictions.
Using Git to manage a web site The HTML source for my (i.e., this) web site lives in a Git repository on my local workstation. This page describes how I set things up so that I can make changes live by running just "git push web". The one-line summary: push into a remote repository that has a detached work tree, and a post-receive hook that runs "git checkout -f". The local repository It doesn't really matter how the local repository is set up, but for the sake of argument, let's suppose you're starting one from scratch. $ mkdir website && cd website $ git init Initialized empty Git repository in /home/ams/website/.git/ $ echo 'Hello, world!' Anyway, however you got there, you have a repository whose contents you want to turn into a web site. The remote repository I assume that the web site will live on a server to which you have ssh access, and that things are set up so that you can ssh to it without having to type a password (i.e., that your public key is in ~/.ssh/authorized_keys and you are running ssh-agent locally).