Tiny core linux apt

The Core Project is a highly modular based system with community build extensions.

It starts with a recent Linux kernel, vmlinuz, and our root filesystem and start-up scripts packaged with a basic set of kernel modules in core.gz. Core (17MB) is simply the kernel + core.gz — this is the foundation for user created desktops, servers, or appliances. TinyCore is Core + Xvesa.tcz + Xprogs.tcz + aterm.tcz + fltk-1.3.tcz + flwm.tcz + wbar.tcz

TinyCore becomes simply an example of what the Core Project can produce, an 23MB FLTK/FLWM desktop.

CorePlus ofers a simple way to get started using the Core philosophy with its included community packaged extensions enabling easy embedded frugal or pendrive installation of the user’s choice of supported desktop, while maintaining the Core principal of mounted extensions with full package management.

It is not a complete desktop nor is all hardware completely supported. It represents only the core needed to boot into a very minimal X desktop typically with wired internet access.

The user has complete control over which applications and/or additional hardware to have supported, be it for a desktop, a netbook, an appliance, or server, selectable by the user by installing additional applications from online repositories, or easily compiling most anything you desire using tools provided.

The latest version: 14.0

News

About Our Project

Our goal is the creation of a nomadic ultra small graphical desktop operating system capable of booting from cdrom, pendrive, or frugally from a hard drive. The desktop boots extremely fast and is able to support additional applications and hardware of the users choice. While Tiny Core always resides in ram, additional applications extensions can either reside in ram, mounted from a persistent storage device, or installed into a persistent storage device.

We invite interested users and developers to explore Tiny Core. Within our forums we have an open developement model. We encourage shared knowledge. We promote community involvement and community built application extensions. Anyone can contribute to our project by packaging their favorite application or hardware support to run in Tiny Core. The Tiny Core Linux Team currently consists of eight members who peruse the forums to assist from answering questions to helping package new extensions.

Join us here and on IRC Freenode #tinycorelinux.

Learn. Share. Grow your knowledge of Linux.

Robert Shingledecker, December 01, 2008

Источник

Install Applications

To have a list of mirrors to choose from, install mirrors.tcz.

To select a mirror, open the App Browser, and click Mirrors, then select a mirror.

Install Applications

To install applications while connected to the internet, open the App Browser.

You will then see a list of extensions, and information about them.

Click on a application you want to install. Then click Go. The application and its dependencies will be downloaded and installed.

When completed, there will be a message saying OK.

OnBoot, OnDemand, Download and Load or Download Only

When installing applications you may select OnBoot, OnDemand, Download and Load or Download Only.

OnBoot: If OnBoot is used, the application is loaded every time the computer is started. Applications you always use, should be in OnBoot.

On Demand: If OnDemand is used, applications are not loaded until you start them. When using OnDemand, the computer starts quicker, and uses less RAM. This is ideal for applications you only use sometimes, particularly for computers with small RAM.

Download and Load: If Download and Load is used, the application is downloaded and loaded this time only. The next time you start the computer, it will not be loaded. It will still be in the tce directory, but the computer will not do anything with it.

Download Only: If Download Only is used, the application is only downloaded. It will be in the tce directory, but the computer will not do anything with it.

The applications in OnBoot and OnDemand can be changed using Apps Audit.

Do not put dependencies in OnBoot or OnDemand. They will be automatically included.

Search

You can enter a search term, and search for a certain type of application.

You can also change search to provides, and find out which extension provides something.

Install Local

You can load applications using Install Local. To do this, open the App Browser, click Local, select an application, and click OK.

Install Applications While Not Connected to the Internet

Extensions may be downloaded from one of the mirrors.

Download Extensions, .dep files and Dependencies

To install applications on a computer which is not connected to the internet, download the extensions.

Include .dep files, dependencies, and dependencies of dependencies.

If the computer will be connected to the internet in the future, include .md5.txt files, as these are used to determine which programs have been updated. They can also be used to check if any extensions have been corrupted.

Put in the /tce/optional Directory

Copy and paste all extensions to the /tce/optional directory.

Using Apps Audit, put applications in OnBoot or OnDemand.

Copy Applications to Other Computers

If you install Tinycore on another computer, you don’t need to download the extensions again. You can just copy them. Extensions are in the /tce/optional directory.

