hm... s.th. just ate my silo.conf (i.e. made a link from /etc/silo.conf
to /boot/silo.conf, which is now no longer existant). What I've done is
upgrading from the package posted on people.ubuntu.com to the package
from proposed again. Is this related to the package in -proposed, or
just a side effect from the package on p.u.c?

-- 
[hardy][sparc]: new kernel in security doesn't boot
https://bugs.launchpad.net/bugs/349655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to