Spida
01-22-2002, 02:39 PM
Hi!
I just cloned one of my systems using tar and a server.
However, now it boots only to the INIT Prompt, showing "INIT-2.4#" How do I get my init-scripts started?
Here is what I did:
On the source system (Redhat 7.1 with 2.4.17):
tar -c -z -v --exclude /mnt/net --exclude /proc -f /mnt/net/image.tar.gz
On the target system (blank system, booted with SuSE Rescue-system, fdisk done):
mount /dev/sda1 /mnt
mkdir /mnt/var
mount /dev/sda5 /mnt/var
cd /mnt
umask 0000
ssh root@ip-of-server "dd if=/path-to/image.tar.gz" | tar xvpz
after that, I chrooted to "/mnt", build a new kernel, and build, installed and configured grub as bootloader.
the grub line says:
kernel (hd0,0)/boot/bzImage-2.4.17 root=/dev/sda1
but because the kernel starts and does a succesfull rw mount on both "/" and "/var", my problem should be somewhere near the init-config.
Please help
Spida
I just cloned one of my systems using tar and a server.
However, now it boots only to the INIT Prompt, showing "INIT-2.4#" How do I get my init-scripts started?
Here is what I did:
On the source system (Redhat 7.1 with 2.4.17):
tar -c -z -v --exclude /mnt/net --exclude /proc -f /mnt/net/image.tar.gz
On the target system (blank system, booted with SuSE Rescue-system, fdisk done):
mount /dev/sda1 /mnt
mkdir /mnt/var
mount /dev/sda5 /mnt/var
cd /mnt
umask 0000
ssh root@ip-of-server "dd if=/path-to/image.tar.gz" | tar xvpz
after that, I chrooted to "/mnt", build a new kernel, and build, installed and configured grub as bootloader.
the grub line says:
kernel (hd0,0)/boot/bzImage-2.4.17 root=/dev/sda1
but because the kernel starts and does a succesfull rw mount on both "/" and "/var", my problem should be somewhere near the init-config.
Please help
Spida