| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dcore:basic_usage_guide [2016/12/26 05:43] – [Window Manager usage] nitram | dcore:basic_usage_guide [2016/12/26 16:03] (current) – [Overview] nitram |
|---|
| |
| As a basic installation is minimal, the system can then be expanded and fully customized with kernel modules, drivers, Xorg graphics, various Window Managers or Desktop Environments, sound and any other desired software. As dCore imports software directly from pre-compiled Debian/Ubuntu repositories, thousands of packages are available. Additional software is also available from the dCore pre-built repository, such as kernel modules and select lightweight software no longer available from Debian/Ubuntu. | As a basic installation is minimal, the system can then be expanded and fully customized with kernel modules, drivers, Xorg graphics, various Window Managers or Desktop Environments, sound and any other desired software. As dCore imports software directly from pre-compiled Debian/Ubuntu repositories, thousands of packages are available. Additional software is also available from the dCore pre-built repository, such as kernel modules and select lightweight software no longer available from Debian/Ubuntu. |
| | |
| | This guide uses a typical persistent installation that requires using the ''backup'' command to save session changes in /home/, /opt/ and other directories. Additional boot codes (linked above), such as home=sda1 and opt=sda1, can also be used for systems set up with these dedicated partitions. |
| | |
| | Although classic, vi is often considered less than user friendly. It is, however, an efficient command line editor that is quite simple to use once a few keyboard commands have been memorized, there are several tutorials online. Regardless, users that wish to use a more user friendly CLI-based editor could import and load ''nano'', provided the dCore install has a working network connection: |
| | <code> |
| | sce-import -b nano # Import nano, add to sceboot.lst so it's always available |
| | sce-load nano # Load nano for use during this session (not required on reboot) |
| | nano file_name # Open file with nano, prepend sudo for root owned files |
| | # The ^ command key (eg. ^X to exit) denotes the Ctrl key |
| | </code> |
| | |
| | Congratulations, already imported and loaded your first extension! |
| |
| ==== Basic GUI Management ==== | ==== Basic GUI Management ==== |
| |
| === flwm_topside Mouse Usage === | === flwm_topside Mouse Usage === |
| Neither a traditional panel or even wbar is required, although wbar is included in the dCorePlus ISO. The applications and main menu can be accessed by clicking on free desktop space with any mouse button or by right clicking on any window title bar. All open applications are automatically listed in the main menu. Title bars are located horizontally across the top of the windows and include the window title. Mouse click on the top right window buttons: iconize window, toggle maximize horizontally, toggle maximize vertically and close window. Menu items can be selected by clicking a highlighted item with any mouse button. New windows are smart placed based on open screen space and the mouse cursor is automatically moved to the top left corner of the new window. Re-position a window by holding left of middle click on the window title bar and dragging the window. Resize a window by holding left click on any corner or edge (cursor changes) and dragging the window smaller or larger. | Neither a traditional panel or even wbar is required, although wbar is included in the dCorePlus ISO. The applications and main menu can be accessed by clicking on free desktop space with any mouse button or by right clicking on any window title bar. All open applications are automatically listed in the main menu. Title bars are located horizontally across the top of the windows and include the window title. Mouse click on the top right window buttons: iconize window, toggle maximize horizontally, toggle maximize vertically and close window. Menu items can be selected by clicking a highlighted item with any mouse button. New windows are smart placed based on open screen space and the mouse cursor is automatically moved to the top left corner of the new window. Re-position a window by holding left or middle click on the window title bar and dragging the window. Resize a window by holding left click on any corner or edge (cursor changes) and dragging the window smaller or larger. |
| |
| === flwm_topside Keyboard Shortcuts === | === flwm_topside Keyboard Shortcuts === |
| |
| ==== Base File System Updates ==== | ==== Base File System Updates ==== |
| The dCore initrd file (base file system) is updated frequently due to active development and users have the option to track either stable or RC release. Although less tested, RC release provide the latest bug fixes and features. Users wishing to assist with testing should run an up to date RC release before reporting bugs. Essentially the ''version -r'' (RC release) or ''version -c'' (stable release) commands are used to check and install base file system updates. Ensure the /etc/sysconfig/boot_path file is properly configured. Reboot the system to apply the update. Review [[http://wiki.tinycorelinux.net/dcore:upgrading_kernel_and_initrd#dcore_initrd_updates|dCore Initrd Updates]] for more information. | The dCore initrd file (base file system) is updated frequently due to active development and users have the option to track either stable or RC release. Although less tested, RC releases provide the latest bug fixes and features. Users wishing to assist with testing should run an up to date RC release before reporting bugs. Essentially the ''version -r'' (RC release) or ''version -c'' (stable release) commands are used to check and install base file system updates. Ensure the /etc/sysconfig/boot_path file is properly configured. Reboot the system to apply the update. Review [[http://wiki.tinycorelinux.net/dcore:upgrading_kernel_and_initrd#dcore_initrd_updates|dCore Initrd Updates]] for more information. |
| |
| ==== SCE Updates ==== | ==== SCE Updates ==== |
| As bug fixes and security releases become available, SCEs should be periodically updated. See the [[http://wiki.tinycorelinux.net/dcore:sce-update_command|dCore sce-update Command]] and [[http://wiki.tinycorelinux.net/dcore:extension_strategies#version_conflicts|Version Conflicts]] wiki entries for more information. A system reboot is recommended to apply updates if outdated SCEs were already loaded during the session. | As bug fixes and security releases become available, SCEs should be periodically updated. Review [[http://wiki.tinycorelinux.net/dcore:sce-update_command|dCore sce-update Command]] and [[http://wiki.tinycorelinux.net/dcore:extension_strategies#version_conflicts|Version Conflicts]] for more information. A system reboot is recommended to apply updates if outdated SCEs were already loaded during the session. |
| |
| ==== Persistence and System Changes ==== | ==== Persistence and System Changes ==== |
| Like Tiny Core Linux, an installation is not persistent unless a TCE directory has been set up. This stores all imported SCE extensions so they are persistent and available across reboots. The TCE directory also stores the mydata.tgz backup file when running the ''backup'' command. By default this contains any files located in the home and opt directory. If it is necessary to add additional files for backup outside of these default directories, they should be entered into /opt/.filetool.lst. Any files or directories the user wants to exclude from ''backup'', to keep the backup file smaller, should be added into /opt/.xfiletool.lst. Although these files can be manually modified, when working in a graphic environment it may be easiest to use the Backup Restore GUI, launched by running ''filetool'' or accessed via System Tools -> Control Panel -> Backup/Restore. | Like Tiny Core Linux, an installation is not persistent unless a TCE directory has been set up. This stores all imported SCE extensions so they are available across reboots. The TCE directory also stores the mydata.tgz backup file when running the ''backup'' command. By default this contains any files located in the home and opt directory. If it is necessary to add additional files for backup outside of these default directories, they should be entered into /opt/.filetool.lst. Any files or directories the user wants to exclude from ''backup'', to keep the backup file smaller, should be added into /opt/.xfiletool.lst. Although these files can be manually modified, when working in a graphic environment it may be easiest to use the Backup Restore GUI, launched by running ''filetool'' or accessed via System Tools -> Control Panel -> Backup/Restore. |
| |
| Additional important configuration files include: | Most system related configuration files are located in the /etc/sysconfig/ and /opt/ directories. Additional important configuration files for launching executables and applications at boot: |
| * /opt/bootlocal.sh: Enter desired root commands to run in the background during system boot. | * /opt/bootlocal.sh: Enter desired root commands to run in the background during system boot. |
| * /opt/bootsyn.sh: Enter desired high priority root commands to run during system boot. | * /opt/bootsyn.sh: Enter desired high priority root commands to run during system boot. |
| * ~/.X.d/: Create a plain text file (not script) containing non-root commands to launch later in the boot cycle. For example, create a file named 'startups' containing: | * ~/.X.d/: Create a plain text file (not script) containing non-root commands to launch later in the boot cycle, typically graphic applications. For example, create a file named 'startups' containing: |
| * conky & | <code> |
| * dillo & | conky & |
| * xset s 300 & | dillo & |
| | xset s 300 & |
| | </code> |
| |
| When running a persistent system, the ''backup'' command must be run before shutdown whenever configuration changes were made during the session, otherwise the data will be lost. | When using a persistent system, the ''backup'' command must be run before shutdown whenever configuration changes were made during the session, otherwise the data will be lost. |
| |
| ==== Backup ==== | ==== Backup ==== |
| As all other critical files are stored within the TCE directory, a periodic copy/paste of this entire directory to other media effectively backs up the entire system, including SCE, mydata.tgz and mydatabk.tgz files. | As all other critical files are stored within the TCE directory, a periodic copy/paste of this entire directory to other media effectively backs up the entire system, including SCE, mydata.tgz and mydatabk.tgz files. |
| |
| When the system is set up and is running well, a safe backup should periodically be performed via ''filetool.sh -sb'', to backup mydata.tgz to mydatabk.tgz. Numerous mydata.tgz or mydatabk.tgz backup files can be manually kept if desired. The mydata.tgz file can be manually replaced with a known good version in the event of file corruption or system misconfiguration. | When the system is set up and is running well, a safe backup should periodically be performed via ''filetool.sh -sb'', to copy mydata.tgz to mydatabk.tgz. Several mydata.tgz or mydatabk.tgz backup files can be manually saved if desired. The mydata.tgz file can be manually replaced with a known good version in the event of file corruption or system misconfiguration. |
| |
| Although rare, there is a possiblity an updated SCE may not work correctly due to an RC bug, broken Debian/Ubuntu package or corrupt file system. Modifying SAFEBACKUP=TRUE in /etc/sysconfig/sceconfig will automatically backup the old SCE in /etc/sysconfig/tcedir/sce/backup/ when running ''sce-update'' or re-importing an SCE, which can be manually restored as needed. Note the modified /etc/sysconfig/sceconfig file needs to be added to /opt/.filetool.lst and ''backup'' run for the configuration change to be saved. | Although rare, there is a possiblity an updated SCE may not work correctly due to an RC bug, broken Debian/Ubuntu package or corrupt file system. Modifying SAFEBACKUP=TRUE in /etc/sysconfig/sceconfig will automatically backup the old SCE in /etc/sysconfig/tcedir/sce/backup/ when running ''sce-update'' or re-importing an SCE, which can be manually restored as needed. Note the modified /etc/sysconfig/sceconfig file needs to be added to /opt/.filetool.lst and ''backup'' run for the configuration change to be saved. |
| |
| ==== Maintenance ==== | ==== Maintenance ==== |
| Aside from the updates and backups discussed above, dCore requires little maintenance. An advantage of using self-contained extensions that link to the main file system is that when the SCE is removed, all traces of the main program and dependencies are gone, with the exception of home direcctory configuration files. | Aside from the updates and backups discussed above, dCore requires little maintenance. An advantage of using self-contained extensions that link to the main file system is that when the SCE is removed, all traces of the main program and dependencies are gone, no cruft left behind with the exception of home directory configuration files. |
| |
| Optional periodic maintenance tasks: | Optional periodic maintenance tasks: |
| * Manually cleanup unneeded home directory files. | * Manually remove unneeded home directory files. |
| * Run ''sce-debpurge'' and ''sce-debpurge -n'' to remove outdated and unneeded Debian (*.deb) files to reclaim drive space. | * Run ''sce-debpurge'' and ''sce-debpurge -n'' to remove outdated and unneeded Debian (*.deb) files to reclaim drive space. |
| * Run ''sce-remove'' and remove SCE(s) no longer required to reclaim drive space and improve ''sce-update -a'' (update all SCEs) efficiency. | * Run ''sce-remove'' to remove SCE(s) no longer required, reclaims drive space and improves ''sce-update -a'' (update all SCEs) efficiency. |
| * If using /etc/sysconfig/sceconfig SAFEBACKUP=TRUE, manually remove /etc/sysconfig/tcedir/sce/backup/ items as desired. | * If using /etc/sysconfig/sceconfig SAFEBACKUP=TRUE, manually remove old /etc/sysconfig/tcedir/sce/backup/ items as desired. |
| |
| ==== Resources ==== | ==== Resources ==== |
| The above should help new users quick start a dCore system, much more information is outlined in the dCore wiki and discussed in the dCore subforums, additional resources: | The above should help new users quick start a dCore system. More information is outlined in the dCore wiki and discussed in the dCore subforums: |
| * FAQ: http://wiki.tinycorelinux.net/dcore:faq | * FAQ: http://wiki.tinycorelinux.net/dcore:faq |
| * Wiki: http://wiki.tinycorelinux.net/dcore:welcome | * Wiki: http://wiki.tinycorelinux.net/dcore:welcome |
