ScPup & ScPup64 - Slackware Current based Woof-CE pups

Message

watchdog · #121 Post by **watchdog** » Sun 05 May 2019, 04:32

peebee wrote:
What processors do you both have??

Do you get the problem on both ScPup32 and ScPup64??

I have the problem on both ScPup32 and ScPup64 and I remember Upupdd and Upupcc. I posted my inxi report at:

http://www.murga-linux.com/puppy/viewto ... 54#1026054

I have solved my issue compiling mplayer with the default config settings.

OscarTalks · #122 Post by **OscarTalks** » Sun 05 May 2019, 12:28

This is MPlayer 1.4 compiled in ScPup32 with my choice of options.
GUI enabled with default "Blue" skin included.
(can be used as gmplayer or with gnome-mplayer as frontend)
Binary codecs included in /usr/lib/mplayer/codecs (not likely to be needed but not difficult to do).
Added to Right-click > Open With options
Added -lavdopts threads=2 in .desktop file for multi-thread playback of some formats such as hevc (which often needs it).
Uploaded for testing for a short while
http://smokey01.com/OscarTalks/mplayer- ... -scpup.pet

By the way, the creation of pet.specs file in dir2pet is fixed,
BUT new2dir is still not writing the symlinks into new dir
So when compiling to build a package with new2dir make install, you have to know and remember to add them manually.

peebee · #123 Post by **peebee** » Sat 11 May 2019, 12:47

Versions 19.04+3 - see posts #1 and #2

peebee · #124 Post by **peebee** » Tue 21 May 2019, 15:28

https://sourceforge.net/projects/lxpup/ ... LXQt-ydrv/

ydrv's to change ScPup 32 & 64 to the LXQt desktop

Wiz57 · #125 Post by **Wiz57** » Thu 23 May 2019, 21:58

Hi peebee!
I'm tempted to try out the ydrv for ScPup 32 for LxQT desktop, but
curious...this old netbook (Acer Aspire One A150 aka ZG5, Intel Atom
N270, Intel graphics) only has 1 gig RAM...do you think LxQT would
"run"?? What I might do is make a second frugal install on the HD of
ScPup, then swap the ydrv for LxQT, add my Palemoon, then edit
my menu.lst to include LxQTPupSC and see what happens!! Not sure
what the system requirements are for QT5, but my curiosity is piqued!
Any ideas?
Wiz

norgo · #126 Post by **norgo** » Mon 27 May 2019, 20:23

Wiz57 wrote:...this old netbook (Acer Aspire One A150 aka ZG5, Intel Atom
N270, Intel graphics) only has 1 gig RAM...do you think LxQT would
"run"??...

I am not peebee but maybe you accept my answer too.
YES 1GB is definitively sufficient to run LXQT.

here a screenshot of my 13 years old laptop with 1 GB RAM running peebee's ScPup and LXQT.

Wiz57 · #127 Post by **Wiz57** » Mon 27 May 2019, 21:54

Thank you norgo!
Looks pretty good! Think I'll give it a go as well.
Wiz

Lobster · #128 Post by **Lobster** » Tue 04 Jun 2019, 08:21

Should this be released as Puppy 8.1 Community Edition?

peebee · #129 Post by **peebee** » Sun 09 Jun 2019, 08:26

Versions 19.06+0 - see posts #1 and #2

New base iso
Woof-CE update
New kernels
Slackware Current updates

darry19662018 · #130 Post by **darry19662018** » Sun 09 Jun 2019, 10:13

peebee wrote:Versions 19.06+0 - see posts #1 and #2

New base iso
Woof-CE update
New kernels
Slackware Current updates

Very nice so far running on a compaq dv6000.

Everything worked out of the box as well as package manager.

Wiz57 · #131 Post by **Wiz57** » Sun 09 Jun 2019, 12:12

Thanks peebee! As usual, updated this old netbook with ScPup 19.06 +0 32 bit, no problems! Updated the savefile, here with it now.
Much appreciated, a very stable and smooth puppy!
Wiz

Terry H · #132 Post by **Terry H** » Sun 09 Jun 2019, 21:26

Downloaded ScPup64-19.06+0. Manual frugal install, updated an existing save folder. All working well. Another great release peebee.

Code: Select all

