Prev: rsync: mkstemp "some files" failed: Cannot allocate memory (12)
Next: can somebody list contents of linux-image-2.6.32-trunk-686? [was: Re: trying to understand/purge linux-image-2.6.32-trunk-686]
From: Hugo Vanwoerkom on 2 Jun 2010 12:30 Hi, Before dependency based boot I added my own boot scripts with update-rc.d, like: update-rc.d faketty start 29 2 3 4 5 . and the update-rc.d man page still refers to sequence numbers (NN=29): "NN is the two-digit sequence number that determines where in the sequence init will run the scripts." But with dependency based boot those sequence numbers went out the window. What does one do now, run update-rc.d as before and then 'dpkg-reconfigure sysv-rc'? Hugo -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hu60rv$j3o$1(a)dough.gmane.org
From: Jordan Metzmeier on 2 Jun 2010 12:40 On 06/02/2010 12:28 PM, Hugo Vanwoerkom wrote: > Hi, > > Before dependency based boot I added my own boot scripts with > update-rc.d, like: > > update-rc.d faketty start 29 2 3 4 5 . > > and the update-rc.d man page still refers to sequence numbers (NN=29): > > "NN is the two-digit sequence number that determines where in the > sequence init will run the scripts." > > But with dependency based boot those sequence numbers went out the > window. > > What does one do now, run update-rc.d as before and then > 'dpkg-reconfigure sysv-rc'? > > Hugo > > I am not sure how dependency based booting changes things, but the manpage of update-rc.d recommends using another tool such as sysv-rc-conf. " Please note that this program was designed for use in package main‐ tainer scripts and, accordingly, has only the very limited functional‐ ity required by such scripts. System administrators are not encouraged to use update-rc.d to manage runlevels. They should edit the links directly or use runlevel editors such as sysv-rc-conf and bum instead." I would try one of the alternatives. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C068854.2000904(a)gmail.com
From: Sven Joachim on 2 Jun 2010 12:50 On 2010-06-02 18:28 +0200, Hugo Vanwoerkom wrote: > Before dependency based boot I added my own boot scripts with > update-rc.d, like: > > update-rc.d faketty start 29 2 3 4 5 . > > and the update-rc.d man page still refers to sequence numbers (NN=29): > > "NN is the two-digit sequence number that determines where in the > sequence init will run the scripts." > > But with dependency based boot those sequence numbers went out the window. Yes, they are meaningless now. If it is important that the script runs before or after some other script, you need to specify this in the LSB headers. > What does one do now, run update-rc.d as before and then > dpkg-reconfigure sysv-rc'? Just run update-rc.d, it will run insserv for you (assuming that you have already converted to dependency-based boot). Sven -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/87ocftwfdz.fsf(a)turtle.gmx.de
From: Hugo Vanwoerkom on 2 Jun 2010 12:50 Jordan Metzmeier wrote: > On 06/02/2010 12:28 PM, Hugo Vanwoerkom wrote: >> Hi, >> >> Before dependency based boot I added my own boot scripts with >> update-rc.d, like: >> >> update-rc.d faketty start 29 2 3 4 5 . >> >> and the update-rc.d man page still refers to sequence numbers (NN=29): >> >> "NN is the two-digit sequence number that determines where in the >> sequence init will run the scripts." >> >> But with dependency based boot those sequence numbers went out the >> window. >> >> What does one do now, run update-rc.d as before and then >> 'dpkg-reconfigure sysv-rc'? >> >> Hugo >> >> > > I am not sure how dependency based booting changes things, but the > manpage of update-rc.d recommends using another tool such as sysv-rc-conf. > > " Please note that this program was designed for use in package main‐ > tainer scripts and, accordingly, has only the very limited functional‐ > ity required by such scripts. System administrators are not encouraged > to use update-rc.d to manage runlevels. They should edit the links > directly or use runlevel editors such as sysv-rc-conf and bum instead." > > I would try one of the alternatives. > > I will but I read that 'sysv-rc-conf provides a terminal GUI for managing "/etc/rc{runlevel}.d/" symlinks.' and I invoke update-rd.d from a script so I'd rather not have another GUI. Hugo -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hu61su$m4u$1(a)dough.gmane.org
From: Hugo Vanwoerkom on 2 Jun 2010 13:10
Sven Joachim wrote: > On 2010-06-02 18:28 +0200, Hugo Vanwoerkom wrote: > >> Before dependency based boot I added my own boot scripts with >> update-rc.d, like: >> >> update-rc.d faketty start 29 2 3 4 5 . >> >> and the update-rc.d man page still refers to sequence numbers (NN=29): >> >> "NN is the two-digit sequence number that determines where in the >> sequence init will run the scripts." >> >> But with dependency based boot those sequence numbers went out the window. > > Yes, they are meaningless now. If it is important that the script runs > before or after some other script, you need to specify this in the LSB > headers. > >> What does one do now, run update-rc.d as before and then >> dpkg-reconfigure sysv-rc'? > > Just run update-rc.d, it will run insserv for you (assuming that you > have already converted to dependency-based boot). > Thanks Sven, I have converted to dependency based boot and thus will keep the update-rc.d statements in my script and insserv will be invoked. Hugo -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hu62rf$qe6$1(a)dough.gmane.org |