Language Selection

English French German Italian Portuguese Spanish

Tiny Core: The Little Distro That Could

Filed under
Linux

Every now and again there comes along an amazing piece of technology that is really quite impressive. Tiny Core is a tiny live Linux system and one such marvel. What makes it so special is the way it works and how it treats the system that it loads.

Tiny Core is a live Linux environment which boots from an array of devices. It’s designed to be run from a CD or USB device, but it can also be installed to and loaded from a hard drive. The operating system centers around a main philosophy, that the system should always remain in a pristine state.

So Tiny Core is exactly what the name suggests, a tiny core of an operating system which boots to a fully functional desktop. From here, the user is able to configure the system as they please. It’s a “from the ground up” approach that aims to be extremely flexible. The core system provides most of what the user needs to boot to a working environment, which they can then tweak from there. This is one of the no-so-tiny core philosophies of the distro - it must be small, fast, efficient, and let the user turn it into whatever system they desire.

Let’s face it. Most Live CDs collected along the way just tend to sit on the shelf, or get used as a rescue system. Tiny Core on the other hand, is meant to be used in a completely different way.

rest here




More in Tux Machines

Android Leftovers

GNOME News

  • The future is here
    Nautilus from master, updated everyday, parallel installable, in less than 3 minutes. I cannot believe this is possible. Note that due to be sandboxed with no permission handling there are things that are not working, like opening with an application. For someone not aware of the whole platform and the Linux desktop, it’s difficult to see how many implications this bring to us and the changes that will allow in the upcoming months. This truly changes the game for GNOME (and any other desktop) as a project and platform, including 3rd party developers and companies using Linux desktops or that want to support it.
  • GUADEC’16 report
    I got a chance to attend GUADEC’16 which happened in Karlsruhe, Germany from 11 – 17 August. I stayed for the whole duration including Workshop Day, core days and the later BOF days which were very learning. I’m grateful to my mentor David Woodhouse who guided me all the time. I thank GNOME community for giving me the chance to speak at intern lightning talk and i tried my best to present my project in front of those great people. I hope to get a chance someday again to speak up. We have finished our GSoC project so i am free now to wander around to find some more places and tasks in GNOME’s huge shelter. My experience of attending GUADEC was awesome, despite being a less speaker i was very comfortable to talk and interact to people in the community. I made some new friends in the community and i came to know a lot more about it. I loved attending social events after the long day of great and motivating talks. I am thankful to the GUADEC organizers, i didn’t feel any problem for a second staying 6,000 kms away from home.
  • GUADEC 2016
    I came back from Karlsruhe last week, where GUADEC 2016 took place. It was a wonderful event. Even though it was only my second GUADEC, I felt at home in this community, meeting with old and new friends.
  • Summer Talks, PurpleEgg
    The topics were different but related: The Flock talk talked about how to make things better for a developer using Fedora Workstation as their development workstation, while the GUADEC talk was about the work we are doing to move Fedora to a model where the OS is immutable and separate from applications. A shared idea of the two talks is that your workstation is not your development environment environment. Installing development tools, language runtimes, and header files as part of your base operating system implies that every project you are developing wants the same development environment, and that simply is not the case.

Fedora News

  • UDP Failures and RNGs
  • F24-20160823 updated Live isos
    New Kernel means new set of updated lives. I am happy to release the F24-20160823 updated lives isos.
  • Curse you, Jon Masters! Why do you always have to be right!
    Long story short, Fedora 24 came out and I'm given the taste of the same medicine: the video on the ASUS is completely busted. I was able to limp along for now by using the old kernel 4.4.6-301.fc23, but come on, this is clearly a massive regression. Think anyone is there to bisect and find the culprit? Of course not. I have to do it it myself. So, how did F24 ship? Well... I didn't test beta versions, so I don't have much ground to complain.
  • Communication Anti-Patterns
  • Autocloud: What's new?
    Autocloud was released during the Fedora 23 cycle as a part of the Two Week Atomic Process. Previously, it used to listen to fedmsg for successful Koji builds. Whenever, there is a new message the AutocloudConsumer queues these message for processing. The Autocloud job service then listens to the queue, downloads the images and runs the tests using Tunir. A more detailed post about it’s release can be read here. During the Fedora 24 cycle things changed. There was a change on how the Fedora composes are built. Thanks to adamw for writing a detailed blogpost on what, why and how things changed.