| 1 |
On 08/08/2015 14:26, Neil Bothwick wrote: |
| 2 |
> On Sat, 08 Aug 2015 02:57:29 -0400, Felix Miata wrote: |
| 3 |
> |
| 4 |
>> I don't get why any distro leaves this out, why anyone wouldn't like to |
| 5 |
>> automatically notice while booting any announcement that something |
| 6 |
>> failed, especially someone who has just gotten a new installation up |
| 7 |
>> for the first times. Why isn't --noclear set by default? |
| 8 |
> |
| 9 |
> It doesn't matter, it's just a default. This is Gentoo, it works how you |
| 10 |
> tell it to work. That particular setting is even mentioned n the elog |
| 11 |
> output. |
| 12 |
|
| 13 |
I think Felix still has quite a bit of the SuSE/RHEL/Fedora/Ubuntu mindset. |
| 14 |
|
| 15 |
Those distros do a lot of hand-holding, a lot of trying to figure out |
| 16 |
what you mean, and take pride in delivering a full complete consistent |
| 17 |
experience (whatever that is). |
| 18 |
|
| 19 |
Gentoo has no truck with such things. The software is what it is, and if |
| 20 |
the user doesn't like what is provided, the user must change it because |
| 21 |
the dev ain't gonna. Just like Slackware come to think of it. |
| 22 |
|
| 23 |
The Gentoo approach is that the user already knows what he/she wants and |
| 24 |
knows how to get it. This is a perfectly valid approach - Gentoo users |
| 25 |
rapidly move from n00b status to a different status of having a good |
| 26 |
idea what they want. So the vast majority of Gentoo usage is done with |
| 27 |
that knowledge in place, and very little usage is done in a state of "I |
| 28 |
don't yet know what I'm doing". |
| 29 |
|
| 30 |
This is what amuses me so much about efforts to make Gentoo "more |
| 31 |
user-friendly" - whatever that is. Our devs cater to the overwhelming |
| 32 |
majority case, and helpful guides on how to get there are at a minimum. |
| 33 |
|
| 34 |
I like this approach for the same reason I prefer Linux over Windows. |
| 35 |
Gentoo assumes I have a brain and can use it, and do not need to be |
| 36 |
treated like a clueless n00b form now till the end of time. I find that |
| 37 |
very validative and empowering, even though the prove I had to pay was 6 |
| 38 |
weeks of being mostly confused while getting up to speed. And that was |
| 39 |
10 years ago. |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
> |
| 44 |
>> Once I set this and rebooted I saw several things that needed fixing |
| 45 |
>> that I didn't have a clue about: |
| 46 |
> |
| 47 |
> You really should enable logging to /var/log/rc.log and get into the |
| 48 |
> habit of checking it when rebooting after a change. I always check it |
| 49 |
> after booting a new kernel for instance. |
| 50 |
> |
| 51 |
> |
| 52 |
|
| 53 |
|
| 54 |
-- |
| 55 |
Alan McKinnon |
| 56 |
alan.mckinnon@×××××.com |
Archives