Language Selection

English French German Italian Portuguese Spanish

Mini Review of a Tiny PCLOS

Filed under
PCLOS
Reviews
-s

TinyMe is a scaled down version of PCLinuxOS 2007. The latest version is delivered as a 177 MB liveCD and features the Lightweight X11 Desktop Enviroment, Synaptic, and the PCLinuxOS Control Center. It comes with a few applications, so it could be a really light version of PCLOS for older computers or a foundation on which to build your own system as you choose.

The boot screen and silent boot splash are straight from PCLOS, but the window manager login screen is quite different. TinyMe 4.1 comes with LXDE and Openbox and so the LXSession is the graphical login manager. It works well and looks fairly good, but has some extraneous entries listed. The LXdesktop is a standard setup: a panel at the bottom with a start button and some quick launchers, pager, clock and network applet. TinyMe developers have included a nice wallpaper of rain drops on glass with a blue sky background. The TinyMe acorn logo sits in the middle. It didn't scale for my 1280x800 screen resolution, but no biggie. Version 4.1 comes with a Home icon and gkrellm.

The menus are quite sparce, but most applications installed end up with link. As delivered, GQView is included as for image viewing and medit for text editing or simple document creation. The Settings heading contains About Me, Password, Redo MBR, and Openbox Configuration Manager. System tools include Configure Your Computer (PCLOS Control Center), Disk Management, PCMan File Manager, Root Terminal, Run as Different User, Searchmonkey, and Synaptic Package Manager. Under Network is Opera and TightVNC. Under the hood we find Linux 2.6.18.8, Xorg 7.1.1, and GCC 4.1.1.


Some Stuff

There is no entry in the menu for the hard drive installer, but it can be found at /usr/sbin/draklive-install. It is the same PCLOS customized Mandriva Live installer found in PCLinuxOS and works just as well. With such a small system to install, it finished in just a few minutes. I setup the bootloader to be installed onto the root partition and that worked out really well. I had no problems with any of it.

The installed system boots on my laptop in 19 seconds and takes up about 700 MB of space. I opened Synaptic to install a few things and found PCLOS software repositories already set up. The Gimp I installed while running the liveCD was transferred to the harddrive install and I followed it up with Gnome. I wasn't able to locate a Gnome meta package so I checked most of the important Gnome packages. It downloaded about 150 MB of software and installed without issue. Gnome didn't show up in the LXSession menu, so I had to choose Text.Console and start it manually. One could probably install the Gnome login manager if they seriously wanted to use Gnome. I just speculated that this TinyMe might be the perfect start for the user wishing to run PCLOS under the Gnome desktop without any of the KDE baggage that's so hard to remove completely. And my results were such that I believe it would work out well for that very purpose. Even with Gnome installed the system still weighed in at less than one gig. Apps opened immediately and the system as a whole was very stable.


Gnome

TinyME might make a good start for a server as all the important LAMP packages are in the PCLOS repositories as well. One doesn't need all the extra goodies that come with the big desktops these days for a server and LXDE would be good for those that like graphical server tools such as webmin.

I didn't have an older computer handy on which to test it, but I imagine it would be great for it. PCLOS developers build support for about everything into their kernels and LXDE only requires a Pentium II and 128 MB ram if one wishes to use like Firefox or OpenOffice.org. It is said that LXDE alone can run in as little as 64 MB ram.

TinyME might be useful to those folks that commonly use ftp or net installs because they prefer to only download what they use. This way, they can still test hardware support before installing without downloading 700 MB.

As it was on my modern HP laptop, hardware support was great. My sound, graphics, and wired ethernet chip were auto-configured. For my wireless chip I easily used Ndiswrapper to load the drivers and had no issue with WPA or WEP. Battery monitoring and cpufreq were accomplished at the commandline as well with the default system. Removeable media is seen, but there are issues with the file manager. Directories show up in PCMan, but clicking on them shot an error. Other media, such as ondisk partitions mounted and opened without issue just by clicking on them.

All in all, it's a fairly neato little image. It's fun to play with as it is or could be a great start to your very own system. See some more screenshots in the gallery. Visit the TinyMe Homepage for downloads.




Thanks for the review/a few comments

Hello,

I'm KDulcimer, head developer and release manager for TinyMe.

Thanks for the review. To this point, TinyMe has been an effort to take PCLinuxOS 2007 Final and hack it down to something really, really small. We take a look at Puppy Linux (an excellent small distribution) and a few other small distros for comparison (and to steal applications from them Big Grin).

However, we're taking a hard look at starting over for the next Test. We've had some input from the Ripper Gang on building PCLOS from scratch. So look for a smaller ISO and more bugs next time. Wink

