I tried:
yabootconfig -r /dev/hda11 -b /dev/hda13 -t /mnt/sysimage
and got this:
id: unknown group name: 0
/mnt/sysimage/sbin/yabootconfig: line 455: [: != unary operator expected
Install yaboot bootstrap on /dev/hda13 to boot from Linux from /dev/hda11? [Yes]
Creating a simple /mnt/sysimage/etc/yaboot.conf
yabootconfig: Cannot find a kernel, please locate one
Enter path to a kernet image:
When I entered "/boot/initrd-2.6.9-1.667.img" I got "No such file or
directory"
Then I entered "/mtn/sysimage/boot/initrd-2.6.9-1.667.img" I got:
yabootconfig: Unable to determine OpenFirmware device name to /dev/hda, aborting...
Any thoughts?
Thanks,
Soetji
Christian Walther wrote:
Soetji Anto wrote:
> I didn't find /etc/yaboot.conf instead I found it at
> /mnt/sysimages/etc/yaboot.conf. The file has already:
> initrd=/boot/initrd-2.6.9-1.667.img
>
> When I run:
> yabootconfig -r /dev/hda11 -b /dev/hda13
>
> I got the following error:
> id: unknown group name: 0
> /mnt/sysimage/sbin/yabootconfig: line 455: [: != unary operator expected
> yabootconfig: / does not appear to be a valid root filesystem
Try
yabootconfig -r /dev/hda11 -b /dev/hda13 -t /mnt/sysimage
While we're at it, here's my own experience with yabootconfig in a HD
install from the re1115.0 ISOs I did yesterday:
o At the end of the install, there's no yaboot.conf anywhere
o Running yabootconfig fails because it expects the device from which
/mnt/sysimage is mounted to be in /dev/, but it is /tmp/hda13. After a
few failed attempts at fixing yabootconfig to cope with this situation,
I got it to work by just hardcoding the right values into yabootconfig.
-Christian
_______________________________________________
Fedora-ppc mailing list
Fedora-ppc(a)lists.infradead.org
http://lists.infradead.org/mailman/listinfo/fedora-ppc