| 1 |
Tanstaafl wrote: |
| 2 |
> On 2012-02-05 1:41 PM, Dale <rdalek1967@×××××.com> wrote: |
| 3 |
>> They removed the setting because it broke a good bit of systems. No one |
| 4 |
>> wanted to fix it, so they got rid of it. From my understanding, if you |
| 5 |
>> still want the setting, you can leave it there. |
| 6 |
> |
| 7 |
> Yeah, I fugured out that much, but my main question was about the |
| 8 |
> defaults... |
| 9 |
> |
| 10 |
> What *are* the defaults? Is the example setting that is commented out |
| 11 |
> the default? |
| 12 |
> |
| 13 |
> |
| 14 |
|
| 15 |
The default is no. The reason I know this is that is the supported way |
| 16 |
to boot, one service at a time. Also, that is the way it does when the |
| 17 |
option is not in the file at all. |
| 18 |
|
| 19 |
If it defaults to yes, then it would break all those systems that had to |
| 20 |
cut it off after trying it when turned on. Some services just can't |
| 21 |
start fast enough I guess. It has been a while since I tried that |
| 22 |
option but it did work on my slower x86 rig. I think it is the newer |
| 23 |
multi-core machines that have issues. |
| 24 |
|
| 25 |
My rule of thumb on updates, if I haven't changed the file, I let it |
| 26 |
update it as it sees fit. If it is a file I edited, like fstab, rc-conf |
| 27 |
etc, then I do the updates line by line myself. The exception would be |
| 28 |
this one since it is not a line that I changed. |
| 29 |
|
| 30 |
Dale |
| 31 |
|
| 32 |
:-) :-) |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
I am only responsible for what I said ... Not for what you understood or |
| 37 |
how you interpreted my words! |
| 38 |
|
| 39 |
Miss the compile output? Hint: |
| 40 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives