Dpup Exprimo 5.X.3.1.10.3 SMP multicore optimized version
User review
I got great results with the following
I tested squeeze-5.X.3.1.10.2-SCSI.iso
with Charlie6's xf86-input-k.3.2.11-wacom-0.14.0.pet
that I got from Murga wacom thread
and the Wacom Bamboo tablet
.... and it worked beautifully!!
I didn't have the problems that I experience with Lucid Puppy.
i.e. not problems with a black screen when I make a Pupsave file
and there was no persistency problems.
I got great results with the following
I tested squeeze-5.X.3.1.10.2-SCSI.iso
with Charlie6's xf86-input-k.3.2.11-wacom-0.14.0.pet
that I got from Murga wacom thread
and the Wacom Bamboo tablet
.... and it worked beautifully!!
I didn't have the problems that I experience with Lucid Puppy.
i.e. not problems with a black screen when I make a Pupsave file
and there was no persistency problems.
Last edited by don570 on Tue 03 Apr 2012, 17:08, edited 1 time in total.
Bluetooth starting file is and has been in /etc/init.d...do you mean something else ?1) your bluetooth start-up file (that lives in /root/Startup) is missing
I believe the pet really overwrites some existing files. It has been packaged and tested by stu90. I dont have working bluetooth system so I cant much test it. Of course I could inspect the overlapping files but...if it works...2) when I downloaded .5 bluetooth pet, for the first time in my dpup try-outs, it warned me of copying over libs. I knew I needed .5, so I went ahead and installed. But the file is necessary, and you don't want to scare off new users and bluetooth. Maybe this pet should come pre-installed
I believe Jemimah could answer better to that problem. You could pm her ? And if you get working solution...please post the procedure here.3) fn brightness works, but with no on-screen scale (similar to volume control). I don't mind, but is a file missing (the way volup, etc was missing from previous version)?
Well...that is the best part of puppy land. You can find working solution from other puppy. There is so many kind hardware and needs that several puppies complements each other...There is official Puppies for older hardware and so on... I cant much use Racy because the xorg does not like my touchpad. The same problem with Saluki and also with Precise Pangolin...which has Barrys compiled xorg-server:I hadn't realized that Racy 5.2.2 had a 3.07 kernel, so I tried that out. Racy saw my router, but couldn't connect, nor was the ClickPad fully functioning. My xorg re-config crashed Racy.
Somewhere in this compile happened the same kind intolerance to my touchpad which affects Racy and Saluki. So...I stick with Dpup. It supports my hw perfectly.There were some issues, such as the xorg-server segfaulting, so I recompiled it, used version 1.11.4 instead of 1.11.3 used by Ubuntu.
Great news is that Barry K has returned to use aufs. So...it ensures the support to the aufs in Barrys woof and his builds. Slacko and Dpup have been examples using aufs all the time. Well...Slacko tested unionfs for awhile. I did one compile and got weird errors...didnt like it at all.
It seems to be gtk-theme related..whether you see the changing selected box or not. Nodoka themes shows the selected box alright. Aurora doesnt. So....it might be better to change the default theme for next version...sniff...Strange for me, the PupShutdown does not accept keyboard.
I pressed the power-button, the PupShutdown dialog arises, but it cannot be managed by the keyboard.
Re: Shutdown without mouse
PupShutdown-1.8.1shinobar wrote:Strange for me, the PupShutdown does not accept keyboard.
I pressed the power-button, the PupShutdown dialog arises, but it cannot be managed by the keyboard.
-Added keyboard shortcuts for the eight standard shutdown options: Alt+P (Power-Off), Alt+R (Reboot), Alt+L (Log-Out), Alt+S (Lock Screen), Alt+X (Restart X), Alt+W (Restart WM), Alt+T (Manage Task) and Alt+F (Backup Files). Thanks shinobar.
http://murga-linux.com/puppy/viewtopic.php?t=56077
Re: Shutdown without mouse
pemasu wrote:It seems to be gtk-theme related..whether you see the changing selected box or not. Nodoka themes shows the selected box alright. Aurora doesnt.
Great. Both works fine. With keyboard:radky wrote:PupShutdown-1.8.1
-Added keyboard shortcuts for the eight standard shutdown options: Alt+P (Power-Off), Alt+R (Reboot), Alt+L (Log-Out), Alt+S (Lock Screen), Alt+X (Restart X), Alt+W (Restart WM), Alt+T (Manage Task) and Alt+F (Backup Files).
[F12] >> [↑] >> [Enter] (Nodoka theme)
or
[F12] >> [↑] >> [Alt][P] (PupShutdown-1.8.1)
But still i propose another solution for the case we loose mouse and keyboard, or the display. Or for the keyboard-less systems.
I made a timeout feature against radky's PupShutdown. It goes to power off if no replay for 60 seconds. This timeout behavior is only when the PupShutdown is launched by the power button thanks to the acpid. Eternal wait (normal behavior) if the PupShutdown is launched from the menu.
Attached my proposal. It requires thePupShutdown and the acpid. Contains 3 files, /etc/acpi/actions/acpi_poweroff.sh, /usr/bin/wmpoweroff, and /usr/local/PupShutdown/PupShutdown.
EDIT: UPDATED 14:19:09 4 Apr 2012
EDIT: UPDATED 5 Apr 2012 http://www.murga-linux.com/puppy/viewto ... 422#617422
Last edited by shinobar on Thu 05 Apr 2012, 14:27, edited 3 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
acpi_poweroff.sh updated
Updated the pet (timestamp 14:19:09). Only the file /etc/acpi/actions/acpi_poweroff.sh to be configurable the behavior.pemasu wrote:Thanks Shinobar. I will test.
Skipping the dialog is preferable for the keyboard-less systems. I frequently use Puppy for the keyboard-less monitoring systems in manufacturing factories. Boot from USB flash, no HDD, and no saving back thanks to the pupsaveconfig.#!/bin/sh
# Patriot Jan 2009 for Puppy Linux 4.1.1 GPL
# Revision 0.0.6
# 13sep09 dialogbox by shinobar
# 4nov09 TIMELIMIT 30sec
# 26dec09 wmpoweroff, adjustable less than 10sec.
# 4apr2012 shinobar: PupShutdown with time limit
TIMELIMIT=60 # in second, 0: eternal wait, negatives: skip dialog
SOUND="/usr/share/audio/bark.au"
PLAY="aplay"
[ -f "$SOUND" ] && which $(basename $PLAY) >/dev/null && $(basename $PLAY) "$SOUND"
#echo "DISPLAY=$DISPLAY" >> /root/acpi.log
X_pid=`ps ax | awk '{if (match($5, "X$") || $5 == "X") print $1}'`
if [ "$X_pid" != "" ]; then
#if [ "$DISPLAY" != "" ]; then
[ $TIMELIMIT -ge 0 ] && [ -x /usr/local/PupShutdown/PupShutdown ] && P="/usr/local/PupShutdown/PupShutdown $TIMELIMIT"
[ "$P" = "" ] && P=wmpoweroff
else
P=poweroff
fi
exec $P
Last edited by shinobar on Wed 04 Apr 2012, 05:55, edited 2 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
I have tested now PupShutdown-timeout-20120404.pet. It seems that from script /etc/acpi/actions/acpi_poweroff.sh the part: && P="/usr/local/PupShutdown/PupShutdown $TIMELIMIT"
does not carry the TIMELIMIT value to the modified script: /usr/local/PupShutdown/PupShutdown.
The part:
does not take TIMEOUT timelimit in action. I am not sure should it be TIMELIMIT as in acpi_poweroff.sh script to carry it here, but even changing the TIMEOUT to TIMELIMIT does not help. The powerbutton shuts down after sleep 1.
Also the MENU > Shutdown which launches the PupShutdown script shuts down after 1 second.
It could be easiest solution that I revert back to just shutting down with powerbutton and forget the PupShutdown usage. It seemed good change but as always: every action has also counter-action.....
And Shinobar has shown that there is real need for just shutting down.
does not carry the TIMELIMIT value to the modified script: /usr/local/PupShutdown/PupShutdown.
The part:
Code: Select all
# 4Apr2012 shinobar: tieout
[ $TIMEOUT -eq 0 ] && exit
for I in $(seq $TIMEOUT); do
sleep 1
pidof PSD-bin &>/dev/null || exit
done
wmpoweroff
Also the MENU > Shutdown which launches the PupShutdown script shuts down after 1 second.
It could be easiest solution that I revert back to just shutting down with powerbutton and forget the PupShutdown usage. It seemed good change but as always: every action has also counter-action.....
And Shinobar has shown that there is real need for just shutting down.
The brightness scale only works on the EEEPC, which sends acpi events when you changes the brightness. With other machines the kernel changes the brightness silently and AFAIK there's no easy way to know from a script when it happens or how bright it is.pemasu wrote:I believe Jemimah could answer better to that problem. You could pm her ? And if you get working solution...please post the procedure here.3) fn brightness works, but with no on-screen scale (similar to volume control). I don't mind, but is a file missing (the way volup, etc was missing from previous version)?
I have removed the overwriting - preinstalled bluetooth files from bluetooth-0.5.pet. Jakfish or someone with bluetooth connection testing possibility could test the reloaded bluetooth-0.5.pet. It is now of course slimmer.
http://www.smokey01.com/pemasu/pet_pack ... th-0.5.pet
http://www.smokey01.com/pemasu/pet_pack ... th-0.5.pet
Yes, bluetooth .05 installs, works, without overwriting files.
I've been doing so much testing of this OS that I've lost my place and hadn't realized that the /root/Startup/bluetooth.sh was put in by this pet. My mistake, I thought it was part of the stock OS.
As jemimah's warning about graphic for screen resolution, that makes sense, and the graphic is unnecessary--all that matters is that it works, and it does.
Jake
I've been doing so much testing of this OS that I've lost my place and hadn't realized that the /root/Startup/bluetooth.sh was put in by this pet. My mistake, I thought it was part of the stock OS.
As jemimah's warning about graphic for screen resolution, that makes sense, and the graphic is unnecessary--all that matters is that it works, and it does.
Jake
Thank you Jakfish of the report. Good to know. And thank you of your extensive testing and work for improving the distro. As you and all the other. My distro evolves based on requests, fixes, suggestions and hacks by the users.
That makes this woof building satisfactory...and the fact that Dpup works as my main OS.
That makes this woof building satisfactory...and the fact that Dpup works as my main OS.
This should make Jim1911 happy. Openbibleviewer-0.7.0.
It needs qt4-libs, for example basic and clucene.
http://www.smokey01.com/pemasu/QT-4.8.0 ... t-dpup.pet
http://www.smokey01.com/pemasu/QT-4.8.0 ... .3.3.4.pet
http://qt-apps.org/content/show.php?content=123227
It needs qt4-libs, for example basic and clucene.
http://www.smokey01.com/pemasu/QT-4.8.0 ... t-dpup.pet
http://www.smokey01.com/pemasu/QT-4.8.0 ... .3.3.4.pet
http://qt-apps.org/content/show.php?content=123227
PupShutdown-timeout-20120405
Right. Was missing:pemasu wrote:I have tested now PupShutdown-timeout-20120404.pet. It seems that from script /etc/acpi/actions/acpi_poweroff.sh the part: && P="/usr/local/PupShutdown/PupShutdown $TIMELIMIT"
does not carry the TIMELIMIT value to the modified script: /usr/local/PupShutdown/PupShutdown.
Code: Select all
TIMEOUT=$1 # 5Apr2012 shinobar: timeout# 5Apr2012 shinobar: timeout
...
TIMEOUT=$(echo $TIMEOUT| tr -dc '0-9-')
[ "$TIMEOUT" ] || TIMEOUT=0
Anyway it would be nice if the time limit is shown on the dialog...
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Now the PupShutdown works perfect. I can include the modified scripts to the next version.
About information of the shutdown timelimit default in PupShutdown would be great. It would be Dpup Exprimo speciality atm...but maybe Radky would be interested to think about it....
Or if there would be the default timelimit shown when you press the shutdown button. Which ever way...it would be good to have.....
Oh yeah...the wmpoweroff, wmexit and wmreboot needs killall enlightenment row. It might be that I have missed them in some of the scripts during the updates but now I noticed the need and remind of it :
snippet.....
About information of the shutdown timelimit default in PupShutdown would be great. It would be Dpup Exprimo speciality atm...but maybe Radky would be interested to think about it....
Or if there would be the default timelimit shown when you press the shutdown button. Which ever way...it would be good to have.....
Oh yeah...the wmpoweroff, wmexit and wmreboot needs killall enlightenment row. It might be that I have missed them in some of the scripts during the updates but now I noticed the need and remind of it :
snippet.....
Code: Select all
PSPEFD="`ps -C pup_event_frontend_d | grep 'pup_event_front' | grep -v 'defunct'`"
done
sleep 0.2
killall enlightenment
sync
Last edited by pemasu on Thu 05 Apr 2012, 21:58, edited 2 times in total.
Tmanjim3630 wrote:Tman thanks for the help. on this startup of ff and closing problem is gone.Tman wrote:Jim, try modifying /usr/local/bin/defaultbrowser to the following:jim3630 wrote: only issue is firefox when reopen gives error msg ff is already running.And then create an icon entry for defaultbrowser, or just type it in the terminal.Code: Select all
#!/bin/sh yaf-splash -bg red -fg white -placement center -timeout 2 -text "loading.." & killall firefox 2> /dev/null sleep 0.3 exec /usr/lib/firefox/run-mozilla.sh /usr/lib/firefox/firefox "$@"
this has happened in the past with other pups but don't recall why occurred.
will keep your fix saved away.
after some time without the problem today it returned and applying your fix it worked!
any idea why this happens?
thanks again for the fix.
------------
seems only one having this problem. like to know what am doing wrong here.
pemasu
do you know if this is something I did or your pup?
Last edited by jim3630 on Fri 06 Apr 2012, 13:17, edited 1 time in total.