Puppy Newsletter


A group of 'dogs' with smokey01 in the front-seat is now putting together a monthly newsletter covering stuff from the kennel.

There has been some discussion in the forum some time now, and the first edition is released as scheduled - the first in every month. Hopefully this project will end up as one of the major resources for us. Much is happening in the Puppy world, but until now we have missed a encompassing channel. If you are interesting in a collaborating project, please join these good guys. Else, enjoy reading.

Happy new year.

Posted on 2 Jan 2017, 13:37 by zigbert - Categories: Puppy
Comments - Edit - Delete


Audioplayer's resource hunger


Testing resource hunger of audioplayers
This test contains the basic audio players; DeadBeeF and Audacious. It contains the mediaplayer VLC, the very comprehensive Exaile and the database driven music managers; pMusic and Clementine. Of course, this is not a fair compete since features differs a lot from player to player. In the end, it might be less important how much system resources the player uses. The functionality is in most cases what makes our choice. But still, it's good to know when running a low-powered system, and when choosing the default player.

From my personal view, I am interesting to see how pMusic is working compared to other players. pMusic has got a lot of criticism of its hunger on cpu resources. I want to disprove this reputation.


The test
My test-machine is an AsusEEE netbook 1001px (cpu:2x1.66Ghz atom).
This is a low-powered netbook that makes it easier to measure the differences in cpu-usage. Running on a modern pc, none of these players will make your system hot.

The OS is XenialPup 7.0.4.
VLC and DeadBeeF is installed by default. On this system I was able to run both Clementine and Exaile which is the most comparable to pMusic. Tried to install Amarok with no success. If you run another player of XenialPup 7.0.4, it would be great if you gave me a link to the pet/sfs. I am interested to extend my test with more players.

The task is to play a mp3 file.
I have used the default setting for each player, and started the app at least twice to ensure no first-run operation misleads the test-result.

The compared players are:
Audacious 3.6.2, Clemetine 1.2.3, DeaDBeeF 0.7.2, Exaile 3.2.2, pMusic 5.2.4, VLC 2.2.2


Cpu-usage playing mp3 with gui shown
Exaile		 7.5 %

VLC 8.3 %
DeaDBeeF 8.8 %
Audacious 10.0 %
pMusic 12.1 %
Clementine 18.2 %

Surprisingly. I guessed DeadBeef would be the winner because of its reputation of being lightweight. Exaile is a much more comprehensive option than DeadBeeF and Audicious, and still, it has less appetite for cpu-cycles.


Memory-usage playing mp3 with gui shown
Audacious	 5 Mb

DeaDBeeF 20 Mb
Exaile 23 Mb
VLC 25 Mb
pMusic 29 Mb
Clementine 33 Mb

Audicious is impressive. I had to verify it one more time. Let's mention that this is the Gtk gui - not the Winamp clone. Else, smaller range than expected. The guis differs from the simple (VLC) to the complex (Clementine), and I had expected the memory usage to differ more.


Size required for installation:
pMusic		 1 Mb

Audacious 8 Mb
DeaDBeeF 10 Mb
VLC 53 Mb
Clementine 66 Mb
Exaile 66 Mb

pMusic is built for Puppy, and take advantage of already existing dependencies. That makes it of course the smallest, but it is also the only player that is not compiled, and that is probably another reason for the result.

Clementine is overall the heavy choice. I hoped to compare with Amarok which I assume it is the biggest brother (153 Mb install), but I were not able to get it work in Xenial. Hopefully, someone make a pack some day, and I will update these results.


Posted on 15 Nov 2016, 02:58 by zigbert - Categories: Puppy
Comments - Edit - Delete


Xenialpup64 alpha


The first alpha release of Xenialpup64 is now available.

kernel 4.6.3
qt5
vlc
ffmpeg
palemoon
deadbeef
hexchat
samba
and all the usual puppy stuff.

xenialpup64 and xenialpup 32bit isos are available here http://ftp.nluug.nl/ftp/pub/os/Linux/distr/puppylinux/test/xenialpup/

please post all bugs found on the xenialpup64 thread here http://murga-linux.com/puppy/viewtopic.php?p=910078#910078

happy testing :)





Posted on 30 Jun 2016, 04:10 by 666philb - Categories: Puppy
Comments - Edit - Delete


LxPupSc - new version jan-17


LxPupSc-17.01.1R with kernel 4.9.0 is available.

See this blog entry for more description of LxPupSc

Posted on 2 Jan 2017, 05:51 by peebee - Categories: Puppy Woof-CE Release
Comments - Edit - Delete


Puppy Linux sandbox


Recent Woof-CE based puppies have a new tool which is rather obscure and thus often overlooked.

