Since my report (bug 203947) has been marked a duplicate of this one, I
thought I'd chime in:
I netbooted, chrooted into my mostly installed system and performed the
following:
apt-get --purge remove silo
then:
[EMAIL PROTECTED]:/# apt-get install silo
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
silo
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/179kB of archives.
After this operation, 393kB of additional disk space will be used.
Selecting previously deselected package silo.
(Reading database ... 15512 files and directories currently installed.)
Unpacking silo (from .../silo_1.4.13a+git20070930-1ubuntu1_sparc.deb) ...
Setting up silo (1.4.13a+git20070930-1ubuntu1) ...
SILO, the Sparc Improved LOader, sets up your system to boot Linux
directly from your hard disk, without the need for a boot floppy or a net
boot.
Install a partition boot record to boot Linux from
UUID=3cb47072-33de-49fd-aed6-d77ccea87723? [Yes]
Creating small silo.conf and running silo.
Config file error: Syntax error near line 1 in file /etc/silo.conf
Error parsing silo config file /etc/silo.conf
[EMAIL PROTECTED]:/# cat /etc/silo.conf
partition=87723
root=UUID=3cb47072-33de-49fd-aed6-d77ccea87723
timeout=20
image=/vmlinuz
label=Linux
read-only
image=/vmlinuz.old
label=LinuxOLD
read-only
Note that SILO counts the lines in the config file starting at 0, so it
looks like the problems with the auto-generated file are:
1) the "root=" line uses a UUID, and SILO doesn't understand UUIDs
2) vmlinuz lives in /boot/ if you don't have a separate /boot partition. So
the correct path in this case would be /boot/vmlinuz
If I again netboot/chroot, edit /etc/silo.conf, and change it to :
partition=1
root=/dev/md0
timeout=20
image=/boot/vmlinuz
label=Linux
read-only
image=/boot/vmlinuz.old
label=LinuxOLD
read-only
My system will then boot.
--
Install hangs on SILO using a LDom on a T5220
https://bugs.launchpad.net/bugs/194032
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