# inxi -CSI
System:    Host: puppypc1956 Kernel: 5.1.6-lxpup64 x86_64 (64 bit) Desktop: JWM 2.3.6 Distro: ScPup64 19.06
CPU:       Dual core Intel Core i5-5200U (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 2700 MHz 1: 1559 MHz 2: 1241 MHz 3: 1910 MHz 4: 1668 MHz
Info:      Processes: 128 Uptime: 15 min Memory: 373.5/7606.5MB Client: Shell (bash) inxi: 2.3.8

darry19662018 · #133 Post by **darry19662018** » Mon 10 Jun 2019, 06:37

# inxi -CSI
System: Host: puppypc30408 Kernel: 4.14.123-lxpup-32-pae i686 (32 bit)
Desktop: JWM 2.3.6 Distro: ScPup 19.06
CPU: Dual core Intel Core2 Duo T5450 (-MCP-) cache: 2048 KB
clock speeds: max: 1667 MHz 1: 1125 MHz 2: 1039 MHz
Info: Processes: 123 Uptime: 2 min Memory: 248.5/998.2MB
Client: Shell (bash) inxi: 2.3.8

BarryK · #134 Post by **BarryK** » Mon 10 Jun 2019, 14:35

Lobster wrote:Should this be released as Puppy 8.1 Community Edition?

Well, no, not yet anyway.

I am running ScPup64 19.06 right now, very nice.

Examining /root/.packages, I see that the PPM will only be installing from the 14.2 repositories.

A problem with the slackware64-current package repository is that it may undergo fundamental changes at any time, such as version changes of glibc or gcc. So, cannot install packages from it with the PPM.

That is a problem, for various reasons. As ScPup is built from slackware-current repo, there is no guarantee that 14.2 packages will work when installed from the PPM. You are going to be hitting library compatibility problems -- and a quick read through this thread shows that is happening.

File Slackware-packages64-14.2-official has dependencies for each package. It got these from the PACKAGES.TXT in the Salix repository, which is only for 14.2.

There are no dependencies available for packages in slackware64-current, that PACKAGES.TXT doesn't have them.

So, summarizing, I think that ScPup will have to wait until Slackware 15.0 is released, then build from those repos. Then you will have stable repos, that will be mirrored everywhere.

Hopefully Salix will update to 15.0 and their PACKAGES.TXT will have the package dependencies, that the 'setup' script in Woof will read, to create the Puppy-package-database format.

I think that the above statements are correct, hope not too confusing.

EDIT:
I should also note, if you compile an app in ScPup and create a PET, there is no guarantee that it will work in a future release of ScPup.

That is, if a future release builds from latest slackware-current, the packages could have changed.

In summary again, Slackware is not suitable for the rolling-release model of distro, due to its lack of dependency management. I have thought how it could be added though ...have become intrigued by this. Slackware needs dependencies of each package, AND versions of each dependency.

EDIT:
I am working on a fix:

http://murga-linux.com/puppy/viewtopic. ... 63#1030163

Terry H · #135 Post by **Terry H** » Mon 10 Jun 2019, 15:07

Terry H wrote:Downloaded ScPup64-19.06+0. Manual frugal install, updated an existing save folder. All working well. Another great release peebee.
Code: Select all
# inxi -CSI
System:    Host: puppypc1956 Kernel: 5.1.6-lxpup64 x86_64 (64 bit) Desktop: JWM 2.3.6 Distro: ScPup64 19.06
CPU:       Dual core Intel Core i5-5200U (-HT-MCP-) cache: 3072 KB 
           clock speeds: max: 2700 MHz 1: 1559 MHz 2: 1241 MHz 3: 1910 MHz 4: 1668 MHz
Info:      Processes: 128 Uptime: 15 min Memory: 373.5/7606.5MB Client: Shell (bash) inxi: 2.3.8

I have changed this installation to create a new save folder, following booting with "pfix=ram". After this post I noticed that once a partition was mounted the icon displayed changed to a completely different icon. So appears there was an incompatibility with recent changes. So to not find any more of these little issues, it was best to start again.

This install with new save folder is functioning well.

Wiz57 · #136 Post by **Wiz57** » Tue 11 Jun 2019, 00:24

Hiya peebee, and also norgo!
Just wanted to let you know I have made a second frugal install on my
hard disk drive on this old netbook of Sc Pup 19.04 32 bit...and in this
one I added the ydrv containing LXQt desktop! It works smooth!
Even with only 1 gig total RAM, I'm liking this LXQt combo! I think what
I might try is extract the new iso of ScPup 19.06 into the directory that
contains 19.04, then just rename the ydrv to reflect the "19.06" reference,
and give that I run.

To Barry...you may be correct regarding Slackware Current, but the thing
I've always enjoyed about Slackware is that updates are normally only
released when a lot of testing has been done, making it a very stable OS
(my favorite anyhow). I've been using various small pendrive type
Slackware derivatives for seems like ages, starting with Slax 5 something
or other. Other than an odd lib missing occasionally, haven't had anything
that I couldn't solve, and I am NOT a linux guru by any stretch.
Slax 7 implemented a different package handler that helped with
dependency resolving, maybe I can dig it out for examination.

Finally...this is only my opinion, not worth 2 cents, but I think the combo
of ScPup and LXQt (I call my installation ScPupLXQt, btw) would be a
great way to introduce Windows refugees to Puppy! Especially those
coming from XP and 7!

Thank you again peebee, great work!
Wiz

Wiz57 · #137 Post by **Wiz57** » Tue 11 Jun 2019, 01:00

Renaming the ydrv WORKED! i'm here now, in ScPupLXQt 19.06 32 bit!
Palemoon browser updated to 28.5.2, everything updated smoothly!
Woohoo!

edit to add
ps...say, this PCManFM file manager is pretty slick too! Used it to update
my installation by extracting the iso! SWEET!!!

foxpup · #138 Post by **foxpup** » Wed 12 Jun 2019, 09:07

BarryK wrote:A problem with the slackware64-current package repository is that it may undergo fundamental changes at any time, such as version changes of glibc or gcc. So, cannot install packages from it with the PPM.

That is a problem, for various reasons. As ScPup is built from slackware-current repo, there is no guarantee that 14.2 packages will work when installed from the PPM. You are going to be hitting library compatibility problems ...

I should also note, if you compile an app in ScPup and create a PET, there is no guarantee that it will work in a future release of ScPup.

That is, if a future release builds from latest slackware-current, the packages could have changed.

In summary again, Slackware is not suitable for the rolling-release model of distro, due to its lack of dependency management.

The library compatibility problems may be present in Sc itself at any given time also!
I presume they may increase at the start and exstinguish near a new Slackware release.
That's a chance you have to take with Sc.
But since Slackware is well taylored it is not such a big risk, I think.

Slackware and Sc is not rolling release and Puppy should not become RR either, my opinion.

BTW, I am looking forward with anticipation to Slackware 15.
Besides Pupppy & derivatives, it is the only linux I always keep on my machines.

matheuszig · #139 Post by **matheuszig** » Fri 14 Jun 2019, 15:10

Help, my mouse acceleration and threshold not change after apply settings, always in default, in any distros, includes Scpup64 and others, but in XenialPup64 mouse settings works fine and i no have problems in this distro, anyone help me ?
My PC:
Mouse Razer Abyssus 2000 750 dpi.
Membrane keyboard.

Core2Quad q9300 2.82 ghz
GT 420
4gb ram
Puppy installed in SD card with adapter, my HDD dead.

matheuszig · #140 Post by **matheuszig** » Sat 15 Jun 2019, 18:35

matheuszig wrote:Help, my mouse acceleration and threshold not change after apply settings, always in default, in any distros, includes Scpup64 and others, but in XenialPup64 mouse settings works fine and i no have problems in this distro, anyone help me ?
My PC:
Mouse Razer Abyssus 2000 750 dpi.
Membrane keyboard.

Core2Quad q9300 2.82 ghz
GT 420
4gb ram
Puppy installed in SD card with adapter, my HDD dead.

I fixed this, ScPup and others distros uses xinput to manage mouse acceleration
to disable mouse acceleration use this command:
xinput --set-prop <device id> 'libinput Accel Profile Enabled' 0, 1

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

ScPup & ScPup64 - Slackware Current based Woof-CE pups

ScPupLXQt 32

mouse acceleration not change in pupxset mouse settings

Re: mouse acceleration not change in pupxset mouse settings