SOLVED: Emerging SILO overwrites silo.conf??

russofris · Apprentice Joined: 14 Sep 2003 Posts: 163

Ignore below... I'm a fool and didn't see it in etc update (I usually just lok for etc/conf.d/* changes ).

My Bad.

_____________________________________________________________________________

Hi there,

This has happened a number of times to me.... When I emerge, or re-emerge SILO, it seems to overwrite the /etc/silo.conf. It does not make use of etc-update, it simply overwrites the file. This is annoying if you have kernels named "gentoo-sparc--2.4.32-r1" in /boot because... well, it's often hard to remember exactly what the kernel name was when a reboot fails. So I end up booting from a livecd, looking at the 3 kernels I have in /boot, and rebuilding the silo.conf.

Has anyone else experienced this? I will look to see if a bug has been filed, and will file one if this seems to be a problem that nobody has reported yet.

Thanx Muchly,
Frank Russo

mightyhal · n00b Joined: 30 Jan 2006 Posts: 15

I've overwritten my /etc/silo.conf several times... I suppose I need to be more careful when etc-updating, but to be honest, I still don't understand why it is set to update my silo.conf file anyway--the conf file it puts in there is huge, with tons of comments and is never right for anyone's setup...

A far more graceful way would be to have an emerge of silo name the file silo.conf.example, since no one needs the silly thing as their actual silo.conf anyway. And it'd make it harder to overwrite silo.conf... which is a pain to fix =)
_________________
MightyHal
---
Sun Blade 1000 dual 900 MHz...

Drunkula · Posted: Fri Mar 10, 2006 2:17 pm Post subject:

Sucks, doesn't it?

Whenever I think of it I try to keep copies of critical files (silo.conf, fstab....) stored in rcs or cvs depending on what's available. It may not be the best solution but it has saved me before.
_________________
Go away or I will replace you with a very small shell script.

russofris · Apprentice Joined: 14 Sep 2003 Posts: 163

As a workaround, you can copy your working silo.conf to /boot and silo -c /boot/silo.conf -f or something. This way, /etc/silo.conf can change all it wants, and as long as the format stays the same, you're all good. Thoughts?

Frank