1 |
On 2012-05-23 5:54 PM, Markos Chandras <hwoarang@g.o> wrote: |
2 |
> On 05/23/2012 10:47 PM, Alan McKinnon wrote: |
3 |
>> Tanstaafl wants to know if a reboot*will* be required*before* he does |
4 |
>> the update. What you are describing tells him that after the update |
5 |
>> completes when it is already too late. |
6 |
>> |
7 |
>> I face the same issue at work. We have a change policy requiring 14 |
8 |
>> days advance notice of any change affecting service. If I do a routine |
9 |
>> world update then have to log an emergency change for an unexpected |
10 |
>> reboot, the change manager will have my nuts for breakfast. |
11 |
>> |
12 |
>> If it happens more than once, I'd be having a really unusual |
13 |
>> conversation with the CTO which probably ends with him standing behind |
14 |
>> me watching while I migrate every single box that isn't RHEL6 (all 200 |
15 |
>> of them) over to RHEL6 where I*do* have exact knowledge in advance of |
16 |
>> the impact of a change. |
17 |
|
18 |
> Did either of you ever open a bug about this or even discuss it in the |
19 |
> gentoo-dev mailing list? What you say sounds like a valid concern to me |
20 |
> but unless you express your needs to maintainers, nothing is ever going |
21 |
> to happen. However, in this particular case, yes a news item would be |
22 |
> the ideal solution. |
23 |
|
24 |
I didn't discuss it on the dev list (I'm not a dev), but I did ask a |
25 |
question about this, but it was more general in nature (how to get |
26 |
ewarn/einfo during --pretend): |
27 |
|
28 |
http://forums.gentoo.org/viewtopic.php?p=5930125#5930125 |
29 |
|
30 |
As a result of that thread, I then opened this bug which was |
31 |
subsequently closed: |
32 |
|
33 |
https://bugs.gentoo.org/show_bug.cgi?id=281248 |