| 1 |
On Thu, 2012-03-22 at 07:48 -0600, schism@×××××××××.org wrote: |
| 2 |
> Normally I don't take to the skies with this sort of thing, but this was |
| 3 |
> ridiculous. In what I am sure was a well-intentioned change, cryptsetup |
| 4 |
> recently silently lost its default USE=static status. For one of the |
| 5 |
> many people actually using cryptsetup in an initrd, this came as a |
| 6 |
> lovely surprise this morning as I found my new kernel/initrd completely |
| 7 |
> unbootable. |
| 8 |
> |
| 9 |
> To compound matters, udev-181's incompatibility with my old kernel (no |
| 10 |
> DEVTMPFS, separate /usr), and my primary system was completely |
| 11 |
> unbootable. |
| 12 |
> |
| 13 |
> Please - if you're going to significantly change functionality that |
| 14 |
> (whether correct or not) people have come to depend on, have the decency |
| 15 |
> to at least publish a news article on it. I may find 'eselect news' |
| 16 |
> annoying, but I at least read it. Before we get to bikeshedding, I'm |
| 17 |
> well aware there were multiple ways to have prevented this, but none of |
| 18 |
> them were in place [1]. What was in place was default behavior that had |
| 19 |
> been there for a very long time. |
| 20 |
> |
| 21 |
> |
| 22 |
> [1] For one, genkernel should bomb out if it can't comply with a |
| 23 |
> command-line arg instead of just putting non-alert text up. |
| 24 |
|
| 25 |
There is already a bug open about this issue: |
| 26 |
https://bugs.gentoo.org/show_bug.cgi?id=409277 |
| 27 |
|
| 28 |
However, I must still thank you for alerting the list about it; you |
| 29 |
saved lots of peoples' systems (probably including mine, if I had not |
| 30 |
read this message) from being rendered unbootable. |
| 31 |
|
| 32 |
-Alexandre Rostovtsev. |
Archives