[hardy]: reinstalling kernel from -proposed/p.u.c makes silo.conf vanish
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi,
noticed this as a side-effect of testing fixes for bug #349655:
installing
* linux-image-
* linux-image-
* linux-restricte
* linux-ubuntu-
from hardy-proposed, then
http://
made silo.conf disappear (i.e. it was a symlink after that to non-existing /boot/silo.conf, not too sure if it was a symlink before, but at least it was present). Other silo files that should have resided in /boot (*.b) were missing as well, just as if silo would have somehow being uninstalled -- even though it was still marked as installed).
There were a few more side-conditions (e.g. I manually purged a few older kernels, and space in boot was a little bit low), but I can say for sure that after these actions silo.conf was still existing.
After installing the package from p.u.c, I rebooted, maybe that might chime in as well (can't say if after the reboot, but before installing the -proposed packages again silo.conf was still present).
Anyway reinstalling silo and taking silo.conf from a backup easily fixed the problem for me.
Cheers,
Stefan.
hm... this is strange, I cannot reproduce this in any way again. Maybe this was just a false alarm, and I've somehow purged silo :/.
Sorry for the noise.