How to manually add softcams on an official DGS image

I've regularly been asked how do I install mgcam or incubuscamd on an official DGS image. Well, truth is, I cheat. I have modified and copied files from a working third party image like Paccos fabulous PGI image over to the official DGS image. And it works.

Here are the files I'm currently using. You will need to be running with a working official DGS firmware. Then ftp the files to the correct/same folders and chmod each file to 775 (important). Then Reboot.
DOWNLOAD

This little package will add mgcam 1.35, incubuscamd 0.97 and satangels key updater only to a DGS image. The green key will switch between cams (only the two softcam options are selectable) and yellow key will restart a cam. The SatAngels keyupdater plugin grabs the latest keys automatically. If you use lines, you'll have to add those yourself to the cccamd.list and/or incubusCamd.conf

Works great on latest DGS r11694

I hope it helps some of you out.
Your download files contain "incubuscamd.sh4". Should the file stay with this name or should we rename it to "incubus-0.97" ?
When we install incubus from SifTeam panel, this is the file name that we find in var/bin
The name of the file does not matter to get the emu to run (IF you start it manually), but because in this package there is a script to start the emu automatically it need to have the same name as when you downloaded it. In sifteam image there is a different script to start the emu and they used a different name.

So in short the name has only to do with the scripts to start the emu.

Ok, it's needed have the same name

Most DGS image search and call shell scripts in /var/bin/init.d at various times during the boot process. You can find those places browsing through the "sbox" boot script. The shell scripts in /var/bin/init.d are called sequentially: early on the 1.* scripts, later 2.*, still later 3.*, and last 4.* In fact, the 4.* scripts are never called at startup (maybe they get a turn at shudown).
So, placing command in a script in /var/bin/init.d/3.emu_start will execute those just before the sbox binary (Ipbox's main program) is executed.
But there's a snag, to execute newcs and mgcamd well, they's have to wait until some files are generated by sbox, so executing them too early will cause an infinite loop (waiting for sbox) during startup.
The solution is to start the script in /var/bin/init.d/3.emu_start, but make the Ipbox "move on" with the execution of sbox. Simply adding an " & " after a command will make this happen (isn't linux great?).
What I did in practice:
1) make the directory /var/bin/init.d
2) put a small script in /var/bin/init.d (I called it 3.emu_start), branching to the real softcam start script. I just has one line (remember the "&" at the end):
bash /var/bin/emu_start.sh >/dev/null &
3) make the second script in /var/bin to start the softcam (I called it emu_start.sh):
# give some signal to the outside world
front_ioctl -job puts "MGCAMD-NEWCS"
# start cardserver (I like newcs 1.65)
/var/bin/newcs-1.65 -C /var/keys/newcs.xml
sleep 5
# wait for sbox process
while { ! [ -f /tmp/pmt.tmp ] ; }
do
sleep 1
done
# start mgcamd
ln -s /tmp/pmt1.tmp /tmp/pmt1_1.tmp
ln -s /tmp/pmt2.tmp /tmp/pmt2_1.tmp
/var/bin/mgcamd-1.33
sleep 1
exit 0
4) put the mgcamd-1.33 and newcs-1.65 binaries in /var/bin
5) make a directory /var/keys
6) put the config files (mg_cfg , newcs.xml , newcamd.list, etc.) in /var/keys
7) chmod 755 the necessary files and reboot
In this way, I get the softcam to start right after sbox has completed, so I get a picture even on coded channels without the "usual" 10 second delay.
Off course, you can use the same method to set up a swapfile, send some parameters to your HDD (hdparm), say "hello world", or whatever you would like your Ipbox to do.