/etc/rc2.d/ renaming?
 

I was having trouble updating the headphone app and openntpd and it was really bugging me. Reading through the errors it was giving me, I saw it was freezing on symbolic linking and exiting
So I went to /etc/rc2.d/ and renamed said files.
Before
S20openntpd
S99zheadphoned
After
S20openntpd.BAK
S99zheadphoned.BAK

And after running update again, it worked.
My question is, what did i just do?
And after the updates, I see no openntpd or headphoned files in /rc2.d/ only the BAK that I made. Shouldn't there be new ones created? Just thinking aloud.

On a side note, everytime I run apt-get "anything" this line always shows up I thought sh was BusyBox, so how is it not found?

Re: /etc/rc2.d/ renaming?
 

you seemed to have moved symlinks pointing to nowhere that were for some reasons in the way.

Re: /etc/rc2.d/ renaming?
 

So I broke said symlinks?

Because I just did the same to hildon-desktop as it was giving me a problem during update and the first thing it did when I tried to update after renaming it is start the hildon desktop.

(if you can read that)

Re: /etc/rc2.d/ renaming?
 

I have about 40 files in said directory.

Following your post, are you saying all of them are symlinks pointing nowhere?

Re: /etc/rc2.d/ renaming?
 

No - you're goiing to need those symlinks.
Possibly including the ones you've removed

They are there to set up any system services and things that happen during change of run-levels.

Here's a related link to something qwerty12 wrote whilst solving this.

As for your invoke-rc.d script: it shouldn't have the "a" before the # on the first line.

Re: /etc/rc2.d/ renaming?
 

if you "cd /etc/rc2.d" and do "wc -l *" you will quickly see which symlink points to a valid file and which not when you get an error reported

delete the broken symlinks and replace them by looking in /etc/init.d and making a new symlink. e.g. if you have "S20foobar" and it is dangling, "rm S20foobar" then "ln -s /etc/init.d/foobar S20foobar" - IF there's an appopriate package.

in theory provided you have been using the package manager to add and remove things you should never get any broken startup scripts.