Here's an intro to using rsync for back-up on the Pi. Once the initial back-up is created, keeping it up to date this way is much much faster than constantly ripping the entire image. You can do this to a local hard drive or over a network.
You actually do not want a complete copy of a running system as a back-up, since some of the stuff ostensibly in the ...
This question is answered as part of the answer to other questions, but it deserves canonical treatment here so it does not have to keep being repeated.
You can't mount the image as a whole because it actually contains two partitions and a boot sector. However, you can mount the individual partitions in the image if you know their offset inside the file. ...
I finally found a resource that is explaining my question.
Yes, truncating is possible!
Summary of the process:
Extracting the partition information from the image using fdisk:
$ fdisk -lu image.img
Disk image.img: 4096 MB, 4096000000 bytes, 8000000 sectors
Units = sectors of 1 * 512 = 512 ...
Custom Splash Screen for Raspberry Pi (Raspbian)
This is a quick and dirty solution for an unanimated custom splash screen during boot.
First of all, you need to install fbi:
apt-get install fbi
Copy your custom splash image to /etc/ and name it "splash.png".
Next, create an init.d script called "asplashscreen" in "/etc/init.d/".
I chose "asplashscreen"...
A working script from the Raspberry Community made by a member there.
You can reuse and tweak the code how ever you like.It is well documented and self explanatory.
# Setting up directories
echo "Starting RaspberryPI backup process!"
# First check if pv package is installed, if not, install it ...
Just use the unxz program:
Note: the original file will be removed. Only the .img file will remain.
If you want to keep the original archive, use
unxz --keep kali-1.1.0-rpi2.img.xz
To take pictures in 0.025s with picamera you'll need a frame-rate greater than or equal to 80fps. The reason for requiring 80 rather 40fps (given that 1/0.025=40) is that currently there's some issue which causes every other frame to get skipped in the multi-image encoder so the effective capture rate winds up as half the camera's framerate.
The Pi's camera ...
You can take a look at Splashy for creating a custom loading (splash) screen.
I can't see it on the list of official packages, so you would have to compile it from source. It is available via git from here.
You should be able to check out the source and build like this:
git clone https://anonscm.debian.org/git/splashy/splashy.git
You mention in a comment to RooTer that A) you have reduced the initial partition size with gparted, but dd still copies the whole card, and B) that you want to include both partitions in the image.
Issue "A" is easy to explain: you are still copying the whole card because that's what /dev/mmcblk0 refers to. The individual partitions are of course /dev/...
you need to recompile a kernel in order to do that.
create your image with no more than 224 colors, and 80x80px in size.
Save the image as png, and run the following (provided you have netpbm installed and kernel source in /usr/src/linux):
$ pngtopnm logo.png | ppmquant -fs 223 | pnmtoplainpnm > logo_linux_clut224.ppm
$ cp logo_linux_clut224.ppm /...
Update 2014-01-29: It has just been announced that the arm/armv6 snapshot images for Raspberry Pi are now being pushed up to the FreeBSD FTP servers on a weekly basis. You can download a copy from your local FreeBSD FTP mirror, in the /pub/FreeBSD/snapshots/ISO-IMAGES/ folder.
Update 2014-01-28: Glen Barber kindly published this SD image of the recent ...
losetup provides partition probing through -P. Using this makes mounting partitions of a full disk image such as the Raspbian SD card image very easy:
losetup -P /dev/loop0 raspbian.img
mount /dev/loop0p2 /mnt
mount /dev/loop0p1 /mnt/boot
I have adapted @goldilocks answer on rsync for back-up on the pi.
I backup to an ext4 partition on a HDD mounted on the Pi.
If the HDD is not mounted, rsync would copy to the mount directory (until the SD Card is full).
If the HDD is not mounted in rw mode copious error messages are produced.
Neither of these is desirable, so I check that my partition is is ...
On Linux or OSX I use dd to make a backup from SD card. Reverse if and of (i.e. to where they point - source and destination) afterwards to restore, but be careful not to restore to a wrong disk. It will be destroyed without a warning!!!
First use fdisk to get the device id of you SD card (check the size)
then I use dd to make a diskimage (...
In this answer, I demonstrate what to do step-by-step for people to understand the logic behind the solution and to be able to apply steps in their other problems.
But firstly, it should be stated that it is a generic (not raspi specific) problem to migrate filesystems from an SD card to a smaller (but big enough for data) SD card.
A laptop ...
So the best way I have found is to use GParted (you can either use a Linux-based OS, or boot from a GParted Live USB). It is simple enough to find detailed instructions on how to do each of these steps in detail, but here is the general method I have found to work:
Run GParted, find your SD card in the device list and shrink the main partition to as small ...
I think you should look into doing this so you can take and restore backups of your card from time to time. Once you get a second card and as long as you don't destroy the original one, it should be easy to experiment. And yes, it should work.
Some instructions on how to set up a card image can be found on the RPI wiki "easy SD card setup". There's also a ...
There are several programs to take screenshots. I use scrot, a command line utility wich is quite complete. In your case:
sudo apt-get install scrot
scrot -s and click on the midori window. You will get a timestamp-based png in the working directory of your terminal. See man scrot for more options!
Yes, you can repartition your card to reclaim the unused space. If you are using Raspbian then you have the option to do this as part of the initial boot. Otherwise you can refer to "How can I resize my / (root) partition?" for more information.
Ok so I finally found an answer and I wish to share it with you guys.
My guess is that the creators created the compressed file from an expanded image by mistake.
The fact that the compressed file is nearly 1.1 GB, compared to 8.1 GB of the extracted files, proves this. Empty space will compress to a couple of bytes. If there were additional packages, there ...
It's shutting down just fine. If you check the schematic, you'll see there is no power management. From USB in to the SoC is just copper (and a fuse), so the chip stays powered up even when it's shut down.
What do I do once I have run shutdown -h now?
Just remove the USB from the socket.
You could try epeg. It's designed exactly for the job you need - to create fast thumbnails from jpeg files. The only problem is, you need to compile it yourself as there is no package for it for RaspberryPi. It's a library but it comes with a simple test tool that you can use.
Linux / OSX
Download the image from here
Extract the .xz file using any of the following methods
tar xf CentOS-Userland-7-armv7hl-Minimal-1511-RaspberryPi2.img.xz
The Unarchiver (OSX)
Install from Mac App Store here
Use the disk cloning command dd to copy the img contents to your ...
Not quite. You would overwrite the partition tables when you re-image it and replace said tables with the ones from the image. After your imaging program is done, it would release the file handle to the image file, but since the partition where the file is stored technically doesn't exist anymore, your program can't read it again. In theory, it would work ...
This is how to resize a raw image file. I know it sounds stupidly simplistic, but it will work.
Create a blank image, of the size you want to expand the original (in my example I use 5GB);
dd if=/dev/zero of=/path/to/temp_image bs=1 count=1 seek=5G
Append this to the original image:
cat /path/to/temp_image >> /path/to/rasperrypi.img
Resize the ...
I had the same requirements as 1 and 2 to distribute a customized OS. After looking around I found many commands, but not a single tool to create a compact .zip file from an SD card, so I wrote mkimg.sh, which works like this:
sudo bash mkimg.sh /dev/sda sdcard.img.zip
This takes the unmounted device at /dev/sda, shrinks down the filesystem and partition, ...
There are a couple of easy prep steps to do before writing a clone master to copies which will save you a lot of headaches.
Configure the clone master for DHCP
Delete everything in /etc/ssh/ssh_host* (these get recreated when you run SSHD)
if you have an /etc/udev/rules.d/70-network* file, you'll need to modify the eth0 entry to something else (I used eth9 ...