Porteus

What is the load order in porteus.

/etc/rc.d/rc.local loads before xdfe. which scripts run after that (or where can I add to a script that starts up last.)

I still have a couple unresolved threads and I am hoping this might solve both of them.

Thanks,

I would suggest to use that rc.local file and nothing else for auto start scripts. That rc script has been implemented for this use.

After rc.local comes the cheatcode: autoexec=
If using this you must use ~ in place of spaces. After that you can use the DM autostart folder. You can use /etc/xdg/autostart for .desktop files or even kde4 ~/.kde4/Autostart. The last two are useful if you need something to run after the login stage. It really depends on what your goal is when deciding the best method.

Great, that was the answer I was looking for.

Adding the following cheatcode started the vncserver at the correct time. Having it in the rc.local file for some reason was showing an error that the /home/guest folder did not exist:
autoexec=/usr/bin/vncserver~-rfbauth~/home/guest/.vnc/passwd

It was more important that the user didn't have to enter this manually so I read the documentation and it said I could

These cheatcodes can also be added to the APPEND line of your /boot/porteus.cfg entries

but the for the porteus xfce 2.0RC2 486 (maybe for others) on my HDD install it was /mnt/sda1/boot/syslinux/porteus.cfg and I just added it to the first menu item.

After I then created a new remaster using make_iso.sh, it started up perfectly with the vncserver running and waiting at the port for a client connection.

The

/etc/xdg/autostart for .desktop files or even kde4 ~/.kde4/Autostart

might just come in useful in the future too THANKS!

These cheatcodes can also be added to the APPEND line of your /boot/porteus.cfg entries
Thanks. We need to update some of the docs on the main website. A search for '/boot/porteus.cfg' on the site brings up many hits. Glad you took the initiative and sorted it out. You have a head for linux.