| 1 |
On Tue, Oct 14, 2014 at 10:39 PM, Grant Edwards |
| 2 |
<grant.b.edwards@×××××.com> wrote: |
| 3 |
> On 2014-10-15, Alec Ten Harmsel <alec@××××××××××××××.com> wrote: |
| 4 |
> |
| 5 |
>> The main problem (imnho) is that you think CentOS cares about |
| 6 |
>> configurability/multiple ways of doing things. |
| 7 |
> |
| 8 |
> Oh, I don't think that -- it's pretty obvious that in the RedHat |
| 9 |
> world, choice is not an option. It's one prix fixe menu, and you can |
| 10 |
> either eat what's set in front of you or go hungry. |
| 11 |
> |
| 12 |
|
| 13 |
I can see the potential benefits of that. It sounds a bit like the |
| 14 |
whole convention over configuration approach. As long as the |
| 15 |
convention works, it does greatly simplify things. |
| 16 |
|
| 17 |
One thing I do like is the trend towards putting default configs in |
| 18 |
/usr and using /etc more for overrides. If everything went that way |
| 19 |
(and we stuck stuff like /var/lib/portage/world in /etc) then you |
| 20 |
could have an /etc with 20 short files in it that reflected all the |
| 21 |
tweaking you did to a system from a generic install. Sure, I love |
| 22 |
config protection and etc-keeper and the like, but I'd like it still |
| 23 |
better if etc wasn't such a mix. |
| 24 |
|
| 25 |
I'd really love it if I could dump 20 files in /etc and run emerge |
| 26 |
-uDNv world and end up with a system identical to the one those 20 |
| 27 |
files were copied from. |
| 28 |
|
| 29 |
-- |
| 30 |
Rich |
Archives