Concepts and scripts.

Before talking about and outlining the scripts and what they do and how they are enacted within the live iso based versions of Suda its necessary to ask what Suda does and why.

The operating system itself starts and goes through its usual boot routine but then is set up so that before we reach the desktop it launches two scripts for networking, in all three versions the most important networking script is based on bringing up X11vnc which allows us to access the source computer ( in the online version as well as the iso versions) via another computer via the internet ( online Suda) and via a local network ( LAN, wireless or wired) via a vncvewer such as Tigervnc - this leverages basic Linux functionality allowing us to view and interact with a desktop remotely. A better view of how this works can be found here https://wiki.archlinux.org/title/X11vnc .

The next thing before login to launch is noVNC, it has to start after X11vnc, and this enables the same functionality of X11vnc but allows us to access the desktop via a web browser, and this is at the core of the online version of Suda. Im not going to go into it too much here ( I cover it in the Trisquel Suda page) but for completeness sake here is the noVNC site https://novnc.com/info.html . 

After login ( which is automatic on the isos and built in to the way online Suda works) these scripts are launched glitchify.sh, sudacam1.sh, sudacam2.sh ( this differs slightly from the online version but its a way around a scripting problem I found using various versions of linux distributions) then finally manifesto.sh as we want the vim window that creates foregrounded.