just wondering: is the ccache also stored in the archive? it would be nice if u had the choise.

well, i gave some hints under "2. How to customise". i don't know where you put your ccache. check the variables, if it is a subfolder of a folder listed in the exclude variables add it to $default_include_list. if not put it either in $default_exclude_list or $custom_exclude_list (i suggest in $custom_exclude_list)._________________Easily backup up your system? klick
Get rid of SSH Brute Force Attempts / Script Kiddies klick

Just tried this one out, and I must say, very nice work indeed. One of my kid's boxes had to be reloaded, so I used my backup to install gentoo on their box, instead of suse or windows, as it had both and was getting pretty messed up. I used the 1.2 version initially and got the console display error. I'm doing the 1.4 version now, and it's a lot better than doing a stage 1 or 3 install on a athlon xp 1900. Just need to create a user account for her and I'll be done. I set the backup file on my internal ftp, and used links from the live cd to get the file, and then untarred it. Very quick way to install gentoo.

Just want to drop in and add my thanks... Getting ready to try some stupid things for the sake of my own stupidity, and did a quick search for backup and found this. Excellent, I was hoping I wouldn't have to write my own. Thanks a lot for sharing this. Gotta love open source.

if your backing up a working install, these should already be taken care of. You might have to update your MBR if it was damaged... but everything else whould have been configured before you backed it up.

Basically, this whole process takes a snapshot of your system, as is (mind you, everything that is created when you boot, like sys/* and proc/ are excluded).

Hi, I have two systems a laptop and a pentium 4 driven desktop workstation. I'm wondering if the CFLAGs I used on my main Gentoo workstation (march=pentium4) are p4 optimized CFLAGS and if this means they will traumatise (or not) my i686 Celeron laptop system due to both processors being compatible with the same architecture somewhat?

Last edited by Asmdroid on Fri Apr 08, 2005 2:05 pm; edited 2 times in total

Hi, I have two systems a laptop and a pentium 4 driven desktop workstation. I'm wondering if the CFLAGs I used on my main Gentoo workstation (march=pentium4) are p4 optimized CFLAGS and if this means they will triaumatise (or not) my i686 Celeron laptop system due to both processors being compatible with the same architecture somewhat?

i'm afraid but that won't work.

/etc/make.conf wrote:

# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.

could you guys specify your problem? how big is your stage4? i never had a tar.bz2 failing on me, although i've started to use tar.gz because of the time gaining. there is a limit to the hole size of the archive (filesystem dependent) - but the creation for the stage4 would stop while creating the tar, so, this isn't the problem_________________Easily backup up your system? klick
Get rid of SSH Brute Force Attempts / Script Kiddies klick

stage4? i never had a tar.bz2 failing on me, although i've started to use tar.gz because of the time gaining. there is a limit to the hole size of the archive (filesystem dependent) - but the creation for the stage4 would stop while creating the tar, so, this isn't the problem

The file that I made was just over 1GB (1.1). I originally stored it to the default directory in the script then transferred across to my USB hard-drive, this took a fair amount of time after continuously sending parts then caching. This could be a problem with my hardware, I'm not sure. The file did include a few useless directories also, CCACHE for example, which isn't appropriate.

do you still have the tar.bz2? could could you experiment further (like extracting ? it doesn't matter if you've inlcuded the ccache folder or not, a tar.bz2 is a tar.bz2 and MUST work.

EDIT: i'm just remembering that i had a lot of errors lately extracting some zipped files, so, did it just break or was it a warning/error at the end of the extracting? if possible post the error message_________________Easily backup up your system? klick
Get rid of SSH Brute Force Attempts / Script Kiddies klick

do you still have the tar.bz2? could could you experiment further (like extracting ? it doesn't matter if you've inlcuded the ccache folder or not, a tar.bz2 is a tar.bz2 and MUST work.

EDIT: i'm just remembering that i had a lot of errors lately extracting some zipped files, so, did it just break or was it a warning/error at the end of the extracting? if possible post the error message

I'm afraid I binned the file so I can't be much help. It was about 3.5Gb because I'd also backed up my /home.

I've managed to restore my system onto a new hard drive using this, but I've ran into a few problems. For instance, I was getting a "Error opening terminal: Eterm." error everytime I tried to run nano, so I tried to fix this by re-emerging ncurses (which seems to be a fix for this sort of problem). However, ncurses fails with:

Any ideas? I saw when I unpacked my stage 4 that it complained about not being able to hardlink a lot of files (don't ask which, it was scrolling way too fast!). Could this be the source of the problem? Do I need to just do an emerge -uD system/world to fix it?

thank you SO much for this script. I just backed up, wiped my system, and tested the restore. IT WORKED FLAWLESSLY.

I really REALLY appreciate all the hard work you put into this backup script. Finally I have something easy and reliable enough to make me want to backup nearly every day (ok ok, i'll keep it to once a week!)

thanks again!

-Feld_________________< bmg505> I think the first line in reiserfsck is

I've managed to restore my system onto a new hard drive using this, but I've ran into a few problems. For instance, I was getting a "Error opening terminal: Eterm." error everytime I tried to run nano, so I tried to fix this by re-emerging ncurses (which seems to be a fix for this sort of problem). However, ncurses fails with:

Any ideas? I saw when I unpacked my stage 4 that it complained about not being able to hardlink a lot of files (don't ask which, it was scrolling way too fast!). Could this be the source of the problem? Do I need to just do an emerge -uD system/world to fix it?

Cheers

Sam

ncurses complains about not being able to run/locate the C++ compiler, which is bad. so i guess you can't emerge anything. i don't know how this happened but could it be due to your personal setup? have you had any hardlinks at all? what does

Code:

# emerge --info
# gcc -info

show?

the only option for hardlinks (if you have any) i saw in tar is

Code:

--check-links
warn if number of hard links to the file on the filesystem mismatch the number of links recorded in the archive

but you need to do that only if you're working with hardlinks and i don't know if it will solve your problem or not. you're the first complaining about this._________________Easily backup up your system? klick
Get rid of SSH Brute Force Attempts / Script Kiddies klick

but you need to do that only if you're working with hardlinks and i don't know if it will solve your problem or not. you're the first complaining about this.

I don't know. I know that I have personally never created any hardlinks...

Of course, the reason I'm doing this restore in this first place is because my old hard drive is on the way out (system just freezes and the logs show a whole load of i/o errors). It might well be that that is the cause of the problem. I did manage to fix this problem by doing a

#emerge --usepkg gcc
#emerge ncurses

Other than that, everything seems to be in tip-top condition. Thanks very much for the script---you've saved me hours of work!