The tool in question is "sandbox". This is a tool that enables the user to run "puppy within puppy". When you run sandbox, you get a fresh environment that resembles the puppy you're running on, except that anything you do inside sandbox will not change anything outside it (with some exceptions ...). It's ideal for testing some nasty pets that like to change your system files without you knowing it - if a pet breaks your installation, well it only does it within sandbox. Your main system continues oblivious to whatever happens in sandbox. And when you leave sandbox, everything you do inside it, is gone.

If you want to setup an alternate environment (with a different savefile), you can do that too. The standard sandbox will lose its contents when you leave, but rw-sandbox will keep it --- the content is gone when you leave the sandbox, but when you re-enter, it will be restored. Just like a savefile.

How to run it? Sandbox and its brother rw-sandbox only runs from terminal. So launch a terminal, and type "sandbox.sh". Choose the layers you want to use, and you will enter the sandbox. Type "exit" to leave the sandbox. Inside the sandbox, you can also launch GUI programs like geany or seamonkey, if you wish to. Just make sure that you kill all of them before leaving sandbox.

To start rw-sandbox, do the same but instead type "rw-sandbox.sh". You will be asked where to create a new savefile (or load an existing one if it already exists). The rest it the same.

Sandbox was originally a feature of Fatdog64, which was backported to Woof-CE last year by request of forum member "eowens". To see what can and cannot be done with sandbox, please see its original documentation page: http://distro.ibiblio.org/fatdog/web/faqs/sandbox.html. Note: Puppy Linux does not have lxc-sandbox, because right now it does not support lxc. Also, the full-desktop emulation is not working on Puppy yet, because it lacks certain tools needed for that. But everything else will work.

And if your copy of Puppy doesn't come with sandbox, pester your favorite developer to rebuild it from Woof-CE. Building fresh from Woof-CE will include sandbox as well as many other updates, such as zigbert's excellent pthemes.


Posted on 14 Apr 2016, 23:19 by jamesb - Categories: Puppy
Comments - Edit - Delete


LxPupSc


LxPupSc is a somewhat different pup....

As default, the desktop environment is LXDE (openbox, lxpanel, pcmanfm) rather than the more usual puppy jwm and rox (although these are still part of the build and there is a desktop switcher to activate them if you prefer).

LxPupSc is a 100% woof-ce 32-bit build but it does have a unique characteristic in that it is built from multiple sources as follows:
- Slackware base components come from Slackware-14.2 (a.k.a Slackware-Current)
- LXDE components come from Arch Linux
- Puppy pets are a mixture of Slacko-14.2 plus specific pet-builds when recompilation is needed for Slackware-Current library compatibility

Plus there are also a bunch of fix-pets, packages-templates, woof-ce patches etc. to get it all to hang together. (What properly goes where is still a bit of a black-art for me and I suspect some rationalisation could be done here!)

The kernel is a woof-ce kernel-kit build.

Thanks are due to many people whose more original work has been plagiarised ruthlessly:
- Jejy69 for the original LxPup way back in 2013 and particularly the menu configuration
- 01Micko for the Slacko-6.3 configuration used as a starting point and for much advice along the way and the pet-build system
- Stemsee for the kernel config
- Iguleder, 01Micko, and pemasu for the kernel-kit
- Mavrothal for testing and fixes (particularly the ppm/dependencies fix) and woof-ce advice and help
- Marv, Billtoo, ETP, radky, rcrsn51, gcmartin and many others for testing and helpful suggestions on the forum thread (apologies to anybody not mentioned)
- Smokey01 for the repository

Along the way, testing has identified some things that have found their way back into woof-ce for the benefit of future puppies (e.g. the sns/firewall-ng fixes).

In using woof-ce I have got a list of "enhancements" that I'd like to see:
- better support for incremental builds (1download to produce a list of changed packages downloaded; 2createpackages to loop to build that list)
- better integration of rootfs-packages and DISTRO_PKGS_SPECS- so that you don't have to tick choices in 3builddidtro-Z (e.g. have yes/no/woof as options)
(an interim change would be to make all rootfs-package chosen by default so you only have to unselect unwanted ones....)
- 3builddistro-Z to have better unattended operation - replace terminal questions scattered through script with a config file so you can start the build and go away and forget about it

The version of LxPupSc at the time of writing is 16.08.1 (hosted on SourceForge)
The forum thread
The repository
LxPup Reviews

Cheers
PeeBee
August 2016

Obligatory screenie:


Posted on 8 Aug 2016, 08:22 by peebee - Categories: Puppy Woof-CE
Comments - Edit - Delete


Pages: [1] [2] [3]