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/default/rcS
TMPTIME=0
SULOGIN=no
DELAYLOGIN=no
UTC=yes
VERBOSE=no
FSCKFIX=no
RAMRUN=no
RAMLOCK=no
CONCURRENCY=none

2.6.34 kernel and sid.

sysvinit 2.88dsf-8

Thanks,
TJ



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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 package, and the startpar program is in the
sysvinit-utils package.

Can you provide the output from /usr/share/insserv/make-testsuite?  Is
there anything special about your environment I could use to replicate
this issue?

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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 /etc/insserv.conf file.
I use my own kernel, thats all special in my system.

Thanks,
TJ

testsuite.log
Description: Binary data


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 would be nice.  Also, the output
from /usr/share/insserv/check-initd-order might be useful.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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 based
boot ordering to work).  Without it, the boot ordering will be
completely broken.  When the insserv.conf file is back, you need to
update the boot ordering, for example using 'update-rc.d bootlogs defaults'.

Yours is a different problem from the one handled in this bug report,
which was that the CONCURRENCY=startpar setting was completely broken.

Putting 581704@ back on CC, to record what the solution to your
problem probably is.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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), the problem vanishes. So it seems that only
the startpar alias is affected; CONCURRENCY=makefile itself is working fine
on all of my systems.

Regards
Stefan Lippers-Hollmann


signature.asc
Description: This is a digitally signed message part.


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 equivalent with CONCURRENCY=makefile
 in sysvinit 2.88dsf-4 anyways), the problem vanishes. So it seems
 that only the startpar alias is affected; CONCURRENCY=makefile
 itself is working fine on all of my systems.

 I believe I figured out the problem and a fix.  Try this patch:

Index: debian/src/sysv-rc/etc/init.d/rc
===
--- debian/src/sysv-rc/etc/init.d/rc(revision 1898)
+++ debian/src/sysv-rc/etc/init.d/rc(working copy)
@@ -117,6 +117,7 @@
 #
 case $CONCURRENCY in
makefile|startpar|shell) # startpar and shell are obsolete
+   CONCURRENCY=makefile
log_action_msg Using makefile-style concurrent boot in 
runlevel $runlevel
# The splash API is not handled with this CONCURRENCY mode.
# It need to be implented in startpar.  Until that is done

Will upload a fixed version soon.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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 CONCURRENCY=makefile (or removing the setting
  alltogether, which has become equivalent with CONCURRENCY=makefile
  in sysvinit 2.88dsf-4 anyways), the problem vanishes. So it seems
  that only the startpar alias is affected; CONCURRENCY=makefile
  itself is working fine on all of my systems.
 
  I believe I figured out the problem and a fix.  Try this patch:
 
 Index: debian/src/sysv-rc/etc/init.d/rc
 ===
 --- debian/src/sysv-rc/etc/init.d/rc(revision 1898)
 +++ debian/src/sysv-rc/etc/init.d/rc(working copy)
 @@ -117,6 +117,7 @@
  #
  case $CONCURRENCY in
 makefile|startpar|shell) # startpar and shell are obsolete
 +   CONCURRENCY=makefile
 log_action_msg Using makefile-style concurrent boot in 
 runlevel $runlevel
 # The splash API is not handled with this CONCURRENCY mode.
 # It need to be implented in startpar.  Until that is done
 
 Will upload a fixed version soon.

Yes, I can confirm that this version works fine.

Thanks a lot
Stefan Lippers-Hollmann


signature.asc
Description: This is a digitally signed message part.


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=makefile on several
systems, and it work for me. :)

 After upgrading, when I rebooted to test the new mechanism, it seems
 that some key init scripts (such as mounting the root filesystem
 read-write and setting the hostname) either didn't run or didn't run
 soon enough; I got a pile of errors about failures to write due to a
 read-only filesystem, and the system stopped at some point and never
 finished booting.  To recover, I had to boot into single-user mode,
 remount the filesystem read-write, and set CONCURRENCY=none in
 /etc/default/rcS.

 I've attached pictures taken of the messages shown when booting with
 CONCURRENCY=startpar.

Can you provide the output from /usr/share/insserv/make-testsuite, and
also the content of /var/log/boot after editing /etc/default/bootlogd
to enable bootlogd and rebooting once to record all errors?  Also,
please provide the output from 'ls /etc/rc?.d'.

Happy hacking,
-- 
Petter Reinholdtsen



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org