** Changed in: silo-installer (Ubuntu)
Status: Confirmed => Fix Released
--
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 maili
This bug was fixed in the package silo - 1.4.14-0ubuntu3
---
silo (1.4.14-0ubuntu3) karmic; urgency=low
* Disable siloconfig from ever running automatically
- siloconfig doesn't properly handle UUIDs, and its default configuration
doesn't set important things like initrd.
** Tags added: patch
--
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.c
The problem sits in the postinst script, which calls siloconfig.
siloconfig is interactive and asks questions in the background:
- Install a boot block using your current SILO configuration?
- Wipe out your old SILO configuration and make a new one?
- Install a partition boot record to boot Li
As anyone can read on [1]:
The officially released architectures for Ubuntu 8.04 will be i386 and
amd64. The SPARC port will continue to be provided with build
infrastructure, and Ubuntu 6.06 LTS, 7.04 and 7.10 will continue to
enable SPARC deployments well into the future, but there will not be
Any news on this topic?
We are few weeks from the final release and I'm trying new net-installers as
they appear but none of them worked.
Please let me know if you need any help testing new images... I'll be very glad
to help you.
Bye
Piero
--
Install hangs on SILO using a LDom on a T5220
http
I noticed an omission in that last bit (should have waited to
cut-n-paste instead of manually making the changes):
partition=1
root=/dev/md0
timeout=20
image=/boot/vmlinuz
label=Linux
read-only
initrd=/boot/initrd.img
image=/boot/vmlinuz.old
label=LinuxOLD
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
** Attachment added: "Syslog dump of installation"
http://launchpadlibrarian.net/12132951/syslog-ubuntu-ldom.txt
--
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 subscri
Looks like silo-installer needs to write out /boot/silo.conf before
installing the silo package into /target. At a guess, anyway.
** Changed in: silo-installer (Ubuntu)
Sourcepackagename: debian-installer => silo-installer
Importance: Undecided => High
--
Install hangs on SILO using a LDom on
Hi there,
my workaround leaves the system bootable but unusable after reboot: it cannot
start any service saying
Warning: Fake start-stop-daemon called, doing nothing.
Bye
Piero
--
Install hangs on SILO using a LDom on a T5220
https://bugs.launchpad.net/bugs/194032
You received this bug notifi
This workaround can't work in my case as I telnet the LDom.
And, If I do a [CTRL-ALT-F2], I'll be on the second tty of my machine
and [ALT-F2] opens the run-command dialog of KDE ;)
--
Install hangs on SILO using a LDom on a T5220
https://bugs.launchpad.net/bugs/194032
You received this bug noti
Here is the workaround:
- go to console 2 (ALT-F2)
- press ENTER
- /target/usr/sbin/siloconfig -r /target
- return to installation screen (ALT-F1)
- press CTRL-C
- continue without installing the bootloader
- finish and reboot
Bye
Piero
--
Install hangs on SILO using a LDom on a T5220
https://b
Hi there,
I'm seeing the same problem here with Ubuntu Hardy Heron ALPHA-5 using the
netboot image found in [1] on a old SUN Ultra5.
Please ask for any other useful info I can provide.
Bye
Piero
[1]http://archive.ubuntu.com/ubuntu/dists/hardy/main/installer-
sparc/current/images/sparc64/netboot
14 matches
Mail list logo
