Page 108 of 111

Posted: Wed 29 Aug 2012, 01:08
by edoc
Thanks for the review - it feels to me as if Firefox and Thunderbird are complicating the simple - trying to compete with Explorer and Chrome I suppose.

I guess for now I will stay with Seamonkey - it is familiar - and just works.

I strip anything having to do with Google off my computer as I want no part of their privacy compromise and other poor practices. I do temporarily have one google E-mail account for a non-profit but that will be going away soon as well - replaced by a non-google E-mail.

Thanks again,

David

Posted: Wed 29 Aug 2012, 07:18
by soundNICK
edoc wrote:Thanks for the review - it feels to me as if Firefox and Thunderbird are complicating the simple - trying to compete with Explorer and Chrome I suppose.

I guess for now I will stay with Seamonkey - it is familiar - and just works.

I strip anything having to do with Google off my computer as I want no part of their privacy compromise and other poor practices. I do temporarily have one google E-mail account for a non-profit but that will be going away soon as well - replaced by a non-google E-mail.

Thanks again,

David
Hmmm... funny time for an entire post to vanish... /or is it/ ?!? : -)

Actually, I hadnt mentioned Opera yet... that is definitely my favorite
alternative browser.

soundNICK

WHEEZY / etcetera

Posted: Thu 30 Aug 2012, 02:33
by soundNICK
pemasu wrote: alpha release Dpup Wheezy [SNIP]

pemasu - found your latest, dPup Wheezy... tried it out yesterday.

nice progress, Id have to say... you are well on your way with a
framework, once Wheezy is made ready for prime time by the debian
team - which is the subject of this post.

dPup-Wheezy - while the basic install is fully functional, broke for me
with many complex apps... libraries in the repo are buggy as a rotting
tree, and nothing but problems in compiled pets.

What I would suggest... just out of fairness to newbies such as myself(!)...
is that the dPup-Wheezy downloads be off limits to anyone but testers_
people who are fully aware of breakage problems they will certainly
encounter, and aware that they will be working with something debian
considers not ready for standard usage. This, in no way, is meant as
criticism of your effort... nothing you can do to fix a repo full of broken
libraries.


If it might be of interest:
++ I did manage to get the recent Darktable compiled to a pet, and working.
++ gimp 2.8 worked at low level... seriously broken for me with numerous
other functions... mine couldnt use script-fus, for instance (may have
left something out, but I think its the lagging development).
++ most recent Okular failed completely with wheezy libs

Only because it had a dpup label, I tried installing one pet compiled in
dPup-Exprimo, which totally broke the Wheezy pinboard... fair enough,
since its an earlier debian distro.
So, I gave up, seeing stuff was breaking in this testing environment.

Hope this report is some way helpful to you.

soundNICK

Posted: Thu 30 Aug 2012, 05:20
by pemasu
Dpup Wheezy is alpha stage testing build. As the first post says. I also explicitly recommended people to test it, rip it apart and brake it and report what works and what doesnt.

That is the whole point. I am only one person with day work and other activities and family. I need other people to try out what works in Puppified dpup wheezy.
If I warn people to test, it would make my aim aimless. Average Puppy user is highly above average Ubuntu user. They are learnt to some stage of misbehavior and that not always everything goes right. And also trying to find out why it does not work. I need those reports. I dont want to underestimate Puppy users. They are great people and they can understand what is the mission when you announce something.

There is serious problems with debian and ubuntu development. Gtk-3.0 dependencies with the applications and libraries. Lack of .la files which makes compiling challenging and so on.

But without feedback....I believe my time wont be enough to get working build in time when Debian Wheezy becomes stable.

Posted: Thu 30 Aug 2012, 08:20
by cthisbear
Wise words >>> Mr pemasu.

" I dont want to underestimate Puppy users. "

You have put out some marvellous releases.


Chris.

Posted: Thu 30 Aug 2012, 12:50
by edoc
cthisbear wrote:Wise words >>> Mr pemasu.
" I dont want to underestimate Puppy users. "
You have put out some marvellous releases.
Chris.
pemasu's efforts have been exceptional and most Puppy users are amazingly skilled.

Meanwhile, I am one of the few Puppy users whom one may easily overestimate ... ;-)

Please stay the course, sir!

Posted: Sat 01 Sep 2012, 01:03
by soundNICK
pemasu wrote:Dpup Wheezy is alpha stage testing build. As the first post says. I also explicitly recommended people to test it, rip it apart and brake it and report what works and what doesnt. [S-N-I-P].
oops... my apologies pemasu... I do see those remarks now, in the dPup
Wheezy thread_ : -)

soundNICK

Posted: Tue 11 Sep 2012, 06:13
by Shep
It's time I sent a long-overdue bouquet...    Image

I rely on a 560MHz, PIII with about 768 MB of RAM, and I have been using this Exprimo series for the last 8 or so months. It is fantastic. Image

98% of my net use revolves about Firefox, and it hasn't once frozen, spat the dummy, or kicked over the traces. :D I regularly surf with up 60 browser tabs (crazy, I know) yet Firefox hasn't faltered. (To maximize the ram available for apps, I always boot with puppy pfix=nocopy.)