Using Apps Audit, put applications in OnBoot or OnDemand.

Using Commands

The following information is included for people using Microcore without a graphical interface, and other advanced users.

Install Applications

To install an application, and put it in On Boot, use

To install an application, and put it in On Demand, use

To download an application to the /tce/optional directory, but not put it in On Boot or On Demand, use

To download an application to the /tce/optional directory, and load it this time, but not put it in On Boot or On Demand, use

If you are running a command line only interface (CLI), then after you load an application using ondemand, then you should refresh your bash path cache with:

App Browser

To search for applications, use

and you will be prompted to enter a search term.

Select an application to install.

You will then have a number of options.

To install it, and put it in On Boot, press i.

To install it, and put it in On Demand, press o.

Start an Application

To start an application that is not loaded, use

Load an Application

To load an application, use

You can then start the application from the menu or wbar.

tce Directory

If you are running a version of Core earlier than 4.2 then you can find the tce directory by opening the terminal and typing

If you are running Core 4.2 or later, then you can find the tce directory by opening the terminal and typing

readlink /etc/sysconfig/tcedir

A note on dependencies and Apps Audit

When an extension is placed in the OnBoot or OnDemand list using Apps Audit the extension and all it’s dependencies are removed from the list of extensions available to be added (the left hand window in Apps Audit). This can result in some extensions apparently disappearing. An example is alsa and alsamixergui:

If a user wishes the alsa sound system to be loaded at boot time the alsa extension is placed in OnBoot, and as alsa-modules is a dependency it will also be removed from the list of extensions available for selection in the left-hand window. The user may occasionally require use of alsamixergui and so places that in OnDemand.

If later alsa is removed from OnBoot, either accidentally or because the user wishes to prevent alsa loading at boot time it does not reappear in the list of extensions available for selection. As a consequence it cannot be added back to OnBoot using Apps Audit. The reason for this is that alsamixergui is in the OnDemand list and has alsa (& consequently alsa-modules) as a dependency so alsa (& alsa-modules) do not appear in the list of extensions available to be added to OnBoot or OnDemand. To be able to restore alsa to OnBoot either the file OnBoot.lst in the tce directory must be edited manually or alsamixergui must be removed from OnDemand, then alsa will be added back to the list of available extensions and can be selected for OnBoot. If the latter method is used alsamixergui will need to be replaced in OnDemand after alsa has been added to OnBoot.

This is only one example, but illustrates a possible cause if an extension is not listed as available by Apps Audit, but has been downloaded to local storage.

Источник

Can I use APT on TinyCore?

Will tinyCore let me use APT? I am looking forward to use a very light version of Linux on a netbook or something. For the last few years I been using Linux Mint and I like it, but I am getting tired of it, since it is too big to my taste now, and I want an easier, faster and more lightweight one, however I am used to apt-get in Ubuntu and Debian. I only use my computers for coding and web development stuff, so I don’t want to get my hands dirty on a Linux stuff for long, all I need is a lightweight OS that doesn’t look stupid and big, vim and a browser to test. However, APT is important to me; will it work with TinyCore or something similar?

Compared to tinyCore apt is an enourmous package with huge depencies. Even if you could get it working it would be larger than the entire tinyCore distribution including GUI. If you want apt, maybe you’re better off with a lightweight Debian based distribution, or just maybe a minimal Debian installation would already suit your needs. That’s the easier way IMO.

I agree with Marco. People are often looking for a «lightweight» distro when what they really need to focus on is details and configuration. I promise all of the major distos are used in production environments more restrictive than a netbook. I have a raspberry pi (single core 600Mhz ARM processor with 1GB ram, which is worse than a cheap phone) running debian wheezy. No problems. Do I try to run eclipse and firefox in KDE with it? No. It can’t handle that effectively. Changing distros would not make any difference, either.

My netbook (Samsung N210, 2GiB RAM, Intel(R) Atom(TM) CPU N450@1.66GHz) runs full Fedora 18 with no problem at all. Not exactly a gamer’s system, and some stuff like compiling and LaTeXing largeish documents is a bit slow, granted; but it is my day-to-day work machine. What a «limited machine» is today would have been a supercomputer for Linus in ’91.

Источник