Welcome to the Tiny Core Linux Wiki at tinycorelinux.net!

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

dcore:faq [2016/10/20 14:26]
nitram [Help, i followed the documentation but can't boot into graphics?]
dcore:faq [2016/12/26 03:17] (current)
nitram [How to i keep my system up to date?]
Line 51: Line 51:
  
 ==== What hardware is supported? ==== ==== What hardware is supported? ====
-Presently x86, Arm V7hf, Allwinner-A10, GK802 and Allwinner-A20. As noted above, most graphic, sound, ethernet and wireless hardware is supported.+Previously x86, Arm V7hf, Allwinner-A10, GK802 and Allwinner-A20 were supported, still available from [[http://tinycorelinux.net/ports.html|Tiny Core Linux ports]]. Present development is focused on x86 architecture. As noted above, most graphic, sound, ethernet and wireless hardware is supported. Post on the forum if encountering difficulties.
  
 ==== What about 64-bit systems? ==== ==== What about 64-bit systems? ====
Line 87: Line 87:
 Review the [[http://wiki.tinycorelinux.net/dcore:sound|dCore Sound]] page and [[http://tinycorelinux.net/dCore/x86/README/README-alsa-utils.txt|dCore sound README]]. Review the [[http://wiki.tinycorelinux.net/dcore:sound|dCore Sound]] page and [[http://tinycorelinux.net/dCore/x86/README/README-alsa-utils.txt|dCore sound README]].
  
-==== What commands and stuff should i know to administer the system? ==== +==== What should i know to administer the system? ==== 
-As dCore is based on Tiny Core Linux, working knowledge of Tiny Core is beneficial. Although dCore is managed primarily by command line, [[http://wiki.tinycorelinux.net/dcore:x-desktop#dcore_window_managers_and_desktop_environments|supported Window Managers]] provide user friendly OnDemand and System Tools menus, including a Control Panel and menu shortcuts for ''sce-import'', run program, screenshot, [[https://en.wikipedia.org/wiki/Top_%28software%29|top process monitor]] and [[https://en.wikipedia.org/wiki/Xkill|Xkill]]. Control Panel items include Backup/Restore, Date/Time, Network, [[http://freecode.com/projects/wbar/|wbar]], Mount Tool, Mouse Tool, System Stats, Wallpaper, Services, Swapfile Tool, Terminal Server and Sce Tools. The Sce Tools button provides quick graphic access (terminal popup) with default options to the most commonly used commands (sce-import, sce-load, sce-debpurge, sce-update, sce-remove).+Review the [[http://wiki.tinycorelinux.net/dcore:basic_usage_guide?&#persistence_and_system_changes|dCore Basic Usage Guide]].
  
-Review [[http://wiki.tinycorelinux.net/dcore:extensions#dcore_sce_extension_management_commands|dCore SCE Extension Management Commands]]. Other common commands include version (update dCore base system) and backup (backup mydata.tgz). In a terminal, pressing tab twice lists all available system commands and running ''busybox --list'' prints all [[http://linux.die.net/man/1/busybox|BusyBox]] commands. Entering ''command_name --help'' (two dashes) usually provides usage information. 
 ==== How to i keep my system up to date? ==== ==== How to i keep my system up to date? ====
-Review the [[http://wiki.tinycorelinux.net/dcore:upgrading_kernel_and_initrd|dCore Updates]] page about updating the dCore base system (kernel and initrd)Review the [[http://wiki.tinycorelinux.net/dcore:sce-update_command|dCore sce-update Command]] for updating SCEs.+Review the [[http://wiki.tinycorelinux.net/dcore:basic_usage_guide?&#kernel_updates|kernel updates]], [[http://wiki.tinycorelinux.net/dcore:basic_usage_guide?&#base_file_system_updates|Base File System Updates]] and [[http://wiki.tinycorelinux.net/dcore:basic_usage_guide?&#sce_updates|SCE Updates]] sections and associated links in the [[http://wiki.tinycorelinux.net/dcore:basic_usage_guide?&#dcore_basic_usage_guide|dCore Basic Usage Guide]].
  
 **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
Line 117: Line 116:
  
 If unsuccessful, like any Linux distribution, additional configuration will be required, which may include trialing: If unsuccessful, like any Linux distribution, additional configuration will be required, which may include trialing:
-  * An /etc/X11/xorg.conf file (run //sudo Xorg -configure//, place as /etc/X11/xorg.conf) or custom /etc/X11/Xorg.conf.d/ entry. Add any added files to backup.+  * An /etc/X11/xorg.conf file (run //sudo Xorg -configure//, place as /etc/X11/xorg.conf) or /etc/X11/Xorg.conf.d/ entry, add files to backup for reboot persistence.
   * A custom xorg.conf file, default configuration often does not work, may include disabling/enabling graphic options, changing resolution or monitor frequency, etc.   * A custom xorg.conf file, default configuration often does not work, may include disabling/enabling graphic options, changing resolution or monitor frequency, etc.
   * A known working xorg.conf file from another distribution on the same hardware.   * A known working xorg.conf file from another distribution on the same hardware.
   * The vesa driver, as an old graphic chip may have lost official support.   * The vesa driver, as an old graphic chip may have lost official support.
  
 +Review /var/log/Xorg.0.log for hints after a failed ''startx'' attempt. If still problems review online Xorg documentation or post on the forum for assistance.
 ==== How do i install additional software? ==== ==== How do i install additional software? ====
-If using a supported Window Manager the built-in Control panel (System Tools → Control Panel) has an 'Sce Tools' button to auto-launch ''sce-import'' and other commonly used SCE management commands. Otherwise from a terminal run //cpanel// or //sce-tools//. This is most suitable for new users, those that prefer graphic applications or those that do not require fine-grained control over SCE extension management.+If using a supported Window Manager the built-in Control panel (System Tools → Control Panel) has an 'SCE Tools' button to auto-launch ''sce-import'' and other commonly used SCE management commands. Otherwise from a terminal run //cpanel// or //sce-tools//. This is most suitable for new users, those that prefer graphic applications or those that do not require fine-grained control over SCE extension management.
  
 Traditionally dCore extensions are managed via command line using the [[http://wiki.tinycorelinux.net/dcore:sce-import_command|dCore ''sce-import'' Command]]. As software is usually installed for use at boot time, a user would typically run ''sce-import -b SCE'' (eg. sce-import -b nano), where SCE is the desired Debian package name. Running simply ''sce-import'' will allow searching for the starting characters of a desired package name. Running ''sce-import -c'' will allow searching for packages that contain the desired search characters. The desired Debian package and dependencies are downloaded directly from the applicable Debian or Ubuntu repository and the SCE creation process can be monitored in the terminal. An imported SCE still needs to be loaded into the filesystem for use, review the [[ http://wiki.tinycorelinux.net/dcore:sce-load_command|dCore ''sce-load'' Command]] and [[http://wiki.tinycorelinux.net/dcore:sce-ondemand_command|dCore ''sce-ondemand'' Command]]. Traditionally dCore extensions are managed via command line using the [[http://wiki.tinycorelinux.net/dcore:sce-import_command|dCore ''sce-import'' Command]]. As software is usually installed for use at boot time, a user would typically run ''sce-import -b SCE'' (eg. sce-import -b nano), where SCE is the desired Debian package name. Running simply ''sce-import'' will allow searching for the starting characters of a desired package name. Running ''sce-import -c'' will allow searching for packages that contain the desired search characters. The desired Debian package and dependencies are downloaded directly from the applicable Debian or Ubuntu repository and the SCE creation process can be monitored in the terminal. An imported SCE still needs to be loaded into the filesystem for use, review the [[ http://wiki.tinycorelinux.net/dcore:sce-load_command|dCore ''sce-load'' Command]] and [[http://wiki.tinycorelinux.net/dcore:sce-ondemand_command|dCore ''sce-ondemand'' Command]].
Line 131: Line 131:
  
 ==== Which repositories are used, can i add more, no sources.list? ==== ==== Which repositories are used, can i add more, no sources.list? ====
-Debian based dCores automatically have access to the main, contrib, non-free and security repositories. Ubuntu based dCores automatically have access to the main, universe, multiverse and security repositories. dCore does not utilize a sources.list file. Additional repositories can be added in /opt/debextra. Simply create a non-executable appropriately named text file containing the exact repository information for each repository added. This repository will then be accessible via ''sce-import'' to search and install software. Additional information can be found in the [[http://wiki.tinycorelinux.net/dcore:handling_extensions#additional_repositories|additional repositories]] wiki link and by exploring the [[http://forum.tinycorelinux.net/index.php/board,75.0.html|dCore Extra Repositories sub-forum]]. +Debian based dCores automatically have access to the main, contrib, non-free and security repositories. Ubuntu based dCores automatically have access to the main, universe, multiverse and security repositories. dCore does not utilize a sources.list file. Additional repositories can be added in /opt/debextra/. Simply create a non-executable appropriately named text file containing the exact repository information for each repository added. This repository will then be accessible via ''sce-import'' to search and install software. Additional information can be found in the [[http://wiki.tinycorelinux.net/dcore:handling_extensions#dcore_repositories|dCore Repositories]] wiki link and [[http://forum.tinycorelinux.net/index.php/board,75.0.html|dCore Extra Repositories sub-forum]].
-For more information, see the [[dcore:handling_extensions#repositories|section on repositories]].+
  
 ==== Can i add a PPA? ==== ==== Can i add a PPA? ====
-Ubuntu-based dCores can add Personal Package Archives. Review the [[http://wiki.tinycorelinux.net/dcore:ppa-add_command|dCore ''ppa-add'' Command]] and [[http://wiki.tinycorelinux.net/dcore:handling_extensions#additional_repositories|Additional Repositories]] section.+Ubuntu-based dCores can add [[https://help.launchpad.net/Packaging/PPA|Personal Package Archives]]. Review the [[http://wiki.tinycorelinux.net/dcore:ppa-add_command|dCore sce-ppa-add Command]] and [[http://wiki.tinycorelinux.net/dcore:handling_extensions#additional_repositories|dCore Additional Repositories]] section.
  
 ==== How do i install Flash or Java? ==== ==== How do i install Flash or Java? ====
Line 145: Line 144:
  
 ==== What is the magic behind dCore? ==== ==== What is the magic behind dCore? ====
-All the scripts that make up the dCore tools for importing and handling extensions are available at http://git.tinycorelinux.net. Most relevant scripts can be found in /usr/bin. The kernel configuration is outlined [[http://tinycorelinux.net/dCore/x86/import/src/kernel-3.16.6/config-3.16.6-tinycore-mountdevtmpfs|here]] (for 3.16.6)]. This [[http://forum.tinycorelinux.net/index.php/topic,18882.0.html|thread]] explains how the initrd (base file system) is created.+Scripts that make up the dCore tools for importing and handling extensions are available at http://git.tinycorelinux.net, most relevant scripts can be found in /usr/bin. This link summarizes the most recent [[http://tinycorelinux.net/dCore/x86/import/src/kernel-4.2.9/config-4.2.9-tinycore-devtmpfs|4.2.9 kernel configuration]]. This [[http://forum.tinycorelinux.net/index.php/topic,18882.0.html|forum thread]] briefly explains how base file system (initrd) is created for an upcoming dCore release. Important scripts at the heart of the Tiny Core base system can be found in /etc/init.d/, including tc-config and tc-functions.
  
 ==== dCore defaults to user tc, uses sudo without a password, is it secure? ==== ==== dCore defaults to user tc, uses sudo without a password, is it secure? ====
-dCore makes it easy to get a system running. The user determines the level of security required, dependent on use case. There are numerous facets to system security, some are addressed: +dCore makes it easy to get a system running. The user determines the level of security required, dependent on use case. There are numerous facets to system security, which can not be adequately addressed within the scope of a FAQ page. Numerous online resources are available regarding Linux security and hardening. Some noteworthy mentions
-  * Boot codes include secure (set password), protect (password encrypt backup), noautologin. +  * Available boot codes include secure (set password), protect (password encrypt backup), noautologin. 
-  * BIOS and boot loader passwords can be specified+  * BIOSboot loader and login passwords can be configured
-  * An alternate user name can be specified.  +  * An alternate user name can be specified. 
-  * A firewall can be installed.  +  * A firewall can be installed and configured
-  * Running off a live CD/DVD ensures the initrd and kernel are not tampered with+  * Running from a live CD/DVD ensures the initrd and kernel remain untampered
-  * By default only the TCE partition is mounted after boot.  +  * By default only the TCE partition is mounted after boot. 
-  * SCE md5sum files can be copied to other media and periodically checked. +  * SCE md5sum files can be copied to other media and periodically checked against the extensions
-  * Removing an SCE removes all it's files and dependencies, aside from configurations.+  * Removing an SCE removes all it's files and dependencies, aside from any configuration files.
   * A base install runs with few background processes.   * A base install runs with few background processes.
-  * Most networking/sharing applications are not in base (eg. Samba, NFS, SSH, browser, chat).  +  * Most networking/sharing applications are not in base (eg. Samba, NFS, SSH, browser, chat). 
-  * The only networking service running at boot is dhcp+  * The user decides what software gets installed.
-  * The user decides what software gets installed. +
   * Scripts, in-house software and SCEs are transparent and accessible for audit.   * Scripts, in-house software and SCEs are transparent and accessible for audit.
-  * If using removable mediathe installation can be stored for safe keeping. +  * The user is free to audit Debian/Ubuntu repository source code, modify and custom compile if desired. 
 +  * Using removable media allows the installation to be securely stored for safekeeping.
 ==== Is dCore suitable for a server? ==== ==== Is dCore suitable for a server? ====
-dCore is presently used primarily for desktops, laptops and [[dcore:server_applications|home servers]]. In theory, if set up and configured correctly a lean dCore install should have a small attack surface. Most tools offered by Debian and Ubuntu work with dCore and regular software updates are easy to complete. As dCore is in active development and bug fixes are ongoing, it is not yet as stable as more mature Linux distributions. It would be prudent to run a test server for several weeks prior to making a formal decision. Feedback is appreciated via the forum. More information can be found on the [[http://wiki.tinycorelinux.net/dcore:server_applications|Server Applications]] wiki page.+dCore is presently used primarily for desktops, laptops and [[dcore:server_applications|home servers]]. Theoretically, if set up and configured correctly a lean dCore install should have a small attack surface. Most tools offered by Debian and Ubuntu work with dCore and regular software updates are easy to complete. As dCore is in active development and bug fixes are ongoing, it is not yet as stable as more mature Linux distributions. It would be prudent to run a test server for several weeks prior to making a formal decision. Feedback is appreciated via the forum. More information can be found on the [[http://wiki.tinycorelinux.net/dcore:server_applications|Server Applications]] wiki page.
  
 **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
Line 173: Line 171:
 ==== Where can i learn more? ==== ==== Where can i learn more? ====
   *Review these [[http://tinycorelinux.net/dCore/x86/README/|READMEs]] for a quick start.   *Review these [[http://tinycorelinux.net/dCore/x86/README/|READMEs]] for a quick start.
-  *The [[http://wiki.tinycorelinux.net/dcore:welcome|dCore wiki]] is becoming quite extensive. +  *This [[http://wiki.tinycorelinux.net/dcore:welcome|dCore wiki]] is becoming more extensive. 
-  *The [[http://tinycorelinux.net/book.html|Tiny Core book]] is a must readalthough based on Tiny Core basic concepts apply.+  *The [[http://tinycorelinux.net/book.html|Tiny Core book]] is essentialmost concepts apply to dCore.
  
 ==== Still stuck, more questions, where to get help? ==== ==== Still stuck, more questions, where to get help? ====
-Visit the [[http://forum.tinycorelinux.net/index.php|forum]] and review old posts, note the dCore specific sub-forums. If stuck request assistance on the forum. Provide a detailed yet concise summary of the issuemention what was tried, dCore flavor and version (available via ''version''), install method, hardware utilized, etc. Please review the [[http://forum.tinycorelinux.net/index.php/board,47.0.html?PHPSESSID=GHlCbHy3oHybqMaUDhTi52|Tiny Core]] forum rules before posting. There are also numerous online articles about [[http://stackoverflow.com/help/how-to-ask|how to ask a good question]] and [[http://forums.debian.net/viewtopic.php?f=12&t=116898|how to get help with a technical problem]].+Visit the [[http://forum.tinycorelinux.net/index.php|forum]] and review old posts, note the dCore specific sub-forums. Request assistance on the forum. Provide a reasonable summary of the issue and if applicable mention what was tried, dCore flavor and version (available via ''version''), install method, hardware utilized, etc. Please review the [[http://forum.tinycorelinux.net/index.php/board,47.0.html?PHPSESSID=GHlCbHy3oHybqMaUDhTi52|Tiny Core]] forum rules before posting. There are numerous online articles about [[http://stackoverflow.com/help/how-to-ask|how to ask a good question]] and [[http://forums.debian.net/viewtopic.php?f=12&t=116898|how to get help with a technical problem]].
  
 **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]** **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**
  
Print/export