Tag Info

Hot answers tagged

12

You start at the beginning, square one. I'm sorry but you wiped everything, that's a brutal command. Not only did you wipe out the linux install, but you took the windows data with it. What you did didn't just wipe stuff in the partitions (/dev/sda1, 2, etc.), it wiped the partition table too because it matched /dev/sda which is the drive device itself. ...


10

I think you are looking for lvconvert --merge. From the man page: --merge Merges a snapshot into its origin volume. To check if your kernel supports this feature, look for snapshot-merge in the output of dmsetup targets. If both the origin and snapshot volume are not open the merge will start immediately. Otherwise, the merge ...


7

Arch isn't designed to work like that: it is a rolling release, so you are always going to have to continue to upgrade packages as they are pushed to your repo: the only alternative is to freeze everything. Having said that, what you are asking can best be managed, within the Arch framework by doing two things: updating regularly (so that you are only ...


6

First off - stop the VM or remount the volume as read only: mount -o remount,ro /home/ Presuming you are using ext[3,4], you are not lost, but it's not an easy task. The data blocks themselves are not cleared, but the pointers (inodes) are. Most files can be recovered using tools such as photorec . It will identify a file based on it's magic number. ...


5

LVM does support read-write snapshots in fact that's the default. Merging a modified snapshot will delete the data on the snapshot origin volume the same way merging an unmodified snapshot would. If you expect to discard modifications then I recommend RW snapshots and merge if you want to keep them. If you expect to keep the modifications then you should ...


3

First off, you should read up a little on rsync's include/exclude syntax. I get the feeling that what you want to do is better done using ** globs than * globs. (** expands to any number of entries, whereas * expands only to a single entry possibly matching multiple directory entries. The details are in man rsync under Include/Exclude Pattern Rules.) That ...


3

Most of what you are trying to do can probably be accomplished simply by using the one_fs setting. Set the filesystems you want to include in your backups, then use that setting to ignore the rest (proc, sys, dev, etc.). I'd include /lost+found because that directory should always be empty unless you've backed-up a corrupted filesystem, in which case you ...


3

Linux distros in general are not set up with anything like a restore system. There are small exceptions. The RPM based distro I use keeps an archive of all previous versions of packages when they are upgraded. It's possible to install those packages and roll the software back to what it was before an upgrade, but this creates dependency chaos and is less ...


3

You should be able to tar up everything and extract it to the new drive. First plug in the second drive, then boot into something that doesn't use the source drive, such as a live CD. After that just copy everything over. For example: # Mount the source drive mkdir /mnt/source mount /dev/sda1 /mnt/source # Mount the destination drive mkdir /mnt/destination ...


3

(If you have three questions, it's better to ask three separate questions. But since the answers are short I'll answer them all.) Both rsync and rdiff-backup have fairly powerful file selection mechanisms, based on inclusion and exclusion rules. I wrote an rsync filter tutorial. Rdiff-backup's filters are based on the same principles but the details are ...


2

It's going to depend on the filesystem you're using, not just the OS or package manager. If you run / on btrfs, you could leverage its snapshot ability to do this. I've only just started in with Arch, but as an example of what could be done: Ubuntu has apt-btrfs-snapshot. It's a relatively simple script that hooks into apt to create a btrfs snapshot right ...


2

You colud use Clonezilla. It is Linux LiveCD distribution created to make backup copies of full disks or partitions. Download it, burn on CD and boot computer. After that you need to choose source and destination - when you want to back up whole drive you need another drive to write backup on it. When you choose to back up only one partition your backup can ...


2

You can use chmod to first copy permissions to the backup. chmod --reference <reference> <target> Copy backup file to linux system using a different name like file.bak cp /mnt/windows/FILE /etc/directory/FILE.bak apply the permissions from the original file chmod --reference /etc/directory/FILE /etc/directory/FILE.bak mv backup to target ...


2

I suggest you to use rsync instead of backuping your files manually. With this tool, you can do exactly what you're doing with some extra features. For example, you can pass the --progress argument to know the last file copied. Another feature is that you can copy only the new files or the modified ones, which will reduce the amount of data transmitted ...


2

Right off the bat make a dd disk image of the drive, and work with that instead of the drive itself. That lets you experiment. dd if=/dev/sda3 bs=1M > sda3.img Beyond that I'm not sure. I'd hit google. Might look at it later. edit; http://www.cgsecurity.org/wiki/TestDisk looks promising.


2

First of all you should be aware of slapcat's limitations: For some backend types, your slapd(8) should not be running (at least, not in read-write mode) when you do this to ensure consistency of the database. It is always safe to run slapcat with the slapd-bdb(5), slapd-hdb(5), and slapd-null(5) backends. So you better pack that backup in ...


2

The CVSWeb got it covered, but ident /etc/rc.d/rtadvd on my 8.2-RELEASE-p3 system yields $FreeBSD: src/etc/rc.d/rtadvd,v 1.12.2.1.6.1 2010/12/21 17:09:25 kensmith Exp $ which I can't find there... hope this still helps, rev 1.12 is tagged RELENG_8.


1

The source code has this: for (cp = fp->fname; *cp; cp++) if (!vflag && (*cp < ' ' || *cp >= 0177)) *cp = '?'; So it looks like it will substitute '?' for non-printable-ASCII characters unless you give restore the -v option or, in interactive mode, type the verbose command.


1

Dumping a tarball of / is likely not going to work very well, as you end up overwriting a ton of stuff specific to the "new" machine. You're much better off just backing up only the things not included in a stock operating system install. It's generally a better idea to separate your configuration from your data, and separate them both from the operating ...


1

If you have the binary .deb file, you can use Midnight commander (mc) from the shell to just navigate inside and retrieve files from it. For your convenience, this is the file as found in pure-ftpd-mysql_1.0.36-1.1_i386.deb: #! /bin/sh ### BEGIN INIT INFO # Provides: pure-ftpd-mysql # Required-Start: $remote_fs $syslog # Required-Stop: ...


1

For Solaris-only, look at "ZFS send" (assuming Solaris 10 update 2 or later). The process is to first take a snapshot, and then "send" it to another place. Eg: zfs snapshot POOL/dataset@backup1 zfs send POOL/dataset@backup1 | ssh $USER@$HOST zfs receive $TARGETPOOL/$TARGETDATASET The above solution have rock solid reliability. rsync is your second best ...


1

By and large I'm afraid the unix paradigm is that you're expected not to make mistakes like that, or to have backups in place. You can try recovering some of the files with foremost but I've never had cause to work with it so I don't know how much help it'll be.


1

This file is in the base system, so grab the base system archive and extract that particular file. cd /tmp wget -r ftp://ftp.fi.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/base cd / cat /tmp/ftp.fi.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/base/base.?? | tar -xzf - etc/rc.d/rtadvd Alternatively, since this file is identical to its source, ...


1

My advice: Restore your backup. If you don't have a backup: After re-installing from scratch - this is the time to setup a regular backup job. A backup job could also save the output of fdisk -l and the MBR (the first 512 (?) bytes of the boot device via dd). Of course: You could also do some repair attempts to rescue your Ubuntu Partition (which starts > ...



Only top voted, non community-wiki answers of a minimum length are eligible