Ben, in referencing silo's bug #109321 (
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109321 ), it seems the
solution you gave me below (I imagine to be executed under /boot) fixes
or remedies that bug? Has silo version 1.2.3 incorporated a fix
directly? I can't seem to find the fix logs anywhere (broken link?).
If it has been fixed, this bug is still listed under an *active* bug.
My past situation looked strikingly famliar to this bug except I
uncovered a problem after an upgrade to 1.2.3.
Mario
Ben Collins wrote:
>>I was thinking there was a problem with silo trying to look at
>>/etc/silo.conf since it's not contained in the /boot drive partition.
>>Is this possible? I witnessed a silo.conf in the /boot directory
>>partition, but I'm not sure how it got there. The silo execution that
>>fixed my drive was almost eighty characters long cause I had to tell it
>>where to get its information and where to write the boot block etc, etc.
>>
>
>Yeah, this is a non-bugs then. Most likely when it reran itself, it got
>things worng because you had it setup wrong. Best thing to do:
>
>mv /etc/silo.conf /boot
>ln -s /boot/silo.conf /etc/
>ln -s . /boot/etc
>ln -s . /boot/boot
>
>Just to make things clean and easy.
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:28:44 EDT