Solution 1:

If you do not have backups, you could try installing rcconf and see if it will re-create the links. But in reality all Debian init files would have following information at the top of each script:

### BEGIN INIT INFO
# Provides:          inetd
# Required-Start:    $local_fs $remote_fs
# Required-Stop:     $local_fs $remote_fs
# Should-Start:      $syslog
# Should-Stop:       $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start or stop the xinetd daemon.
### END INIT INFO

Based on this information alone you could partially restore everything with some basic shell scripting.

# Default-Start: 2 3 4 5 tells you that the Start symlinks to this init script should go into /etc/init{2,3,4,5}.d/S<XX>blah.

# Default-Stop: 0 1 6 means that Kill links do into/etc/init{0,1,6}.d/K<XX>blah.

The problem here is the <XX> part. This is the order your processes start and stop, so if you do not know the order, you could potentially end up with a hung boot. For example when you are trying to start NFS before the Networking.