P4M's should be i686 compatible shouldn't they ?
I noticed the other week that the Ubuntu installer had selected the i386 kernel build on my Thinkpad...thinking that this was a mistake on the part of the installer I changed this to the i686 one (moving restricted modules over to i686 as well after my wireless broke)
Since doing that I have experienced a couple of hard lockups...two when running Mozilla Firefox and one when using VMware Player (The VMware kernel modules taint the kernel but they don't usually give me any bother) Similarly I have never heard of Firefox crashes killing a whole machine.
Moving back to the i386 kernel I cannot repeat these problems.
My understanding is that i686 was everything from a Pentium Pro upwards..the P4M being based on the PIII core I thought this would be fine, but maybe there are some instructions not implemented on the P4M...Any thoughts ? My Music server (A real PIII) is running the i686 kernel and is rock solid.
I'm not sure about your i686 kernel issues (tho I have heard of them before...). But the Install CD has limited space, they do not have room for i686 kernels as well, so they go for the lowest common denominator and install i386 which should work on all machines. This isn't isn't a mistake from the installer. Just so you know.
As far as I know, Pentium 4 M's should be i686... Don't know what's causing your problems there...
On Sat, 2006-02-04 at 18:06 +0000, Richard Brooklyn wrote:
I'm not sure about your i686 kernel issues (tho I have heard of them before...). But the Install CD has limited space, they do not have room for i686 kernels as well, so they go for the lowest common denominator and install i386 which should work on all machines. This isn't isn't a mistake from the installer. Just so you know.
That did cross my mind, but the Music Server was installed in the same way from the same media yet it is running the i686 kernel (I didn't change that one manually)
On Sat, 2006-02-04 at 23:00 +0000, Wayne Stallwood wrote:
for i686 kernels as well, so they go for the lowest common denominator and install i386 which should work on all machines. This isn't isn't a mistake from the installer. Just so you know.
That did cross my mind, but the Music Server was installed in the same way from the same media yet it is running the i686 kernel (I didn't change that one manually)
Are you using a DVD installation disc? The normal CD one only contains a i386 kernel as far as I know... Maybe Pentium M's have issues with some i686 instructions or something.... *shrug*
On Sun, 2006-02-05 at 11:06 +0000, Richard Brooklyn wrote:
Are you using a DVD installation disc? The normal CD one only contains a i386 kernel as far as I know... Maybe Pentium M's have issues with some i686 instructions or something.... *shrug*
AFAIK Ubuntu don't offer a DVD installation. You just get a basic installation with the rest then coming from the on-line repository.
Googling about it seems that both P-M's and P4M's (which are different BTW) should be happy with i686 instructions, the only reference I can find to anything similar was a guy running a i686 kernel build on an AMD k7.
Seeing as the kernel is still an option in my bootloader, I may start it up again and take a closer look to see if I missed anything when I tried to change over to it...perhaps system.map or somesuch.
On Sunday 05 February 2006 11:22, Wayne Stallwood wrote:
On Sun, 2006-02-05 at 11:06 +0000, Richard Brooklyn wrote:
Are you using a DVD installation disc? The normal CD one only contains a i386 kernel as far as I know... Maybe Pentium M's have issues with some i686 instructions or something.... *shrug*
Googling about it seems that both P-M's and P4M's (which are different BTW) should be happy with i686 instructions, the only reference I can find to anything similar was a guy running a i686 kernel build on an AMD k7.
If you run a i686 kernel, it would be worth installing libc6-i686 to take advantage of the new CPU instructions as well as any optimisations the compiler brings.
It is possible that running libc6-i686 on top of a i386 kernel may produce some unexpected results, but the other way round should be perfectly safe.
Regards, Paul.
I have two hard drives in my computer. One is the working drive and the other is a backup copy of the working drive. The backup drive is updated once a day where files have changed.
I want to be able to run a script, at intervals, which will check all the files on the backup drive and delete those which are no longer present on the working drive.
The root directory on the working drive will, of course, be / and the root of the backup drive will be something like /mnt/point.
I'm having considerable difficulty in working out how to do this.
Some help would be very welcome from the scripting experts.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On 2/9/06, Barry Samuels bjsamuels@beenthere-donethat.org.uk wrote:
I want to be able to run a script, at intervals, which will check all the files on the backup drive and delete those which are no longer present on the working drive.
What if you accidently delete the original file? You'll lose the backup!
Be careful what you wish for.
Tim.
On Thu, Feb 09, 2006 at 02:07:10PM +0000, Barry Samuels wrote:
I have two hard drives in my computer. One is the working drive and the other is a backup copy of the working drive. The backup drive is updated once a day where files have changed.
I want to be able to run a script, at intervals, which will check all the files on the backup drive and delete those which are no longer present on the working drive.
Have you investigated "rsync"?
J.
On 2006.02.09 14:11, Tim Green wrote:
On 2/9/06, Barry Samuels bjsamuels@beenthere-donethat.org.uk wrote:
I want to be able to run a script, at intervals, which will check
all the files on the backup drive and delete those which are no longer present on the working drive.
What if you accidently delete the original file? You'll lose the backup!
Be careful what you wish for.
Tim.
I don't understand that. What original file? How will I lose the backup.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
On 2/9/06, Barry Samuels bjsamuels@beenthere-donethat.org.uk wrote:
On 2006.02.09 14:11, Tim Green wrote:
On 2/9/06, Barry Samuels bjsamuels@beenthere-donethat.org.uk wrote:
I want to be able to run a script, at intervals, which will check
all the files on the backup drive and delete those which are no longer present on the working drive.
What if you accidently delete the original file? You'll lose the backup!
I don't understand that. What original file? How will I lose the backup.
I'll give an example:
You have a file called VImportant.txt, and there is a copy on the backup drive.
One day you accidentally delete VImportant.txt, and then your script will delete the copy on the backup drive.
The file is gone, and so has the backup.
Are you sure this is what you want?
Tim.
Barry Samuels wrote:
I have two hard drives in my computer. One is the working drive and the other is a backup copy of the working drive. The backup drive is updated once a day where files have changed.
I want to be able to run a script, at intervals, which will check all the files on the backup drive and delete those which are no longer present on the working drive.
The root directory on the working drive will, of course, be / and the root of the backup drive will be something like /mnt/point.
I'm having considerable difficulty in working out how to do this.
Some help would be very welcome from the scripting experts.
Take a look at rdiff-backup. It does what you want, but also saves versions so you can restore deleted files, and/or previous versions. In other words, the main backup reflects the contents of your "mirrored" drive, but elsewhere in the archive it stores versioning info such that deleted files can be restored.
See: http://www.nongnu.org/rdiff-backup/
From that page:
"What is it?
rdiff-backup backs up one directory to another, possibly over a network. The target directory ends up a copy of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the best features of a mirror and an incremental backup. rdiff-backup also preserves subdirectories, hard links, dev files, permissions, uid/gid ownership, modification times, extended attributes, acls, and resource forks. Also, rdiff-backup can operate in a bandwidth efficient manner over a pipe, like rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive up to a remote location, and only the differences will be transmitted. Finally, rdiff-backup is easy to use and settings have sensical defaults."
Gentoo has an ebuild for this. We use it extensively over SSH using keys to back up remote sites.
Cheers, Laurie.
On Thu, Feb 09, 2006 at 02:07:10PM +0000, Barry Samuels wrote:
I have two hard drives in my computer. One is the working drive and the other is a backup copy of the working drive. The backup drive is updated once a day where files have changed.
I want to be able to run a script, at intervals, which will check all the files on the backup drive and delete those which are no longer present on the working drive.
The root directory on the working drive will, of course, be / and the root of the backup drive will be something like /mnt/point.
I'm having considerable difficulty in working out how to do this.
Some help would be very welcome from the scripting experts.
I'm pretty sure that rsync can do this for you all on a single command line.
Jonathan McDowell noodles@earth.li
On Thu, Feb 09, 2006 at 02:07:10PM +0000, Barry Samuels wrote:
I want to be able to run a script, at intervals, which will check all the files on the backup drive and delete those which are no longer present on the working drive.
Have you investigated "rsync"?
I think that's a good idea. rsnapshot could add features which might be useful, too.
Hope that helps,
On 09/02/06, Chris Green chris@areti.co.uk wrote:
I'm pretty sure that rsync can do this for you all on a single command line.
I use dirvish, which makes a rotational 14 images of your data using rsync, but uses links so that the data doesn't take up much more space. Jen
On 2006.02.09 14:45, Tim Green wrote:
I'll give an example:
You have a file called VImportant.txt, and there is a copy on the backup drive.
One day you accidentally delete VImportant.txt, and then your script will delete the copy on the backup drive.
The file is gone, and so has the backup.
Are you sure this is what you want?
Tim.
Yes that is what I want. I probably shouldn't have used the term backup in my original post. I want to maintain a mirror copy of my main drive (no I don't want RAID) although I have a tape backup system in place.
The clean up operation, to remove redundant files, would take place only at infrequent intervals.
Jonathan give me a prod in the right direction. I don't have rsync installed but I do have Unison so I'm going to use that for the infrequent cleanups particularly as it has a GUI front-end. I can then check the files before they are deleted.
Thanks to all for the various suggestions.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain
-
Barry Samuels -
Chris Green -
Jenny Hopkins -
Jonathan McDowell -
Laurie Brown -
MJ Ray -
Paul -
Richard Brooklyn -
Tim Green -
Wayne Stallwood