Using PartImage in Ubuntu. Old screenshots, this tutorial is no longer maintained. More importantly, PartImage does not support Ext4 partitions, and Ubuntu defaults to the Ext4 filesystem format. I'm told (which does support Ext4) is a good alternative. You might also want to look into . PartImage is a program that will copy the image of an entire partition, making it easy to restore a partition (including all its programs, files, and directories) exactly as they were before. This tutorial assumes that you have a Ubuntu live CD and somewhere you can save the partition (an external hard drive or another partition).
Your first step is to boot up the live CD. Then, go to the terminal. To install PartImage paste in the terminal the command: sudo apt-get update && sudo apt-get install partimage After it's been installed, you may need to find out the names of your partitions. Sudo fdisk -l I happen to be, for this example, backing up my partition to another partition (I'm backing up /dev/hda1 on /dev/hda5. Sudo partimage. Backup using dd command in linux. Backup an entire hard disk using dd command The ' dd ' command is one of the original Unix utilities and should be in everyone's tool box. It can strip headers, extract parts of binary files and write into the middle of floppy disks; it is used by the Linux kernel Makefiles to make boot images. It can be used to copy and convert magnetic tape formats, convert between ASCII and EBCDIC, swap bytes, and force to upper and lowercase.
For blocked I/O, the dd command has no competition in the standard tool set. Like most well-behaved commands, dd reads from its standard input and writes to its standard output, unless a command line specification has been given. Unlike most commands, dd uses a keyword=value format for its parameters. . # dd --help For more options check dd man page Using dd you can create backups of an entire harddisk or just a parts of it. Full hard disk copy dd if=/dev/hdx of=/dev/hdy dd if=/dev/hdx of=/path/to/image dd if=/dev/hdx | gzip > /path/to/image.gz MBR backup MBR restore. Super Nerdy Cool » Real time file synchronization like Dropbox via Unison. UnisonNetworkOnPortForward: #! /bin/bash ## can't have extension in filename # ssh username@server.ip -f -N -L 9922:server.ip:22 ## minimal sudo -u local.username ssh username@server.ip -Y -C -f -N -L 9922:server.ip:22 ## multiple instances can run in case of disconnect and reconnect This script forwards my local port 9922 to the server’s port 22 via ssh.
That way, I can ssh username@localhost -p 9922 if I wanted to connect to the server. I do this so that file synchronization can resume after a disconnect and reconnect (changed files does not get synced after a reconnect if I connect to the remote server directly). Run sudo cp unisonNetworkOnPortForward /etc/network/if-up.d/ on Debian or Ubuntu. UnisonMonitor.sh: #! Add to /etc/rc.local before the last line: sudo -u local.username /path/to/unisonMonitor.sh & unisonSync.sh: #!
Run unisonSync.sh when you want to manually sync the two folders.
One : Downloads. One : Services. Syncany - Open-source file synchronization and filesharing application. Networking - How can I transfer files between two Ubuntu computers on a LAN without installing additional software. How to synchronize two git repositories. Two machine workflow with git « Thoughts and pictures from central Ohio.
For SCM, our project is using the new hotness in version control – git, hosted on github.com. For a good long while, I was the only contributor who was using the repository there. When you’re the only contributor, you can get away with sins that aren’t acceptable when you’re part of a team. Sins like pushing half-baked code to your SCM as you move back and forth between two machines (I have both a laptop and desktop machine).
But, once you’ve brought others into your team and started hooking up continuous integration services like RunCodeRun, this practice is no longer cool. Like many new to git, it took awhile to get past the centralized mindset that had been pounded into my brain by years and years of thinking of CVS and SVN as the be-all and end-all of how you did these things. Solving my problem of switching machines without impacting my teammates is one of those things that helps to rewire my thinking. The fourth remote is the subject of this post however. To set this up on a Mac: