Puppy Linux Discussion Forum

Volhout · Joined: 28 Dec 2008 Posts: 547

Used RUFUS to put the R41es on a USB stick
Made a save file 256Mb

Opened jre1.7-25 sfs (36.5Mbyte) from Slackware 14.2 folder on ibiblio.
SFS do not become part of save file.
Installed Arduino 1.0.5 (22Mbyte, tar.gz) from arduino website.
I do this for all puppies that I test.

But:
My save file is 70% full now (only 90Mb left of 256Mbyte).

How did the save file drow so fast...??

Any idea ? Is it because this is an "es" release ?

Volhout

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

@Volhout Boot X-Slacko Slim using pfix=ram parameter. Mount your save file by double clicking and look inside what occupies disk space on save file

Volhout · Joined: 28 Dec 2008 Posts: 547

Dear mistfire,

I have tried to duplicate this 3 times, but was not succesfull.
Not sure what had happened that time.

At this moment I get consistent:
create save file (256Mbyte)
actial size 239Mbyte
available when nothing stored (maybe puppy initial settings) 232 Mbyte
After installing arduino (22Mbyte tar-gz file) save file 151 Mbyte
Actual size arduino folder 60Mbyte + size sketchbook (work area containing libraries and examples in /root) could make up for the 80 Mbyte that is extracted from the save file size.

It seems logical now.

Sorry for the confusion,

Volhout

rasul · Joined: 08 Sep 2012 Posts: 31 Location: Tehran, Iran

Volhout · Joined: 28 Dec 2008 Posts: 547

Yesterday I did a full install of XSlacko Slim 4.2r41es on my netbook (asus X101ch) mechanical harddisk (sda4), alongside lubuntu16.04(sda1) and Slacko 5.7.0(sda3). It boots fine and fast, grub4dos boot setup.

Installed Java and Arduino, LinAXEpad, Saleae, and all works.
Please suggest what devx I should install. Still the Slacko 6.3.2 devx (you changed kernel after R37, does that have impact?).

Regards,

Volhout.

P.S. I noticed one minor issue when I tried a frugal install of R41es on the same netbook. It takes minutes before the the screen comes alive (black with mouse cursor for 2 minutes or so). This does not happen in the full install mentioned above. This may relate to the rather awkward N2600 CPU.

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

rasul · Joined: 08 Sep 2012 Posts: 31 Location: Tehran, Iran

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

rasul · Joined: 08 Sep 2012 Posts: 31 Location: Tehran, Iran

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

@rasul it seems that the bluetooth and wifi modules are very recent you can request someone to compile those drivers (if the source code is available) on the hardware section of this puppy forum.

rasul · Joined: 08 Sep 2012 Posts: 31 Location: Tehran, Iran

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

@rasul probably yes

Marv · Joined: 04 May 2005 Posts: 1216 Location: SW Wisconsin

A quick question on volume management pertaining to CD/DVD playing in particular.

Running 4.2r41 as a frugal Grub4Dos install on a core 2 duo laptop and on a Pentium M laptop alongside X-slacko 4.2, LxPupSc 17.03.21 and X-tahr 2.0. Tested both with savefile and pfix=ram.

pup-volume-monitor and pup_event_frontend_d are both enabled and running (checked in the task manager), and in puppy event manager all boxes are ticked wrt auto running of CDs and DVDs. When inserting a disk (CD or DVD), nothing shows up in /root/.pup_event and no handler is called. Bouncing to X-slacko 4.2 (or LxPupSc) when a disk is inserted, the usual entry is created in /root/.pup_event for the disk inserted and either a handler or a dialog box is run. I know that Thunar or PcManFM also do volume management but usually the pup_volume_monitor still creates the entries and will call a handler if running. Any thoughts or is this by design? Run X-slacko 4.2 as the closest comparison.

EDIT1: Substituting /usr/local/pup_event/frontend_funcs from X-slacko 4.2 for the one currently in X-slim restores normal function. Correct entries show up in ~/.pup_event and handlers start normally. My guess is that it is the rox detection in the script currently in X-slim but that is just that, a guess, at the moment.
EDIT2: Made a little testscript and checked. It is the roxtest. The script from X-slacko has none. The frontend_funcs script from LxPupSc works also. It still has a test for roxdesktop but that doesn't exit the script if no rox running ie. lxde or xfce desktops.

mistfire · Joined: 04 Nov 2008 Posts: 1272 Location: PH

@Marv you are right I modified /usr/local/pup_event/frontend_funcs to detect if the rox filer pinboard is running. Since X-Slacko Slim is running in xfce desktop, some routines for rox-filer pinboard must be disabled if the rox pinboard is not running. This will make cpu process more efficient and less write cycle.

What part of the script does the rox desktop test does not exit?

UPDATE: pup_event_frontend_d must required to run all the time because it was responsible for other periodic tasks. Only rox related functions are modified.