Recommended procedures after installing GLFPE to local drive 26 Sep 2020 GLF ------------------------------------------------------------------------------------- GLFPE Linux (as well as other GLF OS distributions such as GPROG) are intended to be fully functional OS systems using live boot, without requiring permanent installation to a PC's local hard drive. Installationis however supported as a user option. Because the OS is focused on the live boot experience, certain typical actions which are expected to be performed once upon startup or user request are not appropriate for long term use in a permanent installation. Though some live boot distributions allow for persistent data storage on USB drive partitions, GLF distributions intentionally do not. A live boot system WITHOUT persistence starts over from "scratch", presenting the same interface each time it is booted, regardless of actions taken by a user in a prior session. This requires the user to intentionally save any desired session data to an external drive if it is to be used later. That restriction is sometimes inconvenient but enforces "Vegas Rules" (that is, what happens in Vegas stays in Vegas). Any UNINTENTIONAL changes such as deletion of configuration data from the OS, uninstallation of an application, or even malware HACKING are discarded simply by rebooting. The inconvenience of forcing a user to explicitly save his word processing or programming work to external drive is considered a low price to pay for the reliability, stability, and relative security of the read-only OS platform provided. A user who wishes persistent data storage can simply install the OS to a bootable local drive instead, whether it be a permanent local drive or a removable external drive. It is then the user's responsibility to customize his own OS experience, for good or ill. After a user initially installs the OS from a live boot image to local drive (procedures documented elsewhere), upon booting the newly installed system the user may wish (and is recommended by GLF) to remove certain menu items or scripts to avoid trouble caused by unintended duplication of data or processes. Specific recommendations for GLFPE and similar distributions ------------------------------------------------------------ An automated startup script was introduced into GLFPE and similar distributions to immediately request the user change his password. It is entirely appropriate for a live boot session to urge override of the fixed and widely published default password built into the OS image. If the password is not changed, any hacker could simply try the well known default password to log in, in person or remotely. However, a permanent system need only change the password once. Removing the automated startup invocation avoids the unnecessary "nag". To do so, use the GUI File Manager (caja) to navigate to the user home folder. Turn on the viewing of hidden files. Look for the ".config" folder and look under it for "autostart" folder. Inside that folder you should find a launcher shortcut (*.desktop) file used to initiate the one-time password change. If you delete that launcher, the startup request script will no longer run. Another example for GLFPE is under the Applications/Programming menu as "GLFPE-examples". That menu item lauches a script intended to be run only once to rename certain folders (if they exist) under user's home and set up symbolic links to other folders already containing a large amount of data. A quirk of the live boot system is that the runtime user weorkspace is created on the fly at boot time, and so any data in the user's home folder consumes RAM and therefore reduces apparent disk space available during the session. The "GLFPE-examples" script is part of a tricky technical dodge in the GLFPE live boot system to allow large data folders to show up as user data under "home" (normal user permissions) without unnecessarily consuming RAM or RAMDISK space. The data actually resides in a special folder (/usr/share/work/user) and the symlinks are set up to allow access to the otherwise obscurely hidden data without requiring a copy directly to "home". The user is expected to click the menu item only once after booting the live session, at which point a lot of source code and other facilities make themselves apparent. However, if the system is permanently installed, the user should not be encouraged to press the same item again (possibly unintended side effects). The user should either delete the menu item from the list, or delete the target script (under /usr/local/bin) or otherwise disable it (unmark the executable flag).