The grub and bootup splash screen have been fixed by RPMs from Gettinther (and it's quite impressive if I do say so myself). The installer icon has been marked to be included in next release. We're looking at including the latest Abiword in the next test as well.

A default TinyMe installation should be just over 500MB.

Installing a different login manager takes manually editing a configuration file as well as enabling the manager in the PCLOS CC.

You are not able to mount the device because you do not have a line in /etc/fstab for that drive/partition. I'm sure there's a way to have PCManFM mount the removable drives in /media like PCLOS official, but I don't know what it is.

My laptop as well runs at 1280x800 and the background not scaling is a bit of an annoyance to me as well. I'll mark it up in the bugs list.

I'll bet GIMP pulled in a ton of dependencies. Smile

I have as a test machine a PII @ 266MHz w/ 128MB of RAM. So far TinyMe fits pretty well, but I have to say, it's got a little ways to go to get the speed I want. Try running TinyMe in Virtualbox @ 800x600. It's quite usable and you don't feel crammed at all. I think LXDE actually works better at that resolution than 1280x800.

Please note that TinyMe has its own repository in addition to the PCLOS repos. TinyMe users should keep that repo enabled along with a PCLOS repo.

I have it in my own personal notes to try to upgrade TinyMe to a full PCLOS and write down the process.

Thank you again for your review and your input. You can bet I'll be looking at this article when I'm working on the next test release to see how I can make it better.

~KDulcimer
http://tinyme.mypclinuxos.com

Interesting. I haven't seen

Interesting. I haven't seen this data on LXDE. Can you provide a link? I got LXDE to run in VirtualBox with as little as 48MB of RAM + swap space. I'm working on giving it a real-life whirl on a 266Mhz PII. I'm starting with 128MB of RAM and cutting back until it doesn't boot anymore. Big Grin

As far as a browser, we're pretty set on Opera. We can only do so much to it to slim it down and stay within their liscense.

~KDulcimer
http://tinyme.mypclinuxos.com

What page were you

What page were you specifically looking at?

Try going to Tools--> Quick Preferences--> Edit Site Preferences--> Network tab--> change browser ID to "Mask as Firefox".

I didn't see a problem with msn.com in Opera on WinXP. Often, a page not loading correctly in Opera is due to the page containing invalid code. I'll be sure to make sure the Flash plugins work for our Opera.

LXDE does not come with a window manager. We are using Openbox for our WM. However, you may theorhetically use any WM with LXDE: xfwm4, kwin, even Emerald with Beryl/Compiz-fusion! Wink Big Grin

~KDulcimer
http://tinyme.mypclinuxos.com

Very good review. I will

Very good review. I will certainly love to try TinyMe when the stable version is released. Thanks for this one.

I was also impressed by the look of tinyme. However, compared to the speed of zenwalk with xfce, tinyme (on the same machine, amd athlon 1600+) isn't that responsive.

______________________
Caballos

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Programming: Python, LLVM and Erlang

  • Sending Emails in Python — Tutorial with Code Examples

    What do you need to send an email with Python? Some basic programming and web knowledge along with the elementary Python skills. I assume you’ve already had a web app built with this language and now you need to extend its functionality with notifications or other emails sending. [...] Sending multiple emails to different recipients and making them personal is the special thing about emails in Python. To add several more recipients, you can just type their addresses in separated by a comma, add Cc and Bcc. But if you work with a bulk email sending, Python will save you with loops. One of the options is to create a database in a CSV format (we assume it is saved to the same folder as your Python script). We often see our names in transactional or even promotional examples. Here is how we can make it with Python.

  • Binning Data with Pandas qcut and cut

    When dealing with continuous numeric data, it is often helpful to bin the data into multiple buckets for further analysis. There are several different terms for binning including bucketing, discrete binning, discretization or quantization. Pandas supports these approaches using the cut and qcut functions. This article will briefly describe why you may want to bin your data and how to use the pandas functions to convert continuous data to a set of discrete buckets. Like many pandas functions, cut and qcut may seem simple but there is a lot of capability packed into those functions. Even for more experience users, I think you will learn a couple of tricks that will be useful for your own analysis. [...] The concept of breaking continuous values into discrete bins is relatively straightforward to understand and is a useful concept in real world analysis. Fortunately, pandas provides the cut and qcut functions to make this as simple or complex as you need it to be. I hope this article proves useful in understanding these pandas functions. Please feel free to comment below if you have any questions.

  • Analysing music habits with Spotify API and Python

    I’m using Spotify since 2013 as the main source of music, and back at that time the app automatically created a playlist for songs that I liked from artists’ radios. By innertion I’m still using the playlist to save songs that I like. As the playlist became a bit big and a bit old (6 years, huh), I’ve decided to try to analyze it.

  • Python IDEs and Code Editors

    A code editor is a tool that is used to write and edit code. They are usually lightweight and can be great for learning. However, once your program gets larger, you need to test and debug your code, that's where IDEs come in. An IDE (Integrated Development Environment) understand your code much better than a text editor. It usually provides features such as build automation, code linting, testing and debugging. This can significantly speed up your work. The downside is that IDEs can be complicated to use.

  • Announcing Anaconda Distribution 2019.10

    As there were some significant changes in the previous Anaconda Distribution 2019.07 installers, this release focuses on polishing up rough edges in that release and bringing all the packages up to date with the latest available in repo.anaconda.com. This means many key packages are updated including Numpy, Scipy, Scikit-Learn, Matplotlib, Pandas, Jupyter Notebook, and many more. As many of the package updates have addressed Common Vulnerabilities and Exposures (CVEs), it is important to update to the latest. Another key change since the last release is that Apple released macOS version 10.15 – Catalina. Unfortunately, this was a breaking release for previous versions of Anaconda that used the pkg installer. The Anaconda Distribution 2019.10 installers address the issues and should install without trouble on macOS Catalina. If you would rather repair your current Anaconda installation, please check out this blog post for tips.

  • Apple's Numbers and the All-in-One CSV export

    The hierarchical form requires a number of generator functions for Sheet-from-CSV, Table-from-CSV, and Row-from-CSV. Each of these works with a single underlying iterator over the source file and a fairly complex hand-off of state. If we only use the sheet iterator, the tables and rows are skipped. If we use the table within a sheet, the first table name comes from the header that started a sheet; the table names come from distinct headers until the sheet name changes. The table-within-sheet iteration is very tricky. The first table is a simple yield of information gathered by the sheet iterator. Any subsequent tables, however, may be based one one of two conditions: either no rows have been consumed, in which case the table iterator consumes (and ignores) rows; or, all the rows of the table have been consumed and the current row is another "sheet: table" header.

  • Formatting NFL data for doing data science with Python

    No matter what medium of content you consume these days (podcasts, articles, tweets, etc.), you'll probably come across some reference to data. Whether it's to back up a talking point or put a meta-view on how data is everywhere, data and its analysis are in high demand. As a programmer, I've found data science to be more comparable to wizardry than an exact science. I've coveted the ability to get ahold of raw data and glean something useful and concrete from it. What a useful talent!

  • Sony Pushes More AMD Jaguar Optimizations To Upstream LLVM 10 Compiler

    Sony engineers working on the PlayStation compiler toolchain continue upstreaming various improvements to the LLVM source tree for helping the AMD APUs powering their latest game console. Several times now we've pointed out Sony engineers contributing AMD "btver2" improvements to upstream LLVM with the company using LLVM/Clang as their default code compiler and the PlayStation 4 relying on a Jaguar APU.

  • [llvm-dev] GitHub Migration Schedule and Plans
    Hi,
    
    We're less than 2 weeks away from the developer meeting, so I wanted to
    give an update on the GitHub migration and what's (hopefully) going to
    happen during the developer meeting.
    
    Everyone who has added their information to the github-usernames.txt
    file in SVN before today should have received an invite to become a collaborator
    on the llvm-project repository.  If you did not receive an invite and think
    you should have, please contact me off-list.  I will continue to monitor the
    file for new updates and periodically send out new batches of invites.
    
    There is still some ongoing work to get the buildbots ready and the mailing lists
    ready, but we are optimistic that the work will be done in time.
    
    The team at GitHub has finished implementing the "Require Linear History"
    branch protection that we requested.  The feature is in beta and currently
    enabled in the llvm-project repository.  This means that we will have the
    option to commit directly via git, in addition to using the git-llvm script.
    A patch that updates git-llvm to push to git instead of svn can be found here:
    https://reviews.llvm.org/D67772.  You should be able to test it out on your
    own fork of the llvm-project repository.
    
    The current plan is to begin the final migration steps on the evening (PDT)
    of October 21.  Here is what will happen:
    
    1. Make SVN read-only.
    2. Turn-off the SVN->git update process.
    3. Commit the new git-llvm script directly to github.
    4. Grant all contributors write access to the repository.
    5. Email lists announcing that the migration is complete.
    
    Once the migration is complete, if you run into any issues, please file
    a bug, and mark it as a blocker for the github metabug PR39393.
    
    If you have any questions or think I am missing something, please
    let me know.
    
    Thanks,
    Tom
    
    
  • LLVM Plans To Switch From Its SVN To Git Workflow Next Week

    On 21 October they plan to make LLVM's SVN repository read-only and finish their git-llvm script to bring all the changes into Git, and then allow developers to begin contributing to the LLVM GitHub project as the new official source repository.

  • Excellent Free Books to Learn Erlang

    Erlang is a general-purpose, concurrent, declarative, functional programming language and runtime environment developed by Ericsson, a Swedish multinational provider of communications technology and services. Erlang is dynamically typed and has a pattern matching syntax. The language solves difficult problems inherent in parallel, concurrent environments. It uses sets of parallel supervised processes, not a single sequential process as found in most programming languages. Erlang was created in 1986 at the Ellemtel Telecommunication Systems Laboratories for telecommunication systems. The objective was to build a simple and efficient programming language resilient large-scale concurrent industrial applications. Besides telecommunication systems and applications and other large industrial real-time systems, Erlang is particularly suitable for servers for internet applications, e-commerce, and networked database applications. The versatility of the language is, in part, due to its extensive collection of libraries.

today's howtos

Kubernetes at SUSE and Red Hat

  • Eirinix: Writing Extensions for Eirini

    At the recent Cloud Foundry Summit EU in the Netherlands, Vlad Iovanov and Ettore Di Giacinto of SUSE presented a talk about Eirini — a project that allows the deployment and management of applications on Kubernetes using the Cloud Foundry Platform. They introduced eirinix — a framework that allows developers to extend Eirini. Eirinix is built from the Quarks codebase, which leverages Kubernetes Mutating Webhooks. With the flexibility of Kubernetes and Eirini’s architecture, developers can now build features around Eirini, like Persi support, access to the application via SSH, ASGs via Network Policies and more. In this talk, they explained how this can be done, and how everyone can start contributing to a rich ecosystem of extensions that will improve Eirini and the developer experience of Cloud Foundry.

  • Building an open ML platform with Red Hat OpenShift and Open Data Hub Project

    Unaddressed, these challenges impact the speed, efficiency and productivity of the highly valuable data science teams. This leads to frustration, lack of job satisfaction and ultimately the promise of AI/ML to the business is not redeemed. IT departments are being challenged to address the above. IT has to deliver a cloud-like experience to data scientists. That means a platform that offers freedom of choice, is easy to access, is fast and agile, scales on-demand and is resilient. The use of open source technologies will prevent lockin, and maintain long term strategic leverage over cost. In many ways, a similar dynamic has played out in the world of application development in the past few years that has led to microservices, the hybrid cloud and automation and agile processes. And IT has addressed this with containers, kubernetes and open hybrid cloud. So how does IT address this challenge in the world of AI – by learning from their own experiences in the world of application development and applying to the world of AI/ML. IT addresses the challenge by building an AI platform that is container based, that helps build AI/ML services with agile process that accelerates innovation and is built with the hybrid cloud in mind.

  • Launching OpenShift/Kubernetes Support for Solarflare Cloud Onload

    This is a guest post co-written by Solarflare, a Xilinx company. Miklos Reiter is Software Development Manager at Solarflare and leads the development of Solarflare’s Cloud Onload Operator. Zvonko Kaiser is Team Lead at Red Hat and leads the development of the Node Feature Discovery operator.

Python Across Platforms

  • Chemists bitten by Python scripts: How different OSes produced different results during test number-crunching

    Chemistry boffins at the University of Hawaii have found, rather disturbingly, that different computer operating systems running a particular set of Python scripts used for their research can produce different results when running the same code. In a research paper published last week in the academic journal Organic Letters, chemists Jayanti Bhandari Neupane, Ram Neupane, Yuheng Luo, Wesley Yoshida, Rui Sun, and Philip Williams describe their efforts to verify an experiment involving cyanobacteria, better known as blue-green algae. Williams, associate chair and professor in the department of chemistry at the University of Hawaii at Manoa, said in a phone interview with The Register on Monday this week that his group was looking at secondary metabolites, like penicillin, that can be used to treat cancer or Alzheimer's.

  • Chemists discover cross-platform Python scripts not so cross-platform

    In a paper published October 8, researchers at the University of Hawaii found that a programming error in a set of Python scripts commonly used for computational analysis of chemistry data returned varying results based on which operating system they were run on—throwing doubt on the results of more than 150 published chemistry studies. While trying to analyze results from an experiment involving cyanobacteria, the researchers—Jayanti Bhandari Neupane, Ram Neupane, Yuheng Luo, Wesley Yoshida, Rui Sun, and Philip Williams—discovered significant variations in results run against the same nuclear magnetic resonance spectroscopy (NMR) data. The scripts, called the "Willoughby-Hoye" scripts after their authors—Patrick Willoughby and Thomas Hoye of the University of Minnesota—were found to return correct results on macOS Mavericks and Windows 10. But on macOS Mojave and Ubuntu, the results were off by nearly a full percent.