Tanstaafl wrote: > On 2012-02-05 1:41 PM, Dale <rdalek1...@gmail.com> wrote: >> They removed the setting because it broke a good bit of systems. No one >> wanted to fix it, so they got rid of it. From my understanding, if you >> still want the setting, you can leave it there. > > Yeah, I fugured out that much, but my main question was about the > defaults... > > What *are* the defaults? Is the example setting that is commented out > the default? > >
The default is no. The reason I know this is that is the supported way to boot, one service at a time. Also, that is the way it does when the option is not in the file at all. If it defaults to yes, then it would break all those systems that had to cut it off after trying it when turned on. Some services just can't start fast enough I guess. It has been a while since I tried that option but it did work on my slower x86 rig. I think it is the newer multi-core machines that have issues. My rule of thumb on updates, if I haven't changed the file, I let it update it as it sees fit. If it is a file I edited, like fstab, rc-conf etc, then I do the updates line by line myself. The exception would be this one since it is not a line that I changed. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
