Quote:

This is a bit different for the shell-startup script but you are right for both devices and/or libraries where mossys:devs or mossys:libs is always first and it does either scan the DEVS: or LIBS: path after that (unless the respective device/library is already loaded).

For the shell-startup script, dos/CLIInitNewCli() first tries to open the script from s:shell-startup and if that doesn't work it explicitly tries MOSSYS:s/shell-startup. Typically, and you can check with shell cmd assign s: EXISTS, the S directory on the system boot partition has precedence over the one in MorphOS/S:

Typical output :

Code:

So basically, you can indeed put some execute mossys:s/shell-startup in front of your custom shell-startup script to avoid duplicating any lines in the script or if you want to make sure that you don't miss anything there for future updates of the script.