| 1 |
On Wed, 20 Apr 2011 20:12:21 -0500 |
| 2 |
Donnie Berkholz <dberkholz@g.o> wrote: |
| 3 |
|
| 4 |
> From a glance over the guide, it wasn't immediately obvious what in |
| 5 |
> there would result in a broken system. Perhaps it's the "run |
| 6 |
> dispatch-conf" that's buried in the middle of a paragraph without |
| 7 |
> enough emphasis? That's particularly confusing for people who use |
| 8 |
> etc-update instead, and it *needs* to move somewhere more obvious |
| 9 |
> like a separate code listing with big <important> tags and bold text. |
| 10 |
> The line of red text just isn't enough, it needs to stand out even |
| 11 |
> more. |
| 12 |
|
| 13 |
I have converted all my systems to baselayout-2/openrc now, and on all |
| 14 |
of them, the very /last/ message shown after the emerge run is that "[x] |
| 15 |
important configuration files [in /etc]" need to be updated. |
| 16 |
|
| 17 |
I would think that Gentoo users are already primed to this message and |
| 18 |
that they would respond accordingly. Even when it's dozens of packages |
| 19 |
you have updated, this message should stand out, because it's basically |
| 20 |
the first one you read scrolling back up. |
| 21 |
|
| 22 |
> One potential cleaner approach to the same idea Kfir suggested is to |
| 23 |
> make it an interactive emerge with an ACCEPT_LICENSE-like feature |
| 24 |
> that pops up something you must read and agree to. |
| 25 |
|
| 26 |
I've been thinking about an openrc mechanism that refuses rebooting |
| 27 |
(reboot, halt, which are calls that openrc handles) |
| 28 |
when /etc/{conf,init}.d files have not been updated. Anyone game to get |
| 29 |
coding? :) |
| 30 |
|
| 31 |
|
| 32 |
jer |
Archives