I was getting strange, rather annoying behavior on my fedora 8 installed notebook...one day when i came home and booted my notebook it started hanging during the boot process and it was taking ages to give me login screen...today when i went crazy with this stupid HAL daemon hang problem, i checked the /var/log/messages on search for HAL daemon errors & I found the following line i.e.
OCT 30 23:13:35 engineer gnome-keyring-daemon[2671]: failed to initialize a HAL context: (null)
After some googling found on ubuntu's forum one guy fix the same kind of error though changing the HAL daemon's priority and it was solved for him, in fact, its a conflict of priority HAL daemon went in a kind of race condition with some other daemon.
what i did is that, as he suggested moved the HAL daemon almost the last daemon to run in rc5.d directory i.e.
# cd /etc/rc5.d
# mv S98haldaemon S99haldaemon
after doing this trick the problem vanished.
cheers
Why not just use rysnc after booting the target from a livecd (assuming it's a new install), enabling ssh and mounting the target partition?
original:
mkdir /mnt/fake
mount -o bind / /mnt/fake
cd /mnt/fake
rsync -avz --progress ./* user@other.systems.ip.address:/some/mount
/boot /home or /var other other partitions can be done the same way, and attributes are preserved. Bind mounting will keep rsync from trying to copy /proc /dev or /sys from your original / partition, too. Only / has to be bind mounted before copying.
I guess its the perfect way, though there are many other options !
cheers
