Re: Ordering init scripts & use of CONCURRENCY

[Arthur Machlas <arthur.machlas@gmail.com>]

>On Wed, Jun 9, 2010 at 10:18 AM, Sven Joachim <svenjoac@gmx.de> wrote:
>
>> On 2010-06-09 16:48 +0200, Arthur Machlas wrote:
>>
>> Then ran:
>> dpkg-reconfigure insserv
>
> This is a no-op in Squeeze, you want to run the "insserv" command so
> that the order of the symlinks in rc?.d is changed to reflect the
> changed dependencies.
>
You're right. I ran insserv and the numbering changed as appropriate.
Previously both loadcpufreq and phc_vids were s02, I guess I just got
lucky in that loadcpufreq was done before phc_vids, but now I
shouldn't have to worry about getting lucky on reboot. That sounds
vaguely innapropriate, but I hope you get the meaning.
>>
>> Second, there are two ways, or so it seems, to enable concurrent boot.
>> I.e., starting scripts in parallel.
>
> Concurrent boot is the default nowadays.
>
>> One method says to use
>> CONCURRENCY=shell, and the other says CONCURRENCY=startpar
>
> Both are obsolete aliases for CONCURRENCY=makefile (the default).
>
So should I just delete my CONCURRENCY addition to the /etc/defaul/rcS
file and it will return to default, or should I switch it to makefile?

Thanks for the informative reply.