Bug#581704: sysvinit

2010-06-11 Thread Petter Reinholdtsen
[Tanker Jedi] > It is good question. I had to delete many files in /etc/init.d to > install sysvinit, because a blue window always warned me at apt-get > upgrade. Right. If you deleted /etc/insserv.conf, try reinstalling insserv to get the /etc/insserv.conf file back (it is needed for dependency

Bug#581704: [Pkg-sysvinit-devel] Bug#581704: sysvinit

2010-06-11 Thread Petter Reinholdtsen
[Tanker Jedi] > Of course, i have upgraded them. Good. > I do not know it is problem that i do not have /etc/insserv.conf file. Missing /etc/insserv.conf is definitely a problem if you use dependency based boot sequencing. Any idea why it is missing? The output from the make-testsuite script w

Bug#581704: [Pkg-sysvinit-devel] Bug#581704: sysvinit

2010-06-11 Thread Tanker Jedi
Of course, i have upgraded them. tankerj...@napsugar:~$ apt-cache policy sysv-rc sysv-rc: Telepítve: 2.88dsf-8 Jelölt: 2.88dsf-8 tankerj...@napsugar:~$ apt-cache policy sysvinit-utils sysvinit-utils: Telepítve: 2.88dsf-8 Jelölt: 2.88dsf-8 I do not know it is problem that i do not have /

Bug#581704: [Pkg-sysvinit-devel] Bug#581704: sysvinit

2010-06-11 Thread Petter Reinholdtsen
[Tanker Jedi] > I have similar problems. It seems that / is read-only beacuse i get > similar errors like Josh Triplet in message 3. Today i have upgraded the > sysvinit packages but i did not help. Did you also upgrade the sysvinit-utils and sysv-rc packages? The fix is in the sysv-rc packag

Bug#581704: sysvinit

2010-06-11 Thread Tanker Jedi
I have similar problems. It seems that / is read-only beacuse i get similar errors like Josh Triplet in message 3. Today i have upgraded the sysvinit packages but i did not help. I tried to use startpar and makefile values in rcS, but only none was useful. tankerj...@napsugar:~$ cat /etc/d

Bug#581704: sysvinit: Failing to run init script (or ordering problem) after upgrade from startpar to makefile

2010-05-15 Thread Stefan Lippers-Hollmann
Hi On Saturday 15 May 2010, Petter Reinholdtsen wrote: > [Stefan Lippers-Hollmann] > > Hi > > > > I can reproduce this problem on systems that are using > > $ grep CONCURRENCY /etc/default/rcS > > CONCURRENCY=startpar > > Thank you. Now I see it too. > > > After setting it to CONCURRE

Bug#581704: sysvinit: Failing to run init script (or ordering problem) after upgrade from startpar to makefile

2010-05-15 Thread Petter Reinholdtsen
[Stefan Lippers-Hollmann] > Hi > > I can reproduce this problem on systems that are using > $ grep CONCURRENCY /etc/default/rcS > CONCURRENCY=startpar Thank you. Now I see it too. > After setting it to CONCURRENCY=makefile (or removing the setting > alltogether, which has become eq

Bug#581704: sysvinit: Failing to run init script (or ordering problem) after upgrade from startpar to makefile

2010-05-15 Thread Stefan Lippers-Hollmann
Hi I can reproduce this problem on systems that are using $ grep CONCURRENCY /etc/default/rcS CONCURRENCY=startpar After setting it to CONCURRENCY=makefile (or removing the setting alltogether, which has become equivalent with CONCURRENCY=makefile in sysvinit 2.88dsf-4 anyways)

Bug#581704: [Pkg-sysvinit-devel] Bug#581704: sysvinit: Failing to run init script (or ordering problem) after upgrade from startpar to makefile

2010-05-14 Thread Petter Reinholdtsen
[Josh Triplett] > I already used CONCURRENCY=startpar on my system, and it worked > quite well, but I didn't use CONCURRENCY=makefile because it > actually boots slower on my system. Interesting. I assume there are bugs in some combination of init.d scripts on your system. I use CONCURRENCY=make