It is sheer joy to surf with this combo of Dpup Exprimo and Firefox. (We're now up to Firefox 15.0.1, it's a dizzying ride just keeping abreast of browser updates. Image )

I look forward to the next gem from pemasu. Mind you, expectations are now so high .... :lol:


-

Posted: Tue 11 Sep 2012, 13:43
by edoc
Nice report!

Can you explain what this does, please?

"Puppy pfix=nocopy"

I had never heard of this one.

Posted: Tue 11 Sep 2012, 13:59
by Shep
edoc wrote:Can you explain what this does, please?

"Puppy pfix=nocopy"

I had never heard of this one.
Hi edoc. I boot from the CD every time, and "pfix=nocopy" tells puppy not to load the .sfs file (containing most of the puppy software) into ram, instead that data must read from the HD as needed. This means that RAM that would otherwise be occupied by the .sfs file (~150MB) is free for applications to use. (It also means that some apps might be a tiny bit slower to start up on first use because they are coming off the HD rather than from ram.)

If you have installed puppy on your HD as a full install, then I think "pfix=nocopy" would have no effect, as it is already the economical way puppy works.

Posted: Tue 11 Sep 2012, 14:51
by edoc
I do use Frugal installs but the "pfix=nocopy" is real good to know should I have an app that needs to run in limited RAM.

Thanks!

Posted: Wed 12 Sep 2012, 09:10
by piteapup
nice to see dpup still going on...
gonna be testing it later on today...
hope pemasu gets to intergreat memtest86+ on the iso.
and i will see if it runs on my atom n2600/gma3600 netbook
which is a pain as only fedora17 lxde spin gives me 1024x600,
also for shep/edocs if you want to go the other way and run apps only in ram have a look at "ramdisk gui" this is great for running/testing opera as a example
just unpack the opera .tar.xz into it-100mb is big enough..
ramdisk gui link:-
http://www.murga-linux.com/puppy/viewto ... e6eb986483
have fun.

Posted: Wed 12 Sep 2012, 14:02
by edoc
I have Exprimo running on a Samsung NB30 and a MSI Netbook, so it does handle them fine.

I did have some minor problems on the Samsung with display overlap on sub-windows in Seamonkey E-mail setup (I have a workaround) and the display is dimmed if I boot without AC power (haven't found a way around that as F-key display controls are non-respomnsive).

Thanks for the ramdisk gui link.

Posted: Tue 18 Sep 2012, 06:15
by Shep
I could search through this 144 page thread to see whether it has previously been mentioned, or I could just post away .....

Pburn 3.7.4 in Exprimo 5.X.15 does not generate the correct md5sum. After burning the .iso it offers to check the md5sum, but even after ejecting and reinserting the CD, the correct md5sum is not generated.

Only by leaving Pburn and using the commandline (md5sum /dev/sr0) can I get confirmation of an error-free burn.

Posted: Tue 18 Sep 2012, 13:29
by pemasu
Shep. Basically Pburn uses md5sum binary for it also. There is something incompatible in Pburn itself why the Pburn md5sum does not work. I dont have a glue what is behind that misbehavior. Sorry.

If you launch pburn in console, do you get any error messages when it is time for md5sum checking.

Posted: Wed 19 Sep 2012, 11:47
by Shep
pemasu wrote:Shep. Basically Pburn uses md5sum binary for it also. There is something incompatible in Pburn itself why the Pburn md5sum does not work. I dont have a glue what is behind that misbehavior. Sorry.
It works correctly in some puppies, after ejecting & reinserting the CD.
If you launch pburn in console, do you get any error messages when it is time for md5sum checking.
After launching Pburn in a terminal, I tried TOOLS > DISK INFO to check the md5sum of my CD. It gives the same wrong answer, and there is no error message.

Posted: Wed 19 Sep 2012, 23:10
by Tman
Hi Pemasu,

I thought you might be interested in my modification of Iguleder's buildpkg.
Same ..concept ... you just run buildpet [script-name] from the terminal.
Some sample scripts are in /usr/share/buildpet. I've attached a tarball of the rest of the scripts that I have. A few are new, most are from Iguleders builder tarball.

I hope to be able to make a frontend for this soon, so that there will be a menu entry for it like Puppizard, and also, so you can just click on the script and it should ask you if you want to build the pet.

buildpet and tarball of scripts
-

Posted: Thu 20 Sep 2012, 03:31
by pemasu
Thanks Tman. I will test them soon. Yes, I am interested. Automated and semiautomated building scripts are handy. Thank you or your work and sharing it.

Posted: Thu 20 Sep 2012, 14:56
by Tman
EDIT: buildpet version 0.4 is released.

Previous versions did not work if you did this in the terminal:

Code: Select all

cd /usr/share/buildpet/document
buildpet leafpad.bp
and it only worked if you did something like this:

Code: Select all

buildpet /usr/share/buildpet/document/leafpad.bp
Now it works either way.

I have started a new thread for it as well.. the link is 2 posts up.

Twitter Problems with Seamonkey?

Posted: Wed 03 Oct 2012, 13:20
by edoc
On my Netbook, which I have not yet updated from 5x14, Twitter kills performance in Seamonkey.

Is this a known problem that was addressed in 5x15 or in the other development track of Exprimo?

It only happens when Twitter is open.

Thanks!