Thinking Small With Tiny Core Linux

I recently had the need to build a virtual appliance, a small Linux server that did one thing, and required no interaction. And by small, I mean really small, tiny. After considering the options and searching around a bit, I found the Tiny Core Linux, and when they say tiny, they mean it. The Tiny Core download is only 12MB.
Tiny Core Linux is meant to be a minimalist desktop operating system. The main download includes a window manager, a text editor, and thats about it. The desktop includes a Mac-like dock at the bottom of the screen, and in the dock is an application to download and install more applications. However, for my purposes, I did not need the GUI, all I needed was a server. So I downloaded and installed the tc-install tool, launched it and installed the OS into a very small virtual machine.
-
- Login or register to post comments
Printer-friendly version
- 2919 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
GitLab Web IDE
| Record Terminal Activity For Ubuntu 16.04 LTS Server
At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands.
|
Linux Kernel Maintainer Statistics
As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems.
| Security: Updates, Trustjacking, Breach Detection
|
Recent comments
1 hour 6 min ago
1 hour 18 min ago
8 hours 10 min ago
1 day 10 hours ago
1 day 11 hours ago
1 day 16 hours ago
2 days 17 hours ago
3 days 23 hours ago
3 days 23 hours ago
4 days 11 hours ago