On 10/30/2014 11:19 AM, Teo wrote:
> Will I (and others in my situation) hit the problem again "only"
> when dist-upgrading to 14.10 (which is already out btw) or also
> when installing the grub updates that have been available for a
> while? (which I have always avoided installing just in case)?
It can happen on any update, but won't necessarily happen on every update.
> Secondly and most important, what should I do "so that the package
> system knows" whatever it needs to know, so that I can
> dist-upgrade without screwing up my working system again?
Assuming you are on a bios booting machine and therefore using
grub-pc, use dpkg-reconfigure grub-pc to select the correct drive(s)
where it should be installed.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/30/2014 11:19 AM, Teo wrote:
> Will I (and others in my situation) hit the problem again "only"
> when dist-upgrading to 14.10 (which is already out btw) or also
> when installing the grub updates that have been available for a
> while? (which I have always avoided installing just in case)?
It can happen on any update, but won't necessarily happen on every update.
> Secondly and most important, what should I do "so that the package
> system knows" whatever it needs to know, so that I can
> dist-upgrade without screwing up my working system again?
Assuming you are on a bios booting machine and therefore using
grub-pc, use dpkg-reconfigure grub-pc to select the correct drive(s)
where it should be installed.
-----BEGIN PGP SIGNATURE-----
UUnY1AAoJEI5FoC IzSKrwZxQH/ jWlHYbmK7WdHiNV 0iSlK3Ux hQyzL1E+ CvkVmSr2Rg+ 9gUXFH43VREa/ VlftCYWjYghAjmZ u/wT9B8o uTc8ZCPRNC1rdnm UdetaG8ed5SNiFl /sl2q/dlrVDcEXA PwyI bbkMeoCxHUs4ak5 SHkIVXri2O1cAyo DUSMcyUrJBhnmy+ dcD/ iSSzRLT+ 6GcSEoNNUXAvg1U 7hpaqiYug10xBhW h5NIVE2waaw 3uGED2K7hlXvLD+ 9QOaTtEKcVikmcT mS8kw2FMyEvU9g0 sQA=
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJ
U4ANKhj6/
fBeoLt4teeTiN0Q
wPruW60Ku5dxoqh
AdD2FtiXUr8kykQ
L9alqFZHViWp0NR
=9F0a
-----END PGP SIGNATURE-----